What Matters
Five trading accounts do not establish five independent risks. Different venues can share a custodian, collateral issuer, settlement network or operational provider. DN’s Venue Concentration Index measures how capital is distributed across user-defined dependency groups and estimates exposure to a chosen group disruption. It separates diversification by account from diversification by the infrastructure and entities those accounts depend on.
DN Evidence Block
Last reviewed: 14 October 2026. Edition: 2027 early edition; no future observations.
Primary-source basis: BIS research on DeFi interconnectedness; Circle’s native-USDC information and third-party bridged-USDC terms. Sources support the dependency framework, not a live venue risk ranking.
Original DN contribution: grouped concentration calculator, effective allocation-group count and selected-group disruption scenarios.
Dataset and test period: five synthetic $20,000 allocations, reviewed and calculated on 14 October 2026. No account balances collected, custody arrangements audited or failure probabilities estimated.
Research: Decentralised News. Independent reviewer: not assigned. Group labels are illustrative and do not identify real corporate relationships.
DN Alpha Thesis: count dependencies before counting accounts
Spreading trading capital can reduce the amount directly exposed to one venue. But the benefit depends on the failure being considered. An exchange withdrawal interruption, an issuer problem and a network outage affect different sets of balances.
If five accounts all hold the same issuer’s stablecoin, they can still have a common asset dependency. If two applications use the same settlement network, a network interruption can affect both even when their contracts and operators differ. Neither observation proves they will fail together; it identifies a scenario worth testing.
The useful question is not simply “How many platforms do I use?” It is “Which balances become impaired or unavailable if this particular dependency fails?”
Five layers to map separately
| Layer | What to group | What to verify | Important limitation |
|---|---|---|---|
| Venue or legal counterparty | Balances associated with the same relevant entity | Account agreement, contracting entity and withdrawal terms | Shared ownership alone does not prove identical creditor claims |
| Custody or asset control | Balances subject to a common custody dependency | Custodian, segregation, wallet controls and recovery arrangements | An off-exchange arrangement can change exposure without removing every dependency |
| Collateral issuer | Balances dependent on the same issuer | Token contract, issuer and redemption eligibility | The token ticker is insufficient; representations can differ |
| Settlement or bridging | Balances affected by a specified chain or bridge disruption | Network, bridge mechanism and exit route | Native and bridged tokens need different dependency maps |
| Operational control | Accounts relying on the same signer, API provider or access system | Fallback access, permissions and tested recovery | An access outage can block actions without causing immediate asset loss |
Circle describes native USDC across supported networks. Moving that asset between networks does not by itself remove the shared issuer dependency. Its third-party bridged-USDC terms describe circumstances where bridging or unbridging can be unavailable. These are different kinds of exposure, so the same capital should be examined under separate lenses.
BIS research identifies interconnectedness and liquidity mismatches among DeFi vulnerabilities. DN’s framework applies a narrower portfolio question: how much of your selected capital is assigned to one dependency under one defined scenario?
The index: transparent concentration, not a safety score
Let each balance be assigned to exactly one group for the selected lens. Add balances within each group, divide by total included capital and call that group’s share w.
DN Group Concentration Index = 100 × sum of squared group shares.
Effective allocation-group count = 1 / sum of squared group shares.
Selected-group affected capital = capital assigned to the selected group.
Illustrative permanent loss = affected capital × assumed loss percentage.
Illustrative temporarily unavailable capital = affected capital × assumed unavailable percentage.
The squared-share measure is the Herfindahl concentration calculation, applied here to a declared capital map. DN’s contribution is the dependency mapping workflow and scenario tool, not the invention of the formula. A higher index means more concentration; it does not mean a measured probability of failure.
The reciprocal translates concentration into the number of equally weighted groups that would produce the same value. It does not certify independence, legal separation or equal risk. Do not use antitrust concentration thresholds as trading safety categories.
How five equal accounts become 2.78 effective groups
| Account | Capital | Selected dependency group | Account share |
|---|---|---|---|
| Account 1 | $20,000 | A | 20% |
| Account 2 | $20,000 | A | 20% |
| Account 3 | $20,000 | B | 20% |
| Account 4 | $20,000 | B | 20% |
| Account 5 | $20,000 | C | 20% |
Measured by account alone, five equal balances have a concentration index of 20 and an effective count of 5. Under the hypothetical dependency mapping, groups A, B and C contain 40%, 40% and 20% of capital. Their squared shares sum to 0.36: the grouped index is 36 and the effective allocation-group count is approximately 2.78.
If all five allocations instead depend on one issuer under the issuer lens, that lens reports an index of 100 and an effective count of 1. This is an exposure statement, not a forecast that the issuer will fail.
If group A is temporarily inaccessible, the scenario affects $40,000. A separate assumption of 40% permanent loss on that group implies $16,000 of loss. Temporary unavailability and permanent loss are alternative outputs here; they must not be added together as if they were disjoint amounts.
DN Dependency Concentration Calculator
Choose one lens, then map each capital allocation to A, B, C, D or E. Reuse a group only when your chosen scenario treats those allocations as sharing the dependency. Labels do not verify real relationships.
| Allocation | Included capital ($) | Dependency group |
|---|---|---|
| Account 1 | ||
| Account 2 | ||
| Account 3 | ||
| Account 4 | ||
| Account 5 |
Do not sum exposure across lenses
A $20,000 position may depend on a venue, an issuer and a network. Reporting $20,000 against each dependency is appropriate within separate scenarios. Adding those three figures and calling it $60,000 of capital is double counting.
For a combined disruption, identify the unique allocations affected by any selected dependency and count each allocation once. The calculator analyses one lens at a time. It does not compute overlapping multi-layer event unions.
If an account contains several assets or custody arrangements, split its capital into separate allocation rows before mapping. This five-row tool is a compact first pass; larger portfolios require a ledger with more rows. A mixed balance placed entirely into one group can materially distort the result.
Which allocation structure fits which objective?
| Structure | Potential use | Costs and access | Main limitation |
|---|---|---|---|
| One venue, several subaccounts | Strategy separation and permissions | Internal transfers and shared venue rules | More logins or subaccounts need not diversify legal or custody exposure |
| Several centralised venues | Execution access and direct venue exposure limits | Repeated identity checks, prefunding and withdrawal costs | Shared collateral or providers can remain; legal rights differ by entity |
| Centralised venues plus onchain protocols | Different execution and custody mechanisms | Network fees, signing and smart-contract due diligence | Issuer, network, bridge or operational dependencies may overlap |
| Trading sleeve plus separate reserve custody | Limit capital committed to trading systems | Transfer timing, custody overhead and opportunity cost | Separate reserves may arrive too late to meet a trading need |
No structure earns a universal “best” label. Moving capital changes liquidity, access, custody and operational complexity. A mathematically more even allocation can still increase practical risk if it requires unreliable routes or poorly understood products.
An evidence-first dependency audit
- Set the denominator. Use current USD-equivalent capital allocated to the audited sleeve. Exclude duplicate views of the same collateral. Treat derivative notional and debt separately.
- Define the event. Specify a custody failure, issuer impairment or access interruption. Do not use one vague “risk group” for unrelated events.
- Collect primary evidence. Record legal entity, custodian, token contract, network, bridge and critical access providers, with sources and review dates.
- Mark unknowns. Do not assume unidentified providers are independent. Run both separate-group and shared-group sensitivities; neither replaces missing diligence.
- Map the response. Check whether the remaining accounts can accept funds, hedge or close exposure when the affected group is unavailable.
A conservative grouping can reveal a large possible common dependency, but it is still an assumption. Separate documented relationships from analyst hypotheses. Update the map when account terms, token representations, custody arrangements or network architecture change.
Connect concentration to capital and liquidity
The Crypto Collateral Efficiency Index asks how much capital is deployable. The Crypto Emergency Liquidity Index asks whether reserves can arrive in time. This concentration tool asks how much of that capital shares a selected dependency.
Read Building a Multi-Exchange Hedged Position for strategy mechanics. Use DN Decision Briefs and Pathfinder for further platform research. Adding a venue is a commercial and operational decision, not an automatic improvement in diversification.
Methodology and limitations
DN reviewed the cited primary sources on 14 October 2026 and calculated a synthetic five-allocation dataset. The tool uses squared capital shares and user-defined groups. It does not assess solvency, regulatory protection, recovery timing, custody enforceability, asset quality, smart-contract security or correlations.
Accounts are weighted by included capital, not transaction volume or gross position notional. Negative balances are excluded by the input validation; liabilities require a separate exposure assessment. Concentration measures cannot compare the safety of a high-quality concentrated structure with a low-quality diversified one.
Operational status: no venues are ranked or actively promoted in this edition. Current affiliate links do not establish independence or LIVE status. Future named recommendations require independent operational verification.
Change log: v0.1, 14 October 2026: dependency framework, synthetic dataset and calculator. Corrections: contact DN with primary evidence. Review when material dependency relationships change.
Primary sources
- BIS: DeFi risks and the decentralisation illusion . Context for interconnectedness, concentration and liquidity risks.
- Circle: USDC . Native issuance across supported networks.
- Circle: third-party bridged-USDC terms . Specific bridging and unbridging constraints; terms are not a description of every bridge.
Frequently asked questions
Are five accounts five independent risks?
No. Account count alone does not establish independent custody, issuer, settlement or operational dependencies.
What does an effective group count of 2.78 mean?
It means the grouped capital shares have the same squared-share concentration as approximately 2.78 equally weighted groups. It does not prove independence or safety.
Does using the same stablecoin on two networks diversify issuer risk?
Not by itself. It can change network exposure while retaining the same issuer dependency. Verify native or bridged representation and applicable terms.
Is the scenario loss a forecast?
No. The loss percentage is user-defined and applied to the selected group. The calculator estimates neither failure probability nor actual recovery.
Disclosure
Educational research, not personalised investment or legal advice. Diversification cannot eliminate losses. Dependency groups and loss assumptions require independent verification. DN may receive referral compensation elsewhere on the site; external links here are neutral primary sources without referral codes. No real venue relationships are asserted by the synthetic example.
