Network

GIWA Sepolia#

GIWA is an OP Stack L2 with roughly 1-second blocks. Nothing exotic on the tooling side: Hardhat, Foundry, viem, and any wallet that can add a custom chain all work as they do on Ethereum.

Flashblocks#

The Flashblocks RPC returns a preconfirmation in roughly 200ms, which is what the app uses to acknowledge a trade the moment you sign it. Treat it as a strong hint and nothing more: the same block can change contents between reads there, so no amount taken from that view is settled. Wait for the receipt before you count anything.

Live contracts#

The current stack went live 2026-07-28 at block 31872372. All seven contracts are source-verified on Blockscout, so you can read the exact bytecode-matched source rather than take our word for it. Every address below opens the explorer.

How do I discover launch-specific addresses?#

Use the launch token as the stable identifier. Read its curve and reserved pair from the launch factory:

function curveFor(address token) external view returns (address);
function pairFor(address token) external view returns (address);

You can also capture token, creator, and curve together from the factory's TokenCreated event, and the reserved pair from LaunchPairReserved in the same creation transaction. After graduation, the same pairFor address is the live JoseonSwap pool.

Where can I get the ABIs?#

There is no published npm ABI package. For the current deployment:

1. Open the contract's explorer page — every stack contract above is verified, so the ABI is on the page.
2. For a freshly launched token or curve, wait until verification lands, or reuse the already-verified template ABI against the discovered clone address.
3. Pin the ABI and these deployment addresses together in your integration. Do not mix an ABI from one stack version with addresses from another.

For write-side snippets, see contract calls. For the read API that already indexes these contracts, see Indexer API.

Older stacks#

Earlier launch factories exist on-chain and are no longer indexed or served by the app. If you built against one, point at the addresses above. Curves still mid-flight on an older factory can graduate, since their authorisation was never revoked.

Why new versions instead of upgrades#

A pair's behaviour is fixed by the bytecode its factory deploys, and each contract in the stack points at exactly one other. Changing how pools work therefore cascades through the whole chain of them:

swap factory ──▶ launch factory ──▶ migration manager ──▶ registry ──▶ locker

That is on purpose. Nothing here is a proxy and nothing has an upgrade slot, so the rules a launch shipped with are the rules it keeps. The tradeoff is real: improvements arrive as a new stack, and the app cuts over to it.

Reading verification yourself#

The seven stack contracts are verified. Freshly deployed per-launch contracts — your token and its curve — start out unverified, because the explorer does not automatically match new deployments against already-verified bytecode. We submit them shortly after launch.

If you want to check any address without trusting a page like this one, ask the explorer directly:

curl -s https://sepolia-explorer.giwa.io/api/v2/smart-contracts/<address>

The is_fully_verified field is the answer.