Permissioned DeFi: what changes when the pool checks who you are

A general counsel who has cleared a treasury desk to hold tokenised Treasuries will not necessarily clear it to lend USDC into a public pool alongside anonymous wallets. The desk still wants the yield, the settlement speed and the composability that public DeFi offers over a bilateral credit line. Between the two sits a set of designs that add an admission check to a public protocol, or a compliance layer to the token itself, without rebuilding a bank. Each resolves the tension differently, and the differences matter more than the shared label.

Four designs, one set of questions

Ask the same four questions of every permissioned DeFi pitch: who admits a participant, and on what evidence; what happens to composability once the check is added; where the liquidity actually comes from; and who can freeze or reverse a position after the fact. The answers sort into four distinct architectures, not one spectrum.

Allow-listed pools and vaults

The simplest design leaves the base protocol untouched and adds an access-control layer to a specific market or vault. Morpho's Vaults V2 architecture gives a curator four separate gates, governing who may receive vault shares, send them, receive the underlying assets or deposit them. Per Morpho's own documentation the gates are optional, and if none is set the operation is unrestricted; gate changes run through the vault's timelock, which is configurable and can be set as long as about three weeks, so depositors get a warning window before the rules shift. A curator can also abdicate the gate permanently in either direction: to zero, locking that operation open forever, or to a specific gate contract, locking those rules beyond the curator's own reach, which only becomes a real guarantee if the gate contract is itself immutable. The vault is generic; the permissioning is an add-on the curator chooses. The first live Vaults V2 deployment, the Keyrock USDC vault, went live on 8 October 2025.

Maple Finance built the older version of the same idea: third-party pool delegates underwrote borrowers and vouched for a pool, and lenders joined on the delegate's word. Maple has since moved the underwriting in-house, launching its own lending arm, Maple Direct, in 2023, and its institutional lending pools are permissioned at the lender level too, with KYC'd wallets added to a global allowlist. The admission check is a diligence process run by a named firm, not a cryptographic proof, which is the distinction that mattered in December 2022.

Token-level transfer restrictions and identity credentials

A second design puts the compliance logic inside the asset rather than the pool. ERC-3643, also called T-REX, was created on 9 July 2021 and now carries Final status as an Ethereum standard. It attaches an on-chain identity registry, linking a wallet address to an identity contract and a country code, and a separate compliance contract holding the rules of the offering. Its owner and appointed agents can freeze a whole wallet, freeze part of a balance, or execute a forced transfer that bypasses the usual compliance checks to recover tokens. Because every transfer carries a compliance check, the token is ERC-20-compatible in form but not in practice: generic DEXs and lending markets built for open ERC-20s cannot route it without their own identity layer, so liquidity stays inside venues that have built for the standard.

Others split the check differently. Flux Finance, a Compound v2 fork built by Ondo Finance and since sold to the Ondo Foundation, runs as an on-chain Treasury repo marketplace in which Ondo's OUSG is the collateral asset and stablecoins are lent against it. Backed Finance's bIB01, which tracks a short-dated US Treasury bond ETF, takes the opposite split: qualified investors mint and redeem against the underlying shares, but the issued token is designed to be freely transferable between wallets without a platform-level restriction on each trade. Identity is also increasingly separable from any one token. Quadrata issues a non-transferable passport NFT carrying KYC and jurisdiction status that a contract can query, and Coinbase announced its onchain Verifications on 9 November 2023, built on the Ethereum Attestation Service, letting a self-custodial wallet carry an attestation that it belongs to a verified Coinbase trading account, with country of residence as an optional second attestation. Both put the credential on the wallet rather than the asset, which is the inverse of the ERC-3643 approach.

Segregated permissioned markets on public chains

A third design keeps the pool open on one side and restricts the other. Aave Horizon, first announced in March 2025 and launched in August 2025, is a separate Aave market running alongside Aave's ordinary public ones. Any user can supply stablecoins to it to earn yield, which is where the depth comes from, but only wallets allowlisted by an issuer can hold the tokenised securities and real-world assets used as collateral. Aave does not perform that check: issuers onboard investors, manage the allowlists and set the eligibility requirements, after their own subscription and KYC process. Reported launch partners included Ethena, OpenEden, Securitize, VanEck, Hamilton Lane and WisdomTree, with initial collateral including Superstate's short-duration Treasury and crypto carry funds, Circle's yield fund and Centrifuge's tokenised Janus Henderson products, and three stablecoins on the borrow side: USDC, RLUSD and Aave's own GHO. Aave's own page puts deposits at over $440m and describes Horizon as the largest and fastest-growing real-world asset market onchain, which is the protocol's characterisation of its own market rather than an independently audited ranking.

Permissioned deployments of the same contracts

The fourth design forks the whole market rather than gating a piece of it. Aave Arc, launched on 5 January 2022, was a wholly separate, permissioned instance of the Aave protocol with a whitelister role bolted on; Fireblocks approved the first 30 licensed financial institutions to participate, and set the standard that any later whitelister approved by Aave governance would have to meet or exceed. Aave co-founder Stani Kulechov has since said Aave paused Arc after FTX's 2022 collapse, when, in his words, institutions were "less eager", and has described the market Aave launched in its place as "Arc 2.0". The same deployment pattern carried the Monetary Authority of Singapore's first live Project Guardian industry pilot, announced on 2 November 2022: DBS, J.P. Morgan and SBI Digital Asset Holdings executed foreign-exchange and government bond transactions against liquidity pools on Polygon's mainnet, built on Uniswap and a modified deployment of Aave Arc, including a live cross-currency transaction in tokenised JPY and SGD deposits. Eligibility was enforced not by one central whitelister but by trust anchors, with financial institutions issuing verifiable credentials to traders so that counterparties were known.

Where these designs have actually failed

The clearest permissioned-pool failure had nothing to do with a smart contract. On 5 December 2022, Maple Finance severed ties with Orthogonal Trading, alleging it had misrepresented its financial position and had been operating while effectively insolvent without disclosing that it could not service its debt. Orthogonal held two roles in the same protocol at once: borrower in pools managed by M11 Credit, a Maven 11 Capital subsidiary, and itself the delegate managing a separate USDC credit pool, from which Maple terminated it. M11 Credit issued a default notice on $31m of USDC loans, roughly 80% of that pool's $38.5m of active loans, with a further $5m of wrapped ether loans from another M11 Credit pool, about $36m in total. No on-chain check caught it, and the pool's only remedy afterwards was legal recovery, the same remedy a bilateral lender would have had. Whitelisting and delegate underwriting establish who is admitted; they do not establish that the admitted party is telling the truth.

The freezing question has a cleaner and more uncomfortable answer. On 8 August 2022, Circle froze over 75,000 USDC linked to the 44 Tornado Cash addresses that the US Treasury's Office of Foreign Assets Control had added to its sanctions list, acting at the level of the Ethereum smart contract. That freeze sat entirely outside the four permissioning designs above: it happened at the stablecoin, applied to permissioned and permissionless pools alike, and needed no protocol-level whitelist to work. An institution asking who can freeze its position has to answer separately for the pool, the collateral token and the stablecoin leg, because each layer can have a different answer.

The regulatory reading, with status

Two 2023 reports set the frame regulators are still working from. The Financial Stability Board's report of 16 February 2023 concluded that DeFi "does not differ substantially from traditional finance in the functions it performs or the vulnerabilities to which it is exposed", and noted that these arrangements replicate traditional functions in a supposedly decentralised manner, though the actual level of decentralisation varies widely. It was delivered to that month's G20 Finance Ministers and Central Bank Governors meeting: a report informing policy, not a binding rule. IOSCO's final report, published on 19 December 2023, set out nine policy recommendations across six areas: understanding DeFi arrangements and structures, achieving common standards of regulatory outcomes, identifying and managing key risks, clear and comprehensive disclosure, enforcement of applicable laws, and cross-border cooperation. They are recommendations intended to bring member jurisdictions closer together, not themselves law anywhere.

In the EU, MiCA's recital 22 provides that where crypto-asset services are provided in a fully decentralised manner without any intermediary, they should not fall within the regulation's scope, and that text is in force. Whether a given permissioned design still qualifies is the live question. The European Commission opened a targeted consultation under MiCA Articles 140 and 142 on 20 May 2026, with a deadline of 31 August 2026, testing indicators including an identifiable intermediary, control by an identifiable person over protocol functionality, concentration of governance power, custody or control of user assets, closed-source code and marketing by an identifiable entity, and asking whether responsibility should attach to persons exercising influence over a protocol or to the regulated intermediaries providing access to it. The consultation has closed as this is written, but no amendment has been proposed and recital 22 is unchanged, so the honest status is consulted on, not decided. Several of the designs above, an issuer-controlled allowlist, an owner able to freeze wallets, a curator who can set or abdicate a gate, sit close to the indicators the Commission is testing.

Singapore has stayed in pilot and standard-setting mode rather than moving to binding DeFi rules. Project Guardian's fixed income workstream, convened by ICMA, published a delivery-versus-payment settlement guide and a report on custody arrangements for DLT-based debt securities on 12 November 2025, released at the Singapore FinTech Festival as an addendum to the Guardian Fixed Income Framework first published in November 2024. These are industry deliverables produced with regulators, market infrastructures and financial institutions, not regulation.

What to ask before joining one

None of this is tax, legal, accounting or investment advice, and a design that suits one institution's mandate will not suit another's. The questions below are for a mandate holder's own counsel to work through.

• Who performs the admission check, on what evidence, and does anyone audit it after the fact, given that a whitelist alone did not catch Orthogonal?
• Does the compliance check sit at the pool, the vault, the collateral token or the settlement stablecoin, and could any one of those layers freeze or reverse a position without the others agreeing?
• Where does the counterparty liquidity actually originate: an open supply side, as in Aave Horizon, or a closed pool of admitted lenders, as in an Arc-style deployment or a Maple pool?
• If the design uses gates, an allowlist or a whitelister role, who can change or abdicate that control, on what notice, and is the change timelocked?
• Is the deployment current, or was it paused, discontinued or superseded, as Arc was before Horizon took its place?
• Under which jurisdiction's status does the design sit, and is that status in force, adopted but not yet applying, still in consultation, or only a statement of intent?

The credit and liquidation mechanics inside these pools follow the same logic as the fully public markets: see where DeFi lending yield actually comes from for how loss is contained differently across pooled, isolated and curated-vault designs. The infrastructure questions, oracles, bridges, signing keys, governance thresholds, apply whether or not a whitelist sits in front of the pool: see the DeFi security threat model built for institutions. And because a permissioned design still routes through an intermediary of some kind, whoever runs the allowlist, issues the token or holds the whitelister role, the questions in who actually controls institutional access onchain apply here too, alongside the identity-without-disclosure trade-offs covered in blockchain privacy for regulated finance.

"Institutional DeFi: The Use Cases Worth the Risk", on the Hecto Main Stage at Proof of Talk on 2 June 2026, covered this terrain from the desk's side: Maja Vujinovic, Dax Hansen and Stéphanie Cabossioras discussed where institutional DeFi use cases justify the operational risk, in a session moderated by Hadley Stern.