Melting Native Tokens
This section in the tutorial will show you how to transition an existing Foundry Output to a new state. Specifically, how to melt the tokens that were transferred to an Output where you sent your native tokens.
This transaction will involve three Inputs and three Outputs:
Input #1: The unspent Output of the Alias Address that controls your Foundry, created when you minted your native tokens.
Input #2: The Foundry Output you created when you minted your native tokens, controlled by your [Alias Address](](/shimmer/iota.js/tutorials/native-token-transactions/mint-native-tokens#prepare-the-alias-address) and corresponds to the serial number
1
.Input #3: The UTXO created in when you sent native tokens that holds
12
native tokens that you are going to melt by issuing this transaction.Output #1: The next Alias Output that captures the state of your Alias Address.
Output #2: The next Foundry Output that captures the next state of your Foundry. It declares the melted tokens after transaction confirmation.
Output #3: The same as Input #3 but without any native tokens, as you will have melted them.
Preparation
To perform the transaction that will melt the native tokens, you will need:
A Shimmer Node. You can use the Shimmer Testnet nodes.
The Alias ID of your Alias, in hexadecimal format
0x6dd4...
.The keys of the State Controller of your Alias.
The address (and keys) that holds the native tokens to be melted
rms1qryyzvm...
.
const aliasId = process.argv[2];
if (!aliasId) {
console.error('Please provide your Alias Id');
process.exit(-1);
}
const client = new SingleNodeClient(API_ENDPOINT, {
powProvider: new NeonPowProvider(),
});
const nodeInfo = await client.info();
const protocolInfo = nodeInfo.protocol;
const stateControllerAddress = '0x647f...';
const stateControllerPubKey = '0x55419...';
const stateControllerPrivateKey = '0xa060f...';
const nativeTokenOwnerAddress = '0xc8413...';
const nativeTokenOwnerAddressBech32 = 'rms1qryyzvmx...';
const nativeTokenOwnerPubKey = '0xa5e76a...';
const nativeTokenOwnerPrivateKey = '0xc4e210...';
Set the New State of Your Alias Address
In this step, you need to transition the Alias Address to a new state, as one of its bound elements, the Foundry, is changing its state.
Query for the Alias Output
First, you need to find the unspent Alias Output of your Alias Address through a query to the indexing plugin using the Alias ID. You need to obtain the full Output details, as you will need to use it as Input for your transaction.
const indexerPlugin = new IndexerPluginClient(client);
const outputList = await indexerPlugin.alias(aliasId);
const consumedOutputID = outputList.items[0];
console.log('Consumed Output Id', consumedOutputID);
const initialAliasOutputDetails = await client.output(consumedOutputID);
const initialAliasOutput: IAliasOutput =
initialAliasOutputDetails.output as IAliasOutput;
Assign the New State of the Alias
To continue, you can create the next Alias Output by cloning the one obtained in the previous step, and then increment the stateIndex
.
const nextAliasOutput: IAliasOutput = JSON.parse(
JSON.stringify(initialAliasOutput),
);
nextAliasOutput.stateIndex++;
At the end of this step, you know both Input #1 and Output #1.
Set the New State of Your Foundry
In this step, you need to transition your Foundry to a new state, as some tokens will be put in melted state.
Query for the Foundry Output
First, you need to find the unspent Foundry Output to transition by sending a query to the indexing plugin using the Alias Address. You need to obtain the full Output details as you will need to use it as Input for your transaction.
const aliasIdBech32 = Bech32Helper.toBech32(
ALIAS_ADDRESS_TYPE,
Converter.hexToBytes(aliasId),
protocolInfo.bech32Hrp,
);
const foundryList = await indexerPlugin.foundries({
aliasAddressBech32: aliasIdBech32,
});
if (foundryList.items.length === 0) {
throw new Error('Foundry Output not found');
}
const foundryOutputID = foundryList.items[0];
const initialFoundryOutputDetails = await client.output(foundryOutputID);
const initialFoundryOutput: IFoundryOutput =
initialFoundryOutputDetails.output as IFoundryOutput;
Keep in mind that you will need to use the Bech32Helper.toBech32(bech32Text, humanReadablePart)
(references/client/classes/Bech32Helper/#frombech32) function to convert your Alias ID to a Bech32 address to match the format of the parameter expected by the indexing plugin.
At the end of this step, you know Input #2.
Query for the Native Tokens Output
As you are going to melt all the tokens of your formerly created Output, you need to perform a query to obtain its ID and the number of native tokens involved. You will also use this Output as Input #3 of the transaction.
const tokenClassId: string = TransactionHelper.constructTokenId(
initialAliasOutput.aliasId,
initialFoundryOutput.serialNumber,
initialFoundryOutput.tokenScheme.type,
);
const outputWithTokensToMeltList = await indexerPlugin.basicOutputs({
addressBech32: nativeTokenOwnerAddressBech32,
hasNativeTokens: true,
});
if (outputWithTokensToMeltList.items.length === 0) {
throw new Error('There are no outputs with native tokens');
}
// We assume the first one is the right one
const outputWithTokensToMeltID = outputWithTokensToMeltList.items[0];
const outputWithTokensToMeltDetails = await client.output(
outputWithTokensToMeltID,
);
const outputWithTokensToMelt =
outputWithTokensToMeltDetails.output as IBasicOutput;
if (
!outputWithTokensToMelt.nativeTokens?.some(
(element) => element.id === tokenClassId,
)
) {
throw new Error('Unexpected token class Id');
}
The some
function check that the Output actually holds native tokens of the expected class ID.
At the end of this step, you know Input #3.
Set the Amount of Melted Tokens on the Foundry
Once you know how many tokens you are going to melt, you just need to set the meltedTokens
field of the next Foundry Output.
As an Output can hold tokens of many classes at the same time, you should use the findIndex
function to ensure you are referring to the right token class. In this simple case, you can check that index
is equal to 0
.
const index = outputWithTokensToMelt.nativeTokens?.findIndex(
(element) => element.id === tokenClassId,
);
nextFoundryOutput.tokenScheme.meltedTokens =
outputWithTokensToMelt.nativeTokens[index].amount;
At the end of this step, you know Output #2.
Create the Remainder Output
In this step, you must create the remainder Output. The remainder Output will be the same as Input #3 except for the native tokens of tokenClassId
that are removed from the Output.
const remainderOutput = JSON.parse(
JSON.stringify(outputWithTokensToMelt),
) as IBasicOutput;
// No longer have native tokens (assumption: there is only one entry of native tokens of tokenClassId)
remainderOutput.nativeTokens = remainderOutput.nativeTokens?.filter(
(element) => {
element.id !== tokenClassId;
},
);
At the end of this step you know, Output #3.
Define the transaction
Define the Inputs and Outputs
Now, you can create the transaction essence to melt your native tokens as shown in the following snippet:
const inputs: IUTXOInput[] = [];
const outputs: (IAliasOutput | IFoundryOutput | IBasicOutput)[] = [];
inputs.push(TransactionHelper.inputFromOutputId(consumedOutputID));
inputs.push(TransactionHelper.inputFromOutputId(foundryOutputID));
inputs.push(TransactionHelper.inputFromOutputId(outputWithTokensToMeltID));
outputs.push(nextAliasOutput);
outputs.push(nextFoundryOutput);
outputs.push(remainderOutput);
const inputsCommitment = TransactionHelper.getInputsCommitment([
initialAliasOutput,
initialFoundryOutput,
outputWithTokensToMelt,
]);
const transactionEssence: ITransactionEssence = {
type: TRANSACTION_ESSENCE_TYPE,
networkId: TransactionHelper.networkIdFromNetworkName(
protocolInfo.networkName,
),
inputs,
inputsCommitment,
outputs,
};
At the end of this step, you have defined the transaction essence. It includes three Inputs:
- Input #1: From
consumedOutputID
, the unspent Alias Output of the Alias Address. - Input #2: From
foundryOutputID
, the unspent Foundry Output owned by the Alias Address. - Input #3: From
outputWithTokensToMeltID
, the Basic Output holding native tokens.
And three Outputs:
- Output #1:
nextAliasOutput
, the next Alias Output of the Alias Address. - Output #2:
nextFoundryOutput
, the next Foundry Output, now declaring melted tokens. - Output #3:
remainderOutput
, the remainder of the Basic Output with no native tokens oftokenClassID
.
Provide the Unlocks
In this case, you need to provide three unlocks::
- The State Controller unlock signature for the Alias Output.
- The reference to the former to unlock the Foundry Output. Remember that the Alias controls the Foundry.
- The unlock signature of the controller of the address that holds the native tokens melted.
const wsTsxEssence = new WriteStream();
serializeTransactionEssence(wsTsxEssence, transactionEssence);
const essenceFinal = wsTsxEssence.finalBytes();
const essenceHash = Blake2b.sum256(essenceFinal);
const unlockSignature: ISignatureUnlock = {
type: SIGNATURE_UNLOCK_TYPE,
signature: {
type: ED25519_SIGNATURE_TYPE,
publicKey: stateControllerPubKey,
signature: Converter.bytesToHex(
Ed25519.sign(
Converter.hexToBytes(stateControllerPrivateKey),
essenceHash,
),
true,
),
},
};
const unlockFoundry: IAliasUnlock = {
type: ALIAS_UNLOCK_TYPE,
reference: 0,
};
const unlockTokens: ISignatureUnlock = {
type: SIGNATURE_UNLOCK_TYPE,
signature: {
type: ED25519_SIGNATURE_TYPE,
publicKey: nativeTokenOwnerPubKey,
signature: Converter.bytesToHex(
Ed25519.sign(
Converter.hexToBytes(nativeTokenOwnerPrivateKey),
essenceHash,
),
true,
),
},
};
const transactionPayload: ITransactionPayload = {
type: TRANSACTION_PAYLOAD_TYPE,
essence: transactionEssence,
unlocks: [unlockSignature, unlockFoundry, unlockTokens],
};
Submit the blockB
And finally, you can submit the block. After the block is confirmed, you can query the Shimmer Explorer for your Alias Address and find the new Alias Output with the updated state.
const block: IBlock = {
protocolVersion: DEFAULT_PROTOCOL_VERSION,
parents: [],
payload: transactionPayload,
nonce: '0',
};
const blockId = await client.blockSubmit(block);
console.log('Block Id:', blockId);
Putting It All Together
You can download the code to melt native tokens from the iota.js repository.