Specifies that the NFT-Update-Owner (usually its creator) has approved of this program being added to the NFT
We store this as a hex here for interoperability with all the other places we use hex to store hashes, but it's stored as a 32 byte binary on the chain.
There's many heads to a single metadata, this is the key back to that metadata
This is the ID of the first item in the hashlist. It is also the most recent item. It is stored in a 32byte binary format, and then decompressed based on the location that the file is stored. This lets us fit 256 bits.
Used by the NFT holder (usually the end user owning the NFT) to sort which writers get displayed in what order.
-1 will override to NOT display something that is authorized, while >1 will override TO display something that may or may not be authorized. 0 will follow default behavior.
This is a wrapper on an item. It handles things like describing the location of the next item.
The JSON serialized version of this type is also the expected format of objects stored off chain, so if you wish to manually append an object,
This frequently does not exist on creation, only after upload, which means it is not a mandatory component when instiating a new item.
The JSON of this section is what should be validated by the hash.
JSON doesn't naturally preserve order, so it's important we pick one stringified
representation and then stick with it. Since there's a single source of truth this
just means we need to save the original JSON.stringify
when the item is created.
Whether the api was able to verify that the data hadn't been tampered with. This being set to false suggests tampering.
Inner item, this is the actual data contained within a solstory item.
Instructions for how to display the item in a client.
Reference to a previous solstory item, by objId. Useful for things like corrections.
Base url, used for AccessType.URL, otherwise is "".
CDN for this writer
Title used when displaying this writer.
URL for the logo to display with this writer.
Additional metadata, JSON format.
Whether this writer has been validated by solstory. Meant for fraud and spam protection.
URL for more information about this writer. Homepage link, basically.
Whether this writer is meant to be visible. Set to false for internal programs.
We have an internal object representation, but then we also need to stick these onto string only systems, like ardrive or a sql database.
Generated using TypeDoc
This is the entry point for using the solstory API. You should import the SolstoryAPI as well as any types you need, then access individual modules with
solstoryAPI.<module>.