Passage Protocol

The compliance bridge that makes RWAs DeFi-composable. Wrap once, compose everywhere. Built on Solana with Token-2022 transfer hooks. Testnet live

[Passage Protocol @passageRWA]

$30,000,000,000 in tokenized RWAs sits on-chain today.

Only ~8% of it can actually move in DeFi.

The rest is locked behind KYC allowlists and transfer agents — tokenized, but frozen.

We're fixing that. Meet Passage 🧵

[Passage Protocol @passageRWA]

Fixed-rate, fixed-term is the right primitive, but the collateral list is the tell: 120+ types and nearly all permissionless. The institutional credit actually coming onchain is permissioned paper, and it can't enter these markets until eligibility is enforced at the asset level instead of per venue. Whoever closes that gap gets the fixed-income flow.

[Passage Protocol @passageRWA]

Same fund, three chains. Tokenized treasuries sit near $16B spread across Ethereum, BNB, Stellar, Solana and Avalanche — and every new chain or venue stands up its own allowlist for the same investors. Distribution is scaling horizontally; compliance keeps getting rebuilt vertically at every stop. The protocols that make eligibility portable will quietly own this cycle.

[Passage Protocol @passageRWA]

The pre-IPO token mess this year showed the failure mode isn't intermediation per se — it's the gap between a transfer executing onchain and the issuer recognizing it. Direct issuance closes that gap only if recognition logic lives in the asset itself, not in a ToS document. Otherwise we've rebuilt the DTCC with extra steps.

[Passage Protocol @passageRWA]

Three permissioned-pool launches in two weeks: Raydium (with Superstate), Algebra Integral, Uniswap. Eligibility is becoming standard venue infrastructure. The next problem is already visible: every venue maintains its own allowlist, so compliance state fragments across pools. Tokenizing the asset was step one. Unifying who may hold it is step two.

[Passage Protocol @passageRWA]

Notable detail: eligibility here is enforced per pool, so every new venue means another allowlist to stand up and maintain. Real progress for Solana — but the open design question is whether compliance state lives in the venue or in the asset itself. That determines how far these assets can actually travel.

[Passage Protocol @passageRWA]

Two words the RWA market treats as one: tradeable and valid.
A token is tradeable when a contract will execute the transfer. It’s valid when the issuer recognises the transfer that created it.
The pre-IPO blowups this year were the second failing while the first kept working — void claims settling onchain for months, because the restriction lived in a shareholder agreement instead of in the instrument.
Transfer hooks put the rule in the instrument.

[Passage Protocol @passageRWA]

Solid research. One gap in most programmable-equity stacks: compliance is enforced at the app layer, so composability dies at every venue boundary. We're experimenting with the inverse on Solana — Token-2022 transfer hooks so the check travels with the token (Passage, devnet stage) — curious whether your data shows venue fragmentation as the binding constraint.

[Passage Protocol @passageRWA]

Most RWA composability breaks at the venue boundary: every pool and protocol re-implements the same eligibility checks, so "tokenized" rarely means "composable."

Our approach: put the compliance check inside the token itself with Token-2022 transfer hooks. Wrap once, compose everywhere.

5 programs live on devnet, 21 tests passing. Playable demo: https://t.co/glXsU1YOnM

[Passage Protocol @passageRWA]

Agreed — issuance was never the bottleneck. The unlock is when a permissioned asset can sit as collateral or route through an AMM without breaking its compliance rules. That's why transfer hooks on Token-2022 matter: the check travels with the token instead of walling off the pool. It's what we're building toward at Passage.

[Passage Protocol @passageRWA]

Most RWA volume today lives in isolated pools — tokenized, but not usable. The fix isn't another walled garden, it's making the compliance check travel with the token. Token-2022 transfer hooks make that possible on Solana. 5 programs live on devnet, demo playable: https://t.co/glXsU1YOnM

[Passage Protocol @passageRWA]

If you've built on Token-2022 transfer hooks, you know the hook is the easy part. Resolving the extra accounts is where you lose an afternoon — and @solana/spl-token only covers a plain transfer, not the case where your own program does it by CPI.

Open-sourced ours:
npm i @passage_protocol/hook-kit

[Passage Protocol @passageRWA]

@MeshClans @YashasEdu @kenodnb @0xCheeezzyyyy @rektdiomedes @rektonomist_ @crypto_linn @0xspicexr @MartindRijke Maple growing 22% into a 31% market contraction says the demand was never for permissionless leverage — it was for credit with real underwriting and enforceable eligibility. The winners in onchain credit are starting to look like structured finance desks, not money markets.

[Passage Protocol @passageRWA]

Most RWA compliance lives at the app layer today: allowlists in the frontend, checks in the router. The moment the asset moves somewhere else, the rules stay behind.

Token-2022 transfer hooks flip that — the check travels with the token. That's the whole thesis behind Passage: wrap once, compose everywhere.

Where we are: 5 programs on devnet, 21 passing tests, and a demo you can try — mint test tokens, wrap, swap in a gated AMM.

[Passage Protocol @passageRWA]

Enforcement at the execution layer is the real unlock — routers and frontends stop being the compliance perimeter. Same principle we're applying on Solana at Passage with Token-2022 transfer hooks: the check travels with the token itself, so any venue it touches inherits the rules.

[Passage Protocol @passageRWA]

DTCC trading tokenized Russell 1000 shares and Uniswap shipping permissioned pools, weeks apart. The "will securities go onchain" debate is over.

The real open question: where does compliance get enforced — at every venue separately, or once, in the asset itself?

[Passage Protocol @passageRWA]

The $576M refunded is the stat people misread — futarchy raises are a filter, not just a funnel. Markets rejecting 93% of committed capital is the mechanism working as designed. A small fee on the full committed amount seems defensible given the AMM does real price discovery either way.

[Passage Protocol @passageRWA]

Most RWA compliance today lives at the venue: whitelist the pool, gate the market, repeat for every integration. Token-2022 transfer hooks invert that — the check travels with the token itself.

Wrap once, compose everywhere. 5 programs live on devnet, demo is playable: https://t.co/glXsU1YOnM

[Passage Protocol @passageRWA]

@0x_axert Appreciate the interest — one correction though: we haven't announced any partnerships. What's real today: 5 programs live on Solana devnet, 21 passing tests, and a playable demo. We'd rather under-claim and ship.

[Passage Protocol @passageRWA]

$30,000,000,000 in tokenized RWAs sits on-chain today.

Only ~8% of it can actually move in DeFi.

The rest is locked behind KYC allowlists and transfer agents — tokenized, but frozen.

We're fixing that. Meet Passage 🧵

[Passage Protocol @passageRWA]

Pool-level allowlists are a real step, but they anchor compliance to one venue — every new integration means re-gating. The alternative is putting the check in the token itself: Token-2022 transfer hooks let the rules travel with the asset across any AMM or lending market. That's the design we're testing with Passage on devnet — wrap once, compose everywhere.

[Passage Protocol @passageRWA]

Quiet weekend milestone for Passage: 5 programs live on devnet, 21 passing tests. The demo covers the full loop — grab test tokens, wrap into a compliant Token-2022 asset, swap in a gated AMM. Transfer hooks doing the compliance work per transfer, onchain. Playable here: https://t.co/glXsU1Zmdk