Post
Topic
Board Speculation
Re: Wall Observer BTC/USD - Bitcoin price movement tracking & discussion
by
jbreher
on 22/05/2019, 04:05:21 UTC

But if we want Bitcoin to succeed as the financial backbone of the planet, what are our choices?
1) SV's openness to storing arbitrarily huge amounts of data may lead to a small number of players at each task within the system, governed only by open competition. As a bonus, in the huge data scenario it becomes the backbone of the Internet.
2) BTC has already abandoned being the default money for the world, being utterly unable to even onboard the world to LN in less than a quarter century.
3) BCH is headed towards unlimited numbers of txs, albeit each one limited in size. At the cost of the perhaps unforgivable sin of centralized checkpointing.

So far, SV still looks like the preferable route forward to me. Current market share notwithstanding.

1) Significantly altered bitcoin's game theoretics
2) Significantly altered bitcoin's game theoretics, but those changes can (will?) be rolled back by miners
3) Significantly altered bitcoin's game theoretics

You missed one:
4) The Real Bitcoin™

As in TMSR, or pre-(what was it)-0.85 Bitcoin? OK. Add it to the list. Again, I believe its tx per unit time will be its downfall, just like BTC.

YMMV. Objects in mirror may be closer than they appear. Not to be used for the other purpose. This furniture product is not a gateway to Narnia. Keep chain from testicles.

eta: If rollback occurs upon 2), then it collapses into 4), no?

Pretty much - it's based on 0.5.3.

Thanks. I had lost track of the specifics.

Quote
And as to that question - yes. I was hesitant to give TRB a new number. We could call it 2.5.

As for more TX/s, I'm leaning toward the TMSR/Shelby school of thought that the 1MB blocksize is an immutable part of the protocol. Do you think Bitcoin was intended to scale to the masses?

Yes. Public utterances by Satoshi tend to corroborate that postulate. Though I admit that it is impossible to know what is really in the mind of another.

Quote

The lock limit is not a limitation that was manifested within the protocol (i.e., on the wire). It was strictly a limitation of Bitcoin's client SW implementation. As a professional protocol developer, I look at things that are not enforceable 'on the wire' as not being part of the specification. As a system that works only to the extent that it ingeniously and carefully balances incentives, it is absurd to consider aspects that could be overridden by another client SW implementation as being intentional design decisions. We know (or surmise) from other suboptimal threading aspects of the SW that the original implementation suffers from the programmers' poor understanding of multithreading dynamics.