Skip to main content

Security Report v1.0

Score: 8.3/10 — production-ready for Pioneer network.

After 10 prior audit rounds (94 findings, 78 fixed), the codebase is in good shape. Zero unsafe, no-panic policy enforced via CI, checked arithmetic everywhere, constant-time crypto. Not typical for a project this young.

No fund-loss vulnerabilities. No data corruption risks. Main gap is DoS resistance on the network layer (mostly addressed now).

Chain

Rust 2024, 50+ files, ~22,500+ LoC551 tests
Voyager DPoS+BFT, 1s blocks (v2.1.39+) — succeeded Pioneer PoA round-robin 2026-04-25Chain ID 7119
315M SRX max supply (post-v2 fork; 210M pre-fork)12 crates + 1 binary

Code Audit

Full report: SECURITY_AUDIT_V11.md

0 critical. 2 high (fee tracking split, timestamp non-determinism — neither is fund-loss). 5 medium. 7 low. 8 positive findings.

CategoryScore
Consensus8/10
State9/10
Transactions9/10
Networking7/10
API8/10
Code quality9/10

Attack Vectors

Full report: ATTACK_VECTORS.md

13 vectors analyzed. HIGH+HIGH quadrant empty. Biggest real risk: block withholding (validator offline → chain stall). P0 network items all fixed.

Already solid: tx signing, double spend protection, mempool caps, rate limiting, state trie proofs, chain_id replay protection, validator crypto verification.

Pentest

Full report: PENTEST_RESULTS.md

6/6 tests passed. RPC flood, P2P flood, tx spam, malformed input, double spend, oversized payloads — all handled correctly.

What to Fix

Done ✅: libp2p peer limit, per-IP rate limit, legacy TCP deprecated.

Next: Block skip mechanism, peer reputation, sync randomization, block-level signatures (for Voyager).

Context

The chain currently runs on 3 VPS with 3 validators under founder control. In this environment, actual risk from all findings is LOW. Risk increases as the chain opens to public validators and external traffic.