Cowrie Research

railgun-primary-sources-2026-04-26

4 min read

RAILGUN primary-source snapshot

Fetched: 2026-04-26 UTC

1) Docs overview / project framing

Source: https://docs.railgun.org/wiki/learn/overview.md Source: https://railgun.org/

Selected excerpts from the docs:

RAILGUN is code that exists on every Ethereum node. It’s a privacy system built directly on-chain for Ethereum, BSC, Polygon, and Arbitrum.

The RAILGUN code has no owner.

The RAIL token is purely a governance token and is not a privacy coin. Holding RAIL is not necessary to use the protocol.

RAILGUN is 100% non-custodial.

Additional signals from the docs:

  • RAILGUN is framed as ownerless onchain privacy middleware rather than as a separate privacy chain or a custody product
  • The first-party docs separate the protocol from the wallets that integrate it, which is useful for categorizing it as infrastructure
  • The homepage fetch was sparse in this pass, but the docs explicitly point back to the website, developer guide, and GitHub as the core official surfaces

2) Privacy system / operating model

Source: https://docs.railgun.org/wiki/learn/privacy-system

Selected excerpts from the docs:

The RAILGUN privacy system is a series of smart contracts that privatizes blockchain interactions.

RAILGUN privatizes: Sender, Recipient, Token type, Amount.

RAILGUN users can send transactions through Broadcasters … Interactions sent by users appear to originate from Broadcasters and cannot be linked to a shielding address.

At its core, RAILGUN is low-level infrastructure with an SDK … for protocol integrations of private smart contract interactions and a private wallet.

Additional signals from this page:

  • The project wants to support private smart-contract interactions, not just private transfers
  • Broadcasters and the UTXO-style encrypted Merkle-tree model are central to how the public-chain UX works
  • The docs explicitly describe RAILGUN as low-level infrastructure with SDKs, which is a strong categorization clue

3) Assurance and auditability

Source: https://docs.railgun.org/wiki/assurance/railgun-assurance-suite

Selected excerpts from the docs:

RAILGUN has 3 main tools for auditability and assurance:

Viewing Keys: Shareable read-only private key for auditability or investigatory purposes

Private proofs of Innocence (PPOI): a Zero-Knowledge assurance tool that checks that tokens moving through RAILGUN do not originate from a known list of malicious activity.

Koinly Tax Exports: Easy file exports for use in the Koinly tax software

Additional signals from this page:

  • RAILGUN is not marketing privacy as irreconcilable with compliance or investigations; it publishes first-party assurance tools instead
  • Viewing keys plus PPOI make the project materially different from a simple “privacy coin” categorization
  • Tax-export tooling is another clue that the team is trying to make shielded activity operable, not just private

4) Governance surface

Source: https://docs.railgun.org/wiki/rail-token/protocol-governance Source: https://docs.railgun.org/wiki/rail-token/rail-token-overview.md

Selected excerpts from the docs:

RAIL is described as RAILGUN Protocol’s security token and also as a pure governance token.

1 locked RAIL = 1 vote.

Locked RAIL lets you vote on proposals, submit proposals, or delegate voting power.

Additional signals from these pages:

  • Governance is a meaningful protocol surface, but the docs are careful to separate governance/security incentives from the privacy function itself
  • The docs explicitly say RAIL is not required for protocol use, which helps avoid misclassifying the token as the core product

5) GitHub org / real implementation surface

Source: https://github.com/Railgun-Community Source: https://github.com/Railgun-Community/wallet

Selected excerpts/signals from GitHub:

SDK library to develop RAILGUN wallets

JavaScript library to interact with RAILGUN smart contracts

Write a recipe in minutes to convert your dApp to a zkApp.

The Wallet SDK enables dApp and DeFi developers to provide privacy to users safely and conveniently on Ethereum, Polygon and BNB Chain.

Additional signals from GitHub:

  • The public repo surface is strongly infrastructure- and integration-oriented: wallet SDKs, engine libraries, cookbook patterns, broadcaster tooling, and assurance-related repos
  • This supports cataloging RAILGUN as privacy middleware / SDK infrastructure rather than as a single wallet app or token project
  • Active public repos updated into 2026 suggest the technical surface is still live and maintained

Notes

  • This pass did not locate an official standalone whitepaper or litepaper in first-party materials.
  • The strongest source-of-truth surfaces were the docs portal plus the GitHub organization and wallet SDK repo.
  • RAILGUN appears best categorized as onchain privacy infrastructure / zk wallet middleware / private smart-contract interaction protocol.

Graph View