Sync & Connectivity

Sync & Connectivity

How does wallet sync work?

When you connect a wallet, CryptaCount fetches blockchain data in two parallel categories:

• Transactions — native chain transactions (ETH transfers, contract calls, etc.)
• Token transfers — token transfer events (ERC-20, ERC-721, etc.)

Each category tracks its own sync progress independently, so one never blocks the other. The sync status indicator on the wallet card shows progress for each category separately.

Note

Both categories must complete for a wallet’s data to be fully up to date.

My wallet sync is stuck or not progressing

If a sync appears stuck:

1. Check the sync status indicator on the wallet card — it shows blocks processed per category.
2. If the status shows an error, click the wallet to see error details.
3. Try re-triggering the sync from wallet settings. The sync resumes from each category’s last processed block, not from the beginning.
4. If re-triggering doesn’t help, check whether you need approval — syncs may require a sync request depending on your plan. Go to the wallet and click “Request Sync” if the sync button is disabled.

Automatic retry: If a blockchain data provider is temporarily unavailable, the platform automatically retries failed requests. If the provider is fully down, the sync pauses until the connection is restored.

Sync request flow

Some plans or workspace configurations require approval before syncing. The flow is:

1. You request a sync from the wallet page
2. The request enters Pending status
3. An authorized user reviews and approves or rejects the request
4. On approval, the sync begins automatically
5. Progress is tracked with wallet and completion counts

My balance doesn’t match the block explorer (Etherscan, etc.)

A balance mismatch between CryptaCount and a block explorer usually indicates one of these issues:

Sync hasn’t completed. Wait for both sync categories (Transactions and Token Transfers) to finish. Check the sync status for each.

Pending transactions. CryptaCount syncs confirmed transactions only. Pending (unconfirmed) transactions aren’t reflected until confirmed on-chain.

Spam tokens. CryptaCount’s spam detection may have hidden tokens that the block explorer still shows. Check Settings → Asset Registry and look for spam-flagged assets.

Internal transactions. Some contract interactions generate internal transactions not captured by all sync methods. Check whether the relevant contract calls appear in your transaction list.

Token transfers are showing as TRANSFER_OUT but no TRANSFER_IN

This was a known classification issue that has been fixed. Address comparisons are now case-insensitive, so EVM address case differences no longer cause misclassification.

If you still see this issue:

1. Verify the wallet address in your settings matches what you expect
2. Ensure both wallets (if you control both sides) are connected to the workspace
3. Confirm token transfers have finished syncing
4. Manually reclassify affected transactions from the transaction detail view if needed

How does transaction deduplication work?

Every synced transaction receives a unique identifier based on the chain, block, transaction hash, and event position. This ensures that re-syncing never creates duplicate records, even if the sync is interrupted and restarted.

Sync says “Already up to date” but I know there are new transactions

The sync tracks the last-processed block per category (Transactions vs. Token Transfers). If you’re missing token transfers but native transactions are fine, it means the token transfer category needs to catch up independently.

To resolve:

1. Check the last synced block number for each category in the wallet’s sync details
2. Compare with the block number of the transactions you expect
3. If the block numbers look correct but data is missing, contact support — the sync state may need a reset for that wallet/category

Which blockchain networks are supported?

CryptaCount supports 131 chains across 21 address types. The full list is visible when adding a new wallet — the chain selector shows all available options.

Supported address types include: EVM, Bitcoin (Legacy, P2SH, SegWit, Taproot), Solana, TRON, XRP, Cardano, Cosmos, TON, Polkadot, Stellar, NEAR, Aptos, SUI, StarkNet, Hedera, Avalanche X/P chains, and more.

Exchange (CEX) connections are not syncing

CryptaCount supports centralized exchange data via multiple import methods:

• API connections — Provide read-only API keys for supported exchanges
• CSV import — Upload CSV files from supported exchanges (templates available)
• Excel / PDF import — For exchanges that export in these formats
• Generic CSV — Map columns manually for unsupported formats

Common API connection issues:

• Expired API key — Regenerate the key on the exchange and update it in CryptaCount
• Insufficient permissions — The key needs read access to trades, balances, and deposits/withdrawals. Write access is never required.
• IP whitelist — Some exchanges require IP whitelisting. Contact support for CryptaCount’s server IPs.
• Rate limiting — Large trade histories may take multiple sync cycles. CryptaCount manages rate limits automatically.

CEX API keys are stored encrypted — see Security for details.

How often does data sync?

After the initial full sync, wallets are periodically re-synced. You can also trigger a manual sync at any time from the wallet settings (subject to plan limits and approval requirements).

Can I sync historical data from before I connected the wallet?

Yes. The initial sync fetches the complete on-chain transaction history for the wallet address, going back to the first transaction. There is no cutoff date.