pull down to refresh

COMPETITION ENDS IN ONE WEEK! Minimum feature spec (courtesy of @clenchwallet ):

  • Must track the coordinator fee output and total profit (minus mining fees). There is some variation here when discount codes were applied in Samourai, which are not used by Ashigaru AFAIK
  • Must track common input ownership count revealed & their total BTC value from every tx0 premixe
  • Must track toxic change created from tx0 premixes, and have an extra flag if these coins get spent in a following tx0 premix
  • Must track the total fee cost in sats and as a % of the equal denominations created for any specific tx0 premix
  • Must track when a postmix transaction is spent as stonewall or ricochet, and the fee address paid for richochet
  • Must track the size (5:5, 6:6, 7:7, or up to 8:8) of the round, and the ratio of new entrants + remixers
  • Must track the total liquidity in each pool at each block height (and therefore the +/- change in pool entry/exit
  • Bonus: Flag CPFP spends from Whirlpool, and 1:1 consolidations of 3+ coins from tx0 -> Whirlpool -> Payment
  • Bonus: Flag address reuse for coordinator fees, tx0 inputs, tx0 change outputs, tx0 feeder outputs/Whirlpool inputs, Whirlpool outputs, & postmix Stonewall address reuse
  • Bonus: Flag BIP47 Payment OP_RETURNs, count how many notification transactions each entity has received on chain, and track to see if there is an immediate consolidation of any 2+ notifications and 2+ future input consolidations
  • Bonus: Look forward or backwards by an additional generation for all tx0 premixes and postmix spending
573 sats \ 1 reply \ @Kruw OP 1 Aug

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!

reply

Got it, thanks!

reply

Double Bonus! Payjoin postmix (Marketed as "Cahoots" by Samourai) unnecessary input fingerprinting and multi clustering:

reply

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.

reply
1110 sats \ 38 replies \ @Kruw OP 14 Aug

@k00b I am trying to award @clenchwallet his bounty, but I get this error?

reply

better ask for a lnaddress and send them p2p

reply
10 sats \ 9 replies \ @k00b 14 Aug

why? bounties award the full amount in sats. routing fees come out of the sender's end.

reply

True, I forgot about the bounty behavior having changed since the last time I used it.

reply

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.

reply

I think you can. Do you see the pay bounty button near reply in every comment?

And as I mentioned here, triple-check the user nym before clicking the button, or ensure you allocate the bounty to the right comment.

reply
10 sats \ 5 replies \ @k00b 14 Aug

I was asking supratic.

If we let you give CCs, this would be a lie. It's not theoretical. I've been dealing with people pissed off about receiving CCs for years.

reply

but again, to receive sats, one must have a receive wallet attached to it, correct? or would the sats sit on their sats wallet balance until they attach a wallet?

But I want to get credit for awarding the bounty on SN. Can't have anyone thinking that I don't pay my debts.

reply

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.

reply

There is another way around it: Accept Cowboy Credits for bounties.

reply

that's another option the user needs to set up too. If not set you'll continue getting that error.

10 sats \ 21 replies \ @k00b 14 Aug

they need a receive wallet attached to receive a bounty

reply

Why can't he receive Cowboy Credits for the bounty?

reply

I have C lightning attached to my wallets here, is that not working?

reply
34 sats \ 15 replies \ @k00b 14 Aug

If you have enough liquidity to receive 500k sats, then it should be fine.

reply

It might be that I need to generate an invoice here is SN wallet, I see that as an option...

reply

You wanna give 500K CC that can only be spent on SN!

A bounty should be real money!

reply

I'm a little annoyed every time I send huge zaps someone replies "Too bad those are Soyboy Credits!" etc...

reply

Sweet. I'll check it out later tonight.

reply
10 sats \ 1 reply \ @Kruw OP 10 Aug

@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.

reply

Understood. Wild week.

reply