Where is the official code published?
In the pulsechaincom group on GitLab — gitlab.com/pulsechaincom — which pulsechain.com already linked in 2021 and still links today. It held 23 public projects on 2026-10-17. A GitHub organisation of the same name has one public repository, a 2022 fork of Sourcify.
There is no separate repository for the smart contracts of HEX, PulseX or the bridge. Their sources are published as verified code on the block explorers, which compile the source and compare it with the deployed bytecode.
Which repositories run the chain?
| Repository | What it is | Licence | Commit checked (date) |
|---|---|---|---|
| go-pulse | Execution client, fork of go-ethereum; contains the fork logic | LGPL-3.0-or-later (library), GPL-3.0-or-later (cmd/) |
a224d91967a31c2c3080a8f75784d8de13c80b7b (2025-09-30) |
| erigon-pulse | Alternative execution client, fork of Erigon | LGPL-3.0-or-later, GPL-3.0-or-later |
2e36a257b16267acbbcfacc2b78b2b0cc4f2cba7 (2024-02-19) |
| lighthouse-pulse | Consensus client, fork of Lighthouse; holds the PulseChain chain spec | Apache-2.0 |
e671e9dbf55f132e3189f618d2779a133f583086 (2026-03-30) |
| prysm-pulse | Alternative consensus client, fork of Prysm | GPL-3.0 |
992805a5f6edb4196ac7892bd6fbcdea8baa66d4 (2024-04-05) |
| compressed-allocations | Sacrifice credit data, file format and decoder (tag Mainnet) |
None declared | e12960125cec0da66d367a5e82209940f387669b (2023-05-11) |
| staking-deposit-cli | Validator key and deposit-data tool | CC0-1.0 |
a46f9e1080c3a7428ca4f3c7cc230a8ad0fa4e04 (2025-09-03) |
| pulsechain-mainnet | Mainnet node setup scripts and documentation | None declared | 192dafa9e99b33eab2456edbaae93159a34bb8a5 (2026-07-22) |
| pulsechain-testnet | Testnet V4 node resources and testnet history | None declared | 014a90e6fe22f13b368cf336847ed49aa6079fd3 (2023-06-23) |
“Commit checked” is the head of the default branch on 2026-10-17; the link opens the repository in exactly that state. Licences are given as SPDX identifiers from each repository’s licence file; for go-pulse and erigon-pulse the source headers grant version 3 “or any later version”, while for prysm-pulse, blockscout and ethstats-server the files alone do not say whether later versions apply. “None declared” means the repository has no licence file in its root.
Can I run the official websites myself?
Yes. Five repositories publish self-hostable builds of the official front ends — useful when a site is down, or to rule out a tampered copy:
| Repository | Runs a local copy of | Commit checked (date) |
|---|---|---|
| pulsechain-bridge-server | bridge.pulsechain.com | ba083c1d710adc311b046725275829820ac847c3 (2026-08-26) |
| pulsechain-staking-launchpad-server | launchpad.pulsechain.com | db0cb078c7560a3f0368ad37373e71baa5e38894 (2026-05-17) |
| pulsechain-explorer-server | scan.pulsechain.com (front end) | 935f5a647ce20d0dd9700e45eac79bec43ea2ff9 (2025-09-30) |
| pulsex-server | app.pulsex.com | e5733524b69ef3e394132e00b49663a784ee8f97 (2026-07-15) |
| hex-server | go.hex.com (HEX staking interface) | 2b8909870f905e12ab8e50ed1877773c3b4ab273 (2026-07-21) |
None of the five declares a licence. The bridge and PulseX builds also contain the official contract addresses in their configuration, so any address quoted for the bridge or PulseX can be checked against them.
What else is in the group?
| Repository | What it is | Licence | Commit checked (date) |
|---|---|---|---|
| erigon-lib | Library used by erigon-pulse | Apache-2.0 |
379a0b22241d1765ab8d7b9589c37218669571a3 (2023-06-27) |
| erigon-pulse-snapshot | Snapshot data for syncing erigon-pulse | None declared | 1858bd4a158d18abba50c4be316e6605eaf15b78 (2023-04-05) |
| ethereum_ssz | SSZ encoding library used by lighthouse-pulse | Apache-2.0 |
bf50584d4706a019a1cf72c0059d85d0932824c0 (2024-04-29) |
| ssz_types | SSZ types library used by lighthouse-pulse | Apache-2.0 |
aa3dbb6adeef5c889475179d0e651cffd997c270 (2024-05-02) |
| blockscout | Fork of the Blockscout explorer (older branch) | GPL-3.0 |
21bed05ab8f2a30d07f6033e03482344f5659c43 (2022-03-19) |
| ethhex-uniswap-server | Self-hostable ETH/HEX Uniswap front end | None declared | b7676e2b964762514ed99f04046e23db4f4729a4 (2023-12-08) |
| ethstats-server | Network statistics dashboard server | GPL-3.0 (licence file), LGPL-3.0 (package.json) |
c49c124e57b5f7991a67c673e1a835e3954f3257 (2021-09-16) |
| gas-estimation | Gas price estimation helper | MIT |
c74ba4a61738280820b686b5f29986b471148045 (2024-03-11) |
| pls-faucet | Testnet PLS faucet | MIT |
3d82626640c182ed2f1fafc5b41e0cf300ea97b0 (2022-03-22) |
| pulsechain-cli | Command-line tool for inspecting a PulseChain network | MIT |
2e496d9f189fc7f17be59c6aeb5b82089f33b91d (2022-03-25) |
| sourcify (GitHub) | Fork of the Sourcify contract verifier | MIT |
ec4bd84df4c1df21ae012e74213a70470f6df7f5 (2022-02-16) |
Where are the verified contracts?
PulseChain (links open PulseScan):
Ethereum:
“Partial” means the executable code matches the published source while the embedded metadata hash does not; “Verified” means the explorer shows verified source without a recorded match level. HEX has the same runtime bytecode on both chains — SHA-256 331e6384b4acbab47e393ee5f85290cbdd8783be817b52643441c02bc0164511 — which you can recompute with the script on Verify it yourself. Remember that one address can hold different contracts on the two chains: 0x1715a3E4A142d8b698131108995174F37aEBA10D is a PulseX factory on PulseChain and a bridge mediator on Ethereum.
Which audits are published?
| Audit | Scope | Date | Result |
|---|---|---|---|
| CoinFabrik security audit | HEX contracts | 2019-12 | 0 critical, 0 medium, 3 minor issues, 4 enhancements |
| CoinFabrik economics audit | HEX staking economics | 2019-10 | Confirms longer stakes pay better for realistic parameters; one unrealistic edge case documented |
| ChainSecurity (HEX) | HEX contracts | — | Named on hex.com; no report published as of 2026-10-17 |
| ChainSecurity | Upstream OmniBridge (POA Network) | 2021-04-27 | Code assessment of the bridge’s code family |
| ChainSecurity, via Gnosis Chain | Upstream OmniBridge v6.0 | 2021-09-07 | 0 critical, 1 high (partially corrected), 3 medium, 13 low |
| Quantstamp, via Gnosis Chain | Upstream TokenBridge 5.4.1 | 2020-11-06 | 22 issues, 0 high, 0 medium |
No audit was found for the PulseChain bridge deployment itself, for PulseX or for the PLSX buy-and-burn contract, and there is no evidence of an ABDK audit of HEX (all as of 2026-10-17). The upstream bridge audits cover the code family the bridge is built on, not its PulseChain deployment — see The bridge.