deuslaunch

Risks and support

What to keep in mind when you build on deuslaunch, and how to reach us when something looks wrong.

Risks#

  • No independent audit of these contracts has been published. Being a fork of Pons V1 does not make them reviewed.
  • The owner can change some settings, such as the launch fee and the configs for future launches; Liquidity and controls lists them all. A program should read them from the contracts instead of assuming them.
  • This is a testnet. Addresses, settings and balances will be different on mainnet, and testnet tokens have no value.
  • The code examples are a starting point, not a finished product. Read them, run them with a test wallet first, and keep keys out of code.
  • The site's indexer serves the site. It is not a public API and can change without notice; the chain is the source of truth.
  • Public RPCs limit how fast and how far back you can ask. Expect rate limits and retry with a pause.
  • RPCs, the indexer, wallets and other services can go down, fall behind or show wrong data, and this is normal. deuslaunch is not responsible for losses caused by them or by any other failure.

The full terms are in the Terms of Use.

Report a problem#

If you find a bug or a security issue in the contracts, the site or the indexer, write to us at [email protected] before telling anyone else, and give us time to look into it.

Say what you saw and how to make it happen again, with the transaction hashes or addresses involved. The same address answers questions about building on deuslaunch.

deuslaunch

Launchpad on GIWA.

Liquidity locks at launch, and every trade is signed in your own wallet. Funds never sit with deuslaunch.

© 2026 deuslaunch

Risk notice

Anyone can launch a token here, and any token can lose all of its value. Trades are final once confirmed. Nothing on deuslaunch is financial advice.