depositintent.com & .eth — Deposit Intent Identity

A tokenized deposit is a bank’s liability represented as a token on a programmable ledger — carrying the same deposit insurance protections, the same AML/KYC controls, the same balance sheet treatment as the underlying deposit it represents. What makes it fundamentally different from a conventional deposit is not what it is, but what it can do: it can execute. A tokenized deposit can be programmed to release against conditions, to transfer atomically when an asset leg confirms, to move automatically when a smart contract triggers, to settle a securities trade at machine speed without a human pressing a button at each step.

This programmability is precisely what makes the intent layer critical. When a human makes a wire transfer, the intent is explicit: the human chose to initiate the transfer, authenticated their identity, and approved the specific amount and destination. When an AI agent releases a tokenized deposit as the cash leg of a DVP transaction, none of these explicit human authorization steps occur at the moment of execution. The agent acts on a mandate established in advance — and the mandate is the authorization. If the mandate is not properly structured, cryptographically bound, and verifiable by the settlement infrastructure that receives the deposit release instruction, the entire AML/KYC framework that makes tokenized deposits institutionally superior to stablecoins is undermined.

The IMF’s three-layer framework places intent formation and orchestration at Layer 1 precisely because this is where the regulatory and fiduciary foundation of agentic settlement must be established. The FDIC’s April 2026 definition confirms that tokenized deposits are subject to full AML controls throughout their lifecycle — not just at issuance, but at every transfer, every release, every atomic settlement execution.  depositintent.com  and  depositintent.eth  anchor the namespace for the intent and mandate formation layer that makes this lifecycle AML compliance operational at machine speed — the institutional identity for the authorization infrastructure that precedes every agentic tokenized deposit execution.

The IMF Three-Layer Framework — Intent as Layer 1 for Deposit Settlement

The IMF’s framework for agentic payment systems separates intent formation and orchestration (Layer 1), authorization and control (Layer 2), and settlement execution (Layer 3) — with the explicit argument that keeping uncertain, probabilistic AI decision making separate from deterministic payment execution is the central design principle for safe agentic finance. For tokenized deposits specifically, this separation has direct regulatory implications.

Layer 1 intent formation for a tokenized deposit release must specify: which deposit token, from which bank’s issuance, in what amount, to which counterparty, under what conditions, within what mandate boundaries. This structured intent is not merely a payment instruction — it is the foundation of the AML authorization chain that the FDIC requires to be maintained throughout the tokenized deposit lifecycle. An intent that cannot be traced to a specific mandate, verified against AML policy constraints, and documented in an audit trail is not eligible for Layer 2 authorization. A deposit token that executes without a verifiable intent record violates the BSA/AML framework that gives tokenized deposits their regulatory advantage over stablecoins.

 depositintent  is the namespace for this Layer 1 function — the institutional identity for the mandate formation and AML authorization infrastructure that makes agentic tokenized deposit settlement regulatory-compliant at machine speed.

UK GBTD, Canton Network and the Production Intent Standard

The UK’s GBTD project — with Barclays, HSBC, Lloyds, NatWest, Nationwide, and Santander conducting live transactions — establishes the production standard for tokenized deposit authorization. Quant’s PayScript engine underpins the programmable payment conditions, embedding intent and authorization logic directly into the tokenized deposit release mechanism. When Lloyds used tokenized sterling deposits to purchase a tokenized gilt from Archax, the authorization chain — which bank, which deposit, which conditions, which counterparty — was encoded in the payment conditions that PayScript enforced before the atomic DVP executed.

This is the production implementation of what  depositintent  captures as a namespace: the authorization logic layer that governs when and how a tokenized deposit can be released as the cash leg of a DVP transaction. JPMorgan’s Kinexys processes $2 billion daily through similar authorization frameworks — every deposit token release governed by mandate parameters that define scope, counterparty eligibility, and settlement conditions.  depositintent.eth  is the on-chain resolution address for these mandate parameters — the ENS anchor where authorization scope, AML clearance, and intent records are stored as cryptographically verifiable on-chain entries.

depositintent in the Complete Deposit Infrastructure Stack

depositintent  is the mandate formation layer of the PillarsX Deposit namespace — the intent infrastructure that precedes and enables every tokenized deposit settlement function. It connects directly to  atomicdeposit.com/.eth  as the atomic execution layer that receives authorized deposit release intents,  depositsettle.com/.eth  as the settlement execution layer,  depositinterop.com/.eth  as the cross-platform interoperability layer that routes deposit intents across different bank systems, and  verifiableintent.com/.eth  as the broader verifiable intent standard of which deposit intent is a specific application.

Beyond the Deposit cluster,  depositintent  integrates with  dvpintent.com/.eth  as the DVP-specific intent layer that coordinates with deposit intent for complete atomic settlement,  pvpintent.com/.eth  as the PvP intent layer for currency conversion in cross-border deposit settlement, and  amlintent.com/.eth  as the AML-specific mandate layer that deposit intent must satisfy before execution. Together these namespaces form the complete institutional deposit intent infrastructure — from AML mandate formation through authorization to atomic cash leg execution — covering every layer of the intent architecture that IMF, FDIC, and GENIUS Act require for compliant agentic tokenized deposit settlement.

Strategic Constellations & Bundle Potential

Bundle 1 — Deposit Intent Core
depositintent + atomicdeposit + depositsettle — the complete deposit intent and execution namespace from mandate formation through atomic cash leg to settlement. Targets: UK GBTD participants, HKMA EnsembleTX banks, JPMorgan Kinexys — institutions building agentic tokenized deposit DVP infrastructure.

Bundle 2 — Agentic Deposit Stack
depositintent + depositinterop + atomicdeposit — the complete agentic deposit namespace from intent formation through cross-platform interoperability to atomic execution. Targets: Quant/Overledger, Canton Network participants, institutions building mandate-governed agentic tokenized deposit settlement.

Bundle 3 — Complete DVP Cash Leg Architecture
depositintent + dvpintent + atomicdeposit + dvpatomic + depositsettle — the complete DVP cash leg and asset leg intent namespace. Targets: DTCC, Euroclear, Fnality — institutions building complete agentic atomic DVP settlement infrastructure with tokenized deposit cash legs.

Disclaimer:
PillarsX is a domain portfolio business. Nothing on this page constitutes legal, financial, or regulatory advice. Domain names do not confer regulatory status, licensing, or compliance certification of any kind. All content is for informational purposes only and does not constitute financial advice.