You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One goal of our infra is to maximize royalty volume - where we would eventually take a fee.
Especially in the case of significant changes to the royalty logic required by apps - to ensure that those apps still choose to integrate we should have strong ancillary offerings.
One low hanging fruit is automate royalty distribution via taking fee like 0xSplits does.
Problem we’re facing (that this change will solve)
Right now, users have to manually go find their derivatives that made money and claim manually. Automatic distribution is better UX and people will likely pay for it.
Blockers / Dependencies
n.a
Directions to solve this (and which direction we are on atm)
Do like 0xSplits - allow users to define a % they want to give and anyone can permissionlessly distribute the royalties. They should be able to also change it back. % should have a maximum cap set by governance for security reasons of not draining the vaults
The text was updated successfully, but these errors were encountered:
One goal of our infra is to maximize royalty volume - where we would eventually take a fee.
Especially in the case of significant changes to the royalty logic required by apps - to ensure that those apps still choose to integrate we should have strong ancillary offerings.
One low hanging fruit is automate royalty distribution via taking fee like 0xSplits does.
Problem we’re facing (that this change will solve)
Right now, users have to manually go find their derivatives that made money and claim manually. Automatic distribution is better UX and people will likely pay for it.
Blockers / Dependencies
n.a
Directions to solve this (and which direction we are on atm)
Do like 0xSplits - allow users to define a % they want to give and anyone can permissionlessly distribute the royalties. They should be able to also change it back. % should have a maximum cap set by governance for security reasons of not draining the vaults
Context of this change
One goal of our infra is to maximize royalty volume - where we would eventually take a fee.
Especially in the case of significant changes to the royalty logic required by apps - to ensure that those apps still choose to integrate we should have strong ancillary offerings.
One low hanging fruit is automate royalty distribution via taking fee like 0xSplits does.
Problem we’re facing (that this change will solve)
Right now, users have to manually go find their derivatives that made money and claim manually. Automatic distribution is better UX and people will likely pay for it.
Blockers / Dependencies
n.a
Directions to solve this (and which direction we are on atm)
Do like 0xSplits - allow users to define a % they want to give and anyone can permissionlessly distribute the royalties. They should be able to also change it back. % should have a maximum cap set by governance for security reasons of not draining the vaults
The text was updated successfully, but these errors were encountered: