I. Fundamental technologies
1. Blockchain and distributed ledgers
A blockchain organizes transactions into cryptographically linked blocks replicated across network participants. A distributed ledger need not use a conventional chain of blocks. A transaction typically proceeds through signing, network submission, identity and balance validation, ordering or consensus, state execution, commitment and reconciliation with banking systems.
2. Cryptography
Cryptographic hash functions such as SHA-256 provide tamper-evident commitments; digital signatures such as ECDSA or EdDSA authorize instructions; Merkle trees support efficient transaction-inclusion proofs. These do not alone provide confidentiality, legal ownership, or protection against stolen signing keys. Institutional key custody commonly uses HSMs, MPC, multisignature approvals, segregation of duties, recovery controls and audit logging. Post-quantum readiness requires cryptographic inventory and agility.
3. Consensus and finality
| Mechanism | Characteristics | Financial relevance |
|---|---|---|
| Proof of Work | Computational competition; probabilistic finality | Bitcoin |
| Proof of Stake | Staked validators; protocol-dependent finality | Ethereum |
| PBFT / IBFT / QBFT | Byzantine-fault-tolerant validator voting | Permissioned institutional networks |
| Raft | Crash-fault tolerant, not Byzantine-fault tolerant | Trusted replicated enterprise systems |
| Proof of Authority | Approved validators | Consortium arrangements |
Distinguish ledger finality, operational settlement, legal ownership transfer and discharge of payment obligations. These can occur at different times.
4. Public and permissioned networks
Public networks such as Ethereum generally allow open participation, while permissioned networks restrict admission, validation and visibility. Enterprise architectures may integrate identity, compliance and confidential transaction processing. Permissioning alone does not eliminate governance capture, insider abuse or operational concentration.
5. Smart contracts and tokenization
Smart contracts execute agreed state-transition rules, such as bond issuance, eligibility checks, coupons and redemption. Tokenization represents claims, securities, fund interests, deposits or collateral. The token's legal meaning depends on the underlying contracts, authoritative ownership records and custody arrangements. A tokenized deposit is not automatically equivalent to a stablecoin or CBDC.
II. Financial services use cases
| Use case | Potential benefit | Critical constraint |
|---|---|---|
| Cross-border payments | Extended-hour transfer and visibility | Compliance, FX and interoperability |
| Intraday liquidity | Reduced friction moving eligible funds | Funding and network availability |
| Securities settlement | Shorter settlement cycles | Legal finality, custody and market structure |
| Repo and collateral | Faster pledge, substitution and DvP | Eligibility, lien priority and valuation |
| Tokenized money market funds | Programmable fund ownership records | NAV, redemption and investor protections |
| Trade finance | Shared document provenance and workflow | Off-chain goods and document authenticity |
| FX payment-versus-payment | Coordinated currency settlement | Liquidity and coverage |
| Syndicated lending | Shared multi-party lifecycle | Confidentiality and adoption |
6. Atomic delivery-versus-payment
Atomic DvP links the transfer of a security to the transfer of money: both succeed together or neither completes. Example: a $100 million Treasury security purchase between two eligible institutions. Technical atomicity does not independently guarantee legal finality.
III. JPMorgan Chase case study
7. Quorum, Onyx and Kinexys
JPMorgan's progression includes Quorum (enterprise Ethereum), the original JPM Coin concept (2019), Onyx (2020), Onyx Digital Assets, and the Kinexys brand (2024). JPM Coin (JPMD), developed as an institutional deposit token on selected public networks, should be distinguished technically from the original JPM Coin payments system.
Kinexys by J.P. Morgan supports institutional payments, digital assets and tokenized collateral. JPMorgan reported cumulative platform activity above $4 trillion and average daily transaction value of approximately $7 billion in October 2026; these are company-reported figures requiring verification before public release, not measures of profit or cost savings.
8. Deposit tokens and treasury liquidity
JPMD represents an eligible institutional deposit claim under its terms, not an ordinary retail cryptocurrency. A multinational corporate treasury may seek extended-hour USD liquidity movement among approved participants in New York, London and Singapore. Review redemption, account status, jurisdiction, sanctions screening, key control and ledger reconciliation.
9. Digital Assets and Fund Flow
Tokenized collateral workflows may improve movement of eligible securities or fund interests while underlying assets remain subject to custody and legal arrangements. Kinexys Fund Flow (2026) targets fund investor-register and transaction coordination; a reported initial transaction involved J.P. Morgan Private Bank, J.P. Morgan Asset Management and Citco.
Institutional client → bank identity and compliance → authorized deposit-token or asset service → ledger validators → bank books, custody and settlement reconciliation. Trust boundaries include signing keys, compliance gateways, validators, oracles and legacy bank systems.
IV. New York institutional landscape
| Organization | Platform | Use cases |
|---|---|---|
| JPMorgan Chase | Kinexys, JPM Coin, Fund Flow | Deposits, payments, collateral, funds |
| Goldman Sachs | GS DAP | Digital securities, issuance, fund infrastructure |
| Citi | Citi Token Services | Liquidity, cross-border payments, trade |
| BNY | Digital assets, LiquidityDirect collaborations | Fund records, custody and servicing |
| BlackRock | BUIDL | Tokenized institutional liquidity fund |
| Broadridge | DLR / DLX | Repo, collateral, asset lifecycle |
| DTCC | Tokenization Service | Market infrastructure and securities |
| The Clearing House | Bank-led tokenized deposit initiatives | Interbank settlement |
10. Institutional distinctions
Goldman Sachs and BNY: a 2025 tokenized money market fund initiative used mirrored tokenized ownership records with GS DAP and BNY LiquidityDirect; it does not imply wholesale replacement of conventional fund infrastructure. Citi: Citi Token Services for Cash supports eligible extended-hours liquidity transfers through existing banking interfaces, without requiring customers to manage tokens directly. Broadridge: reported September 2026 DLR monthly repo activity of $7.5 trillion and average daily activity of $359 billion, reflecting processing value rather than economic savings. DTCC: July 2026 demonstration transactions with more than 30 participants covered repo, lending, collateral and DvP; distinguish demonstrations from general production availability.
V. Global institutions
| Institution | Region | Applications |
|---|---|---|
| HSBC | UK / Hong Kong / global | Tokenized deposits, liquidity, bonds |
| UBS | Switzerland | UBS Tokenize, funds, notes, repo |
| Société Générale-FORGE | France | Digital bonds, CoinVertible stablecoins |
| DBS | Singapore | Institutional digital assets and settlement |
| BNP Paribas | France / global | Digital securities and custody |
| Franklin Templeton | US / global | Blockchain-recorded fund interests |
| European Investment Bank | EU | Digital bond issuance |
| Swift | Global | Interoperability and payment messaging |
HSBC expanded tokenized deposit services to eligible U.S. customers in 2026. UBS, SBI and DBS have demonstrated cross-border repo involving digitally issued securities and regulated payment instruments. Société Générale-FORGE provides a useful contrast between bank-associated stablecoins and commercial-bank deposit tokens. BlackRock's BUIDL fund, launched in 2024, surpassed $1 billion in reported assets in March 2025.
VI. Security, risk and governance
| Risk | Failure example | Controls |
|---|---|---|
| Key custody | Compromised signing keys | HSM, MPC, dual approval, recovery |
| Consensus | Validator collusion | BFT design, governance and oversight |
| Smart contracts | Reentrancy, access-control defects | Audit, fuzzing, formal verification |
| Identity | Unauthorized privileged actions | MFA, PAM, least privilege |
| Oracles | False external market data | Multiple sources, validation |
| Bridges | Cross-chain message compromise | Independent verification, limits |
| Privacy | Disclosure of positions | Confidentiality, selective disclosure |
| Finality | Technical completion without legal discharge | Enforceable settlement arrangements |
| Custody | Loss of assets or entitlement | Segregation, reconciliation |
| Resilience | Node/network failure | BCP/DR, recovery tests |
| Compliance | Sanctions/KYC failures | Screening and monitoring |
| Third parties | Concentration failure | Due diligence and exit planning |
| Quantum readiness | Future signature weakness | Inventory and crypto agility |
11. Assurance methodology
- Architecture and trust boundaries: inventory validators, keys, contracts, custody, bridges, oracles and core bank systems.
- Cryptographic and identity assurance: signing, HSM/MPC, recovery, privileged access and algorithm inventory.
- Transaction verification: contract invariants, authorization, replay, atomicity and reconciliation.
- Legal and regulatory analysis: ownership, redemption, finality, sanctions, privacy and cross-border rules.
- Resilience and detection: outages, partitions, oracle failure, incident response and DR testing.
- Independent control validation: evidence, operating effectiveness, residual risks and approval.
Useful contract invariants: unauthorized issuance cannot increase supply; transactions cannot spend unowned assets; atomic DvP cannot settle one leg alone; privileged actions require approved signers; emergency powers must respect ownership rights; ledger records must reconcile to authoritative books.
12. Applicable standards
NIST SP 800-53 Rev. 5, NIST CSF 2.0, NIST SP 800-57, FIPS 140-3, ISO/IEC 27001 and 27002, ISO 22301, PCI DSS where applicable, FFIEC guidance, NYDFS 23 NYCRR 500, EU DORA, FATF standards and CPMI-IOSCO PFMI. Applicability depends on legal entity, product and jurisdiction.
VII. Outlook and research priorities
Priority themes for 2026–2030 include interoperable tokenized bank money, tokenized securities infrastructure, confidential institutional networks, programmable compliance, digital identity, CBDC experiments and post-quantum migration. Highest qualitative near-term opportunities: institutional payments and repo/collateral; strong but constrained opportunities: tokenized funds and securities settlement; adoption-sensitive opportunities: trade finance and syndicated lending.
VIII. Proposed technical laboratory
- Use Hyperledger Besu or a local Ethereum development environment.
- Create issuer, buyer and seller identities.
- Issue a simulated tokenized bond and simulated bank deposit token.
- Implement atomic DvP with transfer eligibility controls.
- Mirror authoritative custody and accounting records.
- Test unauthorized signer, replay, stale oracle and validator outage.
- Map evidence to NIST SP 800-53 and ISO/IEC 27002.
- Document architecture, threat model, test results and residual risks.
Research questions
When does a ledger outperform a replicated database? How should technical and legal finality be reconciled? What failures arise at on-chain/off-chain boundaries? Can privacy coexist with regulatory audit? How should validator governance and quantum readiness be assessed?
Primary-source verification queue
- JPMorgan Kinexys
- Goldman Sachs GS DAP
- Citi Token Services
- DTCC Tokenization Hub
- UBS Tokenize
- Broadridge
- NIST CSF
- BIS CPMI