pull down to refresh
the result will be that any Bitcoin you hold will be slowly (or perhaps not so slowly, depending on your use habits) replaced by worthless scam-Bitcoins
The mechanism itself is what I find fascinating.
If, under the majority node rule, BIP110 fails to gain sufficient adoption, it will naturally fall away by that very rule. Watching how Bitcoin survives and stabilizes through this process is, to me, deeply interesting.
just create an bolt11 invoice. As far as I know, phoenix reusable address is based on bolt12 that SN does not support yet.
Outsourcing logic. You trust the electrum server's index and therefore you don't have to code a lot of logic.
So in the end, it seems that most wallets prioritize regular users’ convenience rather than sovereignty or privacy.
I think there simply should be a mobile wallet built around CBF by default.
Not everyone will use it, but some users will always prefer convenience over privacy.
But right now, there’s effectively no real choice unless he already knows what he's doing.
oh hell I had assumed I needed look at the fee policy for the channel between myself and Stacker.news, but I’ve now realized that the relevant policy is actually on the next hop, between Stacker.news and Megalithic.me, which takes 5000 ppm accroding to amboss and it makes sense it takes 26 sats.
Hm.. I don’t understand how LN node could interpret an incoming htlc as a zap and silently charge an application-level fee.
It was not a zap. It was a regular payment.
I have a private channel with the Stacker.news node, and when I sent the payment, I explicitly selected the Stacker.news channel as the first hop.
Great!! But it seems I can have only one wallet?? How can i delete the existing wallet? or seed? should i uninstall -> reinstall it?
Realized that taproot keypath output is no different than p2pk when it comes to quantum shor algorithm attack
I think segwit addresses are safe from long range attacks because they have another layer of hash
i think i get your point. segwit wraps pubkey around two hashes, sha256 and ripemd160, whereas taproot does not but rather commits to tweaked public key with bech32m and it reveals its tweaked pubkey to scriptpubkey field directly. That may be one attack surface even to the unspent taproot output??
Thanks for the link, I’ll take a look.
vulnerable to quantum computers
i believe everything under ECC is vulnerable to quantum computers, if that comes out publicly to the world. Do you have any reason why you think that taproot is specifically more vulnerable to Q-day?
Pretty sure taproot are slightly heavier.
Hmm.. i doubt that.. as far as key path spending wise..
comparing this taproot txn to this segwith txn which both have one input(taproot / segwit respectively) going to two segwit outputs, one with taproot input(key path spending) has txn weight of 520 WU, and the other with native segwith input has 562 WU.
Oh I didn't realize I could download the app through testflight. Anyway, I managed to recover my funds by deleting and reinstalling the app. I noticed they added a 'recovery tool'. if I run into this issue again, I’ll give that a try next time. Thank you.