Create a sale

One transaction to the factory creates the sale account without any access key, deploys the sale contract, and has the TEE derive the sale's encryption key. Below you can check, with a live RPC call, that the account really has 0 access keys.

Token and sale

Sale name (account label)lowercase a-z, 0-9, - _Ticker

Token name

Auction supply

tokens

Whole tokens sold in the sealed auction.Reserve price

NEAR

Minimum price, NEAR per whole token.

Bid window

hours

From the moment you submit.Min bid size

tokens

Whole tokens.

Where the money and tokens go

Liquidity pool share of raise

Percent of the raise paired with LP tokens at P*. The sale account holds the LP, and it has no keys.Creator allocation

Percent of auction supply, minted extra and vested linearly.

Creator vesting

days

Bid fee (non-refundable)

NEAR

Advanced

Token decimalsPayment tokenEmpty = native NEAR. Otherwise a NEP-141 account id.Challenge window (s)Max bids (≤ 65536)

OutLayer projectWorker code hash (sha256 of the OutLayer wasm)Recorded in the sale at init. Must match the build the secret is locked to.

Result preview

Sale + token account: sale-.sealedlaunch.deathstalker-sl.testnet
Auction: 1,000,000 (76.92%)
LP reserve: 200,000 (15.38%)
Creator: 100,000 (7.69%)
Total minted: 1,300,000
Raise range: ≥ 500 NEAR if fully sold
Factory deposit: …

LP tokens reserve = LP share of the auction supply (an upper bound on what the LP needs, any unused part is burned at settle).

name must be lowercase a-z 0-9 - _ (no leading/trailing - _) (+2 more)

0 access keys check

The account sale-.sealedlaunch.deathstalker-sl.testnet is created by the factory in one atomic batch with no AddKey action. This is a live view_access_key_list RPC call, not a claim.

Enter a valid name first.