@mriou Bonus points for taking into account spending of unconfirmed inputs and how transaction dependencies slow down confirmation times.
@mriou Right; it would have to be a dynamically calculated target.
Block explorers should output “estimated confirmation block height” on unconfirmed txns based upon size of higher fee rate txns in mempool.
RT @Truthcoin: New blog post: helping us with Soft and Hard fork terminology. https://t.co/pY2BQksYIC
@acityinohio @BlockCypher … but is it a suitable platform for scamming?
Alternative perspective: BTC market cap dominance has risen above 87%. https://t.co/xC25IH57RK
@TuurDemeester That’s just the quote from A Princess Bride
The real Dread Pirate Roberts is retired and living like a king in Patagonia. https://t.co/GIZMNB84Ok https://t.co/KmCXfZR4x6
@kristovatlas Self-admission should suffice!
The first step to improving your OPSEC is admitting that your OPSEC is weak.
Every second you spend focused on drama is a second you could have spent constructively focused upon improving your life.
@ciscoguru IIRC Trezor has an ARM CPU, Ledger has some kind of secure element. Is there proof of no backdoors at hardware level?
2 ways to protect your BTC from CPU backdoors:
* Only sign txns with offline computers.
* Only sign multisig txns w/keys on diff machines.