ADPTAffiliate
Settlement Oracle ↗

Available when storage is online · earnings disabled

Share a link. Measure interest.

Register a code with a wallet signature and share it across ADPT pages. The site counts deduplicated link visits. Registration and clicks create no payment entitlement, earnings, or liability. A future reward programme, if enabled after review, will be governed by a separately published policy.

Checking registration and click-storage health…
Your referral link

Phantom, Solflare or any injected Solana wallet. Claiming a code asks for one signature to prove you control the wallet — it moves nothing, approves nothing and cannot spend anything.

Choose your code

3–24 characters: lowercase letters, numbers, hyphen or underscore. First claim wins, one code per wallet, and nobody can take it from you afterwards.

Your link
Your numbers —
What works now
Signed registration
Available when storage is online
A wallet signature proves control and reserves one code. It cannot move funds.
First-touch capture
30 days
The first valid code stays in the visitor's browser until it expires or they clear it.
Click counts
Available when storage is online
Deduplicated unauthenticated visits are counted. A click is not a conversion and earns nothing. The Origin allowlist is browser abuse reduction, not authentication.
Earnings
Disabled
No conversion settlement, reward balance, payout, or financial liability exists.
Policy version: affiliate-revenue-v1-proposed-2026-08-23. Proposed is not active. Any activation requires reviewed eligibility, settlement controls, abuse prevention, reserves, and an explicit public status change.
Current terms, in full
Registration A signed code registration proves wallet control. It creates no payment entitlement and authorises no transfer, approval, or spending.
Click tracking Known codes receive a deduplicated visit count. A click is not a sale, conversion, attributed customer, earning, or amount owed.
Attribution First touch, 30 days, stored in the visitor's own browser. A later code does not replace an unexpired first code. The visitor can clear it at any time.
Earnings now Disabled. No percentage, token-purchase reward, holder distribution, claimable ADPT, payout balance, or liability is active.
Possible future source Only eligible settled external product revenue after direct costs and required refund, chargeback, tax, and operating reserves — never token purchases, swaps, deposits, self-referrals, project-controlled activity, refunds, or reversals.
Activation Requires a published policy version, eligibility and abuse review, settlement and reconciliation controls, and explicit enablement. Registration today does not lock in future terms.
What we cannot tell you
Nothing is owed to anyone right now. Signed code registration and click tracking are available when storage is online. Earnings are not enabled, and neither a code nor a click creates a financial liability.
  • There is no active reward rate. Any future rate must be supported by settled external product revenue after costs and reserves, then published under a reviewed policy.
  • Token trading is not eligible revenue. Paying for token purchases would invite self-referral and circular trading and is excluded from the proposed policy.
  • No claim of profitability, here or anywhere. Four separate tests of our own trading models found no directional edge, and we publish that. Nothing on this page is a projection of earnings, a guarantee of returns, or investment advice.
  • Future eligibility is not automatic. Jurisdiction, abuse prevention, delivery, settlement finality, refunds, reserves, and policy acceptance all require review before any programme can create a reward.
How the link actually works
  • Your link is any ADPT page with ?ref=yourcode on the end. The homepage, the oracle, a meme — all of them can carry it.
  • When someone opens it, the code is stored in their browser with a timestamp and the address bar is cleaned. The first valid code remains for 30 days; later codes do not overwrite it unless it expires or the visitor clears it.
  • For deduplication, the server computes a secret HMAC over the UTC day and request IP, then truncates the result. The IP is not stored and identifiers from different days cannot be linked from the stored values alone. Click records — day-scoped identifier, landing path, and coarse country — are excluded from reporting after 31 days and opportunistically deleted when subsequent click activity occurs. Strict deletion from a dormant table requires scheduled maintenance.
  • Any visitor can erase it: adptRef.clear() in the browser console, or just clearing site data.