OHWOO Protocol Architecture & Mechanics

OHWOO continuously captures protocol value flow, routes it through deterministic smart-contract modules, and redistributes incentives through event-triggered rounds.

Selection is verifiable: a submitted Merkle snapshot defines eligible weighted holders, and on-chain randomness resolves a deterministic winning index.

From meme attention to programmable redistribution.

• On-chain finality for round-critical state and settlement.
• Deterministic accounting for all split and payout paths.
• Composable off-chain automation without bypassing authority checks.
• Auditable proof path: snapshot root + interval check + Merkle proof.
• Operational resilience through fallback draw and timeout reset paths.

1. Harvest Token-2022 withheld taxes into swap tax vault.
2. Keeper executes swap path and forwards USDC to distributor.
3. Distributor splits USDC by configured BPS buckets.
4. Prize staging funds move into pool vault in valid pool window.
5. Snapshot locks round and stores Merkle root + total weight.
6. Draw request transitions to VRF waiting state.
7. VRF fulfillment writes winning index.
8. Claim verifies proof and settles winner/triggerer payout.

sequenceDiagram
  participant U as Users
  participant H as Harvest
  participant SW as Swap + Keeper
  participant D as Distributor
  participant P as Pool
  participant V as VRF

  U->>H: Transfer activity accumulates withheld tax
  H->>SW: Harvest to swap_tax_vault
  SW->>SW: Keeper executes OHO -> USDC swap
  SW->>D: forward_usdc to distributor_vault
  D->>D: Split by BPS
  D->>P: staging -> pool vault
  P->>P: submit_snapshot
  P->>P: draw_winner / keeperDraw
  P->>V: request randomness
  V->>P: fulfill_randomness
  P->>P: claim_prize + advance_round

Only one state path is valid per round: Open, SnapshotLocked, WaitingForVrf, ReadyToClaim.

On successful claim, the protocol advances round id and resets round-scoped fields such as Merkle root, winning index, triggerer, and deadline.

stateDiagram-v2
  [*] --> Open
  Open --> SnapshotLocked: submit_snapshot
  SnapshotLocked --> WaitingForVrf: draw_winner / keeperDraw
  WaitingForVrf --> ReadyToClaim: fulfill_randomness
  ReadyToClaim --> Open: claim_prize / claim_prize_no_triggerer
  WaitingForVrf --> Open: reset_pool (timeout)

Keeper orchestrates harvest, swap, distribute, liquidity, event checks, draw checks, and staking reward checks by cron-configured loops.

Event-driven snapshots can be triggered by holder growth, market cap growth, prize threshold, manual signal, or fallback timeout.

Community-first logic: when state enters SnapshotLocked, keeper waits `KEEPER_DRAW_DELAY_SEC` before fallback draw.

• Strict state gating in pool instructions prevents invalid transition calls.
• PDA and mint ownership checks protect vault routing paths.
• Merkle proof length cap and deterministic hashing reduce proof abuse.
• Under high network load, API updates may lag temporarily; on-chain transaction records remain the source of truth.
• Keeper restarts clear memory-only timers; persisted stores reduce disruption impact.

Think of every eligible wallet as owning a segment on one long number line. The segment length is that wallet's snapshot weight.

The protocol then generates one verifiable random number and drops it onto this number line. Whichever wallet segment contains that random index becomes the winner for the round.

This is why higher snapshot weight increases winning probability, while final selection remains random and verifiable on-chain.

OHWOO does not promise fixed yield.

It offers transparent value routing, verifiable random selection, and auditable redistribution as a long-running on-chain experiment.

Convert attention into transparent, programmable incentive cycles.

Please read and fully understand the following before participating: