How It Works
Once you’ve integrated Divvi and registered a user, Divvi takes care of the rest: 📝 User registrationYour app appends referral metadata to a transaction. Once the transaction is confirmed and registered, the user is linked to you as their referrer. 📊 Activity tracking
Divvi monitors the user’s on-chain activity with the Campaigns you’ve signed up for. 🧮 Reward calculation
Divvi periodically calculates your rewards based on referred user activity and publishes the results on-chain. 💸 Claiming rewards
You can claim your rewards directly from Divvi’s smart contracts whenever you’re ready.
Getting Started
Integrating Divvi is simple. At a high level, here’s what you need to do:- Register yourself in the Divvi ecosystem using a wallet address
- Join the Divvi Campaigns you want to participate in
- Build user experiences that drive engagement with those campaigns
- Append referral metadata to your users’ first transaction
- Register that transaction hash with Divvi
- That’s it! Divvi handles tracking, attribution, and reward calculation. You can claim your rewards periodically from the reward contracts directly.
DivviRegistry Contract Details
The DivviRegistry is the on-chain source of truth for all participating builders, campaigns, and referred users. It records which builders are registered, which campaigns you’ve joined, and which users you’ve referred. The DivviRegistry contract is deployed on the Optimism network at 0xEdb51A8C390fC84B1c2a40e0AE9C9882Fa7b7277. ABI: You can find the contract ABI here by clicking on the implementation contract address and scrolling down to the “Contract ABI” section.Check for existing Referrals
You can check the referral status of a particular user for a given campaign by calling the isUserReferredToProvider method on theDivviRegistry
contract. This will return true
if the user has been referred to the given campaign by any builder.
To determine which builder has referred some user to a given campaign, you can call the getReferringConsumer
method on the DivviRegistry
contract, which will return the builder address which referred the queried user to the given campaign. If the user has not yet been referred
to the campaign, this will return the zero address instead.
Suggest changes to this pageLast updated: Aug 15, 2025, 5:45 PM