For issuers
Provenance for real-world assets
On TX, provenance is a document you publish and a hash the token stores. A matching hash means those exact bytes were the ones you committed. It does not mean the chain checked the warehouse, the title, or the law.
Education only. Nothing here is legal, tax, or investment advice. Issuing a token does not create the off-chain asset, and txLearn does not custody it. Features you enable, including freezing and clawback, are powers you should say out loud in the same document the hash covers.
The issuer path
- Write the record before you sign. Say what one token represents, who the issuer account is, and which documents you are pointing at.
- Pin the evidence, then the record. Each document is an ipfs:// CID. The record names those CIDs. The lesson Store files on IPFS is the free Pinata walkthrough.
- Bind the hash. MsgIssue stores uri and uri_hash. The hash is sha256 of the record. Features are fixed in that same transaction.
- Let a holder check it. They read the token, fetch the file, and compare the hash. Later mints do not change that hash.
Lessons
- What provenance is on TX the hash, the denom, and what is not proved
- Write the provenance record representation, evidence, disclosed powers
- Bind the record to a token MsgIssue, the 10 TX fee, minting later
- How a holder checks it query the token, hash the file, read the features
Each lesson ends with a quiz. Finishing the track unlocks its certificate. The full feature reference, including burn rate and admin, stays in Smart Tokens on TX.
What a holder should see
- The denom is subunit-issuer. The address after the dash is the account that issued it.
- uri_hash on the token equals sha256 of the file at uri.
- The file says what one token represents, and it lists the same features the token has, especially minting, freezing, whitelisting, and clawback.
- The on-chain features match that list. The document alone is not the chain.
The tool can fetch a token and re-hash an ipfs:// record. Check a record.