Abyss

Launch, confirmation, and cancellation

Open Create a launch on Robinhood Chain mainnet (4663). Choose Simple for one pool or Advanced for multiple pools and custom allocations. Set token, price, liquidity and fees, then review the launch. The separate low-level editor exposes raw lifecycle fields and execution mode; it is not the Advanced wizard.

Choose how to launch

AtomicStaged
Launch transactionsOne launch transaction after funding approvals.Begin → prepare markets in one or more transactions → activate.
What activation doesCreates the token, mints and locks positions, executes buys and opens markets within the launch transaction.Mints and locks every position, executes all buys and opens every market in one final transaction.
If a step revertsThe launch transaction is undone. Prior approvals remain.That step is undone; earlier setup remains. Activation cannot leave only some markets open.
CancellationA reverted launch needs no cancellation.Cancel a pending launch to recover unspent external funding. Setup gas is not refundable.

Simple seeks an atomic fit. One-pool Advanced starts atomic; multi-pool Advanced uses staged execution. The final activation must still fit one transaction. Staging is not rollback for earlier confirmed work.

Fund the Initial buy

Launch liquidity starts with the new token only. Quote funding pays for optional opening buys after that liquidity is locked. Keep native ETH for gas in addition to the buy payment.

Funding modeWhat you provideWhat the launch usesUnspent reserved funding
Direct ERC20The market's quote token and an approval when needed.That ERC20 quote.The same quote token.
ETH wrap for WETHNative ETH matching the committed wrap amount.WETH, on either venue.WETH, not automatically unwrapped ETH.
Allowlisted conversionNative ETH or a supported ERC20 input, bound to a specific conversion route and minimum.The converted quote, such as USDG.Unspent quote plus any refundable input; inspect the committed route.

WETH funding uses NativeWrap, not a Kyber swap. Other supported quotes can use a Kyber conversion. The conversion minimum and the token-buy minimum protect different trades.

For ordinary launches, inspect the SDK's funding-escrow spender. For UFG, approve the proxy instead. Compare prompts with the current address table.

Follow the wallet steps

Review and simulation do not sign a launch transaction. Expect the prompts required by your plan:

  1. Approve funding, if needed. Some tokens require Reset approval before Approve. Check token, spender and amount.
  2. Authorize metadata with the separate EIP-712 Abyss Launch Attribution signature. This attributes the launch profile; it does not deploy the token.
  3. Launch atomically, or begin → prepare → activate in stages. The app shows Launch, Continue launch, and transaction progress as appropriate. Check target, native value and gas for each prompt.
  4. Wait for each confirmed transaction before continuing. A declined request leaves the next action unsigned; it does not authorize an automatic retry.

The exact number of wallet confirmations depends on approvals, preparation and mode. Do not assume an atomic launch means one wallet signature. If funding is uncertain, use Check funding and the wallet's transaction history before authorizing another spend.

Check four completion states

CheckWhat to confirm
1. Receipt confirmedThe launch or activation transaction succeeded on the selected chain.
2. Markets ActiveThe token and every market opened; position locks, buys and refunds match the plan. Preparing and Ready are still pending.
3. Metadata publishedName, description and any image have finished publication for that token.
4. API indexedThe launch page resolves with the existing token and its markets.

A confirmed token can appear while profile publication is still running. If the app shows Finish launch profile or Launch completion paused, finish that operation; do not deploy another token. Once Active, use fee and reward actions.

Resume an interrupted launch

In the same browser tab, return to Create a launch with ?resume=1. Reconnect the original wallet and network, then check launch status before continuing. Recovery uses that tab's saved operation. Opening bare /launch/new starts a new operation and clears its previous recovery record; a ?draft= recipe link is not transaction recovery.

In SDK examples, run the same case with --resume <original-run-dir>. It retains the original plan, token identity, receipts and publication session. A fresh --broadcast creates a new nonce and launch identity; it is not a retry of the old plan.

Use the TypeScript lifecycle guide or Python launch guide for exact recovery and cancellation APIs. Keep the original plan and receipt references private and intact.

Resolve a stopped launch

What you seeWhat happenedWhat to do
HTTP 403/429 while checking chain, balance or simulationThe public RPC refused or throttled a request. A 429 is not a contract revert.Wait or switch RPC, inspect transaction status, then resume the same operation.
Staged launch begun but its deadline passedBegin succeeded; preparation or activation did not finish in time.Cancel the pending launch to return unspent external funds. Do not start over expecting the old funds to follow.
eth_getLogs range errorA scan exceeded the RPC's block-range limit.Start at the deployment block and query chunks of at most 10 million blocks.
KYBER_UNAVAILABLE or invalid route for WETHETH→WETH was treated as a swap.Use native wrapping for WETH. Kyber conversion is for other quotes.
INVALID_KYBER_INTENTThe conversion deadline is too long or reused the launch deadline.SDK examples use a 300-second conversion deadline, maximum 1,200 seconds, within the plan's 3,600-second deadline. A valid plan does not extend an expired conversion.
PLAN_NOT_ADMITTED with a gas-envelope errorThe saved transaction's gas requirements changed.Rebuild the immediate unsigned step with buildNextTransaction / build_next_transaction; do not force the old gas limit.
ECONOMIC_REVIEW_REQUIRED with a hash mismatchThe review belongs to a different plan invocation.Review and admit the same saved plan. A fresh nonce changes its hash.
Activation deferred by simulationThe plan exceeded the provider's aggregate proof budget, 50M gas by default.Start with one market, or use a provider supporting a sufficient budget. Buy-output protection needs activation outputs.
PUBLISH_TIMEOUT, API_INDEX_TIMEOUT or image URL error after activationThe token opened; metadata or indexing did not finish.Resume publication for the existing token. Do not deploy again.

Cancel a pending launch

A launch in Preparing or Ready can be cancelled, including after its deadline. Expiry stops preparation and activation but does not automatically refund funding. Submit a cancellation for the original plan and wait for its successful receipt.

Cancellation returns remaining external funding to the creator, or the principal on the UFG route. Wrapped ETH returns as WETH. The token's committed cancellation policy burns the unreleased supply or leaves it permanently inactive. Already-created contracts and spent gas remain. Discarding an app draft does not cancel anything on-chain, and an Active launch cannot be cancelled.

On this page