> For the complete documentation index, see [llms.txt](https://docs.railgun.org/wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.railgun.org/wiki/learn/common-misconceptions.md).

# Common Misconceptions

Corrections to the most common wrong claims about RAILGUN, including addresses, the RAIL token, PPOI, and staking.

**Not RAILGUN:** Cloudflare's discontinued "Railgun" web-acceleration product is a different, unrelated product that happens to share the name.

**RAILGUN Connect** is a WalletConnect-style plugin for RAILGUN wallets, currently in development. It is not a bridge and does not move assets between chains. RAILGUN does not use a bridge or L2 for any part of the protocol.

**Security staking:** the referenced portal is [stakerail.fi](https://stakerail.fi), run by a third party, not the protocol team, as a front end over the on-chain staking contracts. You can also interact with the staking contracts directly, or run your own portal via IPFS. See [Helpful Links](/wiki/learn/helpful-links.md) for the contract addresses.

**PPOI (Private Proofs of Innocence)** is an optional compliance layer, separate from the core RAILGUN contracts, that screens new shields against public bad-actor lists. It does not make RAILGUN's privacy conditional. Transactions are processed by the smart contracts with or without it. The integration of PPOI is up to the individual wallet developers and its main user-facing effect is a delay of about 1 hour before a new shield can be spent forward. Tokens can always be unshielded back immediately.

**0zk addresses** are the only valid RAILGUN private address format today. RAILGUN is a Layer 1 smart-contract system, not a rollup, so there is no "rollup address."

**RAIL** is a real ERC-20 token used only for protocol security (staking). Security stakers evaluate the content of protocol requests and decide whether they should be executed. RAIL is never used to pay transaction or gas fees, has no "RAIL guardian" role, and has no buy-back-and-burn mechanism.

**Treasury funds** never pass through a developer wallet. Protocol deductions go directly to an on-chain treasury contract and are distributed to security stakers autonomously on a fixed schedule. Any change requires a passed on-chain protocol request.

**The trusted setup** uses multi-party computation, not a multisig. It is secure as long as at least one participant destroys their randomness (Toxic Waste) afterward. Verification keys are meant to be public. Forging a fake proof would require undestroyed Toxic Waste, not a "leaked" verification key.

**Viewing keys are shareable by design.** The spending key must never leave your hands. You can generate and share a viewing key (see [View-Only Wallets](https://docs.railgun.org/developer-guide/wallet/private-wallets/view-only-wallets)) to give someone read-only access to your balances and history, with zero ability to spend.

**Merkle trees:** every RAILGUN Merkle tree has a fixed depth of 16 (65,536 leaves per tree).

**Live contract version:** RAILGUN V2, on Ethereum, Polygon, BSC, and Arbitrum. See [Helpful Links](/wiki/learn/helpful-links.md) for current deployment addresses on each chain.