Tie rewards to a wallet address the customer already controls, without asking for an email.
Crypto wallets, on-chain apps and communities where the wallet is the account.
In a wallet-native product the wallet is the identity — there is often no email and no phone. Most affiliate infrastructure assumes both, so rewards either need an off-chain account nobody wants to create, or they do not happen.
Merchant breadth is the same problem as everywhere else: real spending happens at ordinary online retailers, which means the affiliate networks, which means fourteen integrations.
Ethereum and Solana addresses are accepted today and hashed into the same identity graph as email and phone. The wallet can be the only identifier you hold.
POST /v1/end-users · wallet_addresses[]
The link carries a click token tied to the wallet, so a purchase at an ordinary retailer attributes back to an on-chain identity.
POST /v1/links
Conversions arrive with the commission earned and the wallet that earned it. What you do at that point — on-chain or off — is yours.
GET /v1/conversions
No email required. The address is a first-class identifier, not a note in a metadata field.
Rewards apply where people actually shop, while the account stays the wallet the customer already has.
Addresses are hashed into the graph like every other identifier.
Attribution runs through tracking links, as it does for every other rail. Detecting a qualifying purchase from on-chain activity alone is not built.
POST /v1/end-usersPOST /v1/linksGET /v1/conversions