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

March 1st, 2017

”______ are trying to control Bitcoin!”

via Twitter Web Client

@ErikVoorhees @theonevortex @ShapeShift_io If you analyze the mempool and pay more than the current highest fee rate, it’s pretty likely. 😬

via Twitter Web Client in reply to ErikVoorhees

@ErikVoorhees @theonevortex @ShapeShift_io Perhaps you should make a list of recommended wallets that have user friendly fee handling.

via Twitter Web Client in reply to ErikVoorhees

@ErikVoorhees @theonevortex @ShapeShift_io In reality, the fee handling is a failure on part of wallets. Users shouldn’t have to know.

via Twitter Web Client in reply to lopp

@ErikVoorhees @theonevortex @ShapeShift_io A user will plug in that static fee, then sometimes create a tx with many inputs that gets stuck.

via Twitter Web Client in reply to ErikVoorhees

@ErikVoorhees @ShapeShift_io Looks like you’re making some assumptions here. https://t.co/FZCpIm9E44

via Twitter Web Client

@riprowan @SatoshiLite They’re both flawed in the same way. I outlined the cure in my medium post.

via Twitter Web Client in reply to riprowan

@SatoshiLite Bahahaha; it’s a false dilemma regardless. No one needs to choose either.

via Twitter Web Client in reply to SatoshiLite

https://t.co/HN6b9OKPvS updated to Bitcoin Core 0.14; new mempool persistence feature means no more metric cliffs w… https://t.co/EuaDkHt1tJ

via Twitter Web Client

@hitchslappy Well, larger legacy blocks and/or SegWit would reduce fees. Problem is 2nd layer isn’t ready yet.

via Twitter Web Client in reply to hitchslappy

@ollekullberg My point is more regarding dichotomy of exchange rate rise causing rise in transaction fees (even faster than exchange rate.)

via Twitter Web Client in reply to ollekullberg

It’s an odd combination of joy and disappointment, observing the gentrification of Bitcoin. pic.twitter.com/jRFhnagRBS

via Twitter Web Client