So in this instance would my sars be equally distributed to each dev wallet. Or can you structure it from the devs side where dev1 did 0.25 of total release work so 25% of donated sats get channelled to his wallet automatically.
Discussion
Yeah, I need to make the percentages more clear in the UI. Usually I set them up in each release to what I think is a fair distribution besed on the work. Maybe there is a better way to create these. 🤔
Well in many circumstances people who donate should not know the distribution percentages (and don't care). However on the backend all devs want a fair cut so maybe it's tied to the code commit ratio or something.
Then there is the other scenarios where the donators want donation distribution control at the front end. I can imagine this yielding higher donation rates in some cases. Good example might be for sporting teams. You want to reward the midfield and offence today but the defence was horrible so no sats for you!
haha code commit ratio is a really bad idea... way to incentivise garbage
no, it should be entirely according to their rank in the operation, junior, senior, marketing, communications, etc etc etc... you set the roles, and base the breakdown on the ratios of that set of the team based on market rates for the work
it necessarily means there has to be someone in charge and accountable for setting this rank for all contributors
at least that's how i would do it anyway
if someone in marketing, for example, put out some stuff that really pulled in the donations, for example, then their rank should be upgraded, that's the logical upshot of this... it's quite a neat system for establishing fund distribution, it could work not just in the donation situation but for an organisation that is funding off grants and other speculative contributions (if there is some reasonable mechanism for adding contributors to the set of split targets - it could be done for sure and make it very automatic)