Every Asteria registry entry comes with a digital certificate: a high-resolution artwork that gathers the asteroid, its registry name and its data into a single frame. It is generated by code from the same record as the token, so the certificate and the token can never disagree.
What the certificate shows#
Every field on the certificate comes from the registry record or is derived from it. Nothing is typed by hand.
| Field | Source | Example — Vesperine (preview) |
|---|---|---|
| Registry name | registry_name | Vesperine |
| Registry ID | registry_id | ASR-0001 |
| Name meaning | name_meaning | From the Latin vesper — the evening star |
| Official designation | official_designation | Shown once verified; "Pending verification" in preview |
| Spectral class | spectral_class | S-type (silicaceous) |
| Orbit class | orbit.orbit_class | Middle main belt |
| Orbital elements | orbit | a = 2.64 AU, e = 0.11, i = 7.2° |
| Physical data | physical | 3.8 km · albedo 0.24 · 5.6 h rotation · H 14.27 |
| Orbit diagram | Derived from a, e, i | The orbit drawn to scale, Sun at one focus |
| Portrait | Procedural, from a seed | A unique rendered shape tinted by spectral class |
| Dedication | Holder (planned) | Optional, up to 240 characters |
| Token ID and contract | On-chain (planned) | To be announced |
| Fingerprint | Metadata hash (planned) | A short hash and a QR code |
| Disclaimer | Fixed text | Registry name only; no property right conveyed |
- Registry ID
- ASR-0001
- Vesperine — preview entry
- Orbit class
- Middle main belt
- Between the 3:1 and 5:2 Kirkwood gaps
- Orbital period
- 4.29 yr
- Kepler's third law, P = a^1.5
- Absolute magnitude
- H 14.27
- Derived from diameter and albedo
How it is generated#
Certificates are produced programmatically, with one template for every entry. That is what keeps them consistent — and what makes them checkable.
Read the record
The generator loads the registry record — the same one used to build the token metadata.
Derive the numbers
Perihelion, aphelion, orbital period and absolute magnitude are computed from the stored elements and physical data, never entered separately.
Render
The composition is rendered by code into a still image and an animated version in which the orbit moves.
Fingerprint
A hash of the canonical metadata is computed and printed on the certificate in short form, with a QR code (planned).
Publish
The image and animation are stored on IPFS (planned) and referenced from the metadata's
imageandanimation_urlfields.
Verifying a certificate#
Verification is planned for launch. A certificate carries three identifiers, and each one can be checked independently.
| Identifier | Example | What it proves |
|---|---|---|
| Registry ID | ASR-0001 | The entry exists in the Asteria registry |
| Token ID | To be assigned at mint | Which token, in which contract, represents the entry |
| Metadata hash | Short SHA-256 fingerprint | The certificate matches the published metadata |
To check one yourself:
- Look up the registry ID on Asteria's public registry explorer (planned).
- Open the token ID on a block explorer for the published contract, and read its
tokenURIand current holder. - Download the metadata from that URI and hash it. Because JSON can be formatted in many ways, the fingerprint is computed over the canonical form defined by RFC 8785.
# canonicalise the metadata (RFC 8785), then hash it
sha256sum ASR-0001.canonical.json
# compare the first characters with the fingerprint on the certificateFormats#
Both formats are planned; final specifications will be confirmed before launch.
| Format | Planned specification | Best for |
|---|---|---|
| Still image | PNG, 7016 × 4961 px (A3 landscape at 300 dpi), sRGB | Printing, framing, sharing |
| Animated | MP4 (H.264), 1080p, a short seamless loop | Screens, wallets and marketplaces that play animation_url |
Printing your certificate#
The design leans on deep blacks and fine hairlines. A few choices make the difference between a print that glows and one that looks grey.
- Paper. Matte or fine-art cotton paper, around 250–310 gsm. Matte avoids glare on the dark background.
- Size. The still prints natively at A3 and scales cleanly down to A4. Avoid enlarging beyond A2.
- Colour. The file is sRGB. Ask your printer to print it as supplied, without "auto-enhance", which tends to lift the blacks.
- Margins. Do not crop: the fingerprint and QR code sit near the edge and must remain legible.
- Framing. A dark mat suits the design. Keep the print out of direct sunlight.
Dedications#
A dedication is an optional inscription — up to 240 characters — printed beneath the registry name. It is planned for the marketplace and reviewed under the naming guidelines before it appears. How dedications behave when a token changes hands is still being designed, and will be documented before launch.