Referrals for Creators

InkyPump has two referral layers. They are related, but they are not interchangeable.

Contract event attribution

Hooks that support referral write functions can emit:

event Referral(
    uint256 indexed launchId,
    address indexed trader,
    string referralCode
);

Its topic is:

0x796dfbc4bdc1de15340f520a4b17fb287a10b2f6c50e702ee8dc9fa2c714dfc5

The log records the supplied string. It does not validate ownership, create a permanent relationship, move fees, or prove that the code earns cash rewards. Referral selector support also differs by deployment. The current native Ink and Robinhood hooks expose createLaunchWithReferral; the deprecated Ink hook does not. Always choose the selector through the launch’s deployment ABI.

Permanent fee-earning binding

The current fee program binds a referred wallet to a code with a short-lived challenge and wallet signature. The binding is chain-scoped and permanent once accepted. This is the record used for fee accounting. Use the Referral APIs for challenge, accept, dashboard, activity, and eligibility routes.

What creators need to know

A token does not need special launch settings to allow referral accounting.
Do not infer fee entitlement from a Referral log alone.
Do not promise that every historical hook supports the same referral function.
Keep pending, uncertain, finalized, accrued, claimable, reserved, and paid amounts separate in a partner dashboard.
The referral program does not change the trader’s curve fee.

Indexing contract events

Listen on every tradeable deployment returned by GET /api/capabilities, not just the active creation hook. Join referral and trade logs by chain, hook, launch ID, trader, transaction, and log order. Save the block hash so a reorg can be handled. See Read and Index for the canonical event topics and checkpoint rules.

​Contract event attribution

​Permanent fee-earning binding

​What creators need to know

​Indexing contract events

Contract event attribution

Permanent fee-earning binding

What creators need to know

Indexing contract events