Reconciling Cryptoworth balances with onchain activity

Close week starts with a reconciliation: what does Cryptoworth say each wallet holds, what does the chain say, and where do they disagree. The mechanics are simple. The disagreements are where the time goes.

The three places subledger and chain routinely disagree

1. Pending or late-syncing transactions

Connection-side delays mean a transaction confirmed onchain hours ago has not yet flowed through to Cryptoworth. Usually self-resolves; worth a note in the close file and a re-pull at the end of the day.

2. Bridge transactions

Funds moving between chains via a bridge show up as outbound on chain A and inbound on chain B, with timing offsets and sometimes fee differences. If the classification logic does not understand bridges as a single economic event, the subledger reports both legs as standalone events.

3. Dust, airdrops, and contract interactions

Tiny amounts of unknown tokens, surprise airdrops, and interaction artifacts (failed transactions, approval transactions, intermediate routing) clutter chain data. Some are economically meaningful, most are not. The classification rule set has to handle them so they do not skew balances or revenue.

The standard close-week reconciliation loop

1. 1Pull current chain balances for every wallet.
2. 2Pull current subledger balances for the same wallets.
3. 3Tabulate the variance per wallet per asset.
4. 4Investigate any variance above the chosen materiality threshold.
5. 5Resolve via classification fix, missing transaction add, or documented exception.
6. 6Lock the period only when material variances are zero or documented.

The first reconciliation on a new environment is slow. By month three on a stable environment, this loop takes a few hours per close.