We currently use the referrer for 2 different purposes: distribute governance tokens as well as referrer fees (if applicable). It would be better to distinguish between the 2 as some platforms may want to keep the governance tokens for themselves but allow referral fees to go to users of their platform.
Now that we have a new purchase signature (with a Struct), we can distinguish between the 2 values between referrer (gets referrer fees) and protocolReferrer (gets governance tokens). They could obviously be the same as well if the implementer wants to!
add protocolReferrer that will receive UP in struct purchase args
We currently use the
referrer
for 2 different purposes: distribute governance tokens as well as referrer fees (if applicable). It would be better to distinguish between the 2 as some platforms may want to keep the governance tokens for themselves but allow referral fees to go to users of their platform.Now that we have a new
purchase
signature (with a Struct), we can distinguish between the 2 values betweenreferrer
(gets referrer fees) andprotocolReferrer
(gets governance tokens). They could obviously be the same as well if the implementer wants to!add
protocolReferrer
that will receive UP in struct purchase args