On-chain ZK Privacy Ecosystem

RAILGUN brings Zero-Knowledge cryptography directly to supported EVM networks, enabling private balances, transfers and smart-contract interactions without leaving the chain.

4 EVM networks
0zk private address
PRIVACY ENGINE: ACTIVE
0x9f32b7a1c8…aee917bc
ShieldPrivate
DeFi
Selective
reveal
On-chainBuilt on existing networks
Non-custodialKeys remain with users
Zero-knowledgeProofs instead of exposure
ComposableDesigned for dApps and DeFi
01 / PRIVACY LAYER

Privacy is not an add-on. It is financial infrastructure.

Public blockchains are verifiable by design, but that can expose balances, counterparties and strategies. ZK systems aim to preserve validity while minimizing disclosure.

01

Private balances

Shielded balances are represented inside the privacy system instead of being exposed as a public wallet total.

02

Private transfers

Zero-knowledge proofs can validate encrypted token transfers without publishing the full financial context.

03

Private DeFi

The architecture is designed for composable smart-contract interactions rather than a single deposit-and-withdraw flow.

04

Non-custodial control

Users interact from self-custodial wallets and retain control of their assets and signing keys.

05

Broadcaster network

Community broadcasters can submit private interactions so a public origin wallet is not required for every action.

06

Developer toolkit

Wallet SDKs and adapt modules give builders a path to add privacy-aware flows to EVM applications.

02 / SYSTEM MAP

A privacy engine that lives directly on-chain.

RAILGUN is described in its official documentation as code deployed on supported EVM networks, with encrypted notes, private balances and ZK proof verification.

L4Applications & walletsUser interfaces, SDKs and integrations
L3RAILGUN privacy engineEncrypted notes, Merkle state and proof generation
L2Smart contractsOn-chain verification and state transitions
L1Supported EVM networksEthereum, BSC, Polygon and Arbitrum in current docs
ZERO-KNOWLEDGE PROOF CONSOLEzk://local-prover
Create encrypted commitment0x5a9e…b81c
Generate proof locally0x5a9e…b81c
Verify on-chain0x5a9e…b81c
Update private state0x5a9e…b81c
● PROOF VERIFIED
INTERACTIVE / PROOF LAB

Watch a privacy proof take shape.

VISUAL SIMULATIONREADY FOR LOCAL SIMULATION
01Create encrypted commitmentREADY
02Generate Zero-Knowledge proofWAIT
03Verify the proof on-chainWAIT
04Update private stateWAIT
proof://idle
03 / TWO PRIVACY MODELS

Different architectures. A shared belief in financial privacy.

TC

Tornado Cash

A non-custodial privacy protocol that separates the visible relationship between a deposit and a later withdrawal through smart-contract pools and ZK proofs.

Pool modelDeposit / withdrawZK proofs
RG

RAILGUN

An on-chain privacy system focused on private balances, private transfers and composable DeFi interactions across supported EVM networks.

Private balance modelComposable DeFi0zk addresses
!
RESPONSIBLE PRIVACY

Privacy is not the same as lawlessness.

Privacy technology can have legitimate personal, commercial and civil-society uses. Users remain responsible for applicable laws, sanctions, tax rules and operational security.

No guarantee of absolute anonymity. Timing, amount patterns, reused addresses and network metadata can reduce privacy.
Verify every domain and contract before connecting a wallet or signing a transaction.
Features and supported networks can change. Confirm current details in official documentation.
04 / FAQ

Key questions about RAILGUN

What is RAILGUN?

RAILGUN is an on-chain, non-custodial privacy system that uses Zero-Knowledge cryptography for private balances, transfers and smart-contract interactions on supported EVM networks.

Is RAILGUN the same as Tornado Cash?

No. They are separate protocols with different architectures and user flows.

Which networks are supported?

The current official RAILGUN overview lists Ethereum, BSC, Polygon and Arbitrum. Verify documentation before use because support can change.

VERIFY, THEN EXPLORE

Study the technology at its source.

Use official documentation for technical details, current network support, security notes and integration guidance.