Docs
shard is a permissionless token launchpad on NEAR. A launch is one transaction that creates a token at its own account and puts the entire supply into a locked Rhea pool, so the token trades from the first block with nothing to graduate and nothing to pull.
Last updated 25 September 2026. Current network: NEAR mainnet.
The three contracts
| Contract | Account | What it does |
|---|---|---|
| Factory | shardpad.near | Creates the token account, publishes the token code to it, opens the Rhea pool, hands the supply to the locker and keeps the list of launches. Owned by the shard team and upgradable; it never holds a pool position or fees. |
| Token | <ticker>.shardpad.near | A standard NEP-141 token with NEP-148 metadata, 18 decimals, fixed supply of 1,000,000,000. The code is a global contract referenced by hash, so every launch runs identical bytes. No mint, no owner, no pause, no blacklist, no transfer fee. The account keeps zero access keys. |
| Locker | lock.shardpad.near | Owns every pool position. Its only action on the pool is claiming fees. It has no function that removes liquidity by amount, no approvals, no withdraw. |
Rhea DCL: dclv2.ref-labs.near. Pair assets on mainnet: wNEAR wrap.near, native USDC 17208628f84f5d6ad33f0da3bbbeb27ffcb398eac501a31bd6ad2011e36133a1, ZEC zec.omft.near.
Account names are the proof
Only the factory can create accounts under shardpad.near. A token whose account is something.shardpad.near was launched here, with the code and the lock described on this page. A token with the same name or logo at a different account was not. The full account is shown everywhere a token appears, on purpose.
What a launch does
- Creates
<ticker>.shardpad.nearand attaches the token code by hash. - Mints the full supply to the locker and registers the creator and the platform on the token.
- Creates the Rhea DCL pool for token / pair asset at the 1% fee tier, or reuses it if it exists.
- The locker deposits the whole supply into the pool as a single-sided range that starts just above the launch price and has no ceiling, and records the position under its own name.
If a later step fails, the launch parks and anyone can call resume. Only a failure at the very first step refunds the creator and frees the ticker, because nothing irreversible has happened yet.
Price, supply and the first buy
- Supply: 1,000,000,000 tokens, all of it in the pool. The creator receives fees, not tokens.
- Start price: set per pair asset by the factory so that the first fill lands near a $5,000 fully diluted value. The range is priced in 200-point steps (about 2%), so the exact number moves a little with the NEAR price.
- First buy: the creator may buy up to 5% of the supply through the factory in a second transaction, on wNEAR pairs. The cap is enforced on the amount of tokens received, not on the NEAR spent. Bots are not blocked; the pool is live for everyone from the same block.
- No anti-snipe tax and no transfer restrictions: the token stays a plain NEP-141 so that every wallet and aggregator handles it.
Fees
| Who | Share of the 1% pool fee | Share of volume |
|---|---|---|
| Rhea protocol | 20% | 0.20% |
| Creator | 48% | 0.48% |
| shard | 32% | 0.32% |
The 60 / 40 creator / platform split is a constant in the locker code. Claiming (claim) and paying out (payout) are permissionless, and the locker keeps a per-launch ledger of what was claimed and what was paid, so nothing can be paid twice or lost between the two steps. The creator can hand the fee share to another account with set_creator.
There is no launch fee. The creator pays the real network cost, quoted live by preview_launch: token account storage, the factory record, the locker record, two token registrations, pool creation and the position. Roughly 0.18 NEAR without an image; an image adds its size in bytes twice (token metadata and factory record) at the NEAR storage price.
Ticker rules
- 2 to 10 characters:
a-z,0-9,-,_. Separators never at the ends and never doubled. - The symbol is the ticker in upper case. The token code itself refuses any other symbol.
- First come, first served. No suffixes, no reserved words except the factory's own sub-accounts, no admin override. A squatted ticker is a normal live token with its whole supply in the pool.
Security model
- Liquidity principal cannot be withdrawn. The locker has no function that removes liquidity by amount. The only admin capability is
admin_transfer_position, which moves a whole position NFT to another account. It exists for emergency recovery, for example if Rhea ever migrates pools, it can be handed over withtransfer_adminand switched off forever withrenounce_admin. Its current holder is readable on chain throughget_adminon the locker;nullmeans renounced. - Nothing can mint. The token has no mint function and no owner after initialisation.
- The token code cannot change. Token accounts have zero access keys and reference a global contract by hash.
- The factory is upgradable. It is the part that creates launches and can be improved; it never holds positions or fees. Its owner can pause new launches, change the start price per pair asset and change the platform payout address. It cannot touch existing pools.
- Every state change is an event. Launches, fee claims, payouts and admin actions are emitted as NEP-297 events under the
shardstandard, which is what the public API indexes.
Public API
The indexer follows the chain block by block and serves JSON at https://shard-production-97bd.up.railway.app. No key, CORS enabled for this site.
| Endpoint | Returns |
|---|---|
/v1/launches | Every launch with 24h volume, trade count, last price and holder count. |
/v1/tokens/:account/trades | Recent swaps: side, amounts, price, account, block time. |
/v1/tokens/:account/candles?tf=5m|1h|4h|1d | OHLC candles in the pair asset. |
/v1/tokens/:account/holders | Balances with pool, locker and wallets labelled. |
/v1/tokens/:account/stats | 24h volume, change, traders, holders. |
/v1/status | Indexer health: network, cursor, lag, errors. |
Addresses
| Contract | Account |
|---|---|
| Factory | shardpad.near |
| Locker | lock.shardpad.near |
| Rhea DCL | dclv2.ref-labs.near |
Token code hash: AQBpBpgK71xXkqZddDMogiLNZ8ZCNTRoKtGEg3Snzm2e. Every token account's code hash on the explorer should match it.
New here? Start with How to use. Questions: @shardpad_.