composewith.eth
Protocol record · production

RAILGUN

Onchain zero-knowledge privacy system and SDK for shielding ERC-20 tokens, private transfers, and private DeFi interactions on major EVM chains.

91readiness / 100
integration: highethereumbscpolygonarbitrum-one

Also available as JSON · Markdown

Resources

Good for

Avoid for

Readiness score

91/100

Readiness measures how much verified integration surface exists for builders and agents. It does not mean the protocol is easy to use — integration difficulty is tracked separately.

Docs10/10

Docs URL present

SDK8/8

SDK URL present

Template6/6

Template/quickstart present

Support6/6

Support channel present

Capability depth13/20

Shield and unshield ERC-20 tokens: integration_workflow; Private DeFi interactions: production_surface

Production-ready15/15

Has a production-ready capability

Confidence5/5

Protocol provenance confidence is high

Chain coverage8/10

4 chain(s) (capped at 5)

Freshness10/10

Last verified 6 day(s) ago

No critical issues10/10

No open critical issues

No hard caps applied.

Capabilities

Shield and unshield ERC-20 tokens production-ready

Best for: wallets that need private token balances, apps that need shielded deposits and withdrawals on existing EVM chains

  • Shielding and unshielding require fee, relayer, disclosure, and compliance UX that the app must design.

Private DeFi interactions production-ready

Best for: private swaps, lending, and dApp calls without leaving the user's preferred chain, wallet-integrated private DeFi

  • Builders need to verify adapter support, broadcaster fees, pool liquidity, and proof-of-innocence policy before production.

Composes with

kohaku privacy_layer supports

Kohaku can use Railgun private token flows as part of wallet privacy tooling and experiments.

uniswap supporting_protocol supports

Railgun private DeFi flows can involve swaps and liquidity interactions that eventually touch public AMM liquidity.

privacy-pools alternative alternative

Privacy Pools is a related privacy primitive direction focused on association sets and proof-of-innocence concepts.

Known issues

RAILGUN integrations need explicit fee, relayer, and compliance UX medium confirmed Workaround: Add explicit user disclosures, fee estimates, broadcaster selection checks, and proof-of-innocence/compliance handling before production.

Provenance

Last verified 2026-06-04 by composewith.eth research (RAILGUN docs, Railgun Engine, and Kohaku Railgun docs live-verified via WebFetch 2026-06-04) (confidence: high). Score computed by score.v2.