Setting up Cryptoworth for a multi-chain DeFi protocol
The first decision is not which connections to add. It is how to map entities onto the workspace before any wallet gets connected.
A protocol running across 10+ chains usually has more legal entities than the founding team initially planned for — a foundation, an operating company, a tax-resident subsidiary somewhere with banking that actually works. Cryptoworth's workspace model maps to entities, not to chains. Get that mapping wrong at setup, and you spend the next year explaining why a Polygon wallet appears under three different reporting nodes.
The five-step setup we run on every multi-chain DeFi implementation
1. Lock the entity map first
List every legal entity that holds wallets, executes payments, receives revenue, or owes obligations. Diagram which entity owns which wallet — multisigs, hot wallets for operating spend, cold storage. Confirm with whoever runs the legal function before touching the workspace.
2. Add wallets one entity at a time
Do not bulk import. Add wallets per entity, validate that historical activity pulls correctly, and spot-check against the explorer for the first three weeks of data. Multi-chain protocols often have wallets with signer changes, forgotten airdrops, or stale connections you want to find at setup — not at close.
3. Design the classification rule set early
Cryptoworth's classification engine works best when given intent. Set rules for staking rewards, lending interest, AMM LP gains and losses, gas costs, bridge transfers, swaps, and airdrops as separate categories. A protocol active across 10+ chains sees all of these and more.
4. Agree cost-basis methodology upfront
FIFO is the default in most jurisdictions. DeFi-native protocols sometimes want Spec-ID for treasury management or LIFO for tax optimization. Decide before you start posting — switching mid-year is expensive and creates restatement risk.
5. First close, with manual review on every classification
The engine catches most of it; the residual is where methodology decisions become real. Use the first close to refine the rule set for everything that follows.
Most multi-chain implementations take 30–45 days from kickoff to first clean close. Skip steps 1–2 and the timeline stretches to 60+ days fixing what setup did not catch. Worth doing slowly the first time.