"No ETH Seeded" / "No Tokens Seeded" Errors Explained: Fixing a Failed Launch

What triggers these errors

These reverts fire when a contract's owner calls the function that opens trading and seeds the initial liquidity pool, but the contract itself hasn't yet been funded with the ETH or tokens it needs to complete that step.

Why the contract requires this specific order

Many token contracts follow a deploy-then-fund-then-open pattern: deploy the contract, transfer the liquidity portion of tokens and the ETH meant to pair with it to the contract's own address, then call the function that opens trading. If either transfer was skipped, sent to the wrong address, or hasn't confirmed yet, the open-trading call has nothing to seed liquidity with and reverts rather than opening an empty or malformed pool.

How to fix it

• Confirm you transferred tokens to the contract's own address specifically - not your wallet, not a pool address, not the router.
• Confirm you sent ETH to the contract's own address the same way - a plain transfer, not routed through a swap.
• Double-check both transactions actually confirmed on-chain before assuming the funds landed - a pending or failed funding transaction leaves the contract exactly as empty as before you sent it.
• Check the contract's balance directly on a block explorer for both ETH and its own token before retrying the open-trading call.

FAQ

• Do I need to fund the contract before or after deploying it? After - the contract has to exist on-chain before you can send it tokens or ETH.
• Can I open trading with only tokens seeded and no ETH, or vice versa? No - both sides need to be present, since opening trading seeds a liquidity pair that requires both assets.
• Why did my funding transaction succeed but the contract still shows no balance? Double-check the exact recipient address used - funds sent to the wrong address (your own wallet, a pool address) won't show up in the contract's balance.
• Is this a one-time step? Yes - once trading has been opened successfully, this specific error no longer applies; it's only relevant during the initial launch sequence.