At Asteria, tokenization means one precise thing: representing each registry entry as a unique token on a public blockchain, so it can be held, verified and transferred without anyone's permission — including ours. This page explains what that token is and, just as importantly, what it is not.
One entry, one token#
The Asteria registry is a list of entries. Each entry pairs a real, catalogued asteroid with a registry ID (such as ASR-0001), a registry name (such as Vesperine) and a full data record. Tokenization gives every entry exactly one on-chain counterpart:
- One token per entry. A registry ID can be minted once, and only once.
- One entry per asteroid. The planned contract refuses to link a second token to an official designation that is already registered.
- Transfers move the entry. Whoever holds the token is the current holder of the registry entry, as recorded on-chain.
Why ERC-721#
Asteria tokens are designed as ERC-721 (opens in a new tab) tokens — the Ethereum standard for non-fungible tokens. Fungible things are interchangeable: one euro is as good as another. Registry entries are not: Vesperine is not Nyxara. ERC-721 gives each token its own tokenId and a standard set of functions that wallets, block explorers and marketplaces already understand:
| Function | What it does |
|---|---|
ownerOf(tokenId) | Returns the address that currently holds the token |
transferFrom(from, to, tokenId) | Moves the token to another address |
tokenURI(tokenId) | Points to the token's metadata document |
What the token represents#
| The token represents | The token does not represent |
|---|---|
| Your registry entry: registry ID, registry name, and its link to the asteroid's official designation | Ownership of, or any property right in, the asteroid |
| The digital certificate generated for that entry | Any right to land on, mine or use the asteroid |
| The metadata record: orbit, physical data, name meaning and story | An official, IAU-recognised name |
| A transferable, verifiable digital collectible | An investment, a share in Asteria or a claim on its revenue |
The usage rights that come with the certificate artwork — for example, printing it at home or displaying it online — will be set out in the terms of sale, which are still in draft. See the terms overview.
On-chain and off-chain data#
Blockchains are excellent at recording who holds what, and expensive places to store images. Asteria splits its data accordingly.
| Data | Where it lives | Why |
|---|---|---|
| Token ID and current holder | On-chain | The source of truth for who holds an entry |
| Registry ID, registry name, designation hash | On-chain name registry (planned) | A tamper-evident link between token, name and object |
| Royalty information (ERC-2981) | On-chain | Readable by any marketplace that supports it |
| Metadata JSON | IPFS (planned), referenced by tokenURI | Rich data, cheap to store, content-addressed |
| Certificate image and animation | IPFS (planned) | Large media files |
| Waitlist sign-ups and emails | Never on-chain | Personal data does not belong on a public ledger |
IPFS stores files by their content: every file gets a content identifier (CID) derived from its bytes. Change a single byte and the CID changes, so a CID always points to exactly the document it was created for. IPFS files stay available only while someone "pins" them; Asteria plans to pin with more than one independent provider.
What can change, and what cannot#
Some parts of an entry must never change. Others need to, because science improves.
Fixed for the life of the token
- Token ID and registry ID
- Registry name, once recorded on-chain
- The designation hash, once verified
- The core contract logic (an immutable design is planned — see Smart contracts)
Can be updated, with a public trail
- Verification status, from pending to verified
- The official designation, from
nullto a verified value — or an official IAU name, if one is published later - Refined measurements, such as a new diameter estimate from infrared observations
- The schema version, following the versioning policy
- A dedication (planned)
Each update produces a new metadata document with a new CID. Earlier versions remain retrievable, and the contract is planned to emit a standard metadata-update event (ERC-4906) so wallets and marketplaces know to refresh.
Which blockchain?#
The network has not been chosen. The contracts are designed for an EVM-compatible chain, and the decision will be made during Phase 1 of the roadmap, alongside the legal review. The criteria:
- Security — a long, clean track record for the network itself.
- Cost — transaction fees that keep minting and transfers reasonable.
- Compatibility — broad support in wallets, block explorers and marketplaces.
- Footprint — a proof-of-stake network with a modest energy profile.
Until the network is announced in these docs, treat any "Asteria contract" you encounter as fake.
The lifecycle at a glance#
Verify
Each catalogue entry is cross-checked against public small-body databases and linked to its official designation.
Register
The entry receives its registry ID and a curated registry name that follows the naming guidelines.
Mint
At the primary sale, the token is created directly in the buyer's wallet with its metadata and certificate.
Hold or transfer
The holder keeps the token in self-custody, or transfers it peer to peer once secondary trading opens.