RAILGUN security record
As of 2 Nov 2026, RAILGUN has 8 audit reports by 2 security firms on Trustblock; the latest is by Zokyo, dated 3 Feb 2023. Those reports list no open critical findings. It also holds 1 deployed contract on 1 chain.
Record last updated . It holds audits and findings, contracts and incidents up to Oct 2026. Trustblock does not review code.
Audits8
Newest first
| Audit | Security firm | Date | Scope | Critical findings | Report |
|---|---|---|---|---|---|
| RAILGUN Smart Contract Review | Security firm: Zokyo | Date: | Scope: Repository at commit a49a82d | No open critical findings | Open · IPFS |
| RAILGUN Smart Contract Review | Security firm: Zokyo | Date: | Scope: Repository at commit 4385ec7 | No open critical findings | Open · IPFS |
| Railgun | Security firm: Zokyo | Date: | Scope: Not recorded (see the report) | No open critical findings | Open · IPFS |
| RAIL Token Smart Contract Review | Security firm: Zokyo | Date: | Scope: 1 address on Ethereum | No open critical findings | Open · IPFS |
| RAILGUN Smart Contract Review | Security firm: Zokyo | Date: | Scope: Repository at commit 62401e1 | No open critical findings | Open · IPFS |
| RAILGUN Smart Contract Review | Security firm: Zokyo | Date: | Scope: Repository at commit 97af307 | No open critical findings | Open · IPFS |
| RAILGUN Smart Contract Review | Security firm: Zokyo | Date: | Scope: Files named in the report | No open critical findings | Open · IPFS |
| Right to Privacy / Railgun / Nov2021 | Security firm: Hacken | Date: | Scope: Repository at commit d2c6357 | No open critical findings | Open · hacken.io |
Findings24
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 0 |
| Medium | 0 | 0 | 6 |
| Low | 10 | 0 | 8 |
MediumcanExecute causes ambiguityRAILGUN Smart Contract Review · Zokyo · 3 Feb 2023Fixed
The report gives no description here.
Open the reportMediumCentralization riskRAILGUN Smart Contract Review · Zokyo · 3 Feb 2023Fixed
The report gives no description here.
Open the reportMediumPossible re-entrancyRAILGUN Smart Contract Review · Zokyo · 21 Dec 2022Fixed
The report gives no description here.
Open the reportMediumUnchecked possible zero addressRAILGUN Smart Contract Review · Zokyo · 21 Dec 2022Fixed
The report gives no description here.
Open the reportMediumTest Unit FailedRight to Privacy / Railgun / Nov2021 · Hacken · 3 Nov 2021Fixed
While 41 tests are passing, 1 is failing. It fails with the “Out of Gas” message which means your logic could be too complicated and overloaded with loops, maths, and external calls. …
Open the reportMediumToo low test coverageRight to Privacy / Railgun / Nov2021 · Hacken · 3 Nov 2021Fixed
Global test coverage is about 68% for code branches, while the main RailgunLogic contract is covered only for 57.89% of logic branches. The recommended coverage is minimum 95% for branches, while it should be definitely 100% for the main logic contracts.
Open the reportLowBetter return uint256 taskID createdRAILGUN Smart Contract Review · Zokyo · 3 Feb 2023Fixed
The report gives no description here.
Open the reportLowNo validation of input addressRAILGUN Smart Contract Review · Zokyo · 3 Feb 2023Fixed
The report gives no description here.
Open the reportLowReturn value not checkedRAILGUN Smart Contract Review · Zokyo · 3 Feb 2023Fixed
The report gives no description here.
Open the reportLowUnnecessary transferOwnershipRAILGUN Smart Contract Review · Zokyo · 3 Feb 2023Fixed
The report gives no description here.
Open the reportShow 4 more
LowIn Commitments.sol contracts for function provided misleading comments inRAILGUN Smart Contract Review · Zokyo · 23 Nov 2021Fixed
The report gives no description here.
Open the reportLowIn contract RailgunLogic.sol in functions and is usedRAILGUN Smart Contract Review · Zokyo · 23 Nov 2021Fixed
The report gives no description here.
Open the reportLowA public function that could be declared externalRight to Privacy / Railgun / Nov2021 · Hacken · 3 Nov 2021Fixed
`public` functions that are never called by the contract should be declared `external` to save gas.
Open the reportLowMissing zero address validationRight to Privacy / Railgun / Nov2021 · Hacken · 3 Nov 2021Fixed
Accidentally setting `_vestLockImplementation` to zero-address could lead to contract out of work because it doesn’t have the ability to update it in any way.
Open the reportContracts1
| Address | Chain | Source code |
|---|---|---|
| 0xe76c6c83af64e4c60245d8c7de953df673a7a33d | Chain: Ethereum | Source code: Verified source |
Show this on your site
Is this your project? Show this record on your own website. The label states what the record holds, links to this page and updates by itself. It is free and needs no sign-in.
Content
Automatic: the three strongest facts of this project’s own record (its last audit and two more), highlighted. They update with the record. Picking a fact turns Automatic off.
Style
Format
<head><script src="https://widget.trustblock.run/project-widget.min.js" defer></script></head><body><divdata-tb-project-widgetdata-tb-project-slug="railgun"></div></body>
Paste the code where the label should appear. It uses no API credit and updates by itself.
Something wrong on this page? A missing report, a wrong date, a finding that was fixed since. Tell us and we check it against its source.
Tell us