Yes, wallet default45.5%
Yes, I go out of my way to use them18.2%
No, my wallet doesn't support21.2%
I don't go on chain much15.2%
33 votes \ poll ended
pull down to refresh
30 sats \ 0 replies \ @Lumor 11 Apr
Considering that quantum computing could have an easier time attacking naked pubkeys on-chain (Taproot) than more ephemerally exposed pubkeys in the mempool (spending from Segwit), I am hesitant to use Taproot.
reply
10 sats \ 0 replies \ @cyro 11 Apr
I still use Segwit
reply
100 sats \ 0 replies \ @klk 11 Apr
Yes for privacy, but sometimes hurts to pay slightly higher fees than with segwit.
reply
100 sats \ 0 replies \ @Hodl117 11 Apr
My cold wallet does not support taproot, but at least one of my hot (phone, Lightning) wallets does. Maybe someday I'll switch my cold storage over to it -- probably whenever I get my Lightning node up and running.
reply
100 sats \ 13 replies \ @OT 11 Apr
Why do you ask?
reply
152 sats \ 12 replies \ @Wizardsardine OP 11 Apr
Considering making Taproot addresses default in Liana Wallet (currently user has to choose).
reply
200 sats \ 11 replies \ @DarthCoin 11 Apr
from now on, all new txs must be taproot.
reply
0 sats \ 1 reply \ @OT 11 Apr
why?
reply
40 sats \ 0 replies \ @DarthCoin 11 Apr
- greatly increase the efficiency of the Bitcoin network
- reduces transaction sizes and increases throughput during high-stress periods - less fees
- increases privacy and security via transaction and signature compression
- allows for native smart contract implementation - better LN channels
- more seamless support for new future LN implementations
... and some more but don't come to my mind rn
reply
0 sats \ 8 replies \ @flat24 11 Apr
That is, I should move my utxo's saved from bc1 to directions Taproot?
reply
1 sat \ 7 replies \ @DarthCoin 11 Apr
bc1q (segwit) is still OK
bc1p (taproot) is desired.
https://darth-coin.github.io/wallets/move-btc-taproot-address-en.html
bc1 are ok, but I still see people with legacy addresses... losers.
reply
13 sats \ 2 replies \ @dwami 11 Apr
I read that taproot could be more vulnerable to Quantum Computer because they expose the public key while the other sha256 hash it. They argue that since QC are not good at hacking hashes this could protect the others address type till you spend them so they could be attacked only in the confirmation phase while for P2TR you have a long exposure of your public key in the block chain. I do not think this is a problem right now but I would like to hear some opinions of the great minds present out here ;-)
view all 2 replies
0 sats \ 3 replies \ @nichro 11 Apr
Only time I see legacy addresses are for multisig these days
view all 3 replies
10 sats \ 0 replies \ @Dkryptoenth 12 Apr
I don't even know what taproot addresses are ... 🫣 think I should be scolded for that.
reply
10 sats \ 0 replies \ @Satoshi__Nakamoto 11 Apr
My wallet has this feature
reply
0 sats \ 0 replies \ @LibertasBR 11 Apr
I started not long ago and I'm learning little by little. Taproot isn't mentioned in the videos I find to introduce new Bitcoiners (in my language), unfortunately. As soon as I read about it and looked into it more, I set up my cold wallet using that standard and already transferred my sats there.
reply
0 sats \ 0 replies \ @Riberet 11 Apr
Yes, I started using taproot recently.
reply
0 sats \ 5 replies \ @justin_shocknet 11 Apr
Where's the hell no option? Still hoping it gets rolled back to own to script kiddies. 🍿
reply
17 sats \ 1 reply \ @Wizardsardine OP 11 Apr
Good point, should have had a "No, I don't like taproot" option.
reply
10 sats \ 0 replies \ @justin_shocknet 11 Apr
All joking aside there's a case to be made not to use newer address types for cold storage, heck exchanges still aren't using segwit in many cases.
reply
17 sats \ 2 replies \ @ek 11 Apr
You’re so edgy
reply
31 sats \ 1 reply \ @justin_shocknet 11 Apr
I do my best
reply
17 sats \ 0 replies \ @ek 11 Apr
You’re doing great
reply
0 sats \ 1 reply \ @BlokchainB 11 Apr
Not yet. Still mostly using SegWit
reply
47 sats \ 0 replies \ @flat24 11 Apr
x2 ✌️🤠
reply