Introduction
A "Post" in Sage will is the major driver of value in the platform. Users must be able to create Posts, as well as own and profit from the knowledge they are providing.
Creating a Post will be made through the Sage SDK directly on chain. When the Post is created, an event will be fired off for the purposes of aggregating and organizing Posts for others to view and debate.
Posts will always have a parent that acts as an "owner". A parent can be a Channel, a User, or another Post (a comment).
Implementation Details
A Post is a Sui object on chain. It includes a reference back to the objectId of it's parent, text (the content), and optionally an image or series of images.
Each Post is also considered of a different post type: either "Channel Post", "User Post", or a "Comment". Each type is held in it's own dedicated registry as well as a complete registry of all posts.
Additionally, comments can be made on comments, and comments made on those comments, all the way down as far a user may prefer. There is no limitation on how far this nesting can continue past any UX design considerations a Sage application may wish to enforce.
Future Considerations
How can we empower the community to create their own customized Post types (e.g. Frames) that do unique and interesting things? This could create an extreme benefit to the platform. Examples:
Ability to mint an NFT from a Post.
Put their unity game into a Post for others to play.
Create a poll in a Post.
etc etc
Last updated