Security & Transparency
Every claim Catapult makes is backed by on-chain evidence. The audit is public, the hash scheme is open-source, and anyone can reproduce every price sequence independently. Transparency isn't a promise — it's the protocol.
Key Takeaways
Security here is about audits, verification, and the limits users should still respect.
An audit is a strong signal, not a magic shield. Catapult points to Hashlock and Halborn work, and that is useful. Users should still read what was audited, check contract links, and understand that trading risk and smart contract risk are different things.
Users can verify the committed price path after a Turbo session closes. The system publishes a hash before trading and reveals the underlying data later. If the recomputed hash matches, the chart was not quietly changed mid-session.
Burned LP reduces the risk that a creator can pull liquidity after a token graduates. It does not make a token price risk-free, but it removes one of the classic launchpad failure modes: liquidity being removed after traders arrive.
Users can still lose money from leverage, volatility, bad timing, or weak demand for a token. Security checks help prove the rules were followed. They do not turn trading into a guaranteed outcome, and they should not be treated that way.
Proof and audit links
Related content
Every Turbo session's complete price sequence is hashed with Keccak-256 and published on-chain before any trade can execute. No one — including Catapult — can alter a single tick mid-session.
Algorithm: Keccak-256 · Published: Pre-session · Revealed: Post-session
The GBM engine is seeded by a 256-bit random value from Chainlink VRF v2. This is cryptographically verifiable randomness — no server can influence or predict the seed before it's generated.
Source: Chainlink VRF v2 · Type: 256-bit random · Verifiable: On-chain
The pricing algorithm and smart contracts have been audited by Hashlock, a professional blockchain security firm. The audit covers the GBM implementation, provably fair mechanics, and fee distribution logic.
Auditor: Hashlock · Scope: Pricing engine + contracts · Status: Passed
When a Hyper project graduates, the LP token is burned immediately. Permanently. No one — not the creator, not the team, not a multisig — can extract liquidity after graduation.
Mechanism: LP burn on graduation · Reversible: No · Enforced by: Smart contract
First-block buyers on graduated tokens face a penalty fee. This prevents bots from front-running the LP deployment and protects the traders who built the volume that earned graduation.
Target: Block-1 MEV bots · Method: Penalty fee · Scope: Graduation events
The full verification toolchain is open-source. Anyone can reproduce the complete price series post-session using the disclosed salt and raw price array — no special access required.
Tools: Open-source · Access: Public · Dependency: None
Find the session hash
Every live Turbo chart shows a "Provably Fair" section with its unique pre-committed hash.
Wait for session expiry
After the session closes, the salt and raw price array are disclosed on-chain automatically.
Reproduce the hash
Use the open-source tool: keccak256(ticksString + fairSalt + speedTicksInSecond). Compare with the published hash.
Confirm match
If hashes match, the session was provably fair. If they don't match, the session is provably compromised. The protocol cannot fake this.
FAQ
Creator Program
The security model is public. The proof is on-chain. Now let the math work for you.
