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

November 30th, 2015

@jbeardsley @jefft I just got a Cyber Monday deal email at 8 PM - looks like @FamousSmokeShop has a crappy ESP…

via Twitter Web Client

“The Future of Blockchain Technology” panel with @ajbeal, @shannonNullCode, and myself at @Cryptolina https://t.co/VGRQtpQ51r

via Twitter Web Client

An alternative perspective:
Replace By Fee is opt-in for attackers.
Replace By Fee is opt-out for victims.

via Twitter Web Client

Wanted: smart contracts for appointment timeliness. Penalize the counterparty for every TIME_UNIT they are late in fulfilling an obligation.

via Twitter for Android

@kristovatlas Sure, but we have this “fee market” where when someone gets outbid, they are prevented from updating their bid. It’s lopsided.

via Twitter Web Client in reply to kristovatlas

@kristovatlas *shrugs* It’s a fundamental problem of not being able to predict the future. You could also argue CPFP could fix it.

via Twitter Web Client in reply to kristovatlas

@kristovatlas Yeah, when there are demand surges for block space. Core’s fee estimator lags since it uses past day or so of trailing data.

via Twitter Web Client in reply to kristovatlas

@ciscoguru @21 It’s hard to predict specifics because this is a platform for building a new type of market. https://t.co/ernwMpSdl8

via Twitter Web Client

@khannib Right, right. Interesting - so far it’s a fair amount higher than I expected.

via Twitter Web Client in reply to khannib

@ciscoguru I forsee mass adoption of @21 chips occurring when they are embedded in devices that natively use BTC; buyers may be oblivious.

via Twitter Web Client in reply to ciscoguru

@ciscoguru @21 Devs should be buying bitcoin computers to access the micropayment network rather than for the mining aspects.

via Twitter Web Client in reply to ciscoguru

@khannib Nice, so that’s # txs with an input w/sequence != UINT_MAX? I’d phrase it as “Transactions Opting In to RBF”

via Twitter Web Client in reply to khannib

@ciscoguru @21 Pretty sure large miners have to sell most of their coins to pay for operating expenses anyway.

via Twitter Web Client in reply to lopp

@ciscoguru @21 Mining decentralization is more about preventing 51% attacks than about the distribution of the coins.

via Twitter Web Client in reply to ciscoguru

Visualization of the sigOps attack yesterday that caused “full” blocks that were not full: https://t.co/2uX6euD6Mx
https://t.co/ydONKLsdZY

via Twitter Web Client

@ciscoguru In general, anyone whose business relies upon supporting higher number of users and transaction volume has a vested interest.

via Twitter Web Client in reply to lopp

@ciscoguru I’m not so sure that exchanges have /as/ much of an interest especially with the Liquid sidechain being released soon.

via Twitter Web Client in reply to lopp

@ciscoguru Mining centralization is certainly a justifiable fear, which is why I hope @21 succeeds in decentralizing mining again.

via Twitter Web Client in reply to ciscoguru

Point being, anyone who deals with unconfirmed transactions at the moment needs to take action to flag RBF-capable txs and act accordingly.

via Twitter Web Client in reply to lopp

As it stands, anyone sending a tx can “opt-in” to RBF by setting the sequence field on inputs to be < UINT_MAX. But receivers have to check.

via Twitter Web Client in reply to lopp

“Opt-In” Replace By Fee won’t be truly opt-in (agreed upon by both parties) until wallet software & payment processors update their logic.

via Twitter Web Client

@khannib Would it be hard to add stats of transactions opting in to replace-by-fee (inputs with sequence != 4294967295) to your site?

via Twitter Web Client

@kristovatlas They both appear to be problems to me, though the former exacerbates the latter.

via Twitter Web Client in reply to kristovatlas

.@Bitstamp announces that they will support BIP101 as of December. https://t.co/O5HL2BUb0q

via Twitter Web Client

A new milestone: more than 10% of all bitcoins are now encumbered by P2SH! https://t.co/xm9r8QubWB https://t.co/vOQVJ8wWuL

via Twitter Web Client