⭐ Merited by NeuroticFish (5) ,LoyceV (4) ,BlackHatCoiner (4) ,bitmover (3) ,Welsh (3) ,dkbit98 (3) ,HeRetiK (1) ,klarki (1) ,n0nce (1) ,DdmrDdmr (1)
Payments for this week of the campaign have been sent, using an exchange rate of 1 BTC = $23,200. (b8a1ce7a7426a00833a74a1fcaa105a6c11bc417f3ac1d5c0cb8ec83ba7b2d1c)
There's an argument for allowing people to easily see how many of their posts were rejected, without needing to do math. Manually counting the number of posts you made last campaign period is a bit annoying, and will discourage people from checking if they were paid correctly.
In the end, this isn't a perfect process either, especially if people provide addresses via forum PM due to Cloudflare. I've considered building software to do something like this (more likely it would be in the form of automated address changes), but I'm hesitant to trust any software I write with real sums of money
I won't rule making large changes out, but ultimately there will always be trust needed somewhere. If you're after the highest level of privacy, your privacy model should not rely on needing to trust me to keep your payout addresses private.
Genuine question: Why are people looking at the spreadsheet? What information are they taking from it? They have no need to know other users' addresses or post counts, and they can figure out how many of their own posts have been counted based on how much they are paid.
There's an argument for allowing people to easily see how many of their posts were rejected, without needing to do math. Manually counting the number of posts you made last campaign period is a bit annoying, and will discourage people from checking if they were paid correctly.
In fact. What if Dark Star paid from a Chip Mixer chip every week instead of using the same Address? What if Chip Mixer members gave Dark Star a list of 10 Addresses and Dark Star paid them weekly in a random Address from a Chip Mixer chip. Just an idea.
I've thought about this, but it's prone to error. Manually selecting 50+ addresses per week every week means thousands of addresses per year. The only way to rule out mistakes is by automating the entire process.In the end, this isn't a perfect process either, especially if people provide addresses via forum PM due to Cloudflare. I've considered building software to do something like this (more likely it would be in the form of automated address changes), but I'm hesitant to trust any software I write with real sums of money
I won't rule making large changes out, but ultimately there will always be trust needed somewhere. If you're after the highest level of privacy, your privacy model should not rely on needing to trust me to keep your payout addresses private.