Justus Ranvier
Active Member
- Aug 28, 2015
- 875
- 3,746
RES tagging is starting to pay off. Now I'm seeing instigators who were previously trolling in one direction change sides and start trolling in the other direction.
@Justus Ranvier That's an interesting statement what conclusions could you draw from your observed behavior?Now I'm seeing instigators who were previously trolling in one direction change sides and start trolling in the other direction.
Someone is trying to stir up as much conflict as possible. They don't have any preference for < 1 MB blocks or for >1 MB blocks - they only care about maximising drama.@Justus Ranvier That's an interesting statement what conclusions could you draw from your observed behavior?
I don't even attempt to guess in most cases. I'd be nice to set up a Baynesian classifier, but I don't have that kind of time.And do you consider many of your tags to be sock puppets? (It's so funny that last question probably doesn't make scene to half of those reading it)
Read this, which I call a distributed trustless merkle tree.@theZerg
Surely the following is from something I must have read somewhere, but I can't place it? At the risk of sounding stupid, here goes anyway.
I was thinking about partial chain validation and reducing the size of the blockchain for home nodes. Would there be a way for a node to provably only validate say only 50% or 25% of the blockchain? (in each case including all related local transactions). There might even be a relay network amongst other nodes so 4 x 25% nodes could cryptographically confirm they held a 100% validated blockchain?
This idea would obviously reduce the pressure on locally stored data and remove the issue of loosing home nodes. Suppose if it were possible it could even be extended to 1000's of nodes so each could validate 5% of the chain?
Am I thinking of treechains and is there any mileage here?
How do you efficiently take the 60GB linear blockchain and reorganize it into a balanced tree, rebalancing as each new block comes in?So how can we do better? Start with the "big picture" idea and take the
linear blockchain and turn it into a tree:
┌───────┴───────┐
┌───┴───┐ ┌───┴───┐
┌─┴─┐ ┌─┴─┐ ┌─┴─┐ ┌─┴─┐
┌┴┐ ┌┴┐ ┌┴┐ ┌┴┐ ┌┴┐ ┌┴┐ ┌┴┐ ┌┴┐
Might be worth reviewing why we have a blockchain at all.How do you efficiently take the 60GB linear blockchain and reorganize it into a balanced tree, rebalancing as each new block comes in?
Yeah, this was my concern too, so I think we have to be careful with the messaging. I think "Bitcoin Unlimited" is a great name because of all the positive connotations of "unlimited" ("unlimited potential!" "unlimited data plan!" "unlimited breadsticks!"), but when people hear it they'll also tend to think in terms of "unlimited block size" which sounds scary ("oh noes, how would the network handle 1 TB blocks?"). So it's important to present BU in terms of something that allows for an "emergent block size limit" or a "market-determined block size limit." (And contrast this with a block size limit that's determined by the Core committee of central planners.) I don't even like the term "big blocker" for similar reasons. I'm not really pro-big blocks. I'm pro-block choice. I know that if miners really want larger blocks, they're going to get them. I'd prefer they do so safely through the most heavily secured blockchain there is, and not through some dangerous back-alley altcoin.The name "unlimited" looks at first like "Let's just make the blocksize infinite". I know, it's more behind, but most people will think "Infinite blocks? Ha. There is not even a consensus about 8 MB blocks. This is madness".
So your claim should more be like "Let the user set the block limit".
Great, but replace the Dino. We are the zerg! Hired by the Overmind, the zerg of the zerg.A first attempt to compress this down to meme size.
That's is another interesting approach. I would unite it with my reddit comment above and say BU will help smooth communication channels for converging on consensus Schelling points by removing the noise introduced by Core's having its hand on the scale, which is making it inconvenient to express preferences in the Schelling consensus process. (Which ironically (or not?) reminds me of how the /r/Bitcoin censorship has made it difficult to have this debate.)BU doesn't remove that but adds channels to express it in better and hopefully more productive ways. I think some of it is real concern, but a lot of is the broken communication channel that is Bitcoin Core. I think a decentralized approach like BU will at least help in creating additional and better communication channels for determining the effective block size limit.
I have approached AnarchyStar to ask if he wishes to support BU. He previously offered to spin up 1000 XT nodes. If he supported BU we could rapidly gain a % share of the network and start an avalanche.@Zangelbert Bingledack : That is indeed a nice post you made there.
I am wondering now whether I should go and make this build script to create up-down blocksize adjusted Bitcoin builds, just to show the futility of being in the way by not letting users express their options.
subreddit message via /r/Bitcoin[M] sent a minute ago
you have been temporarily banned from posting to /r/Bitcoin. this ban will last for 7 days.
note from the moderators:
spamming non-consensus implementations
you can contact the moderators regarding your ban by replying to this message. warning: using other accounts to circumvent a subreddit ban is considered a violation of reddit's site rules and can result in being banned from reddit entirely.