Chain profile
Permissioned
Kinexys by J.P. Morgan.
Abstract. JPMorgan Chase Bank, N.A. (formerly Onyx Digital Assets · renamed Kinexys November 2024)
Facts
Chain identity at a glance.
- Type
L1
- Native settlement
- JPM Coin (USD deposit token · sometimes branded JPMD) · JPM Coin EUR (VERIFY current product naming) · Tokenized collateral · tokenized MMF shares (BlackRock BUIDL has been a Kinexys participant in tri-party collateral pilots — VERIFY residency vs. off-ledger settlement)
- Account model
- Account-based · Kinexys party-id bound 1:1 to JPM commercial DDA · token is ledger representation of bank deposit liability (cf. Cari DDA pattern but single-operator rather than consortium)
Important — verify before relying
Show our work.
This profile carries inline VERIFY markers on
every field whose value depends on the model's recollection
rather than independent primary-source confirmation.
Renderers and compliance officers MUST verify each claim
against the operator's primary documentation before any
client-facing reliance.
Full discipline header — including sources,
architectural-distinctness narrative, and per-field VERIFY
inventory — at compliance/registries/chains/kinexys.ts.
Vendor stack · L5 → L1
The 5-layer Stable Stack.
Each row is one named vendor slot from the chain's vendorStack. Solid markers are code-enforced
(the chain blocks or signs); dashed markers are
policy-enforced (the chain flags, humans or systems act on
the signal).
L5 → L1 — application down to network
L5 · Application
client-portal
JPM Access portal · JPM Treasury Services onboarding (KYB · CIP · BO disclosure under 12 C.F.R. § 21.21 + 31 C.F.R. § 1010.230 — single-operator bank-grade onboarding)
C1C8 ◇ policy-enforced
treasury-system
JPM general ledger + JPM Treasury Services statement surface (canonical record · OCC examination-cycle reporting)
C8C9C11 ◇ policy-enforced
compliance-pipeline
JPM internal compliance pipeline (NICE Actimize · proprietary) · BSA/AML · OFAC SDN · structuring · velocity (single-bank screening, Travel Rule internal to JPM)
C2C3 ◇ policy-enforced
L4 · Account
account
Kinexys party-id (1:1 with JPM commercial DDA · token is ledger representation of bank deposit liability · NOT a stablecoin · NOT a separate FDIC instrument)
C1C9 ◆ code-enforced
custody
JPMorgan Chase Bank, N.A. — the deposit itself remains on JPM's balance sheet; the token is a memo entry against the underlying DDA
C1 ◇ policy-enforced
L3 · Execution
smart-contract
Kinexys settlement contract (atomic intra-JPM transfer · programmable-payment patterns: time-lock · oracle-conditional · multi-sig · chained-release; NOT EVM-canonical per public statements)
C13C16 ◆ code-enforced
transfer-restriction
Per-counterparty policy contracts (Kinexys participant allowlist · all parties are JPM clients · counterparty risk pre-cleared at client onboarding)
C1C16 ◆ code-enforced
L2 · Consensus
consensus
JPM-operated validator nodes (BFT consensus)
C10 ◆ code-enforced
L1 · Network
network
JPM-operated permissioned ledger transport · no public mempool · no external observer · permissioned, NOT publicly auditable
◆ code-enforced
Fig. 1 —
Vendor slot per layer; solid border = code-enforced, dashed
border = policy-enforced.
Bridges supported
Cross-chain transport surface.
- Kinexys Digital Payments cross-border corridors (JPM-internal multi-currency settlement · NOT a canonical cross-chain bridge to public L1s)
- Public-chain JPM Coin extension (November 2025 milestone · architecture VERIFY — wrapped vs. native vs. bridge mechanism not independently confirmed)
Related paths
Paths that route through Kinexys by J.P. Morgan.
Compliance paths whose settlementChains
include kinexys or whose steps execute
on this chain.
Source
Where the truth lives.
compliance/registries/chains/kinexys.ts —
full discipline header, sources, and per-field VERIFY
inventory live in the chain-profile source file. See the path resolver to see
this chain in a resolved compliance journey.
Explore the architecture
Pick a thread.