출처 검증 리서치: BIS Onchain Activity Measurement

Verified source facts

1. BIS published Working Paper 1377 on September 15, 2026. 2. The paper studies transfer values, token issuance, decentralized-exchange activity and stablecoin holdings. 3. It says simple aggregations can mix economic activity with technical artefacts. 4. The paper identifies transaction aggregation, smart-contract programmability and crosschain comparability as sources of measurement divergence.

Comparison at a glance

1. Control test: Unit

A trading-control disclosure is meaningful only when converted into a testable rule. For unit, inspect transaction, transfer or address. Use a sandbox, non-production context, or the smallest reversible test available, then declare unit. Capture configuration and event evidence without recording credentials, and verify the documented cancel, reject, decrement, or history behavior.

Model the failure path, not just the setup path. Ask which strategy owns the maker and taker orders, which account boundary the venue evaluates, which message reveals intervention, and how reconciliation behaves after a partial fill or disconnect. Platform documentation describes supported settings; it cannot prove that an operator configured them correctly. In this dimension, category error is therefore an explicit audit gap.

The unit row should end with a concrete monitoring rule tied to transaction, transfer or address. Make the operator declare unit, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; category error remains a separate production risk until observed.

2. Control test: Aggregation

For aggregation, inspect raw or economic grouping. Use a sandbox, non-production context, or the smallest reversible test available, then document rule.

In this dimension, double count is therefore an explicit audit gap.

The aggregation row should end with a concrete monitoring rule tied to raw or economic grouping. Make the operator document rule, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; double count remains a separate production risk until observed.

3. Control test: Contracts

For contracts, inspect router and pool events. Use a sandbox, non-production context, or the smallest reversible test available, then classify calls.

In this dimension, event inflation is therefore an explicit audit gap.

The contracts row should end with a concrete monitoring rule tied to router and pool events. Make the operator classify calls, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; event inflation remains a separate production risk until observed.

4. Control test: Internal transfers

For internal transfers, inspect self or treasury movement. Use a sandbox, non-production context, or the smallest reversible test available, then exclude consistently.

In this dimension, false volume is therefore an explicit audit gap.

The internal transfers row should end with a concrete monitoring rule tied to self or treasury movement. Make the operator exclude consistently, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; false volume remains a separate production risk until observed.

5. Control test: Bridges

For bridges, inspect lock, mint and release legs. Use a sandbox, non-production context, or the smallest reversible test available, then link events.

In this dimension, multi-count is therefore an explicit audit gap.

The bridges row should end with a concrete monitoring rule tied to lock, mint and release legs. Make the operator link events, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; multi-count remains a separate production risk until observed.

6. Control test: Addresses

For addresses, inspect wallet, exchange or contract. Use a sandbox, non-production context, or the smallest reversible test available, then retain labels.

In this dimension, user overcount is therefore an explicit audit gap.

The addresses row should end with a concrete monitoring rule tied to wallet, exchange or contract. Make the operator retain labels, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; user overcount remains a separate production risk until observed.

7. Control test: Price basis

For price basis, inspect source and timestamp. Use a sandbox, non-production context, or the smallest reversible test available, then record method.

In this dimension, valuation drift is therefore an explicit audit gap.

The price basis row should end with a concrete monitoring rule tied to source and timestamp. Make the operator record method, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; valuation drift remains a separate production risk until observed.

8. Control test: Chain coverage

For chain coverage, inspect included ledgers. Use a sandbox, non-production context, or the smallest reversible test available, then state omissions.

In this dimension, selection bias is therefore an explicit audit gap.

The chain coverage row should end with a concrete monitoring rule tied to included ledgers. Make the operator state omissions, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; selection bias remains a separate production risk until observed.

9. Control test: Attribution

For attribution, inspect confidence and unknowns. Use a sandbox, non-production context, or the smallest reversible test available, then publish bounds.

In this dimension, false precision is therefore an explicit audit gap.

The attribution row should end with a concrete monitoring rule tied to confidence and unknowns. Make the operator publish bounds, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; false precision remains a separate production risk until observed.

10. Control test: Reproducibility

For reproducibility, inspect query and snapshot. Use a sandbox, non-production context, or the smallest reversible test available, then archive logic.

In this dimension, unverifiable claim is therefore an explicit audit gap.

The reproducibility row should end with a concrete monitoring rule tied to query and snapshot. Make the operator archive logic, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; unverifiable claim remains a separate production risk until observed.

Decision scenarios

Scenario 1: when unit becomes decisive

Consider a reader whose main constraint is transaction, transfer or address. The correct response is not to infer a universal platform or product winner. It is to declare unit, retain the evidence, and define a stop condition before funds or permissions are committed. If the evidence changes, the decision must be reopened. This produces a repeatable operating rule rather than a one-time opinion.

Scenario 2: when aggregation becomes decisive

Consider a reader whose main constraint is raw or economic grouping. It is to document rule, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 3: when contracts becomes decisive

Consider a reader whose main constraint is router and pool events. It is to classify calls, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 4: when internal transfers becomes decisive

Consider a reader whose main constraint is self or treasury movement. It is to exclude consistently, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 5: when bridges becomes decisive

Consider a reader whose main constraint is lock, mint and release legs. It is to link events, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 6: when addresses becomes decisive

Consider a reader whose main constraint is wallet, exchange or contract. It is to retain labels, retain the evidence, and define a stop condition before funds or permissions are committed.

Sources and editorial method

• Working Paper 1377 — Bank for International Settlements
• Working Paper 1377 PDF — Bank for International Settlements
• Annual Economic Report 2026 — Bank for International Settlements