Crypto.org Chain transactions can be imported automatically into your Blockpit Wallet Depot via public key.
The following Crypto.org Chain based transactions are automatically imported:
General
All native transaction types are supported (incl. Governance, Staking, Delegating, etc.) IBC-Transfers (Inter Blockchain Communication Protocol)
Crypto.org Chain is based on Cosmos and can communicate with other Blockchains based on Cosmos.
NFTs
Inflows and outflows of Non Fungible Tokens (NFTs) are automatically imported in the form of Deposit, Withdrawal or Trade transactions.
Your NFT assets will be created completely dynamically through your Public Key.
The following NFT transactions and dApps are supported:
Mints Claims Transfers
Staking, Lending, Airdrop & Bounty Rewards
If rewards are getting imported as Deposit, you can reclassify these transactions to the appropriate transaction type (Staking, Lending, Airdrop or Bounty) as shown in the image below.
Tip: Free NFT mints can be reclassified as Airdrops. You can identify them by the transaction note "Fallback_Claim".
Troubleshooting:
My transactions are imported incorrectly!
- Create your depot a second time under a different name and check if your transactions are now imported correctly.
- If your transactions are imported under an incorrect transaction type, you can edit them manually.
Alternatively, please send us your public wallet address (public key) as well as the corresponding transaction hash via ticket.
How does the asset balance calculation differ between Synced- and Unsynced Depots?
Why is my asset displayed as „Unknown“ in the depot balance?
<%= heading %>