Core Components

The 0–100 Engine is designed as a minimal, auditable set of onchain programs. Each program has a clearly defined role and authority, ensuring deterministic flows with no hidden logic.

​Core Components

  • FundingPool

    • Stores configuration (hard cap H, per-wallet cap C, ticket size τ, funding window, LP window, status).

    • Accepts deposits in multiples of τ.

    • Issues ticket receipts.

  • RandomSelection

    • Uses a random block-hash seed to fairly sample tickets if the pool is oversubscribed.

    • Selection is uniform at the ticket level; unapproved deposits are prepared for refund.

    • Emits approvals and refund readiness.

  • DistributionVault

    • Holds project tokens.

    • Maps approved amounts to Sale allocations.

    • Opens claims before LP deployment.

  • LPDeployer

    • Verifies canonical pool commitment (hash of LP parameters).

    • Probabilistic blockhash trigger enables permissionless pool initialization (Raydium baseline).

  • FeeCollector & Buyback

    • Accrues platform fees.

    • Splits them between Xyber Treasury and the Creator payout vault.

    • Executes market buybacks of $XYBER.

​Security Considerations

Security in 0–100 is not an afterthought — it is built into the mechanics. The protocol is fully non-custodial: users always interact directly with on-chain programs, and funds never pass through any centralized wallet or administrator. Deposits, claims, and refunds are permissionless and transparent.

All liquidity raised through a launch is permanently locked in the DEX pool. There are no hidden keys, no team-controlled backdoors, and no possibility for a creator to withdraw liquidity after listing. This eliminates the most common rug-pull vector in token launches and ensures that every market starts on a stable foundation.

Launch timing is determined by probabilistic block-hash randomness, which makes the exact deployment moment unpredictable. Neither contributors, nor creators, nor even the protocol itself can know or influence when the pool goes live. Combined with precommitted pool parameters, this guarantees that every launch happens exactly as promised, without the risk of fake or manipulated pools.

Overflow handling is equally robust. If a launch is oversubscribed, surplus deposits are automatically prepared for refund. Refunds are pull-based and executable by anyone, meaning contributors can always recover unused funds without relying on a third party.

Finally, the economic flows are transparent and verifiable on-chain. Platform fees automatically buy back $XYBER and support the treasury, while creator rewards are tied only to trading activity after listing. There are no hidden allocations, no silent emissions, and no opaque reserves — only the rules encoded in the programs themselves.

Last updated