The store object

The store object inherits from the Message object's structure as follows:

// Message info
channel:
time:
type:

// Sender info
chain:
sender:

// Content
hash_type:
item_content:
  address:
  item_type:
  item_hash:
  time:
item_hash:
item_type:

Attributes	Description
channel - text	Channel of the message. Ideally, an application would decide and use one channel.
time - float	Time the store was created. in seconds
type - text	Text representing the message object type. Value is STORE
chain - text	The chain used by the sender's account. Value can be NULS2, ETH, DOT, CSDK, SOL, AVAX
sender - text	Chain address who sent and is signing the Store Message.
	-
hash_type - optional text	Defaults to sha256. This is the only supported value for now.
item_content - JSON text	JSON string representing the content of the aggregate. See below for the content of the string.
item_content.type - text	A string of your choice representing what the post is. Should be simple and lowercase. For instance, for a blog post you could have: a "blog" or a "comment"
item_content.address - text	Chain address to associate the Post with.
item_content.time - timestamp	Time the object was created.
item_content.item_hash - text	Text representing the file stored. It can be used to retrieve the object stored through the retrieve endpoint.
item_hash - hash	The hash of the item_content encrypted with SHA256.
item_type - optional text	ipfs, inline or storage