0 sats \ 1 reply \ @delta1 29 Apr \ on: How is tapscript different than P2PKH using opcodes from a developer perspective bitdevs
Murch with the incredibly well written answers every time!
hey! thanks for your thoughtful reply. interestingly i don't ever remember what their specific arguments were, but as a young technologist with little understanding of the fiat system i was swayed by their "authority".
absolutely right about their negative reactionary nature towards bitcoin, i'm convinced most of those commenters make up /r/buttcoin.
thanks for the sympathies :) my coping mechanism is to convince myself i would have lost my keys or sold in a previous run. now that i understand it far better those 2 things are far less likely to happen! we are definitely still early, but everyone must learn that from first principles in their own time right.
we all get bitcoin at the price we deserve
never read the comments. HN put me off Bitcoin in 2011 which is obviously a huge regret. i could have started my proof of work much sooner by being more curious, instead of influenced by salty commenters.
a well made guitar with a good case needs very little maintenance and cleaning to last for life
i have a Fender Telecaster with a spalted maple top that i plan to keep forever 🧡
some notes:
mercury: you are trusting the coordinating server to delete the private key share on each transfer…
liquid: the emergency timelock is 4032 bitcoin blocks, so more like 28 days
you can use the alby extension
but yes if you need to sign then something must have access to your nsec