pull down to refresh
SUBMISSIONS CLOSED
@clenchwallet I will test and review your submission. You will be awarded your bounty by the end of the week if it works!
Got it, thanks!
Double Bonus! Payjoin postmix (Marketed as "Cahoots" by Samourai) unnecessary input fingerprinting and multi clustering:
DeWhirlpooler v0.1.0: https://github.com/clenchwallet/dewhirlpooler/releases/tag/v0.1.0
Your full spec + bonuses, including Payjoin/Cahoots fingerprinting. It is self-hosted for Bitcoin Core + Fulcrum. A bundled historical-index snapshot will be added when the full scan reaches tip.
@k00b I am trying to award @clenchwallet his bounty, but I get this error?
better ask for a lnaddress and send them p2p
Why not? I explained here: #1548027
I could simply dump a 500k CC zap on clenchwallet right now and circumvent this artificial restriction. But I want this bounty to show as "Claimed", so I would rather make use of the feature's intended functionality. It shouldn't be this much of a hassle to give away money.
Ok if that's the case @clenchwallet will need to attach a wallet, there's no other way around it. Also always double-check the @nym because we had a few impersonators coming up and a bounty like this could definitely attract @cIenchwallet (with a i instead of a L) and other similar nyms... so verify you are sending to the right user, because as you know, theres no refunds policy with bitcoin.
they need a receive wallet attached to receive a bounty
Why can't he receive Cowboy Credits for the bounty?
I have C lightning attached to my wallets here, is that not working?
If you have enough liquidity to receive 500k sats, then it should be fine.
Yes, I have it
It might be that I need to generate an invoice here is SN wallet, I see that as an option...
@clenchwallet I didn't forget about your bounty, I had to switch my node to Knots yesterday to monitor the fork. Testing your project now.
Understood. Wild week.
COMPETITION ENDS IN ONE WEEK! Minimum feature spec (courtesy of @clenchwallet ):