Protocol knowledge base
Understand every layer of STONK.
A complete field guide to the tokenized-stock-backed reserve protocol—from a first bond to the final Timelock call.
Choose your path
12 guides. One coherent system.
Protocol guide
Tokens, bonds, staking, backing, oracles, user journeys and integration rules.
Users & integratorsSystem architecture
Kernel boundaries, modules, policies, units, oracle paths and bootstrap wiring.
EngineersFrontend UX reference
Implemented routes, data trust, transaction states, accessibility and release validation.
Frontend engineers & reviewersGovernance guide
Delegation, proposals, Timelock execution, guardian powers and verification.
DelegatesSecurity model
Invariants, trust assumptions, privileged failure modes and incident response.
Reviewers & usersSTK-001 risk acceptance
L2 sequencer failure mode, quantified exposure, compensating controls and strict-upgrade plan.
Reviewers & operatorsSecurity program
Threat model, evidence requirements, release workflow and continuous operations.
Security owners & reviewersMainnet launch gates
Blocking security, economic, control-plane, deployment and incident-readiness checks.
Launch approversLaunch mechanics and liquidity
Bounded market sequence, exposure limits, liquidity plan, halt rules and approvals.
Launch approvers & operatorsAdversarial review — 2026-07-16
Point-in-time findings, remediations, validation evidence and explicit review limitations.
Independent reviewersProduction runbook
Launch prerequisites, deployment invariants, release sequencing and runtime operations.
OperatorsDevelopment guide
Repository map, local workflows, quality gates and production boundaries.
ContributorsSystem map
Backing constrains issuance. Governance constrains control.
Reserve assets enter through bonds, value through validated Chainlink feeds, and bound new issuance. Delayed governance owns steady-state administration; a narrow guardian can only contain emergencies.
For users
Follow the bond, stake, governance and exit journeys without needing contract internals.
For integrators
Use explicit units, manifests, oracle state and failure rules to build safe clients.
For operators
Rehearse deployment, verify authority, monitor liveness and contain incidents.