Escarpescarp

ESCARP DOCS

How Escarp works.

Token details, launch plans, pool quotes and wallet access. Find the steps for each part of your launch.

About Escarp

A Solana launchpad using pump.fun’s native token creation and bonding curve.

Enter your token details and IPFS metadata, choose a SOL or USDC pair, and review the native creation transaction before your wallet signs. Supply and decimals come from the native program.

Preparing saves the launch and its mint address. Wallet approval submits creation; a finalized receipt verifies the mint, metadata, supply, creator and curve. Saving alone does not move funds.

Getting started

Choose where to begin.

  1. Open Create a token, enter a name, symbol and description, and choose SOL or USDC.
  2. Use Pools to inspect an existing pool, or Trade to review a direct pool quote.
  3. Connect your wallet and sign in when you want to save private work. Connection and sign-in are separate actions.
  4. Upload your image and metadata, or provide an existing public IPFS metadata URL. Prepare, review and approve the creation transaction.

Creating a token

Create a regular coin using pump.fun’s native program.

  1. Enter a name, symbol and description. The native program supplies the token supply and decimals; these are not custom allocation settings.
  2. Choose SOL or USDC. Use matching public IPFS metadata containing your name, symbol, description and image. Image uploads publish the image and JSON to public IPFS when storage is connected.
  3. Select Prepare token creation. Review the mint, creator, paired token, network, program accounts, estimated total cost and network fee.
  4. Select Approve devnet token creation. The app checks and simulates the transaction again, then asks your wallet to co-sign the mint creation.
  5. Check the saved signature until finalized. Open token market reads the resulting native curve and mint authorities.

The default flow makes no developer purchase and adds no extra Escarp fee. On devnet, Phantom must have Solana Devnet selected. A real mainnet launch requires its own approval and configuration.

Saving and resuming

Resume the same launch without creating a second mint.

  1. Preparing reserves one mint for the saved launch. Open saved launch restores the latest record for your signed-in wallet.
  2. If an unsigned review expires, prepare that saved launch again. Its mint stays the same.
  3. After signing, check the existing signature. An unknown result needs a chain-status check; do not create a replacement mint.
  4. The separate calculation tool retains private versioned drafts, seven-day share links, revocation, archive and JSON import/export. Those analytical recipes do not create tokens.

Pool quotes

Review a direct Meteora DLMM quote before making a decision.

  1. Sign in, enter the DLMM pool address and select X-to-Y or Y-to-X. Pools shows which token is X and which is Y.
  2. Enter the input amount and slippage in basis points. 100 basis points equals 1%.
  3. Review the network, input and output mints, expected output, minimum receive, fee token and price impact.
  4. Refresh an expired quote or one whose inputs have changed. Quotes expire after 30 seconds.
  5. For an enabled devnet pool, choose Prepare devnet swap. Review the network fee, account rent, minimum receive, programs and accounts.
  6. Select Approve devnet swap to request a wallet signature. Keep Phantom on Solana Devnet. The app checks the blockhash and simulates again before opening the wallet.
  7. After submission, check the saved signature and finalized receipt. Open saved swap resumes the same transaction after a reload. An unknown result needs a status check, not another trade.

Get quote only reads prices; preparing and approving are separate actions. The devnet preset uses a test token and 0.00001 devnet SOL. A listed token is not a safety endorsement.

Pool details

Inspect a pool directly from its on-chain account.

Enter a DLMM pool address after signing in. Check its token pair, network, active bin, bin spacing, source slot and read time.

Liquidity is the tokens supplied to a pool for trading. Pool balances can change as people trade; a price calculation is not a guarantee of what a trade will return.

Mint and pool recognition do not establish token safety. Confirm addresses and the selected network before approving any wallet action.

Understanding fees

Pool fees and transaction costs are separate.

Escarp’s launch policy uses native pool fees with no additional Escarp fee. Fee rates and who receives them depend on the actual venue and pool configuration.

A quote identifies the token used for its pool fee. The protocol portion is included in that fee, not charged a second time.

Solana network costs and account rent are separate from pool fees. Fees entered in the example calculator are calculation assumptions and do not configure a live pool.

A permanent-liquidity claim must be backed by the actual on-chain mechanism and transaction receipt. A saved plan or hidden withdrawal button is not a liquidity lock.

Wallet access

Connection, sign-in and transaction approval each serve a different purpose.

Connecting shares your selected public account. Signing a one-time message proves account control and starts a limited session for private plans.

Signing in does not approve transfers. Any asset movement needs its own transaction review and wallet approval.

Escarp never asks for a seed phrase, private key or wallet export. Check the website, network and wallet prompt before approving an action.