Data & sourcesData & sources

Every number on an Asteria entry is either stored or derived — and at launch, every stored scientific value will trace back to a public source. This page lists each field, its unit and where it comes from, and is plain about which parts are still preview data.

Stored fields#

Stored fields are the values written into each catalogue record. They fall into three groups.

Identity and editorial#

Physical and orbital#

Listing and technical#

Derived fields#

Derived fields are never stored. They are computed from the stored values every time, so they cannot drift out of step with them.

Trait rules#

From fields to token metadata#

The same record feeds the planned token metadata. Familiar marketplace fields — name, description, image and attributes — sit at the top level; the full record lives in a namespaced asteria block, including the official designation and a list of data sources that will be filled in on verification. Here is the generated metadata for Vesperine:

{
  "name": "Vesperine (ASR-0001)",
  "description": "The first light after dusk. A stony wanderer of the middle belt, bright enough to catch the Sun like a struck match. Vesperine opens the Asteria registry — the first entry, the first name. Registry name assigned by Asteria; not an IAU-recognised name. This token is a digital collectible and confers no ownership of any celestial body.",
  "image": "ipfs://<cid>/ASR-0001.png",
  "animation_url": "ipfs://<cid>/ASR-0001.mp4",
  "external_url": "https://asteriaasteroids.xyz/explore/vesperine",
  "attributes": [
    {
      "trait_type": "Spectral class",
      "value": "S-type"
    },
    {
      "trait_type": "Orbit class",
      "value": "Middle main belt"
    },
    {
      "trait_type": "Tier",
      "value": "Celestial"
    },
    {
      "trait_type": "Near-Earth object",
      "value": "No"
    },
    {
      "trait_type": "Diameter (km)",
      "value": 3.8,
      "display_type": "number"
    },
    {
      "trait_type": "Albedo",
      "value": 0.24,
      "display_type": "number"
    },
    {
      "trait_type": "Rotation period (h)",
      "value": 5.6,
      "display_type": "number"
    },
    {
      "trait_type": "Orbital period (yr)",
      "value": 4.29,
      "display_type": "number"
    }
  ],
  "asteria": {
    "schema_version": "1.0.0",
    "registry_id": "ASR-0001",
    "registry_name": "Vesperine",
    "name_meaning": "From the Latin vesper — the evening star, the first light after sunset.",
    "official_designation": null,
    "spectral_class": "S",
    "orbit": {
      "orbit_class": "Middle main belt",
      "semi_major_axis_au": 2.64,
      "eccentricity": 0.11,
      "inclination_deg": 7.2,
      "perihelion_au": 2.35,
      "aphelion_au": 2.93,
      "period_years": 4.289
    },
    "physical": {
      "diameter_km": 3.8,
      "geometric_albedo": 0.24,
      "rotation_period_h": 5.6,
      "absolute_magnitude_h": 14.27
    },
    "data_sources": [
      "To be linked on verification: JPL Small-Body Database, Minor Planet Center"
    ],
    "disclaimer": "Registry name only; not an official IAU designation. No property right in any celestial body is conveyed."
  }
}

The schema, currently at version 1.0.0, is documented field by field in Token metadata.

Planned sources#

At launch, verified entries will draw on established public sources. Asteria does not discover, observe or measure asteroids.

Verification process#

Verification is planned for phase 1 of the roadmap, before any entry is offered.

Status today#

Catalogue entries

14

All preview data

Verified entries

0

Verification is planned

Official designations

0

Set on verification

Metadata schema

v1.0.0

ERC-721 + asteria block

Update policy#

Science moves on, and the catalogue is designed to move with it.

• What can change. Orbits are refined as observations accumulate, and new measurements can revise a diameter, an albedo or a spectral class. Scientific data is planned to be versioned and dated, so that every revision is traceable.
• What never changes. The registry ID, and the registry name once it has been sealed at the naming ceremony.
• How changes are announced. Changes to the data model, the metadata schema and the catalogue are recorded in the changelog.
• Corrections. A channel for reporting data errors is planned to be published before launch.

How revised scientific data will be reflected in already-issued token metadata depends on the final contract and storage design, and will be documented in Smart contracts before launch.

Next steps#