If Institutions Build Permissioned DeFi, What Happens to Uniswap and Aave?

General
1

The RWA discussion got me thinking about something that keeps me up at night: if institutions are building permissioned versions of DeFi protocols, what happens to Uniswap and Aave?

We’re seeing it already:

  • Horizon = permissioned fork of Aave for institutional RWAs
  • Robinhood Chain = institutional L2 with KYC requirements
  • Tokenized treasury platforms = compliant-only liquidity pools

And surveys show 11% of institutions already hold tokenized assets, with 61% planning to invest soon.

That’s massive capital waiting to flow into… permissioned walled gardens.

The Uncomfortable Scenario

Let me paint a picture of 2030:

Permissioned “Institutional DeFi”:

  • $2-4 trillion TVL in tokenized RWAs
  • Serving regulated institutions with KYC/AML
  • Forked versions of Aave, Uniswap, Curve with compliance layers
  • Best developers working here (highest salaries from institutional clients)
  • Most VC funding and regulatory legitimacy

Permissionless Public DeFi:

  • ~$100-200 billion TVL
  • Serving crypto-natives who value censorship resistance
  • Original protocols (Uniswap, Aave, Curve)
  • Smaller developer community, less funding
  • Regulatory scrutiny and compliance pressure

Question: If permissioned “DeFi” has 20x the TVL and liquidity of permissionless DeFi, did we just recreate TradFi’s market structure where institutions dominate and retail gets worse execution?

Liquidity Fragmentation Is the Real Threat

Here’s what worries me most: liquidity is THE moat in DeFi.

  • Uniswap works because it has deep liquidity pools
  • Aave works because lenders and borrowers can find competitive rates
  • If permissioned forks siphon institutional liquidity into walled gardens, public DeFi gets worse for everyone

Imagine:

  • You want to swap $10M USDC → ETH on Uniswap. Slippage: 0.5% ($50k cost)
  • Institution uses permissioned Uniswap fork with deeper liquidity. Slippage: 0.05% ($5k cost)

Public DeFi becomes the worse product because institutions won’t participate due to compliance requirements.

Can Both Coexist, or Will One Dominate?

I go back and forth on this:

Optimistic view: They serve different markets. Institutions need compliance, crypto-natives need permissionless access. Both can thrive serving their respective users.

Pessimistic view: Money flows to the best risk-adjusted returns. If permissioned pools offer better liquidity, lower slippage, and institutional-grade yields, why would anyone use public DeFi except for censorship-resistant use cases?

What Should Public DeFi Do?

I think permissionless protocols need to aggressively differentiate or risk becoming niche:

Option 1: Own censorship-resistant use cases

  • Privacy-preserving DeFi (Tornado Cash successors, private trading)
  • Uncensorable money markets for users institutions won’t serve
  • Flash loan composability that permissioned systems can’t replicate

Option 2: Become the innovation layer

  • Experiment with novel financial primitives (perpetuals, options, prediction markets)
  • Higher risk tolerance than institutions allow
  • Iterate faster than compliance-heavy institutional platforms

Option 3: Build bridges to permissioned capital

  • Hybrid protocols where institutions can participate without KYC-ing the entire protocol
  • One-way liquidity flows from permissioned → permissionless

But honestly? I don’t know if any of this works long-term. If the future of blockchain is institutions using permissioned forks, public DeFi might become a curiosity for crypto enthusiasts rather than a viable alternative financial system.

Questions for the Community

Am I being too pessimistic? Can public DeFi compete for liquidity without compromising on permissionless access?

Or should we accept that permissioned institutional blockchain infrastructure will be 20x larger than public DeFi and focus on serving the users institutions won’t touch?

Would love to hear from folks building protocols—how are you thinking about this institutional competition?

2

Chris, I hear your pessimism, but I want to push back on the framing that permissioned forks “compete” with public DeFi. I think they’re complementary, not competitive.

Here’s why: Public DeFi has composability advantages that permissioned systems can never replicate.

When I build yield strategies, I use:

  • Flash loans from Aave to source capital
  • Swaps on Uniswap for instant liquidity
  • Curve for low-slippage stablecoin swaps
  • Balancer for multi-asset rebalancing
  • All executed atomically in one transaction

Permissioned forks can’t do this. Horizon (permissioned Aave) is a walled garden—I can’t combine it with public Uniswap, can’t flash loan from it to execute cross-protocol arbitrage, can’t integrate it into automated yield strategies.

Public DeFi’s superpower is permissionless composability. Every protocol is a Lego brick. Institutions building walled gardens lose that.

So the question isn’t “will public DeFi compete for institutional capital?” It’s “will public DeFi focus on use cases where composability is the moat?”

And the answer is: absolutely yes. Flash loan arbitrage, MEV strategies, cross-protocol yield optimization—none of that works in permissioned systems.

3

Chris raises a real concern about liquidity fragmentation, but I think the solution is building bridges between permissioned and permissionless liquidity, not treating them as competitors.

From an infrastructure perspective, both ecosystems can coexist if we design the right interoperability layers:

Hybrid Liquidity Models:

  • Institutions deposit KYC’d capital → get tokenized RWAs (permissioned side)
  • Use RWAs as collateral to borrow permissionless stablecoins (USDC, DAI)
  • Deploy those stablecoins into public DeFi protocols

This creates a one-way capital flow: permissioned capital adds liquidity to public DeFi without requiring KYC on the permissionless protocols.

Result: Public DeFi gets deeper liquidity from institutional capital, institutions get access to DeFi yields and composability, and permissionless users aren’t excluded.

We’re already seeing this with Ondo Finance, MakerDAO integrating RWAs as collateral, and Aave exploring institutional vaults.

The key is ensuring permissionless protocols remain accessible to anyone, even as institutions participate via hybrid models.

Think of it like this: permissioned RWAs are the on-ramp, public DeFi is the destination.

4

From a security perspective, I’m less worried about competition and more worried about permissioned systems replicating TradFi vulnerabilities on-chain.

Everyone’s excited about $25B in RWAs, but let’s talk about the risks:

1. Admin Keys and Upgrade Mechanisms
Permissioned protocols like Horizon have admin keys that can:

  • Pause contracts
  • Upgrade logic
  • Freeze user funds
  • Modify access controls

This is the same centralization risk that caused FTX to collapse. Except now it’s on-chain with a “DeFi” label.

2. KYC as a Single Point of Failure
If a permissioned protocol’s KYC provider gets hacked or goes down, the entire system is compromised. We’ve seen this with identity providers in Web2—why would it be different in Web3?

3. Regulatory Capture
Once institutions dominate liquidity on permissioned platforms, regulators can pressure those platforms to censor transactions, freeze assets, or comply with sanctions at the protocol level.

Public DeFi’s value isn’t just “decentralization for decentralization’s sake”—it’s censorship resistance as insurance against institutional capture.

Chris is right to be concerned, but the threat isn’t liquidity competition. It’s that permissioned “DeFi” creates systemic risks while public DeFi remains the only truly censorship-resistant alternative.

Public DeFi should double down on security, immutability, and censorship resistance. Let institutions have their compliant forks—we’ll keep building uncensorable protocols.