Everything about NearPad, in one place.

Overview

NearPad is a launch and trading interface for user-created tokens on NEAR Protocol. A launch deploys a standards-compatible NEP‑141 token, creates a simple Rhea pool against wNEAR, supplies opening liquidity, locks the resulting LP shares, and performs an activation buy.

NearPad is non-custodial: the connected wallet authorizes launch, liquidity, trade, and claim transactions. Token names, symbols, and images are not unique, so always verify the 64-character token account ID.

Launch mechanism

The create screen fixes supply at one billion tokens with 18 decimals. A creator chooses token metadata and at least 1 NEAR of initial liquidity. Live NEAR/USD pricing determines how much supply enters the pool so the opening valuation targets approximately $3,000 FDV. The remaining supply is sent to the permanent token-reserve lock.

Launch requirements

Trading and pricing

Each token trades in its original Rhea pool against wNEAR. Buyers enter an amount in NEAR; the interface wraps it and routes wNEAR through the verified NearPad router. Sellers transfer the token into the same router. Quotes come from Rhea's get_return method.

Displayed values are estimates. The pool can move between quote and execution, and wallet/storage costs are separate from token output.

Graduation

NearPad displays virtual bonding-curve progress against a $9,000 market-cap marker. Reaching 100% marks the token as graduated in the interface.

Graduation does not migrate the token or create a second market. Trading continues in the same permanently locked Rhea pool before and after the marker. It is a progress indicator, not a quality, safety, or liquidity guarantee.

Fees and creator rewards

NearPad routed buys and sells charge an exact 1% fee on the input asset. The router assigns 70% of that fee to the token creator and 30% to protocol operations. Rhea's pool-level fee is separate and is currently configured at 25 basis points (0.25%).

Creator rewards may accrue in wNEAR from buys and in the launched token from sells. The creator profile reads get_claimable from the router and submits claim transactions from the creator's wallet.

Liquidity locks

After initial liquidity is added, NearPad transfers all creator-owned Rhea LP shares for the new pool to the published lock account. Registration is accepted only after the creator share balance is zero and the lock account has a positive share balance.

The token portion not needed for the verified ~$3K opening ratio is also transferred to the permanent reserve lock account. These are distinct controls: the reserve lock holds unused tokens, while the LP lock holds the pool shares.

Risk disclosures

NearPad tokens are user-created and experimental. Review the token account, creator, pool ID, holder concentration, liquidity, and wallet transaction preview before signing.

• Prices can move quickly; small pools can have high price impact.
• Names, tickers, artwork, and social links can be copied.
• NEAR RPCs, Rhea, wallets, indexers, and third-party pricing feeds can be delayed or unavailable.
• USD prices, market caps, charts, holder lists, and transaction labels are display estimates.
• Permanent locks reduce specific withdrawal risks but do not guarantee token value or trading demand.

NearPad provides software and data interfaces, not investment advice, custody, or a representation of token quality.

Network

Contracts and accounts

These mainnet accounts form the current NearPad integration surface. Treat all identifiers as case-sensitive strings and verify them onchain.

Reviewed token deployment

NearPad verifies the deployed code hash and confirms the token account has zero access keys before accepting it into the launch registry.

Reading token state

Every launch uses standard NEP‑141 view methods. Metadata and balances can be read directly from any NEAR RPC without relying on NearPad's database.

curl https://rpc.mainnet.fastnear.com \
  -H "Content-Type: application/json" \
  --data '{
    "jsonrpc":"2.0",
    "id":"nearpad-docs",
    "method":"query",
    "params":{
      "request_type":"call_function",
      "finality":"final",
      "account_id":"TOKEN_ACCOUNT",
      "method_name":"ft_metadata",
      "args_base64":"e30="
    }
  }'

The RPC response returns method bytes as integer values. Convert them to UTF‑8 and parse the resulting JSON.

Reading Rhea pools

NearPad stores the verified Rhea pool_id for each live launch. Use it with the exchange view methods to verify reserves, shares, and executable quotes.

const pool = await view("v2.ref-finance.near", "get_pool", {
  pool_id: POOL_ID
});

const tokenIndex = pool.token_account_ids.indexOf(TOKEN_ACCOUNT);
const nearIndex = pool.token_account_ids.indexOf("wrap.near");

const tokenReserve = Number(pool.amounts[tokenIndex]) / 1e18;
const nearReserve = Number(pool.amounts[nearIndex]) / 1e24;
const priceInNear = nearReserve / tokenReserve;

Pricing and market data

Normalize each reserve by its token decimals before calculating price. NearPad samples pool reserves into 5-minute, 1-hour, 6-hour, and 1-day candles. The USD interface multiplies the wNEAR price by live NEAR/USD.

priceNear = normalizedWnearReserve / normalizedTokenReserve
priceUsd  = priceNear * nearUsd
marketCapUsd = priceUsd * 1_000_000_000
liquidityUsd = normalizedWnearReserve * 2 * nearUsd
progress = min(1, marketCapUsd / 9_000)

For independent discovery, the verified pair URL follows https://dexscreener.com/near/refv1-POOL_ID. A pair may take time to appear after its first indexed swap.

Public read API

The application exposes JSON read endpoints under https://nearpad.family/launch-feed-v5/. They require no wallet connection. Use onchain contract calls when you need a trust-minimized source of truth.

fetch("https://nearpad.family/launch-feed-v5/launches?limit=24")
  .then((response) => response.json())
  .then(({ launches }) => {
    for (const token of launches) {
      console.log(token.contract_id, token.pool_id, token.status);
    }
  });

Responses use snake_case fields. A launch becomes fully tradable when status is pool_live and a numeric pool_id is present.

Indexing

A resilient indexer should combine registered launch data with direct NEAR and Rhea state.

1. Fetch launches and retain each token account, creator, block height, pool ID, and pair asset.
2. Verify NEP‑141 metadata and supply directly from the token account.
3. Read Rhea get_pool for current reserves and get_pool_shares for the permanent lock.
4. Index successful swaps involving the verified pool; derive direction from the input/output token.
5. Use token balance data for holders and normalize every quantity by its own decimals.

NearPad's trade feed synchronizes Rhea activity through NEAR transaction data with a minimum five-second sync window. Routed trades are additionally verified against the published router and pool registration. Consumers should tolerate temporary RPC and indexer delays.

Support and terms

For integration help, launch recovery, or verified platform questions, contact the NearPad community through Telegram or X. Never share a private key or seed phrase; NearPad support will not ask for one.

Onchain data is public and may be read independently. NearPad is provided as is, without warranties. Integrators are responsible for validating account IDs, decimals, pool state, transaction outcomes, and any information shown to their users. Do not imply an official partnership or endorsement without written permission.