A small beginning, on Pearl.

Nacre is an independent launchpad for creating and trading tokens on Pearl with native PRL.

Launching a pearl

Every launch has a fixed supply of 1 billion tokens with six decimals. All supply starts in the curve, with no creator allocation. The starting valuation targets $5,000 using BigONE’s PRL/USDT reference, assuming 1 USDT is approximately $1. Prices are validated against the bid and ask; an unavailable or illiquid feed stops new launches.

A launch signs a real Pearl transaction containing an NCR2 metadata commitment and 64 separate reserve outputs totalling 0.000384 PRL. Token metadata is pinned to IPFS. The launch reserve allocation is network dust, not the virtual liquidity used to calculate price. There is no separate token creation platform fee.

The curve and trading fees

The curve uses a constant-product calculation with virtual starting PRL reserves. Buys increase the price; sells reduce it. Only real PRL received from buys can be paid out to sellers. Virtual reserves cannot be withdrawn.

• Buy fee: 1% of the PRL trade amount, rounded up to an atomic unit.
• Sell fee: 1% of gross PRL proceeds, rounded up to an atomic unit.
• Pearl network fees are separate. Exact fees appear in the transaction review.
• Token outputs carry 0.000006 PRL of native network dust. Buys fund it; sells return released dust and subtract the network fee.

Quotes reserve conservatively against pending trades: buys include pending buys, and sells include pending sells. Pending trades on the opposite side are not treated as available liquidity. Amounts become fixed when signed, within your approved slippage. Pending liquidity can make a quote less favourable than the displayed market price.

How a trade settles

Your wallet signs locally. Nacre manages the market reserve keys, co-signs trades and records token ownership. The token output and PRL payment share one transaction. Each allocation can be spent once. Different pending trades use different confirmed inputs, so one rejected trade does not invalidate sibling transactions.

An approval fixes your input, minimum received, maximum network fee and a two-minute deadline. Choose a slippage tolerance before reviewing; the default is 5%. Tolerances up to 49% are available normally. More than 49%, up to 100%, requires an explicit high-slippage checkbox for that trade. Changing the amount, side, token or tolerance resets this acknowledgement. At 100%, minimum received is zero: a trade may execute for almost nothing in return. This does not bypass available liquidity, the network-fee ceiling, transaction validity or the two-minute deadline. Your browser may refresh the quote within those limits, but a worse price needs a new approval. Sell minimums apply to final PRL received after network fees.

Up to 64 independently funded trades can be pending per token, subject to available confirmed liquidity. Requests queue when allocations or funds are unavailable. Keep the approval tab open until submission. Pending holdings and the projected market cap update before confirmation; tokens, native change and reserve outputs become spendable after two confirmations. A single large sell can require several reserve allocations, reducing the space available for other simultaneous trades.

Existing signed NCR1 trades finish through their original path. Once they settle, the next approved trade can split that market’s shared reserve into independent allocations, retaining its token ID and balances. The split needs confirmations before its new allocations become available. Once submitted, a retry uses the exact same transaction. An uncertain network response does not create a replacement payment. Lost confirmations move affected trades out of confirmed history until they recover; unresolved reserve or indexer problems pause new submissions.

Leaving the website

Once the status says “Saved · safe to leave the website”, Nacre has durably saved your signed approval or transaction. Closing your browser does not cancel an accepted transaction. Return with the same wallet and open Your transactions to see pending and recent outcomes. Nacre checks confirmations when you return; chain confirmation itself does not require your browser to stay open.

Before that message, a request may still be waiting for liquidity or being submitted. Keep the approval tab open. If you lose the connection, check the existing request on return. The browser retains exact-transaction signatures for recovery, not your password. Recovering a saved transaction checks its identity and may broadcast the same bytes again, with no duplicate payment. Unsigned requests are never approved in the background; expired reviews require a new approval.

Wallets and token compatibility

The Nacre browser wallet supports launches, buys and sells. Oyster connects separately for native PRL transfers. Manage launched tokens in Nacre’s Collection. Other token standards and wallets are not interchangeable; use Oyster for native PRL transfers.

Browser recovery phrases are encrypted on-device with AES-GCM and a password-derived key. Keep your phrase and encrypted backup offline. Moving between localhost, a Vercel preview and the production hostname requires importing a backup on that origin; browser storage is not shared between websites.

Remembered devices

Keep unlocked on this device remembers Nacre for 14 days without storing your password. You still review and approve each transaction. Anyone using the remembered browser can approve transfers; Lock wallet removes remembered access across its tabs. The expiry is fixed, and browser backups never include the device unlock key.

Charts and valuation

Charts use confirmed Nacre trades only. Candles group observed trades into 1-hour, 4-hour or daily buckets. Empty intervals are not fabricated. The chart’s USD values use that token’s launch-time PRL reference; they are not a live USD price feed. The initial valuation does not represent $5,000 of funded liquidity.