Newsroom
26 July, 2026 / News / AI / Tags: uniswap, permissioned, pools, tokenized, dowgo

The new open-source standard enables issuer-controlled access checks so approved wallets can trade tokenized funds, securities and equities via automated market makers while standard pools stay open
Uniswap Labs has introduced Permissioned Pools on Uniswap v4, an open-source framework that embeds onchain access controls for regulated assets. Announced on July 23, 2026, the feature lets issuers of tokenized funds, securities, equities and other restricted products limit trading and liquidity provision to pre-approved wallets.
The system operates through Uniswap v4 hooks. Before a swap or the creation of a liquidity provider position can proceed, the pool’s smart contract queries an issuer-managed allowlist. Transactions originating from addresses absent from the list are blocked at the protocol level. Uniswap does not maintain the lists or approve wallets; those responsibilities remain entirely with the asset issuer.
Permissioned Pools keep compliance logic inside the smart contract rather than relying on any frontend interface. Issuers can tailor the rules to meet identity-verification, transfer-restriction or investor-eligibility requirements that apply to a given product. Virtual accounting within v4 supports settlement calculations while the regulated assets themselves stay confined to the permissioned contract environment.
Approved participants continue to trade through automated market makers instead of traditional order books. Liquidity providers deposit assets under the same access rules enforced by the issuer. The design leaves ordinary Uniswap v4 pools unchanged and fully permissionless. Developers and users can still deploy and interact with standard pools under existing protocol rules; the restricted format is an optional choice for assets that require controls.
Superstate, Securitize and Dowgo collaborated with Uniswap Labs as early partners. Superstate, which issues tokenized equities and investment funds, helped shape the format so that eligible shares can interact with automated market makers, lending platforms and other approved decentralized applications. Securitize focused on compatibility between assets issued under its DS Protocol and the new pools, aiming to expand compliant trading venues for tokenized real-world assets.
Dowgo contributed an integration path for the ERC-3643 token standard, which supports onchain identity checks and transfer limitations. Use of the standard by Dowgo remains conditional on obtaining DLT TSS authorization under the European Union’s DLT Pilot Regime, an application currently under review by France’s ACPR.
The launch arrives as tokenized real-world assets have grown to approximately $34 billion as of May 2026, of which about $1.55 billion consists of tokenized equities. Industry projections cited by Uniswap place the broader tokenized-asset market at as much as $11 trillion by 2030, though current volumes remain well below that figure.
The permissioned-pool standard follows Uniswap’s earlier introduction of tokenized securities across its web application, wallet and application programming interface. Those products, linked to companies such as Apple, Nvidia and Tesla, already carried warnings about potential KYC, transfer and geographic restrictions. The new pools give issuers an additional mechanism to enforce such conditions directly within trading infrastructure.
Issuers retain full responsibility for compiling allowlists and for complying with the securities laws and licensing regimes that govern their products. Permissioned Pools address only the onchain access layer; they do not replace broader regulatory obligations.
| Metric | Value (May 2026) | 2030 Forecast |
|---|---|---|
| Total tokenized real-world assets | $34 billion | $11 trillion |
| Tokenized equities | $1.55 billion | Not specified |
By offering a restricted pool option alongside the existing permissionless architecture, Uniswap provides issuers a route to automated-market-maker liquidity without imposing identity checks across the entire protocol. Developers may continue to choose the model that matches the legal and operational requirements of each asset.









