Rezo Fun Product documentation · v1.0Docs · v1.0
Draft specification Whitelist
Contents · 20 sections
  1. 01Overview
  2. 02Network and Deployment
  3. 03Product Architecture
  4. 04Launching a Token
  5. 05Token Standard and Safety
  6. 06Liquidity and Trading
  7. 07Token Discovery and Milestones
  8. 08Trading Fees
  9. 09Creator Revenue
  10. 10Holder Rewards
  11. 11REZO Points
  12. 12Portfolio and Analytics
  13. 13Bridge and Asset Access
  14. 14Protocol Treasury
  15. 15Launch Protection
  16. 16Creator Studio
  17. 17Builder Integrations
  18. 18Smart Contracts and Events
  19. 19Public API and Indexing
  20. 20Security and Risk Disclosures

REZO FUN

Launchpad and trading protocol

REZO brings token creation, discovery, trading, creator revenue, holder benefits and community participation into one coherent onchain experience.

Document
Product documentation
Version
1.0 · Draft specification
Date
November 2026
Website
rezofun.xyz
Target ecosystem
Zero blockchain, within the LayerZero ecosystem
Status

Product blueprint for website documentation and engineering planning. Features, contract mechanics, fee parameters and deployments are proposals unless separately verified and announced.

REZO is a proposed non-custodial token launchpad and trading interface designed for the Zero ecosystem. Its purpose is to make launching and exploring onchain tokens approachable without hiding the risks or mechanics of their markets.

Core principles

  • Open creation. Eligible wallets can create standard tokens through a guided flow.
  • Transparent trading. Prices, fees, slippage and liquidity details are visible before signing.
  • Creator participation. Launches can direct an explicitly defined share of eligible trading fees to creators or recipients.
  • Holder benefits. Supported tokens may distribute a portion of eligible fees to holders.
  • Community activity. REZO Points recognize qualifying participation; points do not guarantee a token distribution.

REZO targets Zero, the blockchain associated with the LayerZero ecosystem. LayerZero interoperability messaging and Zero execution are distinct components. ATLAS is a separate trading infrastructure and is not assumed to power REZO pools or token launches.

Before any Zero deployment, the team must verify network RPC, chain ID, explorer, gas asset, contract execution environment, supported token standards, liquidity venues, wallet support and available bridging routes. No unverified addresses or network values are included in this document.

Testing strategy

  • Build a self-contained prototype on a supported EVM testnet if Zero public tooling is not ready.
  • Run integration tests for launch atomicity, swap quotes, fee distribution, rewards accounting and indexer reorganization handling.
  • Revalidate every assumption and redeploy independently on Zero after tooling is available.

The proposed REZO stack has five logical layers:

  1. Web application and wallet connection.
  2. Launch orchestration and token factory.
  3. Pool and market adapter.
  4. Fee accounting, claims and points.
  5. Indexing and public read APIs.

A pool-based launch design is the preferred initial direction, subject to an available and audited AMM on the target chain. A market adapter isolates the launch logic from any particular exchange implementation.

The Create Token experience collects a name, symbol, description, image, social links, token supply, quote asset, trading fee configuration and optional first purchase. The wallet previews all irreversible settings before signing.

Proposed launch lifecycle

  1. Validate metadata and supported quote assets.
  2. Deploy a fixed-supply token using the REZO Factory.
  3. Create or initialize a market using the configured liquidity adapter.
  4. Allocate the designated launch inventory to the market and apply the selected liquidity protection mechanism.
  5. Optionally execute a creator purchase when supported safely and atomically.
  6. Emit a canonical launch event and publish the token page.
Atomic execution is a design goal, not a live guarantee. If the target market infrastructure cannot support one-transaction deployment, the UI must disclose each step and its failure and recovery behavior.

Standard REZO launch tokens are proposed as fixed-supply, non-rebasing fungible tokens with no transfer tax, hidden mint, blacklist or owner-controlled pause. Any exceptional launch category must be visibly marked and reviewed under separate rules.

Token name, ticker, artwork and links are user-submitted and do not imply endorsement. Contract addresses are the authoritative token identifiers. REZO should show verified contract links and clear warnings about impersonation.

The intended default is an immediately tradable pool rather than a bonding curve with later liquidity migration. Initial inventory can be committed to a pool at launch. The exact lock implementation, price range, capital requirements and third-party LP rights depend on the chosen AMM.

Wording rule Never describe liquidity as permanently locked until the audited deployed contracts make removal impossible. Third-party liquidity may have different withdrawal rights and must be distinguished from launch liquidity.

Trading interface

  • Buy and Sell panels with quote asset selection.
  • Expected output, price impact, slippage tolerance, network cost and total fees.
  • Token chart, liquidity, volume, holders and recent transactions.
  • Transaction states: wallet confirmation, submitted, pending, confirmed and failed.

Explore sorts tokens into New, Trending, Established and Watchlist. A REZO milestone indicates a measurable market event; it does not automatically move liquidity or promise exchange listing.

Proposed milestone signals include age, verified liquidity threshold, unique active traders and sustained activity over a time window. Thresholds should be published before activation and must not be marketed as guarantees of token quality.

REZO may offer simple creator-selectable fee tiers. The following is an illustrative proposal and is not a live fee schedule. Fees are expressed as a percentage of trade notional, not as a percentage of collected fees.

Illustrative fee tiers
Example tier Protocol share Creator and holder stream
1.0%0.25%0.75%
2.0%0.25%1.75%
3.0%0.25%2.75%
Any liquidity provider fee, router fee or external exchange fee must be separately disclosed and incorporated in the final quote. The sum of fee components must be verified by contract tests.

At launch, the creator can choose a fee recipient wallet or, when enabled, a split between multiple recipients. Revenue accrues in the supported quote asset and becomes claimable according to the deployed contract rules.

Creator Studio should show accrued, claimed and pending balances, supported recipient settings, launch performance and a transaction-level accounting history. Changes to recipient configuration should be governed by explicit, documented permissions.

For supported launches, creators may route a defined portion of their fee stream to eligible token holders. Reward entitlement should be based on auditable accounting that prevents double claims and accounts for token transfers.

The distribution design must specify reward currency, snapshots or time-weighted balances, excluded balances, minimum claim thresholds and gas costs. A holder is never guaranteed earnings; rewards depend on actual eligible activity and collected fees.

REZO Points is a participation layer for qualifying activity. The public-facing product uses Points and Rewards terminology rather than promising any future token distribution.

Potential earning categories

  • Qualifying trading activity, subject to daily caps and minimum holding periods.
  • Launching tokens that meet published activity and quality thresholds.
  • Consistent participation over distinct days.
  • Verified community tasks, when enabled.

Anti-abuse controls may include wallet clustering, self-trading detection, creator self-buy exclusions, suspicious circular trades, volume caps and delayed finalization. Points are not transferable, redeemable or monetary claims unless explicit terms later say otherwise.

Portfolio provides wallet balances, cost-basis estimates where data permits, realized and unrealized P&L estimates, trade history, created tokens, claimable fees and REZO Points. Figures must state their pricing source and calculation limitations.

Bridge is a proposed interface for supported external bridging providers and LayerZero-enabled routes, where available. REZO should not claim to operate a native bridge without verified contracts and security review.

Every route should show source/destination networks, token, estimated received amount, fees, expected processing time, approvals and third-party risk. Unsupported routes must be disabled rather than simulated.

A protocol treasury may collect the published protocol fee share and use it for security, operations, ecosystem incentives and development. Buyback or burn mechanisms are not assumed and require separately approved token economics and public disclosures.

REZO can explore configurable launch protection, such as transaction-size limits, a transparent time-decaying launch surcharge or other anti-bot controls. Each mechanism has tradeoffs and can disadvantage ordinary users.

No 99% initial fee or other extreme parameter is proposed as a default. If implemented, protections must be opt-in or clearly disclosed, bounded, audited and displayed in the swap quote.

Creator Studio is the launch management area: token metadata, fee recipient configuration, launch status, holder reward settings, analytics, claim history and public contract references. It must distinguish editable offchain profile data from immutable onchain launch terms.

REZO may offer a developer programme for wallets, terminals and apps that integrate its token discovery or launch flows. Attribution should be deterministic and permissionless where possible, with transparent terms and fraud protections. No revenue-sharing percentage is committed in this draft.

Proposed modules: RezoFactory, RezoToken, MarketAdapter, FeeVault, RewardDistributor and Registry. Names are conceptual and do not refer to deployed contracts.

Illustrative events

Event Signature
TokenCreatedtoken, creator, supply, metadataURI
MarketCreatedtoken, quoteAsset, marketAddress
TradeObservedmarket, trader, amountIn, amountOut
emitted or indexed from market source
FeesAccruedmarket, asset, protocolAmount, recipientAmount
RewardsClaimedaccount, asset, amount
MilestoneReachedtoken, milestoneId
Final ABIs, addresses, event signatures, rounding behavior and access controls must be generated from audited deployed code.

A read-only API may expose tokens, market statistics, recent trades, wallet positions, points and creator fee balances.

Suggested routes

# proposed paths, not active endpoints
GET /v1/tokens
GET /v1/tokens/{address}
GET /v1/markets/{address}/trades
GET /v1/wallets/{address}/activity

Indexers must handle chain reorganizations, idempotent event processing, token decimal differences, pool state reconciliation and clearly labelled stale data. Onchain state remains authoritative.

  • All trades and launches involve smart contract, liquidity, execution and token-price risks.
  • A non-custodial interface does not remove third-party contract or bridge risks.
  • No price floor, guaranteed liquidity, guaranteed reward or token appreciation is promised.
  • A security audit, public bug reporting channel, monitoring and incident response process are prerequisites for a responsible production launch.
  • The interface must explain approvals, contract permissions, slippage and irrevocable transactions.