Armin

Facinated by the Bitcoin privacy problem

Researcher at @mitDCI

Host @bostonbitdevs

[Armin @Arminsdev]

@stevenroose3 @stutxo @secondhq @btcplusplus @CashuBTC @Breedlove22 Love a persimmon. Fun fact if you ever have a not ripe persimmon, you can boil it briefly and it tastes as good 👍

[Armin @Arminsdev]

@stevenroose3 @stutxo @secondhq @btcplusplus @CashuBTC @Breedlove22 Is the fruit tasty? Never tried it

[Jonathan HB @jonhbit]

Its been 10 years, time for an update

This is way easier with Lightning and providers like @lexeapp . Opus and I coded the receive logic in maybe 90 mins - redoing the wiring took longer.

Thanks to @Arminsdev , @neha , and the @mitDCI team for keeping this alive 🙏

Demo:

[Armin @Arminsdev]

@stutxo

[Armin @Arminsdev]

@xstoicunicornx @stutxo it was the best!

[Armin @Arminsdev]

@stutxo Yeah this is what I kinda expected

[Armin @Arminsdev]

@BitsagaRob What is the pegin and pegout mechanism ?

[Armin @Arminsdev]

@BitcoinErrorLog @1440000bytes There are other ways to do this but they come with their own trade offs: https://t.co/TuV96D5gpU

The fixed r-point OP_CAT construction is just much simpler

[satsie @satsie]

New zine drop 🐱 OP_CAT! 🐱

[satsie @satsie]

Pages 1 - 4 of the OP_CAT zine

[Armin @Arminsdev]

New @satsie zine dropped!! All about OP_CAT!

[satsie @satsie]

New zine drop 🐱 OP_CAT! 🐱

[Matthew Vuk 🛳️ @matthewvuk2]

Lillian Wang of @mitDCI publishes her report: "A Comparison of Bitcoin Covenant Proposals for Vaults"

https://t.co/27OTCylLZe

[Trezor @Trezor]

Our third-party e-mail provider has been breached. Please be aware that the email named ‘Critical Security Alert: STM32 Entropy Vulnerability’ is not coming from us, and it’s a phishing attempt. Do not click on any link.

We have taken down the domain, and we are investigating the situation, including how the hackers got access to our legit domain.

[Armin @Arminsdev]

@side_swap Why was sideswap's key part of the PAK list? It's odd that writing these guard rails was your responsibility to begin with

[Neha Narula @neha]

Quick explanation and thoughts on yesterday's Liquid hack:

https://t.co/8LOacgkBuP

[orangesurf @OrangeSurfBTC]

The widely used @mempool fee recommendation algorithm looks at your nodes next 3 projected blocks, finds the median fee rate of each and computes priority tiers.

In contrast, Bitcoin core has historically only used *confirmed* blocks for it's fee estimate, but a new mempool based fee estimate algorithm has now been merged.

This new bitcoin core approach is only used to *lower* the fee estimate meaning estimates quickly drop if the mempool clears out, but won't instantly rise if a flood of high feerate transactions come in after a period of low fees.

https://t.co/GWHZLbwPiz

[Spiral @spiral_xyz]

New from our Bitcoin Wizards division: The Many Headaches of CoinJoin. The anonymity set you were promised assumes an adversary with no memory and no block explorer. Real adversaries have both and who knows what else.

[Boston BitDevs @bostonbitdevs]

Thanks to everyone that came out last night!

Never forget when we were talking about the future of Boltz, opened up Twitter, and this was the first thing that appeared.

[Armin @Arminsdev]

@bostonbitdevs This was halarious!

[Spiral @spiral_xyz]

.@weikeng is building Private Information Retrieval (PIR) for bitcoin: query the UTXO set without revealing what addresses you are interested in. It’s a rare way to gaze into the bitcoin abyss without it gazing back.