Related assets. Distinct identities.
Keep a Solana representation distinct from the asset it references. Connect the records only through relationships the evidence supports.
A shared symbol is a navigation convenience, not proof of interchangeability. Give each mint its own record, then describe a reference relationship with its source, direction, dates, and review state.
What to define
Separate records
Preserve each Solana mint and any referenced Ethereum contract independently.
Explicit relationships
Record the asserted mechanism, source evidence, and unresolved questions.
Independent observations
Keep supplies and prices distinct unless a defined aggregation is supported.
Do not infer the mechanism
A name or one observed price comparison does not establish a continuing conversion relationship. Record what the source actually says, including conditions and dates. Where no supported relationship is available, leave the status unresolved rather than inventing a structure to fit the schema.
Preserve historical mappings
Relationship statements can change while the underlying mint identity stays the same. Version the mapping and identify it in each export manifest. A current related-assets group should not silently replace the one a researcher could have known at an earlier decision time.
Compare like with like
A reference asset’s price should not automatically become the representation’s price. Keep independent observations, align units and timestamps when comparisons are justified, and withhold calculations when the inputs do not meet the agreed conditions. Technical state is not an assurance about economic equivalence.
Review the internal methodology and protocol reference notes for the source concepts behind these guides.
Related does not mean identical.
Tokenized Altcoins on Solana: Identity Before Equivalence
Model each Solana representation separately, then attach supported relationships, market observations, and historical mappings.
Read the guideTokenized Altcoins on Solana: Identity Before Equivalence
Model each Solana representation separately, then attach supported relationships, market observations, and historical mappings.
The full guide covers the decisions, limitations, and sample acceptance cases behind this data scope. Bring those questions into the brief before agreeing a production integration.
Read the complete guideYour next build starts with better data.
Define your assets, fields, evidence, and delivery needs. Start with a clear brief—not an assumed service package.