I've been heads down building @Inherit_to , a self-custodial protection & recovery solution for your Bitcoin. Inherit is an easy way to protect Bitcoin in your hardware wallet against: ✅ Wrench Attacks ✅ Private key loss ✅ Unexpected life events We're fortunate enough to be a part of @PlebLab's Top Builder Program working alongside 13 other Bitcoin startups. Stoked to share more in the coming weeks!

“One of the worst crashes in history!” checks prices … Bitcoin at $96,000

@zachherbert I’d wipe it and start over in case it’s related to a virus.

@evanlinjin do you know if anyone has successfully used a version of async-hwi with bdk_wallet, considering that BDK is being deprecated? Also do you know if people are transitioning away from BDK to implement specialized wallet logic for things like time lock flows?

@salvatoshi Sweet, will try this out. Thank you!

RT @lynk0x: Crypto Traders when there's another opportunity to lose money

@chrismguyot 🔥🔥🔥

I understand at the protocol level, the witness I’ve constructed is sufficient to satisfy the CLTV spend condition and is valid for a Bitcoin transaction. Specifically, for a P2WSH CLTV script, my witness looks like this: witness[0] = The signature (matching the pubkey in my OP_CHECKLOCKTIMEVERIFY script). witness[1] = The full script itself (e.g., OP_CHECKLOCKTIMEVERIFY OP_DROP OP_CHECKSIG). From what I understand, this should be sufficient to satisfy the Bitcoin protocol rules. However, based on what you’ve said, it seems that Ledger’s Bitcoin app intentionally refuses to sign spending transactions with input scripts it doesn’t explicitly recognize, even if the PSBT and witness are valid at the protocol level. In other words, this isn’t a Bitcoin limitation, but rather a firmware policy decision embedded in the Ledger Bitcoin app. Is that an accurate understanding?

Thanks I don’t have an issue with the first part. The goal is specifically signing the spending transaction from the CLTV output—i.e., the transaction that uses the funds locked by OP_CHECKLOCKTIMEVERIFY. The process is broken down below: 1.Lock (Funding) Transaction: -This is where you send funds to a CLTV script. -I am easily able to sign this with Ledger since the input is a standard P2WPKH or similar recognized script. 2.Spending (Redeem) Transaction: -This is where you unlock those CLTV funds after the timelock. -Here, the CLTV script itself appears as the input script in the new transaction. -The problem lies here: Ledger firmware does not appear to recognize that custom script and refuses to sign it. Any guidance?

@RyanSAdams @drakefjustin Would that apply to time-locked bitcoin? 🤔

RT @BillHughesDC: 🚨🚨🚨Biden Administration 11:59 PM interpretive rule drop: TLDR: in order to protect consumers and to avoid a competitive…

@SuperRare @GoodVibesssClub @chrismguyot Wow, the detail in this art is insane! 🔥

RT @CryptoTaxGuyETH: UNIVERSAL WALLET REPORTING LIVES ON (FOR SELF-CUSTODIED CRYPTO) Have you seen a lot of noise on your timeline saying…

Only a matter or time until someone creates Bitcoin-native health insurance. @meanwhilelife but for health insurance.

RT @louishliu: Saylor has a message for people calling his company MicroStrategy a Ponzi scheme. His response is brilliant. https://t.c…

@TheProjectUnity

@Rob_Mahar07 @elonmuskADO $1 Bob

@uncomputab1e I have a few questions on simplicity, could you open DMs or DM me?

RT @elonmusk: America is a nation of builders Soon, you will be free to build