Important next materialCompare TicketsCURRENT OWNERSHIP
A Ticket can change owners without losing its history.
The Registry shows the current eligible holder of a RAOLAX Ticket and can preserve earlier transfers.
When a transferable Ticket moves to another eligible wallet, the new wallet becomes the current holder. Holder-based benefits then follow the rules of each specific programme.
A previous owner does not automatically keep future benefits after selling the Ticket. A new owner does not automatically receive benefits attached to snapshots that happened before the transfer.
Highlight CURRENT HOLDER. Mark the first acquisition simply as ORIGIN / FIRST ACQUISITION FROM MUTERRA. Do not turn it into a separate emotional claim.
PROGRAMME HISTORY
Rewards depend on who qualified at the right moment.
MUTA distributions, Founder NFT Drops, Weighted Draws and other programmes can use a dated snapshot or another published eligibility rule.
The Registry can show which Ticket and wallet qualified when that record matters.
Example:
SNAPSHOT #04 — FOUNDER NFT DROP
Ticket: #0812
Class: First Class
Holder at snapshot: Wallet B
Founder Weight: 10×
Status: Eligible
If Wallet B sells the Ticket after this snapshot, Wallet C does not retroactively become the participant in Snapshot #04. If Wallet B no longer owns the Ticket when a later snapshot occurs, Wallet B does not automatically retain future holder benefits.
The programme rules decide eligibility. The Registry makes the result readable.
TICKET STATUS
The Ticket has a class. Programmes decide what that class changes.
A RAOLAX Ticket record can include:
TICKET ID
CLASS — Cryo / Regular / Crew / First / VIP / Bridge
CURRENT HOLDER
OWNERSHIP HISTORY
FOUNDER WEIGHT
FOUNDER DROP DEGREE
RELEVANT SNAPSHOTS
PROGRAMME ELIGIBILITY
SHIP / EVENT METADATA where implemented
The Registry should not duplicate the full Benefits material. It should show the current record and link to the rules that explain it.
SPECIAL POSITIONS
Some records show more than ownership.
CREW
Crew Passes are earned rather than sold through the normal Ticket flow. The Registry can show who received a Crew position, when it was granted, the role attached to it and the accepted contribution or activity connected to that decision where appropriate.
Crew provenance explains why the position exists. It does not turn every contribution into Crew.
BRIDGE
Bridge carries a decision-making role. The Registry can connect a Bridge Seat to the person or account holding responsibility during a defined period and, where the governance system publishes them, to selected proposals, votes, objections and formal decisions made during that period.
This matters because authority should be attributable: who had the Seat when a decision was made, and what action was recorded.
CONTRIBUTIONS
Accepted work can be linked to the people who created it.
A character, video, article, 3D model, gameplay report, promotion or useful introduction can be connected to its contributors and to the places where MUTERRA later uses it.
Example:
KAEL
Original concept — Igor
Character design — Anna
Lore — Maria, Igor
3D — Anna
Gameplay adaptation — MUTERRA Team
Each contributor name can link to the public contributor profile. Each contribution type can link to the original accepted submission where that source is public.
A contribution record can show:
what was submitted;
who made it;
when it was accepted;
its role or credit;
where it was later used or referenced.
Accepted contribution does not automatically create Ticket ownership, Crew, canon status, NFT ownership, IP ownership or a financial reward. Those are separate records and rules.
OWNERSHIP + CONTEXT
Blockchain can prove that an asset moved. MUTERRA explains what the record means.
A blockchain transaction can show that a Ticket moved from one wallet to another.
The MUTERRA Registry can add the information a user actually needs to understand that movement: Ticket class, current holder, transfer history, relevant snapshots, programme eligibility and connected Crew or Bridge records.
The blockchain record remains the verifiable ownership layer where applicable. The Registry is the readable project layer around it.
PUBLIC PROFILE
You choose how much of your identity is public.
A Ticket or contribution can be linked to a MUTERRA account or verified wallet without requiring the owner or contributor to publish a legal name.
Where supported, a public record can use one of three levels:
WALLET / ACCOUNT ONLY
Show the verified identifier without a public personal profile.
PSEUDONYM
Show a chosen public name and avatar.
PUBLIC PROFILE
Show a public contributor or Founder profile with biography, links, roles and contribution history.
Public ownership and provenance can remain inspectable without forcing unnecessary personal exposure.
EVENT RECORDS
A Ticket can accumulate new records as MUTERRA develops.
A launch snapshot, Founder Drop, RAOLAX event, gameplay milestone or other published programme can add a dated event to the relevant Ticket or participant record.
These events answer practical questions:
Who held the Ticket then?
Was the Ticket eligible?
Which class and Weight applied?
Was a Drop or distribution attached to that snapshot?
Did a Bridge or Crew role exist at that moment?
Do not present “history” as a benefit by itself. Event history is useful because it explains ownership, eligibility and responsibility at a specific time.
BOUNDARIES
A record is evidence. The programme rules create the rights.
The Registry does not by itself guarantee:
profit;
resale value;
liquidity;
future distributions;
permanent holder benefits;
company equity;
MUTERRA IP ownership;
canon inclusion;
a reward for every contribution;
Crew status;
permanent public identification.
The Registry records ownership, eligibility, roles and attribution. Rights and rewards come from the rules of the specific Ticket, asset or programme.
Continue your Founder path
Understand the rule. Then make the decision.
The Library keeps Ticket mechanics, ownership, risk and the wider MUTERRA world connected without mixing their canonical sections.