# Banks and custodians: Stablecoin exposure, traceable to the block

> Monitor the stablecoins you hold, accept or issue, by issuer and chain, with lineage your risk and model-validation teams can trace to the block.

Markdown copy of https://voltfincrypto.com/use-cases/banks-custodians

Monitor the coins you hold, accept or issue by issuer, chain and currency, with lineage your risk, finance and model-validation teams can trace from the report to the block.

Live example: [Stablecoin supply across chains: by issuer, chain and peg](https://voltfincrypto.com/stablecoins)

## Data your risk function can sign off.

Prudential rules ask banks to classify each stablecoin and to know their exposure to it. That starts with facts: who issues it, where it is natively issued and how its supply is moving.

Every row in Voltfin keeps its receipt, from the published dataset back to the contract and the block, so an aggregate is traceable rather than asserted.

Boards, tables and dated reports are built in one workspace, on one set of numbers, for treasury, risk and finance alike.

## Workflows

### Exposure monitor

**The problem.** A coin's risk changes with its issuer, its chains and its supply trend. Limits and classifications need all three.

**With Voltfin.** Supply for each coin you hold or accept, by chain, with its 30-day change and bridged copies apart, on a board you can filter and share.

- **One coin, every chain.** Where a coin's native supply sits, and how it is moving.
- **Bridged apart.** Copies minted by bridges, listed on their own.
- **Shareable state.** A link opens the board with the same filters and pages.

Live example: [USDT across chains](https://voltfincrypto.com/stablecoins/usdt)

### Euro e-money tokens

**The problem.** Euro stablecoins are small next to dollar ones, and spread across issuers and chains, so their footprint is easy to miss.

**With Voltfin.** A euro coin's native supply on each chain, with its 30-day change and bridged copies apart, read the same way as dollar coins, for euro settlement and deposit-token planning.

- **Per chain.** Where the coin's euro supply is natively issued.
- **30-day change.** Issuance and redemptions, day by day.
- **Beside USD.** The same reads, so currencies compare like for like.

Live example: [EURCV across chains](https://voltfincrypto.com/stablecoins/eurcv)

### Traceable inputs

**The problem.** Risk data has to be aggregated completely and accurately, and reviewers ask where each input came from.

**With Voltfin.** A table of supply by token, chain and day in which every row opens its receipt and exports with it.

- **Row-level receipts.** Each row names its dataset version, contract and block.
- **Missing is missing.** A value that could not be read shows as missing, never as zero.
- **Versioned datasets.** A figure keeps pointing at the version it came from.

Live example: [Stablecoins by asset, every row with its receipt](https://voltfincrypto.com/tables/stablecoins)

## The rules behind it

Short summaries for orientation, not legal advice.

- **Basel crypto-asset standard** (BCBS): Its implementation date is 1 January 2026. A stablecoin gets the lighter Group 1b treatment only if it passes a redemption risk test and its issuer is supervised. [Source](https://www.bis.org/bcbs/publ/d545.htm)
- **BCBS 239** (BCBS): Principles for aggregating risk data completely, accurately and quickly, with lineage a supervisor can follow. [Source](https://www.bis.org/publ/bcbs239.htm)
- **GENIUS Act** (United States): Lets subsidiaries of insured banks issue payment stablecoins under federal supervision, with one-to-one reserves. [Source](https://www.govinfo.gov/app/details/PLAW-119publ27)

## Next on the plan

- Tokenized treasuries and money-market funds, for collateral
- Custody balances at a past block, for period-end proofs