Zera FinanceZERA

Protocol notes / v0.1

Build the book before opening the market.

Zera Finance is a launchpad for crowdfunded binary prediction markets. These docs describe the current prelaunch contract model, its boundaries, and what remains before production.

01 / Overview

What Zera is

Zera does not begin with an empty order book. A creator proposes a binary question and opens a dedicated vault. Community collateral funds that vault first. Only a vault that reaches its target can move to the live-market phase.

Funding contributors receive zLP shares in proportion to accepted collateral. The current contracts cover proposal, crowdfunding, activation, failure, and refunds. Trading, resolution, buyback routing, and production staking are separate modules that are not yet implemented and must not be represented as live.

02 / Market lifecycle

Four explicit states

01

Funding

Collateral enters the vault and proportional zLP is minted.

02

Live

The target is reached and the vault is activated.

03

Failed

The deadline passes below target; contributors may reclaim collateral.

04

Resolved

Planned for the trading and oracle module; not in the current vault implementation.

03 / Contracts

Factory + isolated vaults

ZeraFactory.sol

Resolves protocol defaults, collects a configured listing fee, deploys one vault per proposal, and registers the market address.

ZeraMarketVault.sol

Holds one collateral asset, records contributions, mints transferable zLP shares, activates after its target, and permits refunds only after a failed funding round.

No mainnet addresses are published. A repository test suite is not a substitute for an independent security audit before value is deposited.

04 / Staking

Designed, not deployed

$ZERA does not have a production address yet. The intended design lets a creator burn or stake $ZERA to list a proposal, while a future fee router can buy $ZERA and distribute it under the final staking policy. The repository does not currently contain that staking or fee-router implementation, so the app keeps staking controls locked.

05 / Data and storage

Chain state is authoritative

Vault balances, shares, state transitions, and permissions live on-chain. Off-chain storage is for indexed market discovery, metadata, waitlist consent, and operational status only. It must never be treated as the source of truth for balances or payouts.

The planned Cloudflare D1 schema and API contract are documented in the repository. A production binding cannot be claimed until a database is created in the deployment account and its migration is applied.

06 / Prelaunch status

What remains

  • 01Finalize token, treasury, collateral, oracle, and buyback-router addresses.
  • 02Expand invariant and adversarial tests; complete an independent contract review.
  • 03Deploy and verify contracts on the target testnet before any mainnet deployment.
  • 04Create and migrate the production database binding; connect the indexer.
  • 05Replace locked app states only after every public address is documented.