pull down to refresh

Nobody voting yes is actually keeping a meaningful amount of Bitcoin in a Taproot address, can all but guarantee they're bandwagon jumping hypocrites.
My hot wallet is, by utxo count, 97% taproot. My cold storage is 100% taproot but I did that much too early and should have waited for greater adoption and rolled over to a new p2wpkh setup instead.
I remember p2sh taking forever to get used too though, would you say that that was a disaster too?
Between you and @nout we've found the bulk of Taproot outputs....
Why do you use it? What's it doing it wasn't before?
The disaster is in the precedent it set, that useless forks can be astroturfed into activation... And now every shitcoiner that thinks Bitcoin should be an application stack is pushing for new ops
reply
117 sats \ 1 reply \ @optimism 15 Sep
Us and a bunch of degens spamming pics, I guess.
Why do you use it?
On hot wallet basically because its what wasabi coinjoin does most for smaller sized outputs, so it's just a thing for joining the larger anonset. I do think that this is a more recent development; iirc i used to have more p2wpkh before. I don't really care either way on hot. Most of it gets spent through LN often sooner rather than later.
On cold wallet, the honest answer is because i thought it was cool that an observer doesn't know whether its a script or a pk output. Which is, I admit, a dumb reason and i should have skipped it until at least there was a battle tested FROST implementation I could use. So yeah... feel free to call me a retard on that one.
reply
wasabi coinjoin
oh no... I have to get to work today so won't take the privacy bait ;)
but yea with hot its fine for experiments
Cold ... frost ... retard
Privacy again oof...
FROST is an interesting concept though, have looked at it in context of nostr identity re: @bitcoinplebdev's project... but not convinced yet on the Bitcoin side it's any better than multisig or shamir, I also don't spend much time thinking about vaulting products... yet. I do anticipate getting into that rabbit hole for ShockWallet eventually. The ultimate irony would be if I'm the one to actually make it useful.
reply
17 sats \ 4 replies \ @nout 15 Sep
For me it slightly lowered my fees, from usage standpoint it's exactly the same UX across the board and then I'm happy if there are some privacy or scaling capabilities that this enables for me or others in future.
To be clear this is why in the survey I voted "Mixed (please comment)". While I'm using taproot across the board (apparently in some cases also in LN context), it has not been a complete game changer. There is a recent uptick in usage, which may be a good sign, but we will have to see.
reply
it has not been a complete game changer
I think that's the crux of any argument, where the bar for introducing unknown unknowns is.
Since it hasn't been a game changer, resulting in lukewarm adoption at best so far, proponents got it through on pure speculation and hype rather than substance and that is a very dangerous precedent.
reply
Yes, I agree with the argument and different people will have a different tolerance here. Some things are hard to predict and take time to mature.
My guess would be that in 2 years from now there will be much wider taproot adoption with at least 2 notably taproot-only beneficial usecases being deployed and used. At that point, if that happens, I would vote YES.
reply
things are hard to predict
My guess
if
So are you of the opinion we should continue making changes Bitcoin, introduce new unknown unknowns, based on these speculative feels?
Or do you concede that it was a mistake to activate Taproot based on guesses and chance?
reply
I would be in favor of making another change that had similar uncertainty as taproot. I think that's around where my bar is.
reply