POOLZPAD Execution locked
← Contract architecture

POOLZ PAD V1 · testnet preflight

Rehearsal prepared.
Execution locked.

The Robinhood Chain testnet package is ready for controlled review. It defines how fee collection, the 40/40/20 protocol split, vault accounting and transaction evidence will be proven without touching production funds.

Review the rehearsal ↓Read-only preflight · unaudited

No wallet connection · no signing · no broadcast · no production deployment

Network46630Robinhood Chain Testnet
Base V1 contracts7checksum-bound artifacts
Recorded transactions0execution is not authorized
Protocol route40 / 40 / 20fixed V1 fee configuration

Seven-stage rehearsal

Prepared offline.
Proven onchain.

Every transactional stage stays blocked until it has an explicit approval. This keeps the public roadmap visible without turning a preview into an uncontrolled deployment surface.

01Review ready

Offline preflight

Chain isolation, compiled artifacts, deployment order and safety assertions are packaged for review.

02Approval required

Test-only funding

A bounded faucet step will fund the approved test account only after explicit authorization.

03Approval required

Temporary v4 stack

A disposable test-only Uniswap v4 stack is prepared so the rehearsal does not depend on production infrastructure.

04Approval required

Base contracts

Seven Base V1 contract artifacts are ready for a controlled deployment with approved constructor values.

05Approval required

Pool initialization

The POOLZ pool, hook and routing boundaries will be initialized only inside the approved test environment.

06Approval required

Functional rehearsal

A small, bounded swap will demonstrate fee collection, splitting, vault accounting and attribution end to end.

07Review ready

Evidence closure

Finalized receipts will be reconciled before any result is promoted into the public evidence record.

Illustrative fee rehearsal

One test swap.
Every path accounted for.

A 100-unit example makes the intended routing readable before the first authorized transaction. These are configuration examples—not collected funds or live results.

Illustrative values
Example trade100.00illustrative units
Liquidity providers0.250.25% LP fee
Protocol accounting1.001.00% protocol fee
Buyback path0.4040% of protocol fee
Ecosystem path0.4040% of protocol fee
Trader-growth path0.2020% of protocol fee

Public evidence record

Readable status.
Strict proof.

The page distinguishes prepared configuration from observed results. No transaction hash, amount or outcome is presented as live before it can be independently checked.

01
NetworkRobinhood Chain Testnet
CHAIN 46630
02
Base V1 artifactsSeven contract artifacts packaged
PREPARED
03
Fee route1.25% total · 1.00% protocol
PREPARED
04
Protocol split40% buyback · 40% ecosystem · 20% trader growth
PREPARED
05
TransactionsNo authorized test transaction yet
0 RECORDED
06
Production addressesNone published or implied
0 LIVE

Transaction lifecycle

From approval
to public proof.

A result is not treated as complete when a transaction is merely sent. It moves through a fixed evidence sequence before publication.

  1. 01

    Prepared

    Artifacts and approved inputs are checksum-bound before execution.

  2. 02

    Submitted

    The authorized test transaction receives a public network hash.

  3. 03

    Included

    The transaction is observed in a Robinhood testnet block.

  4. 04

    Finalized

    The configured confirmation boundary has passed without conflict.

  5. 05

    Reconciled

    Expected and observed fee movements agree before publication.

Current release boundary

Ready to rehearse.
Not yet executed.

The safe next step is one explicitly authorized, bounded testnet run. Once it is finalized and reconciled, this page can replace prepared states with public transaction evidence.

Review architecture →