Security

What has been checked, and what has not.

The launchpad is on a test network. The contracts have been through repeated independent review passes with every finding fixed, but no third-party audit has closed yet. Read this as a status page, not a guarantee. This page is in English only.

Reviews so far

Before and after each deployment the launchpad modules, the team vesting contract and the deploy scripts went through multi-agent security review rounds: nine full rounds of twelve independent reviewers each, with the corrected code re-reviewed in the following round, plus narrow re-checks of every change since. Two rounds ran stateful fuzzing against the accounting invariants.

What those rounds changed, in the rules that now hold:

Buybacks
Two steps (prepare, then buy in a later block), at most 1% of the market’s depth per buyback and ten minutes apart, so trading around a buyback cannot earn more than the fees it pays. Every buyback burns what it buys.
Opening window
The snipe tax is waived only when both the paying and the receiving wallet hold a Dojang Verified Address; the gate call is gas-capped and a silent gate counts as unverified.
Holder fees
Tokens sitting in the zero address or in protocol contracts earn no share; fees pushed into the escrow from outside still reach holders; claims are all-or-nothing so a wallet cannot be skipped silently.
Graduation
The last buy is filled up to the sellable allocation and refunded the rest, so nobody can block a graduation with a small purchase first; the pool is sized from fixed terms and the position is locked forever.
Fee recipient
The creator can move fees or hand them to holders; the owner can propose a takeover only through a public three-day timelock and can clear a distributor’s controller but never appoint one.
Migrations
Deposits are refundable until the first sale; each epoch settles at the operator’s price bound for the live pool, so earlier sellers cannot lock later settlements; a frozen old coin cannot hold recovered funds hostage.
Setup
Genesis verifies every module link, the PoolManager and the clone implementations; nothing is left with the deployer afterwards.

The full record of each round lives with the repository. An independent audit of the frozen code is a condition for mainnet, together with a legal review and moving the owner and treasury to multisigs.

Known limits

These are understood and accepted for now. None of them lets anyone take funds that are not theirs.

  • A buyback cap binds one buyback at a time. When a launch has accumulated a lot of fees, holders riding a series of buybacks share that buying pressure over several ten-minute steps; it is not atomic.
  • On a launch that sends fees to holders with buybacks on, the buyback share is burned rather than paid to holders.
  • Tokens sent straight to the buyback vault stay there; only what a buyback buys is burned.
  • A Dojang-verified wallet can buy untaxed in the opening window and pass the tokens on. A per-wallet cap inside the window would need a contract change.
  • The holder-fee epoch keeps a token leg for tokens sent directly to a distributor; the protocol path no longer produces any, since buybacks burn.
  • GIWA’s public RPC is several nodes and one can trail by a block. The publisher and keeper read their own transactions’ blocks and retry; a client that does not may see a trade a second late.
  • Site names for wallets are derived from the address and can collide; the address is always the identifier.

Roles and powers

Owner
Fee policy within caps (protocol share ≤ 50%, creator tax cap ≤ 10%, launch fee ≤ 0.01 ETH, opening window ≤ 10 min), launch configs, accepted pair assets (any of which can be stopped), the launch gate and whitelist, the Dojang gate and attesters, the keeper and publisher roles, takeover proposals through the timelock, the treasury address. Settings apply to new launches only. The owner cannot touch curve reserves, escrow balances, buyback funds (beyond buying or paying the creator), holder funds in distributors, migration deposits or locked liquidity. Ownership cannot be renounced.
Operations wallet
One wallet that only holds gas: publishes holder-fee epochs (bounded by what was harvested), runs or skips buybacks, and operates migrations (anchor, sell, settle). It never holds user funds. The owner can replace it.
Creator
Picks the terms at launch (creator tax, snipe tax, buybacks) and can later only move the fee recipient, hand fees to holders, or turn buybacks off. No mint, no freeze, no blacklist, no tax increase, no reach into liquidity.
Anyone
Can push a stalled graduation, claim what the escrow or a distributor owes them, and read every number above from the chain.

Reporting an issue

If you find something, tell us before you tell anyone else and give us time to fix it. Use the feedback button on any page (it reaches the team directly) or a direct message on X. Include the transaction or a reproduction on a fork. We will acknowledge, fix, and credit you if you want.

Do not test against live launches with other people’s funds. A local fork of the chain with the same deployment reproduces everything.

Versions

Deployed contracts are immutable. A new version ships as a complete new set of addresses (factory, hook, escrow, vault, locker, router, distributors, migrations); tokens launched on an earlier set keep trading and paying out against that set, and the site and indexer follow the current one. The current addresses are on the integration page; the legal texts and the risk disclosures are under disclosures.