A connection brings a wallet's or exchange's data into Cryptoworth.
Adding many wallets? Use Bulk Import. This guide shows one connection at a time.
For a wallet, have its public address and blockchain network ready. Never enter a private key or seed phrase. For an exchange, ask its administrator for dedicated read-only API credentials, with trading and withdrawals disabled.
1. Open the connection list
Open the correct entity, then go to Integrations > Connections.
Click +, then Add wallet. This opens the catalog for both wallets and exchanges.
2. Add a blockchain wallet
Example: Ethereum. Choose the network your wallet actually uses, even if the same address works on other chains.
Select Blockchains, search for your network, and select its card.
Enter a clear wallet name and the full public wallet address. Use the wallet's address, not a token contract address.
Keep Sync Transactions checked to import history. Create address book record is optional; Track DeFi adds supported DeFi balances. Leave Sync selected contracts and Custom Date off for a full-history import.
Review the network and address, then click Connect.
Need a later starting date? See How to Set a Custom Sync Start Date. Earlier acquisitions may still be needed for cost basis.
3. Or add an exchange
Example: Gemini. Choose your own exchange; its required fields may differ.
In the catalog, select Exchanges & Custody, search for your exchange, and select its card.
Name the connection. Enter your exchange's read-only API Key and API Secret, plus any other required fields.
Keep Sync Transactions checked. For this Gemini example, leave Sync transactions from blank to use its available history from the beginning.
Check the credentials, then click the exchange form's Connect button.
4. Check the imported data
Return to Integrations > Connections and wait for transaction sync to finish. Check Status and Last Sync Attempt. Balance Synced confirms balances only, not transaction history.
Go to Subledger > Reconciliation and click Sync & Reconcile. Wait for it to finish.
Open Data Sanity Check. Expand any connection marked Gaps detected, then compare Calculated Balance with Reported Balance.
A completed sync does not prove the history is complete. Resolve gaps before calculating cost basis; use the Sanity Check Guide.
Connection failed? Check the selected network, full address, or active read-only API credentials. Check whether the provider is offline before trying again.
Already connected? Open the existing connection instead of adding it again. Duplicate imports can distort balances.