pull down to refresh
Considering making Taproot addresses default in Liana Wallet (currently user has to choose).
from now on, all new txs must be taproot.
That is, I should move my utxo's saved from bc1 to directions Taproot?
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.
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 ;-)
could be more vulnerable to Quantum Computer
sell all your BTC right now ! Is literally pointless to hold BTC if you believe that crap shit.
We all gonna die!
https://video.nostr.build/8345cd80358ff40077d46408074bfadd1b4053ca7e306d6b487fcba14cf13a03.mp4
;-)
Only time I see legacy addresses are for multisig these days
if somebody still use a legacy address, it means they didn't even got doubled their BTC stash in the 2017 fork... LOL such losers.
I always assumed there was a technical or economical reason all multisig I've encountered so far seemed to use "3xxx" nested segwit (instead of native segwit or Taproot)
is that not the case?
Then again I haven't rabbitholed into multisig proper yet
those are not legacy. All those addresses are post-fork.
legacy addresses start with 1
why?
- 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
Why do you ask?