Chain profile
Permissioned
Regulated Liability Network (Citi-led, SETL-stack).
Abstract. Citi-led consortium · SETL (Marqeta-owned) provides underlying ledger technology
Facts
Chain identity at a glance.
- Type
L1
- Native settlement
- Commercial bank money (member-bank deposit liabilities) · Central bank money (Fed reserve-account leg, VERIFY) · Regulated non-bank digital money (regulated stablecoin issuer liabilities, VERIFY)
- Account model
- Multi-class liability tokens (each token cryptographically tagged to its liability class — commercial-bank-money tokens distinct from central-bank-money tokens at the protocol level)
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/rln.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
consortium-app
RLN multi-liability settlement application (Citi · HSBC · Mastercard · BNY Mellon · TD · US Bank · Truist · Wells Fargo)
C1C8C9C13 ◇ policy-enforced
central-bank-leg
Federal Reserve Bank of New York (PoC observer 2022–2023)
C9C10 ◇ policy-enforced
L4 · Account
account
Multi-class liability tokens (commercial-bank deposit · central-bank reserve · regulated non-bank digital money — three asset classes on one ledger)
C1C9 ◆ code-enforced
validator-node
Per-member validator node (Citi · HSBC · BNY · etc. each operate validating infrastructure)
C1C8 ◇ policy-enforced
custody
Member-bank treasury custody (commercial-bank money) · Federal Reserve master account (central-bank money leg)
C1 ◇ policy-enforced
L3 · Execution
smart-contract
RLN settlement contracts (atomic multi-liability swap · liability-class-aware transfer rules · sovereign-leg authorization)
C13C16 ◆ code-enforced
ledger-engine
SETL ledger engine (Marqeta-owned post-2023 acquisition)
C10C13 ◆ code-enforced
L2 · Consensus
consensus
Member-validator consensus (likely BFT variant given regulated-bank participation)
C10 ◆ code-enforced
L1 · Network
network
RLN private network (consortium-operated · NOT public chain)
◆ code-enforced
Fig. 1 —
Vendor slot per layer; solid border = code-enforced, dashed
border = policy-enforced.
Bridges supported
Cross-chain transport surface.
- Internal multi-liability swap (commercial bank money ↔ central bank money ↔ regulated non-bank digital money — atomic on RLN ledger)
Related paths
Paths that route through Regulated Liability Network (Citi-led, SETL-stack).
Compliance paths whose settlementChains
include rln or whose steps execute
on this chain.
Source
Where the truth lives.
compliance/registries/chains/rln.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.