Checked, controlled, and on the record.
StonkPress is tested on every change, watched while live, and controlled by rules published on this page. Here is how the contracts are checked, who controls them, and where their code comes from. The risks of using the protocol are set out under Security & Risks.
How the contracts are checked
- A full test suite. About 50 test files, with fuzz tests that throw thousands of random inputs at the contracts and an invariant test that checks the rules which must always hold. The launch script itself runs end to end inside the tests.
- On every change. The suite runs again, the fuzz tests repeat with 5,000 random inputs each, and Slither scans the code for known classes of bug.
- Watched while live. A monitor follows the deployed contracts and alerts the team on every epoch, a circuit-breaker trip or a pause.
Where the audit stands
Phase Zero, the first and bounded phase of operation, is verified with automated and AI-led review and the controls on this page. StonkPress's own contracts have not yet had a formal human audit, which is a later gate.
Who controls what
| Role | What it is | What it can do |
|---|---|---|
| Governance multisig | A Safe that needs 2 of its 5 signers | Owns and operates the contracts. Holds the Ink Reserve and the DAO fund. |
| Emergency guardian | A second Safe, with the same five signers, that also needs 2 of them | Pauses epochs, staking, the reward pools and oPLATE exercise. It cannot move funds or change parameters. |
- No single key can act alone. Every admin action needs two signatures.
- Every pause has a limit. After 72 hours anyone can lift a pause of epochs, staking or the reward pools, and an oPLATE exercise pause ends by itself. The full rules are under governance risk.
- The protocol does not depend on one operator. Anyone can feed the price and advance an epoch.
- There is no timelock in Phase Zero. An admin change takes effect as soon as two signers approve it.
- Every address is public, under contract addresses.
Where the code comes from
StonkPress builds on designs already used on-chain, changed where a ratio against SPY needs it.
- Epochs, staking and the PAPER, PLATE and RECEIPT tokens follow an established algorithmic-token design, changed to target a ratio against SPY.
- The genesis farm and the reward pool are MasterChef-style reward pools, with Permit2 deposits, an emergency pause, a check that emissions never exceed the PAPER they were funded with, and referrals, which are off.
- oPLATE is adapted from OptionTokenV4, the option-token contract in the Lynex and Orvex code base, changed to take SPY as payment and to exercise straight into staking.
- Bonds run on ApeBond's own contracts. Bond positions follow ERC-5725, the standard for transferable vesting NFTs, which StonkPress's founder co-authored.
- Token and access-control building blocks come from OpenZeppelin.
Audits of the original code do not carry over to the adapted versions, so until StonkPress's own audit, its contracts stand on the checks and controls above.