Fireblocks provides support for tokenization on the Solana blockchain. You can issue Token-2022 tokens or link any Token-2022 or SPL tokens from the Solana ecosystem to your workspace.
The Token-2022 tokens consists of these features:
- Metadata: Attach and update metadata for enhanced token utility
- Transfer hook: Execute custom logic with each token transfer
- Metadata pointer: Reference external metadata sources for flexible token attributes
- Interest bearing: Allow tokens to accrue interest over time
- Mint close authority: Securely close the mint account
- Transfer fee config: Apply dynamic transfer fees for token movement
- Permanent delegate: Assign a permanent delegate for advanced token management
To learn more about these Token Extensions, visit the Solana extension guide.
Issuing Token-2022 tokens from Fireblocks Tokenization engine
To issue these tokens:
- Navigate to the Tokenization page inside your workspace. Select the +Create button to start a new deployment. You will see a list of available contracts for deployment. Scroll to the very bottom, where Solana Token 2022 is listed under Non-EVM tokens.
- You will then see the token info. Select Use Contract to proceed.
- Enter token details and select Continue.
- Choose the issuer vault and select Continue.
Note: This wallet will receive all the authorities for the aforementioned control services. More on that here. - Review Token details, then select Create token.
Once you sign the transaction and it is confirmed on-chain, you are able to see the linked token in your workspace.
Common issues
- Policy: Make sure your policy allows interacting with Solana program calls
- Vault Account: Your workspace should have at least one vault account with a Solana asset wallet that is funded with gas tokens. Once you create a wallet, you will be prompted to perform an on-chain operation to create a wallet. Make sure that step is completed before sending transactions.
Additional remarks
Authorities granted to the deployer at deployment
The following authorities are granted to the issuer of the token at the time of deployment:
- Metadata Pointer Authority
- Mint Authority
- Transfer Hook
- Freeze Authority
- Rate Authority
- Transfer Fee Config Authority
- Withdraw Withheld Authority
- Close Authority
- Permanent Delegate
This is done because Solana requires a signature from each address receiving the authority, and Tokenization does not support Multiple signatures in one transaction.
Multisignature transactions can still be performed outside of tokenization using Program Calls if needed.
Multiple signatures not supported
Some functions, like setAuthority, which require multiple signatures, are not supported for now due to tokenization lacking support for multi signature requests.
Interest-bearing account balances
Another limitation is that balances for interest-bearing accounts may not be displayed correctly, so use with caution.