Protocol documentation · v0.1

Understand the
full flow.

Architecture, allocations and settlement behavior for transparent charitable launches on Ink.

01 / Overview

What is INKIND?

INKIND is a launchpad architecture for tokens whose protocol fees are split into explicit charitable, market and operational destinations. The interface is designed to keep those destinations visible from launch through final settlement.

Current status

The interface and protocol specification are in development. Mainnet transactions remain unavailable until contracts and external integrations are verified.

02 / Architecture

Launch lifecycle

01CreateToken configuration
→
02BootstrapUniswap v4 liquidity
→
03RouteFees by destination
→
04SettleReceipt confirmed

03 / Fee allocation

Deterministic by design

Protocol fees are separated according to a fixed public rule. Each destination is represented independently in the transparency view.

80%

Charity escrow

Held for the selected verified charity and routed to its supported destination.

20%

Treasury

Supports protocol operation, maintenance and infrastructure.

04 / Charity bridge

Allocation is not delivery

If the recipient charity does not settle on Ink, INKIND treats the bridge as a distinct observable process. A source deposit alone is never displayed as a completed donation.

  1. 01
    Source deposit

    The charity allocation enters escrow on Ink.

  2. 02
    Bridge initiation

    The relay transaction and destination network are recorded.

  3. 03
    Destination settlement

    The destination transaction confirms arrival.

  4. 04
    Charity receipt

    The final donation receipt closes the public trail.

05 / Networks

Supported environment

Launch networkInk mainnet
WalletMetaMask
LiquidityUniswap v4
Charity settlementCross-chain when required