Stephan pfp
Stephan
@stephancill
upgraded my fee receiver contract to add a pay method which has a royalties arg dictating an array of recipients and basis points split that they should get here's the contract https://github.com/stephancill/royalty-delegator
2 replies
0 recast
7 reactions

hellno the optimist pfp
hellno the optimist
@hellno.eth
the main benefit is flexibility of recipients in this? vs something like the SplitV2 contract https://docs.splits.org/core/split-v2
1 reply
0 recast
1 reaction

Stephan pfp
Stephan
@stephancill
my use case was so simple and low risk that i didn't really consider using an existing contract because it would take me more time to find one and understand how to use it at the risk of not finding something than it would to just do it myself also i needed these specific features - payments (recipient, amount, memo, royalties) are created and validated by my server - i want to use it as a 7702 delegate - i have an existing implementation that i want to include for backward compatibility in the migration process might look into splits if i decide to use USDC instead though
0 reply
0 recast
0 reaction