Skip to main content

Claiming Stardust Assets

Exchanges and dApp Devs Only

The migration documentation describes the processes needed to claim and migrate output types manually; However, for the average user, this knowledge is not needed and is abstracted in the wallet web application (dashboard). The specific migration knowledge described here is unnecessary for people using a regular wallet.

As detailed in the Stardust Move Models, Stardust assets are represented as Move objects within the ledger. Claiming these assets involves enabling original owners to utilize a Programmable Transaction Block to "unlock" assets such as IOTA, custom Coins, or even Alias and Nft objects.

This process takes advantage of Move's unique features to ensure that assets are transferred and unlocked securely and efficiently to their rightful owners.

Output Types to Move Objects

Stardust assets come in the form of Outputs, and each Output can be of a different type. To understand how Outputs have been transformed into Move Objects based on their types, please refer to the Stardust Move Models page. Below, you will find one or more examples of claiming each Output type.

Examples of Stardust Asset Claim Transactions

Here are some examples of transactions for claiming Stardust assets. Different commands in a PTB are used depending on the claiming scenario, which varies based on the Stardust Output type and composition.

Basic Output

Go to Basic Output.

Nft Output

Go to Nft Output.

Alias Output

Go to Alias Output.

Foundry Output

Go to Foundry Output.

Output Unlockable by an Alias/Nft Address

Go to Output Unlockable by an Alias/Nft Address.

Sponsoring Your Iota Claiming

If some assets are owned by an Iota address that holds no IOTA tokens (needed to pay for gas), the claiming process can benefit from self-sponsorship. This means that an address owning IOTA tokens can be used by the same user to sponsor a transaction claiming Iota assets.

Go to Self-sponsor Iota Claims.