Internal security audit
Repository-local review of the Rust implementation and v3f authenticated testnet candidate. No external auditor was used. This report records verified behavior, known limitations and the current launch boundary.
The repository tests pass and the operator has verified the recorded results. This supports controlled testing only; it does not close the release-blocking cryptographic, consensus, persistence or operational findings.
Verification performed
- Passed:
cargo fmt --all -- --check - Passed:
cargo test --all-targets, with 43 passed, 0 failed and 6 intentionally ignored tests. - Passed:
cargo clippy --lib -- -D warnings - No known vulnerabilities:
cargo-audit audit - Dependency warning:
clear_on_drop 0.2.5is unmaintained throughbulletproofs. - Fuzz smoke runs for transaction, block and authorization decoders completed without observed crashes.
- Recorded proof benchmark: 500 proofs in 2,102.27 ms, or 237.84 proof verifications/s on the local Windows release build.
Findings
The two-row Ristretto proof binds destination ownership, commitment difference, key image and transaction message. Tests cover altered messages, images, ring members, responses and all signer positions. It is handwritten cryptography; tests cannot establish soundness, privacy or resistance to undiscovered attacks.
ChainV3::append applies every block transaction through cloned SpendState. The state checks reward maturity, ring lookup, anonymous proof verification, key-image replay, output uniqueness and atomic replacement before commit. The generic Transaction::validate_for_consensus(height) helper remains fail-closed because it has no output registry; it is not the v3f append path.
Output IDs, spent key images, reward maturity, transaction outputs, atomic batches and serialized recovery are implemented. Reorganization and crash behavior still require production operational review.
V3f checks the 90% miner / 10% treasury split, overflow, public fee commitments, reward issuance and the total supply cap. This is not yet a stable mainnet specification.
The candidate commits difficulty, calculates cumulative work, retargets within bounds and chooses a heavier validated snapshot. Parameters remain weak for public security; the inner reward proof of work is still low difficulty. A deterministic 10-block finality checkpoint rejects deeper reorgs.
Implemented: mutual Ed25519 nonce authentication, bounded peer discovery through static peers and seeds, 64 active connections, 8 attempts per IP per 60 seconds, bounded snapshots, transaction/block relay and timeouts. Still required for hardened operation: ban policy, durable concurrent single-writer coordination, monitoring, key rotation and incident procedures.
The release benchmark validated 237 anonymous transactions in 4,831.51 ms, or 49.05 confirmed tx/s on the local Windows build. The separate 500-proof verifier benchmark reached 2,274.16 proof verifications/s. The 150–250 confirmed tx/s target is not achieved by the complete pipeline; these are local measurements, not a public-network or mainnet throughput guarantee.
There is no public TENEBRA wallet currently exposed on the network site or available for production use. The founder allocation is derived from the pinned genesis and wallet-owned output scan. No private wallet material was accessed. It is not public transferable value and must not be represented as a live mainnet balance.
Project log / monetary log
TNB100,000,000 TNBLoading DEX price...Loading DEX valuation...10,000,000 TNB (10%)90,000,000 TNB (90%)90% miner / 10% treasury49.05 confirmed tx/sVerified network facts
962ea954fe2344106531c67b6fcf391f0ff74d3e3b349b1e41fe8703ba168932TNB / maximum 100,000,000 TNBseed1.tenebra-network.com:39453
seed2.tenebra-network.com:3945310-block checkpointLaunch boundary
The operator may proceed with an authenticated, unlisted controlled testnet after DNS, VPS firewalling, node keys, independent operators and monitoring are supplied. Do not bind the current node to an untrusted public interface and do not claim public mainnet or real TNB value. The implementation, audit results and conversation are recorded in CODEX-HANDOFF.md.
TNB emblem