Everything about Squink, in one place.

Overview

Squink Launch is a noncustodial token launchpad on Ink. A creator deploys a fixed-supply ERC-20 and its bonding curve, users trade against that curve, and a completed curve graduates into a permanently locked Uniswap v4 liquidity position.

Your wallet authorizes launch, buy, sell, graduation, claim and commercial-payment transactions. The Squink interface does not take custody of your private keys.

Launch lifecycle

Every current Squink launch follows the same protocol path. Economics and configuration are snapshotted when the token is created, so an existing launch does not silently inherit later configuration changes.

Bonding curve

The curve uses integer-only constant-product pricing with a 1 ETH phantom quote reserve. At launch, tracked quote is zero and tracked token inventory is one billion tokens. Two hundred million tokens are reserved as the graduation floor, leaving 800 million available through the curve.

Raw ETH or tokens sent directly to a curve do not become the pricing source. Curve accounting uses tracked state so unsolicited transfers cannot rewrite the quoted price.

Graduation

The active launch configuration graduates at 4 ETH net curve quote. Graduation is a protocol state transition, not a quality badge or investment endorsement.

Graduation preserves terminal curve price continuity when constructing the v4 pool. The protocol targets integer continuity within one part per trillion under the frozen continuity policy. Anyone can advance permissionless graduation when the launch is in the required state; it does not depend on the original creator staying online.

Trading and pricing

A Squink token has two trading venues during its life: the bonding curve before graduation and its canonical Uniswap v4 pool afterward. The frontend routes by the authoritative launch phase.

Price

Latest realized execution price or venue quote, depending on the surface.

Market cap / FDV

Valuation views derived from price and the protocol's fixed supply model.

Price impact

The change caused by the size of a proposed trade.

Slippage

The execution movement a wallet transaction is prepared to accept.

Displayed analytics are read models and estimates. A transaction preview and the wallet's final request are the authority for what you are about to sign.

Snipe protection

Every launch opens with anti-snipe protection for the first five seconds. The opening ceiling is 99% and decays rapidly. It applies to buys, while the launcher and creator-fee recipient are automatically exempt; optional launch-time exemptions are immutable once the launch exists.

The active config also caps creator tax at 2%, so the opening protection is composed with the fixed base fee and the launch's snapshotted creator tax without allowing the settlement schedule to consume the entire trade.

Fees

Current launches snapshot configuration ID 2. The launch fee is outside curve pricing and does not count toward graduation progress.

Post-graduation swaps use the Squink hook with a zero native Uniswap LP fee under the protocol's pool policy, avoiding a second pool fee on top of the Squink fee schedule. Each launch remains bound to the fee terms it snapshotted.

Creator earnings and claims

Curve and post-graduation fees are credited to the shared FeeEscrow according to the launch's immutable fee policy. Earnings are claimable rather than blindly pushed, so one recipient cannot block unrelated payouts.

The production fee sweeper periodically moves eligible curve and graduated-pool fees into escrow. Post-graduation token-denominated hook fees can be converted into native ETH under guarded, capped conversion rules before crediting recipients.

Token checks

Squink's paid token-check product adds a visible verification subscription to discovery and token surfaces. It is a commercial display feature, not settlement authority, token safety certification, or investment endorsement.

Advertising

Featured and Sponsored placements are paid discovery inventory. Any connected wallet may sponsor a canonical Squink-launched token whether it is on the curve, transitioning through graduation, or already graduated.

Paid placement does not imply creator affiliation, Squink endorsement, or a token-safety opinion. Moderation suppression remains fail-closed, and arbitrary external ERC-20 addresses cannot be submitted as Squink-token ads.

Risk disclosures

Tokens launched through Squink are user-created and experimental. They can be volatile, illiquid, manipulated, imitated, or lose all value. Graduation only proves a protocol threshold was reached.

• Always verify the token contract address before signing.
• Creator tax varies by launch within the protocol cap and is fixed at creation.
• Smart contracts, wallets, RPC providers, indexers, browsers and external protocols can fail.
• Blockchain transactions can be irreversible.
• Displayed prices, USD values and analytics are informational estimates, not execution guarantees.

Network

Public RPCs

Applications should reject unexpected chain IDs rather than silently falling back to a different network.

Contracts

These are the accepted Squink production coordinates on Ink Mainnet. Per-launch token and curve addresses are created deterministically and should be resolved from factory/indexed launch state rather than hardcoded.

Uniswap v4 dependencies

Events to index

For a trust-minimized launch history, index the factory, each emitted curve, graduation events, the shared hook and FeeEscrow. Reorg-aware consumers should key data by chain/block/transaction/log identity and roll back orphaned blocks.

Reading token state

Start with the factory/indexed launch record to resolve the token, curve, launch configuration and phase. A Squink token keeps the same ERC-20 identity before and after graduation; only the venue changes.

// Representative public read flow
const launch = await api('/v1/tokens/' + tokenAddress);

// launch.phase routes the product surface:
// 0  -> bonding curve
// graduated states -> canonical Uniswap v4 pool

// Treat token_address as the canonical user-facing identity.

Metadata is content-hash bound at launch. Squink verifies the canonical document used for presentation rather than trusting arbitrary name/symbol lookalikes.

Public read API

The production web app consumes indexed HTTP read endpoints for discovery and analytics. They improve performance and presentation; they do not sign transactions or replace onchain settlement checks.

Uniswap v4 pools

After graduation, native ETH is currency0 and the launch token is currency1. The pool uses tick spacing 60 and a full-range locked position. The shared Squink hook is bound to the required Uniswap v4 permission bits and handles the protocol's post-graduation fee accounting.

Integrations should resolve each token's canonical pool ID from graduation state/events. Do not assume that any arbitrary pool containing the token is the Squink graduation pool.

Claiming fees

FeeEscrow tracks claimable liabilities by recipient and asset. The Squink Treasury/claim interface prepares wallet-authorized claims; the application server does not broadcast a claim on the user's behalf.

FeeEscrow: 0xb8bbf885Df73b8DD45727Df9D4618512eb77f77E

Flow
1. Read recipient claimable balance.
2. Review recipient, payout address, asset and amount.
3. Simulate the claim.
4. Sign from the authorized wallet.
5. Verify the receipt and updated escrow liability.

Governance

LaunchAdmin ownership is held by a 2-of-2 Safe. Existing launches snapshot their config ID/hash and immutable economics, so governance actions for future configuration do not rewrite the economics of an already-created token.

The active launch configuration is ID 2 with hash:

Support

For product help, integration questions or suspicious-token reports, use the official Squink channels linked from the application. Never share a wallet recovery phrase, private key, wallet recovery code or remote-access credential with someone claiming to provide support.

Documentation baseline: Public Beta 1.1 · active launch config 2 · Ink Mainnet.