Cryptodude46 | #BIP-110

[Cryptodude46 | #BIP-110 @cryptodude46]

@cguida6 @LukeDashjr PoW change is the nuclear option.
17.000 nodes are enforcing #BIP110 so let's keep calm and hold the line even in case of initial low signaling.
Get prepared! 💪🏻💪🏻💪🏻

[Cryptodude46 | #BIP-110 @cryptodude46]

@cguida6 @LukeDashjr PoW change is the nuclear option.
17.000 nodes are enforcing #BIP110 so let's keep calm and hold the line even in case of initial low signaling.
Get prepared! 💪🏻💪🏻💪🏻

[Cryptodude46 | #BIP-110 @cryptodude46]

@EnjoyingBitcoin And they will lose 15%-20% of the market.

[Cryptodude46 | #BIP-110 @cryptodude46]

We need just to wait and hold the line. #BIP110

[Star Heartsong · making BIP110.run 🤟 @DrStarHeartsong]

🚨BREAKING🚨 You guys... @BitcoinKnots v29+RDTS is now the number #1 🥇 bitcoin node client software version among @LukeDashjr's census of Bitcoin nodes! This just happened. 🔥🏆💯 Keep doing what you're doing, don't stop. #BIP-110.

[Star Heartsong · making BIP110.run 🤟 @DrStarHeartsong]

🚨BREAKING🚨 You guys... @BitcoinKnots v29+RDTS is now the number #1 🥇 bitcoin node client software version among @LukeDashjr's census of Bitcoin nodes! This just happened. 🔥🏆💯 Keep doing what you're doing, don't stop. #BIP-110.

[Luis Marcano 🦉 BITCOIN ONLY👨‍💻RDTS (BIP-110) @MarcanoFilms]

BIP-110 mandatory signaling is days away.

38 / 1430 blocks signaling (2.7%).

Need 1109/2016 for early lock-in.

~587 blocks until mandatory.

We already knew miner support would be weak. That was never the point.
People keep confusing who actually decides the rules of Bitcoin.
Miners produce blocks.

Node runners enforce consensus.
This is decentralized by design. The protocol itself gave us the tools (version bits + mandatory signaling window). We are using them.
Node runners are putting things back in their proper place.
Run Knots. Enforce the rules. Don’t Trust. Verify.
#BIP110 #BitcoinKnots

[Cryptodude46 | #BIP-110 @cryptodude46]

@Rob1Ham Thanks for you effort on this. Appreciated! 🙏

[Rob Hamilton @Rob1Ham]

IMPORTANT UPDATE

WE HAVE CONFIRMATION FUNDS ARE STILL BEING RECOVERED ON NO PASSPHRASE MK3 DEVICES.

THERE IS HOPE FOR RECOVERY IF YOU ACT FAST

MK4S WITH SHORT PASS PHRASES ARE BEING SWEPT

NO ONE IS SAFE ACT NOW

GET YOUR BITCOIN OFF COLD CARDS

[Cryptodude46 | #BIP-110 @cryptodude46]

@nvk

[Cryptodude46 | #BIP-110 @cryptodude46]

@GrassFedBitcoin, @mattkratter , @BtcInfinityShow, any chance to spread on your channels this is a fake news? Thanks

[Udi #BIP110DELAYED @udiWertheimer]

🚨🚨🚨BREAKING: GOOGLE CONFIRMS BIP-110 ACTIVATION HAS BEEN OFFICIALLY CALLED OFF

[Cryptodude46 | #BIP-110 @cryptodude46]

@udiWertheimer, My node is till running and enforcing #BIP110. So do thousands of nodes. Please, explain the community how the "lead devs" @LukeDashjr , @GrassFedBitcoin, @dathon_ohm, @cguida6 might have preventing this from activating on August 8th.

[Udi #BIP110DELAYED @udiWertheimer]

🚨🚨🚨BREAKING: GOOGLE CONFIRMS BIP-110 ACTIVATION HAS BEEN OFFICIALLY CALLED OFF

[Cryptodude46 | #BIP-110 @cryptodude46]

😅

[BULLBITCOIN.COM @BULLBITCOIN_]

Bitcoiners right now

[Cryptodude46 | #BIP-110 @cryptodude46]

@BULLBITCOIN_ 😅

[Cryptodude46 | #BIP-110 @cryptodude46]

Let's speak the truth. It's not self-custody nor @Coldcard users that failed but only @Coinkite disastrously.
The @Coldcard is the only wallet having a low entropy issue. 👇👇👇

[Scott Marmoll @bitcoinsbanker]

Thanks to a generous credit of tokens from @PPQdotAI , Kimi K3 and an ape with a laptop (me) have conducted the following analysis of a bunch of projects / companies wallet softwares. @Coinkite , @OPENDIME , @SeedSigner , @Bitkey , @bluewalletio , @PhoenixWallet , @SparrowWallet , @Trezor , @Blockstream , @Ledger , @BitBoxSwiss , @SpecterDIY , @ElectrumWallet , @SamouraiWallet

🟡 Yellow ≠ broken. None of the nine Yellow products has a confirmed fund-loss-by-default flaw. Yellow means at least one of: (a) something security-critical sits outside independent verification. i.e., closed firmware or secure-element code (Opendime, Ledger, open source please!), vendor-run recovery infrastructure (Phoenix/ACINQ, Jade's oracle, Bitkey's WSM); (b) a real but bounded weakness, such as a zero-work-factor KDF (BlueWallet), weak legacy KDFs on a hot wallet (Electrum), no-SE DIY hardware with thin maintenance (SpecterDIY), a just-patched vulnerability awaiting its report (Bitkey); or (c) a dead/unmaintained product whose crypto reviewed clean (free Samourai!). In every case the entropy/key-generation path itself was reviewed and found sound unless the cell says otherwise.

[Warren Togami @wtogami]

None of my engineer friends have CC. I had no idea CC had so many users. I'm afraid the most vulnerable to CC were those listening to influencers instead of engineers. NVK had antagonized engineers years ago which didn't help a white hat to be able to find this before black hats.

[Cryptodude46 | #BIP-110 @cryptodude46]

@JoelHodlman Throw it in the trash dyi a @SeedSigner

[+rapidlab309 @rapidlab309]

Confirmed #COLDCARD bricked 💀

A rushed firmware hotfix introduced a critical failure: a transient STM32 TRNG error could permanently fault the RNG. Since it’s used before the PIN screen, affected devices to become effectively bricked.
https://t.co/qloYvCygAm

[Softfork Mechanic #BIP-110 @GrassFedBitcoin]

Hey @tradingview you forgot to ask @jarule whether or not the fork was still on 😂

[Cryptodude46 | #BIP-110 @cryptodude46]

@BTCsessions 2 of 3 multisig with seeds created with @SeedSigner , @SpecterDIY and bitcoinlib running on a Raspberry/laptop always offline device.
It requires some technical skills but all of the three are dyi open source projects I would trust the most.

[Cryptodude46 | #BIP-110 @cryptodude46]

@4nt1b110 @wtogami So It would be a mouse and cat game between the attacker and the victim, wouldn't It?
And what about the multisig case disbling RBF should mitigate?
If the miner pools disabled RBF, would that prevent an attacker from RBF a transaction from a vulnerabile multisig address?