search

NearSocial / standards

Standards to define schemas and data format in SocialDB
10 stars 8 forks source link

Bounty schema #12

Open jlwaugh opened 1 year ago

jlwaugh commented 1 year ago

starting point for discussion, based on examples

evgenykuzyakov commented 1 year ago

Context

The more I think about structure of the data in socialdb, the more I lean towards serializing as much as possible into JSON object and then store it as a string instead of sub-objects. This way it's still easy to read (so long as you always read the whole object) and easier to replace, since you don't need to cleanup recursively.

If the fields of the bounty don't have to be used independently by other contracts, then it should be a large serialized object instead. Also think about updates to the bounties, and whether they are more like posts (replaced), or more like profiles (persistent in latest state).