Skip to main content

IOTA Stardust: DeFi & transaction import via public key

Blockpit automatically imports IOTA Stardust transactions via your public wallet address (public key): all common transaction types (Deposits, Withdrawals, Bridging, Trades, etc.). Not recorded: iOTA Synced Balances (Seit IOTA Rebased Launch auf 0 fixiert) as well as native Tokens & NFTs.

​

DeFi stands for Decentralized Finance and enables the transfer and trading of crypto assets within one or more decentralized networks (blockchains). With Blockpit you can import these transactions into an integration for your tax & portfolio tracking.

​

Import method: wallet address (public key)

​

​

How to add your IOTA Stardust integration

All you need is your public wallet address (public key) from IOTA Stardust. Here is how:

​

1️⃣ Open + Integration (or, in the Dashboard, click + Integration on the tab Integrations).

​

2️⃣ Select the tab Blockchain and then IOTA Stardust.

​

3️⃣ Enter a name for the integration and paste your public key (public wallet address) from IOTA Stardust.

​

4️⃣ Select the import time span.

​

💡 Tip: Keep Full History as the preset import time span. Choosing a specific start date only makes sense if you want to add transactions that lie before it manually.

​

5️⃣ To finish, click Continue. Blockpit creates the integration and imports the asset balance and transactions automatically.

​

​

​

What happens after you add it

After Continue, Blockpit imports the IOTA Stardust integration automatically. This is what applies afterwards:

  • Where you see the result: in the Dashboard on the tab Integrations (holdings and balance) and under Transactions (individual transactions)

  • Synchronization: transactions are synchronized fully automatically once a day (Blockpit Plus subscription required); this takes a few minutes to hours. With Sync All or per integration in the Dashboard (tab Integrations) you can trigger it yourself

  • Balance: The Synced Balance and live prices are updated automatically every 7 minutes, without a sync. If the Synced Balance and the calculated balance differ, Blockpit shows the tip Mismatched Balance

​

​

​

Blockpit records these IOTA Stardust transactions automatically

General

✅ All common transaction types (Deposits, Withdrawals, Bridging, Trades, etc.)

⛔ IOTA Synced Balances (hardcoded to 0 since IOTA Rebased launch)

⛔ Native Tokens & NFTs

​

📆 Es können ausschließlich Transaktionen ab dem Start (04. Oktober 2023) des Iota Netzwerks (Stardust) importiert werden.

​

Swaps (Trades)

A swap is the exchange of one crypto asset for another. These exchanges are usually recognized automatically with the label Trade.

​

✅ Supported

​

​

Liquidity Providing/Mining

Providing crypto assets in so-called liquidity pools is shown as several swaps or transactions with the label Trade. The crypto assets you provide are exchanged in equal parts for a so-called LP token. From then on, this LP token represents your share of the respective liquidity pool. As soon as you leave the pool again, it is swapped back.

​

✅ Supported

​

​

Staking, Lending, Airdrop & Bounty Rewards

If generated income is imported automatically as unlabeled Deposit, you can categorize the affected transactions afterwards with the appropriate transaction label (Staking, Interest, Airdrop, Bounty, etc.), as shown in the image below.

​

✅ Supported

​

💡 Tip: You can give free NFT mints the label Airdrop. You recognize them by the transaction note Fallback_Claim.

​

​

​

​

How do I solve problems with my IOTA Stardust integration?

​

Should transactions still be missing or imported incorrectly, or should your Synced Balance be displayed incompletely, you can help our support team to include them (if technically possible) in our import spectrum.

​

Please send us the following via chat request:

  • all available information about the problem

  • your public wallet address (public key)

  • the corresponding transaction hash from IOTA Explorer

​

​

Typical mistakes

✗ Swap appears as unlabeled deposit and withdrawal → connect both transactions afterwards (instructions in the section Swaps)

✗ Liquidity transaction appears as unlabeled deposit and withdrawal → recreate it afterwards (instructions in the section Liquidity Providing)

✗ Income arrives as unlabeled deposit → categorize it afterwards with the appropriate label (Staking, Interest, Airdrop, Bounty)

✗ Free NFT mint is not labeled → give it the label Airdrop; recognizable by the transaction note Fallback_Claim

✗ Missing transaction reported without naming public key and transaction hash → both belong in the chat request

​

​

Did this answer your question?