The below is an off-site archive of all tweets posted by @lopp ever

December 5th, 2016

@mriou Bonus points for taking into account spending of unconfirmed inputs and how transaction dependencies slow down confirmation times.

via Twitter Web Client in reply to lopp

@mriou Right; it would have to be a dynamically calculated target.

via Twitter Web Client in reply to mriou

Block explorers should output “estimated confirmation block height” on unconfirmed txns based upon size of higher fee rate txns in mempool.

via Twitter Web Client

Truthcoin New blog post: helping us with Soft and Hard fork terminology. truthcoin.info/blog/protocol-…

via Twitter for Android (retweeted on 5:07 PM, Dec 5th, 2016 via Twitter Web Client)

@acityinohio @BlockCypher … but is it a suitable platform for scamming?

via Twitter Web Client in reply to acityinohio

Alternative perspective: BTC market cap dominance has risen above 87%. twitter.com/Datavetaren/st…

via Twitter Web Client

@TuurDemeester That’s just the quote from A Princess Bride

via Twitter for Android in reply to TuurDemeester

The real Dread Pirate Roberts is retired and living like a king in Patagonia. motherboard.vice.com/read/someone-a… pic.twitter.com/KmCXfZR4x6

via Twitter Web Client

The first step to improving your OPSEC is admitting that your OPSEC is weak.

via Twitter Web Client

@flyosity @amazon coming full circle and going brick & mortar.

via Twitter Web Client in reply to amazon

Every second you spend focused on drama is a second you could have spent constructively focused upon improving your life.

via Twitter Web Client

@ciscoguru IIRC Trezor has an ARM CPU, Ledger has some kind of secure element. Is there proof of no backdoors at hardware level?

via Twitter Web Client in reply to ciscoguru

2 ways to protect your BTC from CPU backdoors:
* Only sign txns with offline computers.
* Only sign multisig txns w/keys on diff machines.

via Twitter Web Client