Contract interactions

Open a contract to see its read surface, any security assumptions or trust boundary, and each state-changing entrypoint with its caller, prerequisites, effects, and primary signals.

The entrypoint count is the number of state-changing function signatures a contract answers, counting each overload, each selector its fallback() routes to a delegate, and receive().

Table columns

Every contract page uses the same five columns.

Contract Purpose State-changing entrypoints
ZoltarQuestionData Creates immutable, content-addressed scalar or categorical questions and exposes their display metadata. 1
Zoltar Registers universe forks, charges the fork haircut, and mints branch-specific child REP. 6
ReputationToken Implements universe-specific ERC-20 REP, ERC-2612 permits, and ERC-3009 transfers while enforcing the supply ceiling maintained by Zoltar. 10
SecurityPoolFactory Deploys and registers portfolio question ledgers and their shared price feeds. 7
SecurityPool Question ledger for one shared portfolio, question and universe. 22
SecurityPoolForker Routes shared-portfolio question forks and lazy child question preparation. Child-game trust boundary 5
EscalationGame Escrows outcome REP, raises the running resolution cost, detects non-decision, and settles local or carried deposits. 21
OpenOraclePriceCoordinator Per-question adapter to the portfolio universe’s shared REP/ETH feed. 5
ShareToken Stores universe-aware ERC-1155 outcome shares and materializes a holder's persistent source entitlement in selected fork branches. 12