NFT Metadata & Rewards

01 / TWO METADATA LAYERS

Your Ticket and your reward NFTs have different records

A reward programme can use the identity or traits of either asset. Its rules identify the qualifying asset, snapshot, allocation, reward source and delivery process. Metadata alone does not create a royalty or a share of MUTERRA revenue.

02 / YOUR CABIN

A place aboard RAOLAX

A RAOLAX Founder Ticket is represented as an NFT. That Ticket identifies a class and an individual cabin. The cabin is a characteristic of the Ticket, not another Ticket position to be sold alongside it.

Deck, sector, position and other approved attributes can make cabins different from one another. The published Ticket and Drop rules determine which details are recorded, which are assigned and when they are revealed.

03 / DIFFERENT CABINS

Different traits can lead to different stories

Two cabins of the same Founder class can begin with different traits. One might become central to an event; another might remain quiet for years. Some traits can be assigned at random when the published allocation rules permit it. The team and holder cannot know in advance which part of RAOLAX will matter most later.

Cabins are not promised equal demand, utility, rewards or resale values.

04 / EVENTS

A future event can use the ship’s geography

A separately published RAOLAX event might involve a particular deck, sector or cabin type. If that event offers MUTA or an NFT, its rules state who qualifies, the relevant snapshot, what is delivered and when.

A cabin can also matter to a story without creating a payment. Being associated with a particular location does not automatically grant MUTERRA revenue, royalties or a guaranteed reward.

05 / REVEAL & RECORD

The record should say what is known

The Ticket identifies its class and individual position. Approved cabin fields, trait ranges, assignment method, reveal timing and any changes to metadata must be stated in the relevant release rules. This page does not assume all fields are on-chain, fixed at purchase or immutable.

The Registry can preserve Founder origin, current holder and selected events as separate records. A transfer changes the holder, while the Ticket number and its cabin identity stay with the Ticket under the actual metadata rules.

06 / ADDITIONAL NFTS

An additional reward NFT is a separate question

The first four defined Founder NFT cycles each have a ceiling of up to £50,000 Initial Reference Value (IRV) and a planning scale of up to approximately 2,000 additional NFTs. The actual number depends on the asset mix, grades and published issuance rules.

IRV is a programme reference measure. It is not a cash payment, market price, resale value or guaranteed amount for an individual Ticket.

Each Drop has its own published schedule and is not triggered automatically by a MUTA Treasury release. Later programme periods publish their scale, eligibility and schedule before they begin. The end of MUTA Treasury releases does not itself end Founder status or the NFT programme.

Other MUTERRA collections can contain characters, skins and artefacts. They are distinct from a RAOLAX cabin, even if a later programme connects them to a cabin or its holder.

07 / TRANSFER

What moves with the Ticket

The Ticket NFT, its number and cabin identity can move to a new eligible holder where transfer is supported. Completed rewards remain with the recipient recorded for their cycle. Future holder-based eligibility follows the next programme snapshot.

Neither a scarce trait nor a transfer predicts a market price, a buyer or a future programme outcome.

08 / SNAPSHOT TO CLAIM

An allocation stays with the snapshot wallet

Once an allocation is recorded for a cycle, a later Ticket transfer does not move it to the buyer. My MUTERRA can show the entitlement for the linked wallet; delivery or claim follows the rules and available interface for that programme.