Asset Templates
You do not have to design an asset schema from scratch. The platform ships 13 curated templates, each a published schema for a real asset vertical: its fields, their mutability, and the validation rules the vertical needs. Fork one into your workspace, adjust it, and publish, or bind a token to the platform version as is.
How templates work
A template is a published, platform-owned schema version. Forking it copies the field palette into an editable draft in your workspace; you can add, remove, or tighten fields, preview the compiled result, and publish your own version. Every template has already passed the same publish gate your own schemas go through, so a fork starts from a known-good shape. The mutability and field-type model behind these is on Real-World Assets.
The gallery
| Template | Models | Notable rules |
|---|---|---|
| Residential Real Estate | A single residential property: address, parcel id, valuation, occupancy, deed, appraisal history. | Valuation must be positive; occupancy is a closed state set; the deed document is entitlement-gated. |
| Fractional / Commercial Real Estate | A commercial property split into fractional units with rent-roll income and a holder cap table. | The sum of all fractional holders' balances must exactly equal the declared total units; net operating income is a derived, read-only value. |
| Private Credit | A direct loan: principal, rate, repayment schedule, payment ledger, covenant state. | Outstanding principal can never exceed principal; covenant state is a closed set (performing, watch, default, workout, repaid). |
| Trade Invoice | A factored trade-finance invoice: amount, currency, debtor, due schedule, settlement ledger. | The debtor is a relationship to an identity token; currency and status are closed sets. |
| Carbon Credit | A registry-issued offset: project, registry, vintage, serial range, tonnage, retirement status. | Registry is a closed set of recognized registries; vintage year is bounded; the MRV report is entitlement-gated. |
| Fine Art | A collectible artwork: artist, title, year, condition imagery, authentication, provenance history. | Nearly everything is frozen at issuance; provenance is an append-only log; authentication documents are entitlement-gated. |
| Luxury Collectible | A watch, handbag, or similar: maker, serial range, grade, custody state, appraised value. | Grade and custody state are closed sets; appraised value must be positive. |
| Music / IP Royalty | A royalty stream: work, ISWC, rights type, territory, rate schedule, earnings history, split holders. | The royalty term exposes a derived current value from its schedule; the royalty-split cap table must sum above zero. |
| Fund Shares / Private Equity | Units in a private fund: status, NAV per share, NAV history, capital-call schedule, required accreditation, holders. | The only template with a schema-level transfer rule: every platform-relayed transfer is denied unless the recipient is currently accredited. See the note below. |
| Debt Instrument (Bond / Muni) | A bond: issuer, CUSIP, face value, coupon schedule, maturity, rating, redemption status. | Rating and redemption status are closed sets; face value must be positive. |
| Commodity / Warehouse Receipt | Stored physical commodity: type, quantity, unit, grade, warehouse, custody status, inspections. | The warehouse is a relationship to an identity token; unit of measure, grade, and custody status are closed sets. |
| Precious Metals | Bullion: metal, refiner, serial range, weight, fineness, assay certificate, custody status. | Fineness is bounded at parts-per-thousand (at most 1000); the assay certificate is required and entitlement-gated. |
| Generic RWA | A minimal catch-all for asset types without a vertical: name, description, class, valuation, status, one document. | Deliberately unopinionated and data-only (no image field), the baseline to extend when nothing else fits. |
The template that gates transfers
What the field types give you
Across the gallery you can see the field palette doing vertical-specific work: money and number fields carry range constraints, state and enum fields enforce closed vocabularies, schedule fields expose a derived current value, relationship fields bind to other tokens (a debtor, a warehouse), document and media fields carry entitlement-gated visibility, append-log fields hold histories that can never be rewritten, and holder-positions fields tie the record to the on-chain cap table. Each field's mutability (frozen, versioned, append-log) is enforced on every write, as described in Real-World Assets.
Related
- Real-World Assets: the schema model, mutability, and the public resolver.
- Tokens and Assets: forking and publishing from the console's schema builder.
- Holder Eligibility and Transfers: how the transfer rule in a template is enforced.
- Cap Tables and Distributions: the holder positions several templates track.