/v1/studio/drop/{slug}/provenance
What a drop sells, fixed before anyone bought
Request
https://api.xrpl.to/v1/studio/drop/fuzzybears/provenance| Path parameter | Value | Description |
|---|---|---|
| slug | A collection slug, or its identity as issuer:taxon |
curl 'https://api.xrpl.to/v1/studio/drop/fuzzybears/provenance'
Response
{ slug, provenance, provenance_tx, rule, cids, minted_nfts, art }
What it does
What a drop sells, fixed before anyone bought
- Notes
- The drop's fingerprint (provenance): the SHA-256, in hex, of its CIDs in order, joined by a newline. The minter writes it on the ledger when the drop is made: an AccountSet of minter_address that changes nothing, whose memo (type xrpnft/provenance) reads "<slug> <provenance>" (provenance_tx, once validated). Each CID names its file's content, so anyone can check from the ledger that what each NFT shows was fixed before the sale (minted_nfts: CID to NFTokenID). The files of NFTs not sold yet stay off IPFS: their CIDs show nothing. An edition's copies are keyed "<cid>#<n>" in minted_nfts. art: the new art a dynamic drop's creator has put on its NFTs since (by NFT key, "*" for every copy of an edition).