Devancore Inc.

Digital asset firms

Use case

Digital asset operating risk is evidence that cannot explain what happened on-chain.

Wallet attribution, finality evidence, controls, reconciliation, and capital views need to read from one operating record—not separate chain tools and spreadsheets.

Document source: https://devancore.com/use-cases/digital-asset-firms

On this page

Actions

Digital asset firms

Digital asset operating risk is evidence that cannot explain what happened on-chain.

Wallet attribution, finality evidence, controls, reconciliation, and capital views need to read from one operating record—not separate chain tools and spreadsheets.

Digital asset firms can often see movement on-chain. The harder problem is institutional evidence: which entity, account, or strategy the movement belongs to, who approved it, what finality state applies, whether it reconciled, and what record supports downstream reporting.

When wallet context, workflow controls, finality state, and reconciliation results live outside the operating book, every downstream process becomes weaker. Exposure, compliance review, audit trail, capital views, tax support, and investor reporting all depend on reconstructing context after the fact.

Devancore is designed to connect on-chain and off-chain lifecycle activity into one controlled operating model. The platform supports attribution, workflow evidence, finality state, reconciliation outcomes, and reporting inputs; the firm determines applicable policy, treatment, and compliance conclusions.

This material is informational and does not constitute legal, regulatory, custody, investment, AML, accounting, tax, or compliance advice.

Operating model swimlane showing wallet transfer, custody movement, and tokenized instrument flows moving through attribution, workflow, control, and evidence columns, with Devancore capturing, mapping, recording, controlling, and preserving the operating record.

Entity and account mapping

A wallet address is not an institutional identity.

Digital asset firms need a maintained attribution layer that connects wallet addresses to entities, accounts, funds, strategies, counterparties, and control evidence.
  • Address versus identity

    The blockchain gives a durable address. The institution needs a durable identity. A wallet address can represent a fund, custody account, counterparty, strategy, settlement account, omnibus structure, temporary operational wallet, or deprecated address. Without attribution, the firm can see movement but cannot prove the operating context of that movement.

  • Reference data, not spreadsheet notes

    Digital asset operations should treat wallet attribution as reference data maintained inside the operating model, not as ad hoc notes assembled when a reviewer asks.

  • Legibility to institutional workflows

    Wallet attribution is where digital asset firms become legible to traditional institutional workflows. The counterparty record, fund record, account record, and wallet record need to agree. If the wallet sits outside the operating book, reconciliation, exposure, compliance review, audit trail, capital views, tax support, and investor reporting all become weaker.

  • Compliance record support

    Devancore supports the operating record AML and compliance teams need: attribution, screening results where integrated, review workflow, exception state, and evidence preservation. Compliance determination remains with the firm.

Attribution objects the operating record should preserve

Attribution object Why it matters
Legal entity Connects address to counterparty, issuer, custodian, adviser, or fund
Account or fund Connects movement to books, reporting, investor, or strategy context
Wallet status Active, deprecated, pending verification, blocked, review required
Verification evidence Source, method, date, reviewer, renewal or recertification state
Address type Operational wallet, custody wallet, settlement address, issuer address
Risk context Configured screening, policy, or monitoring state

Evidence stack showing wallet attribution progressing from address capture through entity mapping, verification evidence, wallet status, screening outcome, and operating record preservation.

Decision fork asking whether a wallet is mapped to entity, account, and verification evidence, with attributed movement supporting downstream workflows and unattributed movement leaving chain activity visible but unexplained.

Rail state and position integrity

On-chain visibility is not the same as operational finality.

Digital asset firms need explicit finality states, confirmation evidence, and reconciliation results before position, cash, exposure, and reporting views can be trusted.
  • Instant settlement language is too loose

    Digital asset markets often speak as if settlement is instant. Operationally, that language is too loose. A transaction may be created, signed, submitted, visible, included, confirmed under a firm policy, reversed by an operational correction, matched to an internal record, reconciled to a custodian or wallet source, and then used in position, exposure, accounting, or reporting views. Those states are not the same.

  • Finality preserves evidence, not legal conclusions

    A finality model does not decide legal finality by itself. It preserves the evidence that the firm, its counsel, its service providers, and its control framework can use.

  • Reconciliation spans more than the chain

    For a digital asset firm, reconciliation may involve wallet balances, chain events, custody APIs, transfer-agent records, issuer records, administrator records, internal ledgers, and bank or stablecoin cash movements. A chain event is evidence, but it still needs to be mapped to the internal instruction and position record.

  • One reconciliation model

    Devancore helps prevent digital rail activity from becoming a separate reconciliation world. The practical claim is continuity: on-chain evidence should update the same operating record that supports traditional post-trade workflows.

Operating states on the digital rail

State Operating meaning
Instruction created Firm intends to move or receive value
Submitted or broadcast Instruction has left the internal workflow
Visible on rail External source shows an event or pending state
Confirmation policy satisfied Firm-specific threshold or evidence condition has been met
Operational finality evidence recorded Event can support downstream position or cash state
Reconciled Internal record matches external source or exception is opened
Reportable Record is ready for the relevant reporting or review workflow

Linear pipeline showing digital rail activity progressing from instruction created through submitted, visible on rail, confirmation policy satisfied, finality recorded, reconciled, and reportable states.

Capital, liquidity, and exposure

Capital and risk views need current positions, current attribution, and current finality state.

Digital asset firms need operating views for exposure, liquidity, concentration, funding, collateral, and capital support that read from the same controlled record as operations.
  • Durable claim over fragile treatment detail

    Specific stablecoin or digital asset treatment claims are fragile. Regulatory treatment changes, firm type matters, and the same wording may be wrong for a broker-dealer, adviser, fund, proprietary trading firm, payment firm, or non-US entity. The stronger claim is that capital and risk views need to read from the same controlled operating record as operations.

  • Support both regulated and non-regulated contexts

    For registered broker-dealers, digital asset positions may feed capital, customer protection, books-and-records, and reporting workflows. For non-broker-dealer digital asset firms, the relevant standard may come from investor diligence, risk committee policy, fund documents, service-provider requirements, internal capital policy, or jurisdictional regulation. Devancore can support both without overclaiming either.

  • One record for operations and risk

    Devancore can support capital, liquidity, exposure, and risk views by giving the firm a current record with position state, wallet attribution, valuation inputs, finality evidence, exception status, and review history. The firm determines the applicable treatment.

  • Better than exports and snapshots

    The same record that helps prove a transfer was approved and final should also support exposure, capital, liquidity, and reporting views. That is more durable than running digital asset risk from portfolio exports and wallet snapshots.

Views and the inputs they require

View Required inputs
Exposure Positions, prices, counterparty, wallet, account, strategy, venue
Liquidity Asset type, settlement status, wallet state, transferability, redemption terms
Concentration Issuer, protocol, counterparty, custodian, chain, fund, strategy
Funding and collateral Cash leg, collateral movements, pledges, encumbrances, settlement evidence
Capital support Classification, valuation, firm treatment, exception state, review evidence
Management reporting Current state, unresolved exceptions, source evidence, trend

Risk register showing exposure drift, liquidity misread, concentration blind spots, and capital support gaps when attribution or finality state is stale, with controls tied to one operating record.

Digital rail outward

Digital asset firms still need one operating model across on-chain and off-chain activity.

The digital rail may be the starting point, but institutional operations still touch banks, custodians, administrators, issuers, brokers, service providers, and reporting systems.
  • Hybrid by operation, not by exception

    Digital asset firms are often described as on-chain businesses. Operationally, they are hybrid businesses. They may hold tokenized instruments, stable-value instruments, native digital assets, fiat cash, fund interests, traditional securities exposure, bank accounts, custody relationships, administrator records, tax records, investor reporting obligations, and counterparty agreements.

  • Off-chain evidence still matters

    Even a firm whose core activity is digital needs off-chain evidence and service-provider connectivity. Settlement, position, cash, controls, and reporting each produce different evidence depending on whether the activity originated on-chain or off-chain.

  • Same framework, different entry point

    Digital firms should not accept a weaker operating model because the rail is new. On-chain activity should enter the same institutional control framework that traditional post-trade activity uses. Broker-dealers enter through regulatory safety. Asset managers enter through IBOR, ABOR, tax, and portfolio operations. Digital asset firms enter through institutional evidence for on-chain activity.

  • One event record across rails

    The framework is the same: one event record, one finality model, one position view, one control framework, one reporting base.

Operating surfaces across rails

Operating surface On-chain evidence Off-chain evidence
Settlement Transaction hash, block, contract event, wallet movement Instruction, approval, custodian or service-provider record
Position Token balance, wallet source, issuer record Internal book, administrator record, valuation source
Cash Stable-value movement, wallet balance Bank statement, fund record, subscription or redemption record
Controls Policy gate, wallet rule, smart-contract condition Maker-checker, RBAC, exception case, review evidence
Reporting Ledger evidence, attribution, finality state Investor, management, regulatory, audit, or diligence package

Branching flow showing lifecycle events producing on-chain and off-chain evidence paths that converge through control state into one operating record for position, finality, and attribution.

Related references

Platform modules

  • System of Record

    https://devancore.com/platform/system-of-record

    Authoritative operating record for on-chain and off-chain lifecycle events.

  • Trade Lifecycle & Operations

    https://devancore.com/platform/trade-lifecycle

    Workflow layer for instruction, settlement, exception handling, repair, and evidence.

  • Finance & Reporting

    https://devancore.com/platform/finance-reporting

    Capital, exposure, reconciliation, reporting, and finance evidence.

  • Controls & Compliance

    https://devancore.com/platform/controls

    Maker-checker, RBAC, audit trail, wallet-review workflow, and supervisory evidence.

  • Connectivity

    https://devancore.com/platform/connectivity

    Integration with OMS, custodians, wallets, banks, APIs, ISO 20022, and rail data.

How it works

  • Architecture

    https://devancore.com/how-it-works/architecture

    Lifecycle record and unified position model behind digital and traditional activity.

  • Settlement & Finality

    https://devancore.com/how-it-works/finality

    Workflow status and finality evidence across traditional and digital settlement rails.

  • Security & Controls

    https://devancore.com/how-it-works/security

    Maker-checker, role-scoped access, audit trail, and evidence preservation.

Resources and use cases

  • Hybrid Settlement Thesis

    https://devancore.com/resources/hybrid-settlement-thesis

    Strategic thesis for one post-trade operating system across traditional and digital rails.

  • Regulatory Reference

    https://devancore.com/resources/regulatory-reference

    Operating map for regulatory obligations where digital activity touches regulated workflows.

  • Broker-Dealers

    https://devancore.com/use-cases/broker-dealers

    Broker-dealer view of settlement, capital, customer protection, records, and supervision.

  • Asset Managers

    https://devancore.com/use-cases/asset-managers

    Asset-manager view of IBOR, ABOR, tax, portfolio capital, and global compliance evidence.

Glossary anchors

Contact

Request a briefing or platform walkthrough with the Devancore team.

Request access https://devancore.com/access