Share this page!

Maybe Scrolly?
Murch Profile picture
Twitter logo
Apr 29 • 7 tweets • 4 min read
It's been a while since I asked. Were there any updates on bech32m/P2TR readiness that I missed? #bech32msupport, #P2TRsupport

Software wallets, hardware signers, web wallets, ATMs,… ImageImageImageImage
…exchanges, payment processors, libraries,… ImageImageImageImage
…mining pools: Image
Full table: en.bitcoin.it/wiki/Bech32_ad…
Updated LND to "Code merged": P2TR support coming with v0.15. Image
Update:
• Trust Wallet: sending support, P2TR not planned
• Bitaccess BTM: Working on sending support, planning P2TR
Update:
• @exodus_io added support for sending to bech32m addresses (via support.exodus.com/article/1480-b…) Image

• • •

Missing some Tweet in this thread? You can try to force a refresh
　

Keep Current with Murch

Murch Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @murchandamus

Murch Profile picture
May 2
🧵I've been seeing a few comments lately that blockweight is an ugly hack, the witness discount was a mistake, and that the blocksize increase was unnecessary. A few thoughts.👇
Segwit was a bug fix, an efficiency improvement, and a blocksize increase. Economic incentives drive segwit adoption. Blocks have been mostly bigger than 1 MB since end of 2018.

via transactionfee.info/charts/block-s…; 2017–today; 7d, 30d, 100d averages; 1 MB line added by hand.👇 ImageImageImage
We have seen in the past what happens when blockspace demand exceeds the stable block production: feerates explode through the roof as transactions outbid each other to get confirmed. Then the market slowly adopts best practices to do more with less blockspace.👇 Image
Read 8 tweets
Murch Profile picture
Apr 15
1/ It's not only about RPis at home. A 10 s block interval would mean that block propagation and block validation take a significant chunk of the interval.
You'd get blockchain forks abound, poor block relay because of many competing chaintips, bad network convergence,…
2/ … large miners would be hugely advantaged by being able to build on top of their own block immediately instead of needing to wait to receive foreign blocks, which causes mining centralization and supercharges selfish mining.
3/ The high cost-of-node-option (CONOP) would crowd out most validators due to bandwidth, computational, and disk space requirements as well as the slow IBD. Small businesses and retail users would be forced to rely on 3rd parties for validation.
Read 6 tweets
Murch Profile picture
Apr 11
@achow101, @glozow, and I have been scrutinizing the Bitcoin Core wallet coin selection lately. We have multiple ideas for improvements, but we have very little usage data to evaluate them. So far, we have one scenario generated from a service's data.
We're looking for…
• people living on Bitcoin
• Bitcoin power users
• fervent sat stackers
• services

that would be willing to share payment history (from any wallet) with us.
We're looking for large sequences of `{±amount, feerate}`. Amounts can be slightly altered or rounded for privacy. Image
We mostly care that the payment sequence was generated by one entity rather than us assembling random unrelated data from the blockchain. The data would be used to add scenarios to github.com/achow101/coin-…, which we're using to test Bitcoin Core wallet improvements.
Read 4 tweets
Murch Profile picture
Apr 11
As people were getting ready to get married on the beach, a brief discussion of economic incentives of cross-input signature aggregation (CISA) led to an interesting comment (H/T @n1ckler) that made me rethink my characterization of its potential cost savings. 🧵/9
CISA refers to the idea of multiple inputs on a single transaction sharing a single signature. This is possible due to all signatures committing to the same message (i.e. to all outputs via `SIGHASH_DEFAULT`) and the signing algorithm's linearity. 2/9 bitcoin.stackexchange.com/a/107068/5406
Enabling CISA would require a new output type as it would be a breaking change to how P2TR works. 3/9 bitcoin.stackexchange.com/q/106240/5406
Read 9 tweets
Murch Profile picture
Feb 19
"bits" is a horrible name for a subunit of bitcoin. I'll die in that hill.
Other examples why "bit" as the standard unit of bitcoin amounts would be confusing AF:
• "This setup has 180-bit security"
• "If you keep all your bitcoin in one address, a single bit flip could lose it all."
• "The current difficulty bits are 0x170a1078."
Read 7 tweets
Murch Profile picture
Nov 14, 2021
🥕🥕🥕🥕🥕🥕🥕🥕🥕🥕🥕🥕🥕🥕🥕🥕
🥕🥕🥕🥕🥕TAPROOT IS LIVE🥕🥕🥕🥕🥕
🥕🥕🥕🥕🥕🥕🥕🥕🥕🥕🥕🥕🥕🥕🥕🥕
First Taproot transactions are in block 709635:
First Scriptpath spend:
Read 5 tweets

Did Thread Reader help you today?

Support us! We are indie developers!

This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us on Twitter!

:(