You hold an asset that is worth what it is worth whether or not anybody can trade it. AssetMesh does not try to make it tradeable. It makes it legible — to machines, to a denomination that already circulates, and to somebody diligencing you who has never met you.
“Publish a record about your asset” is heard as “hand over your data” until somebody lists the fields. There are no other fields. The format has no place to put an LP, a cost basis or a key, and no version of it will.
| In the file | Detail |
|---|---|
| publishedWhat the asset is, its class and its jurisdiction | A Chicago commercial property. Enough for a machine to know what kind of thing it is reading. |
| publishedA public identifier, if you choose to give one | A county parcel number, a title reference. Optional — the record works without it. |
| publishedDated claims, and who made each one | An appraised value, an occupancy figure, a custody statement — each naming its author and the date it runs out. |
| publishedObligations issued against the asset | What a holder is owed, in what unit, by whom, until when. |
| neverYour LPs, your cap table, your fund terms | The format has no field for any of it, and no version of it will. This is not a disclosure regime. |
| neverYour cost basis, your debt stack, your returns | Not asked for, not represented, not inferable from anything in the file. |
| neverCustody of the asset, or any key to it | A record is a description. Nothing in AssetMesh takes possession of anything. |
The format refuses an appraisal, audit, custody or title claim made by the party it is about. So the first record costs you an appraiser, an auditor or a custodian who will put their name to a number — a real engagement with a real fee. This is the whole cost, and it is deliberately not avoidable: it is the only reason a stranger has to believe any of it.
Every claim carries an expiry, and an expired claim stops counting rather than quietly ageing. A record you publish and never touch again decays into an empty one — which is the correct behaviour and is still work somebody has to own.
An obligation names who is on the hook. Publishing one is a statement about what you will do, and the format makes it checkable by anybody rather than only by the holder.
One JSON file at your own domain, under /.well-known/. Two commands write and check it. No account, no server, no integration, and nothing to sign up for.
Each is the first assumption of a different person in the room, and every one of them is wrong in a way that matters.
There is no token. `rwa/1` is a JSON file at a URL. Nothing is minted, nothing is on a chain, and nothing about the format requires either.
Nothing is listed, matched or traded. The argument is the opposite one: an asset does not need its own market, it needs a unit somebody already holds.
AssetMesh holds nothing, takes custody of nothing, and is not a counterparty to anything you issue. The obligation names you.
Publishing a record is not soliciting anybody. The format has no investor, no subscription and no allocation — and it refuses the one instrument shape that is reliably a security.
A standard is worth nothing until it has nodes, and the companies that publish first carry the cost of a format nobody else is using yet. So the intention is that early issuers hold a stake in the standard itself rather than a discount on it — the people who make it real owning part of what they made real.
What is not settled
If you hold real assets and would consider being the first record published by somebody who is not us, that is the conversation. It starts with one asset and one appraiser, not a term sheet.
Start that conversation →One file, at your own domain. It does not validate yet, and it names every placeholder still in it.
npx assetmesh adoptReplace each independent attestation’s author with the appraiser, auditor or custodian who actually made the claim. This is the work; the rest is typing.
Every problem at once, with a path and a stable code. Exit 1 on any.
npx assetmesh checkAt /.well-known/rwa.json. A committed file is not a served file — the failure this estate has made most often is checking the repository instead of the domain.
Served at /.well-known/rwa.json · the securities line