Blockpit automatically imports Juno transactions via your public wallet address (public key): all common transaction types (incl. Governance, Staking, Bank, etc.), IBC transfers (bridging) as well as all 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 Juno integration
All you need is your public wallet address (public key) from Juno. Here is how:
1️⃣ Open + Integration (or, in the Dashboard, click + Integration on the tab Integrations).
2️⃣ Select the tab Blockchain and then Juno.
3️⃣ Enter a name for the integration and paste your public key (public wallet address) from Juno.
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 Juno 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 Allor per integration in the Dashboard (tabIntegrations) you can trigger it yourselfBalance: 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 Juno transactions automatically
General
✅ All common transaction types (incl. Governance, Staking, Bank, etc.)
✅ IBC transfers (bridging)
✅ All tokens & NFTs
✅ All Synced Balances
❗ Certain internal transactions on EVM chains (e.g., withdrawal transactions related to wrapping; deposit transactions related to bridging) can currently not be imported automatically in all cases. Missing transaction data must therefore be added manually.
❗ Transfers from smart contract interactions can currently not be imported. Missing transaction data must be added manually.
My asset balance is not displayed correctly?
Due to the problem described above, the synchronized asset balance of your integration may deviate. Please also note that transactions added manually in automatic blockchain integrations have no effect on the displayed Synced Balance, only on the calculated balance.
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 Juno 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 chain.root
Typical mistakes
✗ Missing transaction added manually, but the Synced Balance still deviates → transactions added manually in automatic blockchain integrations only change the calculated balance, not the Synced Balance
✗ 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