Search for projects by name or address
An onchain privacy system for Ethereum based on encrypted UTXO-style private balances and zk-proven DeFi interactions.
An onchain privacy system for Ethereum based on encrypted UTXO-style private balances and zk-proven DeFi interactions.
Railgun is a non-custodial privacy protocol on Ethereum built around encrypted UTXO-style private balances rather than fixed-denomination pools. This design enables in-protocol transfers of shielded tokens and interactions with DeFi smart contracts on L1.
A shield transaction moves assets from a public address on Ethereum into the Railgun contract and creates encrypted commitments in a Merkle-tree state. Later private transfers or unshields use zk-SNARK proofs to spend those commitments without revealing the sender, recipient, token type, or amount. Notes created by deposits and private transactions represents ownership of tokens in Railgun, users must keep them secret and make sure the notes are not lost.
Railgun supports private transfers and cross-contract interactions without fragmenting liquidity across denominations. DeFi calls can be executed through the RelayAdapt contract, which temporarily unshields tokens to Ethereum L1, performs a sequence of contract calls, and shields the resulting assets back into Railgun in a single transaction (facilitated by a relayer).
Railgun has a DAO governed by holders of the RAIL token. The DAO has the authority to arbitrarily change the logic of the protocol and its shielded tokens.
Railgun protocol supports relayed withdrawals, in which a relayer (called a broadcaster in Railgun ecosystem) processes withdrawals on the user’s behalf for a fee, which enables sending funds to fresh addresses. Transactions from private addresses can be sent through relayers over the Waku network, which increases network-level privacy. Railgun allows interactions between shielded tokens and DeFi, which allows depositing and withdrawing different tokens.
Practical privacy also depends on the timing and amounts of deposits and withdrawals. Users are advised to research OPSEC best practice.
There are mandatory onchain protocol fees of 0.25% for shields and 0.25% for unshields. The NFT fee field is currently set to 0. Shield and unshield fees are sent to the Railgun Treasury.
Relayers can charge additional offchain fees for submitting transactions on a user’s behalf. These relayer fees are not set by the core protocol contracts.
Railgun protocol does not enforce any compliance measures. However it allows using Private Proof of Innocence(PPoI), which can attest to the origin and history of shielded tokens. Relayers and some wallets require a valid PPoI for their services, but they are not generally enforced.
Additionally, Railgun users can share a read-only viewing key to expose all sent and received private transactions, if required by a regulator or enforcer.
Because Railgun allows private transfers, optional PPoIs that can be enforced by relayers, and interactions with DeFi, its anonymity set depends on many details. A withdrawal from Railgun could be connected with a deposit of another token, or could not correspond to any deposit if a user received a private transfer from another user. The anonymity set, in the best case, corresponds to the set of all Railgun users.
To find incoming transfers and rebuild the balance, a wallet downloads every new commitment emitted by the Railgun contract and tries to decrypt each one locally with the user’s viewing key; successful decryptions are saved as the user’s notes. Because every commitment is requested, the RPC provider does not learn which notes belong to the user from the queries alone.
2025 Sep 04 — 2026 Sep 04
2025 Sep 04 — 2026 Sep 04
Asset | Deposits 7D | Deposits 30D | Deposits Total | Value Locked |
|---|---|---|---|---|
WETH | 467 $6.48 M | 1.80 K $26.22 M | 42.29 K $1.50 B | $52.17 M |
USDC | 123 $3.25 M | 608 $8.81 M | 8.86 K $288.34 M | $17.08 M |
USDT | 217 $4.02 M | 736 $20.29 M | 10.31 K $367.81 M | $10.21 M |
DAI | 19 $1.42 M | 61 $3.92 M | 2.10 K $192.02 M | $5.82 M |
WBTC | 0 $0.00 | 15 $264.87 K | 647 $41.40 M | $2.38 M |
NEAR | 0 $0.00 | 0 $0.00 | 0 $0.00 | $1.61 M |
RAIL | 2 $1.91 K | 4 $11.83 K | 320 $3.69 M | $625.18 K |
FLUID | 0 $0.00 | 0 $0.00 | 2 $1.55 M | $208.27 K |
| Total | 828 $15.20 M | 3.23 K $59.52 M | 64.54 K $2.40 B | $90.13 M |
Railgun features an omnipotent DAO governed by the stakers of the RAIL token. The DAO has the authority to change ZK circuit logic on the core Railgun contract, which can arbitrarily change the rules for shielded tokens; as well as manage blacklisted tokens, mint RAIL tokens and manage governance rewards. See docs here: https://docs.railgun.org/wiki/rail-token/protocol-governance
| Normal upgrade path | Create a proposal with an IPFS link and onchain calldata in the Voting contract → collect 500.00 K RAIL sponsorship within 1mo → wait 2d → cast Yay votes within 5d and Nay votes within 6d → pass with a simple majority and 2.00 M RAIL quorum → wait 7d → permissionless execution through the Delegator within 14d. |
|---|---|
| Exit window | 7d — a passed proposal must wait this long before it can be executed, giving users time to unshield funds. |
| Governance token |
|
|---|---|
| Stake lock | Unstaking has 1mo delay. |
| Voting venue | Voting contract on Ethereum. Proposal text is distributed over IPFS, its CID is available as a parameter of |
| Proposal threshold | No threshold to create a proposal. A proposal must receive sponsorship from 500.00 K RAIL stake within 1mo. |
| Quorum | 2.00 M RAIL, with a simple majority required for acceptance. |
| Execution model | Onchain calldata · Permissionless execution through the Delegator. A passed proposal waits 7d, after which anyone can execute it through the Delegator contract within 14d. |
Circuit-specific Phase 2 trusted setup for Railgun’s 54 Groth16 circuits (parameterised by transaction input/output counts) over the BN254 curve. It builds on the Polygon zkEVM ceremony https://github.com/iden3/snarkjs/tree/master?tab=readme-ov-file as phase 1, which contains 55 participants.
A separate Phase 2 ceremony was publicly announced, open to anonymous and identified participants, and wrapped up in late December 2022.
Verified against the ceremony artifact IPFS hash
QmWAySHYhaZqioKi1ufrPJC1n1ZVtHP2w4hLA9XqqJCFne: the
/contributors directory contains 328 sequentially-numbered attestation files with
GitHub or Twitter handles, and the /zkeys directory contains 54 final zkey files (one
per circuit). Parsing the final zkey binary for the 1x1 circuit shows 304 Phase 2
contributions on that circuit.
Verifier | Verification | Used in | Known deployments | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Railgun verifier | by | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Verifier ID: Railgun 91 circuit verifier 03.07.2026Known deployments Verification steps Railgun smart contract acts as a verifier for ZK proofs for all 91 Railgun circuits. 91 different verification keys for these circuits are stored onchain in the verifier smart contract. This regeneration attests that the verification keys stored onchain correspond to circuits published in Railgun repo. Generally, to regenerate all Railgun verification keys, the following has to be done:
Helper scripts that implement the flow above and more detailed explanations could be found in this script .zip archive. This .zip must be extracted in | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Swap USDC to DAI proposal: https://tools.l2beat.com/decoder-new/?hash=0x83963ddea866aa6d77200fd5f6633d59aa6d4dc9a807496277f6910cc76a0369&data=AwA Actions: 1. Treasury → Delegator: 15109.211424 USDC 2. Delegator: USDC.approve(Curve3pool, 15109.211424) 3. Curve3pool: exchange USDC→DAI (min dy = 15031.466111962828487747 DAI, 0.5% slippage) 4. Delegator → Treasury: 15031.466111962828487747 DAI (floor) 5. Delegator → Treasury: 75.535005587752906974 DAI (expected bonus)
Swap USDC to DAI proposal: https://tools.l2beat.com/decoder-new/?hash=0x83963ddea866aa6d77200fd5f6633d59aa6d4dc9a807496277f6910cc76a0369&data=AwA
Actions:
| EOA (eth:0x5a02474A3083Bc969f20F92E7a8bd3824EC607f0) { | |
| +++ description: None | |
| proxyType: | |
| - | "EOA" |
| + | "EIP7702 EOA" |
| sourceHashes: | |
| + | ["0xd9649be084919b1ae25d4d396555667632253f10ddb6a9bddc939db45f797b10"] |
| values: | |
| + | {"$implementation":"eth:0x5A7FC11397E9a8AD41BF10bf13F22B0a63f96f6d","nonce":0} |
| } |
| contract Voting (eth:0xc480F68A3dcC3EdD82134FAB45C14A0FcF1dA3CC) [railgun/Voting] { | |
| +++ description: Token-weighted Railgun governance contract. Proposals must be sponsored, voted through quorum, and then executed through the Delegator. | |
| +++ severity: HIGH | |
| values.proposalCount: | |
| - | 28 |
| + | 29 |
| } |
New proposal on Railgun DAO: "Base deployment of RAILGUN Privacy System". Onchain execution of this proposal sends tasks to OPStackSender contract: https://tools.l2beat.com/decoder-new/?hash=0xfd5860b22fad6d5bf81cd4e9c809b2016ed08971b0fbf96aaf033fdbf87b52ec&data=AwA. These tasks initialize verification keys for all railgun circuits on the main Railgun contract on Base ( base:0x0047d1F97674614189E80566575FB615788AcF25 ). Railgun smart contracts on Base are already deployed, with bytecode matching the deployment on Ethereum. The proposal doesn't look malicious.
New proposal on Railgun DAO: “Base deployment of RAILGUN Privacy System”.
Onchain execution of this proposal sends tasks to OPStackSender contract: https://tools.l2beat.com/decoder-new/?hash=0xfd5860b22fad6d5bf81cd4e9c809b2016ed08971b0fbf96aaf033fdbf87b52ec&data=AwA. These tasks initialize verification keys for all railgun circuits on the main Railgun contract on Base (base:0x0047d1F97674614189E80566575FB615788AcF25).
Railgun smart contracts on Base are already deployed, with bytecode matching the deployment on Ethereum.
The proposal doesn’t look malicious.
| contract Voting (eth:0xc480F68A3dcC3EdD82134FAB45C14A0FcF1dA3CC) [railgun/Voting] { | |
| +++ description: Token-weighted Railgun governance contract. Proposals must be sponsored, voted through quorum, and then executed through the Delegator. | |
| +++ severity: HIGH | |
| values.proposalCount: | |
| - | 27 |
| + | 28 |
| } |
New railgun proposal created: https://tools.l2beat.com/decoder-new/?hash=0xb0f02fe28a805756fbd58c90a0704c26be69882460b1bd8885ca9fe93dd77718&data=AwA. It sweeps most tokens from railgun treasury (excluding WETH, RAIL which have most value) to 0xA4f2eA0a81179362558eBC1d2Bc817c9a0134ee3. Also triggers an action on arbitrum deployment. IPFS-published proposal description: "This proposal will gather tokens that are not part of the biweekly security staker rewards and use them to issue a research grant. The previous research funding ended earlier this year, so this would be a new and separate funding. All slightly significant tokens on Arbitrum will be collected. Most tokens not related to RAIL Security Rewards on Ethereum treasury will be collected.\n\nThe sum for this will be to fund the further development on the following (but not limited to): \n\n- RAILGUN-reloaded SDK, \n- RAILGUN v3,\n- Hardware Support \n- Post-Quantum Research \n- Multisig Support \n- and incentivise researchers and ecosystem.\n\nPlease do your own security review & vote YES to support this grant." Looks legit.
New railgun proposal created: https://tools.l2beat.com/decoder-new/?hash=0xb0f02fe28a805756fbd58c90a0704c26be69882460b1bd8885ca9fe93dd77718&data=AwA. It sweeps most tokens from railgun treasury (excluding WETH, RAIL which have most value) to 0xA4f2eA0a81179362558eBC1d2Bc817c9a0134ee3. Also triggers an action on arbitrum deployment.
IPFS-published proposal description: “This proposal will gather tokens that are not part of the biweekly security staker rewards and use them to issue a research grant. The previous research funding ended earlier this year, so this would be a new and separate funding. All slightly significant tokens on Arbitrum will be collected. Most tokens not related to RAIL Security Rewards on Ethereum treasury will be collected.\n\nThe sum for this will be to fund the further development on the following (but not limited to): \n\n- RAILGUN-reloaded SDK, \n- RAILGUN v3,\n- Hardware Support \n- Post-Quantum Research \n- Multisig Support \n- and incentivise researchers and ecosystem.\n\nPlease do your own security review & vote YES to support this grant.”
Looks legit.
| contract Voting (eth:0xc480F68A3dcC3EdD82134FAB45C14A0FcF1dA3CC) [railgun/Voting] { | |
| +++ description: Token-weighted Railgun governance contract. Proposals must be sponsored, voted through quorum, and then executed through the Delegator. | |
| +++ severity: HIGH | |
| values.proposalCount: | |
| - | 26 |
| + | 27 |
| } |
The RailgunSmartWallet implementation upgrade proposed and reviewed in the entry below (2026-07-30) has now been executed by governance. The new implementation (https://disco.l2beat.com/diff/eth:0xB4F2d77bD12c6b548Ae398244d7FAD4ABCE4D89b/eth:0xd662c4b1f22aceb0beacdf3a493de6f478686a0c): - adds an Action event (caller + per-transaction nullifier/commitment counts, unshield flag, and boundParamsHash) emitted in shield() and transact() as an anchoring point for wallets/indexers to decode batched and nested Railgun transactions, - changes Verifier.verify() and validateTransaction() return signatures to also return the boundParamsHash for the new event (validation logic unchanged), - moves the token blocklist check from validateCommitmentPreimage() (now pure) directly into shield() (same effective behavior: blocked tokens still cannot be shielded). No permission, fee, or escrow logic changes.
The RailgunSmartWallet implementation upgrade proposed and reviewed in the entry below (2026-07-30) has now been executed by governance. The new implementation (https://disco.l2beat.com/diff/eth:0xB4F2d77bD12c6b548Ae398244d7FAD4ABCE4D89b/eth:0xd662c4b1f22aceb0beacdf3a493de6f478686a0c):
Action event (caller + per-transaction nullifier/commitment counts, unshield flag, and boundParamsHash) emitted in shield() and transact() as an anchoring point for wallets/indexers to decode batched and nested Railgun transactions,Verifier.verify() and validateTransaction() return signatures to also return the boundParamsHash for the new event (validation logic unchanged),validateCommitmentPreimage() (now pure) directly into shield() (same effective behavior: blocked tokens still cannot be shielded).No permission, fee, or escrow logic changes.
| contract RailgunSmartWallet (eth:0xFA7093CDD9EE6932B4eb2c9e1cde7CE00B1FA4b9) [railgun/RailgunSmartWallet] { | |
| +++ description: Main system contract and escrow that accepts shielded deposits, verifies private transactions and unshields, and maintains the commitment tree. | |
| sourceHashes.1: | |
| - | "0x0ad85e59396caf20dd30307894a735a097dbd0d914bc1851af97c04cc874ad3b" |
| + | "0xb6d8961a0f486e51d0c52fe1292f627928dba2087f6e643379207033c0966965" |
| +++ description: Current Railgun smart wallet implementation. | |
| +++ severity: HIGH | |
| values.$implementation: | |
| - | "eth:0xB4F2d77bD12c6b548Ae398244d7FAD4ABCE4D89b" |
| + | "eth:0xD662C4B1F22AcEb0BEaCdf3A493De6f478686A0C" |
| implementationNames.eth:0xB4F2d77bD12c6b548Ae398244d7FAD4ABCE4D89b: | |
| - | "RailgunSmartWallet" |
| implementationNames.eth:0xD662C4B1F22AcEb0BEaCdf3A493De6f478686A0C: | |
| + | "RailgunSmartWallet" |
| } |
New railgun proposal created. It is evaluated as not malicious. The trx: https://tools.l2beat.com/decoder-new/?hash=0x818c219e6081d0b650f6be93fb19e1829c154c299f2dae0c7e2f6a6dcd3f2a71&data=AwA. Proposed upgrade of the main Railgun contract: https://disco.l2beat.com/diff/eth:0xB4F2d77bD12c6b548Ae398244d7FAD4ABCE4D89b/eth:0xd662c4b1f22aceb0beacdf3a493de6f478686a0c. Changes: - Added Action event that has overview of trxs in the action. This event is now emitted in transact() - verify() and validateTransaction() now also return hashBoundParams to be included in the new event - minor refactoring. Proposal also executes task 6 on Arbitrum Executor, which is this one: https://tools.l2beat.com/decoder-new/?hash=0xa2403ae37d69e9b92b5934bfb13779176d8484402b211ed8f55cd3d415ef0d66&data=AwA. It makes the same railgun contract upgrade on Arbitrum. The newly deployed railgun contracts have poseidon hash libraries not verified, it is confirmed that the EVM byte code of these libraries is equivalent to the previous deployment (no vulnerabilities introduced) on Ethereum and Arbitrum.
New railgun proposal created. It is evaluated as not malicious. The trx: https://tools.l2beat.com/decoder-new/?hash=0x818c219e6081d0b650f6be93fb19e1829c154c299f2dae0c7e2f6a6dcd3f2a71&data=AwA. Proposed upgrade of the main Railgun contract: https://disco.l2beat.com/diff/eth:0xB4F2d77bD12c6b548Ae398244d7FAD4ABCE4D89b/eth:0xd662c4b1f22aceb0beacdf3a493de6f478686a0c.
Changes:
Proposal also executes task 6 on Arbitrum Executor, which is this one: https://tools.l2beat.com/decoder-new/?hash=0xa2403ae37d69e9b92b5934bfb13779176d8484402b211ed8f55cd3d415ef0d66&data=AwA. It makes the same railgun contract upgrade on Arbitrum.
The newly deployed railgun contracts have poseidon hash libraries not verified, it is confirmed that the EVM byte code of these libraries is equivalent to the previous deployment (no vulnerabilities introduced) on Ethereum and Arbitrum.
| contract Voting (eth:0xc480F68A3dcC3EdD82134FAB45C14A0FcF1dA3CC) [railgun/Voting] { | |
| +++ description: Token-weighted Railgun governance contract. Proposals must be sponsored, voted through quorum, and then executed through the Delegator. | |
| +++ severity: HIGH | |
| values.proposalCount: | |
| - | 25 |
| + | 26 |
| } |

Token-weighted Railgun governance contract. Proposals must be sponsored, voted through quorum, and then executed through the Delegator.


Collects Railgun fees. Managed through access control roles.
Main system contract and escrow that accepts shielded deposits, verifies private transactions and unshields, and maintains the commitment tree.
Admin interface for Railgun’s pausable upgradeable proxies. It does not hold funds, but its controller can operate every proxy attached to it.
Reward distributor that pulls assets from the Railgun treasury and allocates them to stakers via token voting.
Older Railgun sweeper generation that still holds Treasury transfer rights. It is upgradeable and forwards balances to an immutable receiver.
Permission router proxy owned by Railgun governance.
RAIL governance token contract with a capped (100,000,000 RAIL total supply) mint schedule and an early anti-bot transfer override.
RAIL staking contract that tracks delegated voting power, enforces a 1mo unstake delay, and snapshots staking balances for governance every 1d. Its parameters define the governance voting system.
Immutable payout stream that can pull a fixed amount of a configured asset from the Railgun treasury to a fixed beneficiary whenever the next interval is due.
Helper that forwards all ETH or ERC20 balances it holds to a fixed receiver.
Read-only helper contract that batches governance snapshot and reward-view calls.
Execution adapter contract for Railgun. To interact with public contracts from shielded pools, tokens are unshielded to RelayAdapter, which performs specified calls and shields tokens back to the same user.