Decentralized finance has spent its first era proving that open, permissionless liquidity works. Jake Claver argues the next era is different: institutional capital will not enter a liquidity pool that has no accountable party standing behind it, and the fix is neither to ban DeFi nor to pretend the risk is not there. It is to regulate the risk layer properly.
Prefer the app?Watch on YouTube
A liquidity pool is not just code
A liquidity pool holds real assets, has real participants, charges real fees, and carries real financial risk: smart-contract risk, liquidity risk, market risk, and counterparty risk. When something goes wrong, someone has to be answerable. A DAO, a public code repository, an anonymous founder, or a front end carrying a use-at-your-own-risk notice does not satisfy a fiduciary. Banks, broker-dealers, insurers, corporate treasuries, retirement plans, and family offices are all governed by duties that make an anonymous counterparty a non-starter.
Classify the pool before it launches
The regulatory home of a pool follows what is actually inside it. A pool holding digital commodities belongs in a commodities framework, which points toward CFTC-registered roles such as a commodity pool operator, a commodity trading advisor, or an introducing broker. A pool holding tokenized securities or investment contracts points toward securities infrastructure instead: a broker-dealer, an alternative trading system, a qualified custodian, and proper disclosure and suitability documentation. The principle is simple. A commodity pool should not pretend it is not a commodity pool, and a securities pool should not pretend it is not a securities pool.
Identity, and the arrival of know your agent
Serious pools will require a digital identity layer rather than an anonymous wallet connection. That means know your customer for individuals, know your business for entities, and a newer category Claver calls know your agent. The reason is that finance is moving toward autonomous software acting on behalf of people and institutions: trading agents, treasury agents, client agents. If capital markets become programmable, the participants are no longer only people, and an agent moving money with unclear authority and no defined risk limits is not something an institution can accept. Permissions have to be defined before an agent ever touches a pool.
Credentialed access rather than open access
The practical result is that pools become gated by credentials attached to an identity rather than open to any wallet. One pool might admit only accredited investors, another only qualified purchasers, another only regulated institutions, and another only agents operating under limited permissions. Different pools carry different risk, so different participants need different credentials. Claver frames this as the shift from open access to trusted access, and argues it is what allows scale rather than what prevents it.
Someone has to underwrite and supervise
A regulated intermediary in the structure should be doing more than lending its name. Underwriting means understanding what is in the pool, how the strategy works, what the liquidity profile looks like under stress, and where the failure points are, including smart-contract exploits, oracle failure, a liquidity crunch, or a governance attack. Oversight means the authority to enforce the rules: to pause a pool in an emergency, block a non-compliant wallet, or remove an agent operating outside its permissions. Claver draws a distinction worth keeping: centralized control and accountable oversight are not the same thing.
The seven-part framework
The video closes on a checklist for designing a pool for this next phase: legal classification decided before launch; the correct regulated intermediaries involved; a responsible party with real authority; digital identity and credentials governing access; transparent risk disclosures; on-chain proof paired with off-chain accountability; and predetermined emergency protocols, because the answers to who can pause a pool and who notifies participants will not become clear during a crisis if they were not clear before one.
Why the XRP Ledger comes up
Claver’s argument for the XRP Ledger is an infrastructure argument rather than a market one. The ledger was built for payments and settlement, has a decentralized exchange at the protocol level, settles quickly at low cost, and has an operating record without network downtime. Newer amendments have added the identity and permissioning primitives this model needs, including credentials and permissioned domains. If the destination is tokenized assets, regulated pools, verified identity, and institutional liquidity, his view is that a neutral settlement asset has to move value between those markets, and that this is the role XRP was designed for. Watch the full breakdown above for the complete argument.
Educational only, not tax, legal, or investment advice. Check primary sources and speak with a qualified professional before making financial decisions.
Part of our guide on tokenizing real-world assets.
Part of our guide: Digital Asset Custody.
