Know the protocol.

Science is the starting point. Community is what stays.

xdesci.family is a community token launchpad on Robinhood Chain (4663). A market begins on a bonding curve against an eligible reserve. Once its target is reached, it becomes ready to graduate into a canonical Uniswap v4 pool.

Explore contains tokens launched through the platform. Cards give a market overview; Lab groups markets by lifecycle; Family Pulse shows confirmed activity. Stock references in the reserve selector are separate from the community tokens in Explore.

Choose a reserve. Give your community a name. Review before you sign.

1. Connect a compatible wallet on Robinhood Chain and enter the token name and ticker.
2. Choose an enabled reserve and prepare your public description and logo.
3. Review the fixed reserve target, creation charge, gas and wallet transaction. Stock launches require a fresh quote bound to that exact launch.
4. Confirm creation. The market appears after confirmed indexing; save public metadata through wallet-authenticated sign-in.

Admission does not guarantee a usable quote at every moment. Stale prices, issuer pauses, multiplier changes or rate limits can temporarily prevent a new stock launch. Current protocol eligibility and the launch form take precedence over this reference list. Pending catalog references are not supported reserves.

Each amount requires a fresh quote. Available liquidity and transfer restrictions can limit ETH routes. External pool fees are included in the quoted output and shown separately from the 2.5% application fee; network gas is additional. Selling for ETH may first require approval of the token being sold. An expired quote must be reviewed again.

A fixed allocation and a reserve target set at launch.

Each token mints 1 billion units once. Virtual reserves determine the curve price. Buys add net reserve after fees and release tokens; sells return tokens and remove reserve. The progress bar follows the actual net reserve, so sells can reduce progress while the curve is open.

PONS uses a 30-minute time-weighted reference. Stock pricing uses a short-lived signed reference derived from the reported bid, issuer multiplier and ETH reference. A launch reference is not an executable stock-market quote.

The final buy accepts only what is needed to reach the target. Excess native ETH is refunded; an ERC20 reserve pulls only the accepted amount. Unsold rounding dust from the curve allocation is burned at graduation.

Curve → Ready → Pool

Filling the target closes curve trading and moves the market to Ready. Graduation is a separate permissionless contract call. Automation attempts it when eligible; it is not bundled into the final buyer’s transaction. A failed graduation can be retried without undoing that buy or releasing reserved funds.

The collected net reserve and 250 million liquidity tokens move to the canonical v4 hook. The pool opens at the final curve price with a full-range liquidity position. Settlement rounding dust remains recorded and retained by the hook.

Token ownership and protocol governance are separate.

A launched token has no owner from creation. Its supply is minted once; there is no extra mint, transfer-tax, blacklist or upgrade function. Holders can burn their own tokens. Graduation does not require a later ownership-renunciation transaction.

The wider protocol retains separate administrative responsibilities: reserve configuration, stock-price signer administration and governance-initiated reward-recipient changes. These roles do not grant token ownership or access to withdraw the locked liquidity.

One trading fee. A clear creator and platform split.

The 2.5% application fee applies on buys and sells, on the curve and in the canonical v4 pool. Buys pay it from accepted reserve input; sells pay it from gross reserve output. Integer rounding follows the contracts. The entire 2.5% is not the creator’s payment.

Creating a market has a separate $3 charge, paid in ETH using the eligible ETH/USD reference and sent to the treasury. Network gas is additional.

Eligible rewards can be distributed automatically or claimed by the credited wallet. Repeat automated payouts for the same wallet and reserve have a 300-second cooldown after a successful payout. This is a gas throttle, not a five-minute delivery guarantee. Unpaid credits remain claimable.

A new reward recipient receives future rewards, not past credits.

• The current reward recipient may propose another wallet. That wallet must accept the current proposal.
• Governance may schedule a community takeover (CTO). It has a 48-hour delay and requires acceptance by the proposed recipient.
• Acceptance changes future fee accruals. Already credited rewards remain with the wallet that earned them.

The original creator address, token balances, reserve and permanent liquidity are unchanged by a recipient handover. A social announcement alone does not change the onchain recipient.

A wallet identity, with a name your family can recognize.

Your optional family ID and avatar are publicly linked to your wallet. IDs use 3–24 lowercase letters, digits or underscores and start with a letter. Changing an ID releases its old spelling. A matching wallet session is required to save changes; signing in is not a token-transfer approval.

Token logos support static raster files, GIF and animated WebP. Animation input is limited to 3 MiB, 80 frames, 10 seconds and 16 million pixels across all frames. Accepted animations are normalized to WebP within 256 pixels and 1 MiB; an animation that cannot be preserved is rejected.

Images are decoded and re-encoded to strip EXIF/XMP metadata. This cannot hide text, faces or other information visible in the image. A hosted logo is public metadata, not image bytes inside the token contract or automatic registration with external wallets and explorers.

Fast updates, with confirmed history underneath.

A shared event stream updates displayed market data without manual refresh. Canonical indexing remains the basis for launches, fee balances and transaction records. A fast chart update does not make an unconfirmed transaction final; connection or stale-source conditions are surfaced in the interface.

Prices and MCAP/FDV are shown in USD using the relevant reserve reference. A USD reference can be delayed even when onchain activity is current. MCAP/FDV uses the full protocol allocation, not only tokens sold on the curve.

Quiet chart periods may carry forward the last close with zero volume. They do not represent extra swaps. Volume uses actual exchanged amounts. The migration guide is a target reference, not a promised future valuation. Wallet quotes still enforce current state, slippage and deadlines.

Public, versioned data. Exact amounts. Verifiable contracts.

Start with the V1 manifest for deployed contract bindings and ABI discovery. Read canonical checkpoints, admitted reserve assets, launched markets and confirmed events through the versioned API. Raw token amounts are decimal strings; apply the declared decimals before display.

Event block bounds are inclusive, with at most 10,000 blocks per range and 500 events per page. Keep the same block bounds while following each returned cursor; after completion, continue at the previous end block plus one. Preserve checkpoint hashes and restart a range if a reorganization invalidates its snapshot. Handle errors and HTTP 429 responses, and respect retry instructions.

Pseudonymous wallets. Deliberate public sharing.

Wallet access is pseudonymous, not anonymous. Transactions, balances, creators, reward claims and CTO changes are public blockchain records. Other people can connect those records with information shared elsewhere.

The application stores public profiles, launch metadata, normalized images, indexed records and the data needed for sign-in and abuse prevention. Sign-in uses an HttpOnly session cookie lasting up to 24 hours. Language and interface choices can be stored in your browser; a saved language choice takes precedence over the connection’s country signal.

IP-based rate limits use scoped, daily keyed identifiers rather than storing raw IP addresses in the application’s rate-limit table. Expired buckets are cleaned up by the service. The site serves its fonts locally. Hosting, database, network and wallet providers may separately process connection information under their own policies; this does not establish their logging or retention practices.

Editing or deleting a profile does not erase previously cached images, screenshots or copies held by others. Avoid putting private information in a name, avatar, description or link. Never share a recovery phrase or private key. This section describes product behavior; it does not promise full anonymity or instant erasure from external services.

Verify the address. Follow the published record.

The platform token is a separate, deferred release. Its address will be announced only after verification. Do not assume a similarly named token is official. The V3 fee vault does not allocate or execute automatic buybacks. Any future platform-token buyback is a manual treasury decision.

Community-token trading does not cause that token to be bought back or burned by the fee vault. Follow the official social links shown in the application, and verify contract identities using the protocol manifest.