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

May 30th, 2015

glassbottommeg Players would hide the dongs where the filtering couldn’t see, or make them only visible from one angle / make multi-part penis sculptures.

via Twitter for iPhone (retweeted on 11:38 PM, May 30th, 2015 via Twitter Web Client)

glassbottommeg Funny story - we were asked to make dong detection software for LEGO Universe too. We found it to be utterly impossible at any scale.

via Twitter for iPhone (retweeted on 11:35 PM, May 30th, 2015 via Twitter Web Client)

From my perspective, the Core Devs who are fighting against increasing the block size are losing the community’s support; Gavin is winning.

via Twitter Web Client

I rarely disagree with Greg Maxwell, but I think it IS the job of Core Devs to convince the community to accept or refuse major changes.

via Twitter Web Client

At the end of the day, Bitcoin is not what the Core developers agree upon. It’s not what the miners agree upon. It’s what we ALL agree upon.

via Twitter Web Client

Seems to me that everyone is overlooking the fact that @gavinandresen’s 20 MB block limit proposal will keep the default block size at 750KB

via Twitter Web Client

@pm_lyon Probably hard to do a 1:1 comparison because we’re also doing work related to all of the wallets we manage

via Twitter for Android in reply to pm_lyon

@pm_lyon My best efforts so far have reduced it to exactly 24 hours but I’m sure that there are still some bottlenecks I haven’t found.

via Twitter for Android in reply to pm_lyon

@pm_lyon Yeah, we are multithreading our tx processing and using a cluster of RAM based DBs.

via Twitter for Android in reply to pm_lyon

@aantonop Thanks! I hope my writing encourages other Bitcoin developers to post lessons learned / best practices. We’re in this together.

via Twitter Web Client in reply to aantonop

@pm_lyon Thus our ‘source of truth’ as to if a UTXO is spendable is whether or not it exists in the UTXO table.

via Twitter Web Client

@pm_lyon Originally we’d mark outputs as ‘spent’ on the tx itself, now we instead delete the UTXO from the UTXO table.

via Twitter Web Client

@pm_lyon Thanks for the response. It sounds like you’re doing something similar to us; we have a separate table for unspent outputs.

via Twitter Web Client

@LaurentMT @MarsuTwitt My assumption is that it was just variance that hit coincidentally.

via Twitter Web Client in reply to LaurentMT

LaurentMT Interesting charts about last night bitcoin “stress test” (from @blockr_io) cc: @lopp @MarsuTwitt pic.twitter.com/pVQwgojMXp

via Twitter Web Client (retweeted on 10:41 AM, May 30th, 2015 via Twitter Web Client)

@LaurentMT @MarsuTwitt Obviously we need to perform more stress tests in order to gather more data points :-)

via Twitter Web Client in reply to LaurentMT

.@Cpzhao confirms what many of us have suspected about @OKCoinBTC’s volume, trading practices, and more: reddit.com/r/Bitcoin/comm…

via Twitter for Android

@gavinandresen Does this mean you are now considering increasing the default block size along with the limit?

via Twitter for Android in reply to gavinandresen

A unique realtime visualization of unconfirmed bitcoin transactions: dailyblockchain.github.io

via Twitter Web Client

@flyosity Another possibility, if Bitcoin maximalism does take hold - I guarantee in that scenario the Bitcoin Barons will free him ;-)

via Twitter Web Client in reply to flyosity

@flyosity I’m optimistic, but I find it unlikely that he’ll spend his entire life in prison given the current trajectory of public sentiment

via Twitter Web Client in reply to flyosity

@oocBlog @pierre_rochard @port8333 is monitoring every node that accepts incoming connections AFAIK. Which is ~20% of the nodes by my guess.

via Twitter Web Client in reply to oocBlog

@oocBlog @pierre_rochard Hmmmm you should talk with Addy at @port8333; I think he has the data, just not exposing it via his API.

via Twitter Web Client in reply to oocBlog