| On July 22nd, 2015, Bitcoin XT developer Mike Hearn said: Once XT 0.11A is launched (which will include the biggerblocks patchset by Gavin and myself), there will be a separate git branch that is Core 0.11 + only those patches and nothing else. Whilst we won't provide downloadable binaries of that branch, anyone who wants to can just compile it in the usual manner and get what you're asking for. This seems like a reasonable compromise: if someone else wants to create binaries of this branch they are welcome to do so, but rebranding, gitian building and signing downloads for all 3 platforms is a lot of work and I don't want to do it over and over again for different combinations of patches. One last thing I'd like to say: quoted text: "XT includes a bunch of other changes aside from blocksize that are also controversial" If you're wanting bigger blocks, you are already on board with a change that is considered so controversial it must not happen, according to the Bitcoin Core developers. So you may wish to think about what "controversial" actually means, who gets to label something as "controversial" and how much you care about their opinions. One of the things we've been working on that will also launch with the new XT is a manifesto that lays out principles we consider to be important. These are how XT differentiates itself from Core. The other changes in XT all follow those principles, so you can read them and evaluate whether you believe those principles are controversial or common sense. If you believe the latter, you should have no worries about the other patches. Original post:https://www.reddit.com/r/Bitcoin/comments/3e64dk/time_to_end_bitcoin_reliance_on_core_and_end_this/ctbyqwy |
| On July 8th, 2015, Bitcoin XT developer Mike Hearn said: "Hello, As you may have noticed, Bitcoin unfortunately has run out of capacity due to someone DoS attacking the network. We now get a preview of coming attractions (so far that means, people complaining that their transactions are not confirming). Gavin has prepared patches that implement a hard fork in January for bigger blocks. I spent the last couple of days testing and doing a second code review of the patches, this revealed some further bugs and I have sent him patches to fix them. However Gavin is on vacation and so not much will happen until he is back next week. In the past week we also found that Gavin's XT node was under attack via Tor. In case this was a trial run, I have prepared a patch to help with that a bit, though DoS attacks are an ongoing matter of concern that require significant effort to raise the bar. I will put that patch into the next XT release. I will try and find time to look at ways to resolve the current tx flooding attack in the next day or two. I suspect it can be mitigated through heavier reliance on coin age priority, as coin age is not something that can be trivially bought on the spot, unlike fee priority. If anyone wants to beat me to it, please go ahead. thanks, -mike" Original post: https://groups.google.com/d/msg/bitcoin-xt/Iov4vcCOg9M/qOTSP07wQEUJ |
| On June 9th, 2015, Bitcoin XT developer Mike Hearn said: "What's gonna happen is-- either today or tomorrow, I will release another version of Bitcoin XT-- which also doesn't include any blocksize changes, but it just tidies a few things up. And then probably within a week or two Gavin will have a change that's ready to submit to me, through Bitcoin XT, and then we'll integrate that and release it as a version of Bitcoin XT that anyone can upgrade to." Mike goes on to explain that Bitcoin XT will use a majority-voting mechanism before the increased block-size change goes into effect, so that it only goes into effect if a certain percentage of nodes are using it. Full Video Episode: https://www.youtube.com/watch?v=8JmvkyQyD8w (Clip is taken from 50 min 37 sec onward) |
Please visit the "How Can I Help?" page to see what you can do to assist Bitcoin XT.
common misconception: "xx MB is too big of a jump"
answer: It's just a maximum block-size limit. It does not mean we are going to instantly start making xx MB blocks. Blocks will continue growing at their current pace. This is perhaps the biggest misconception that we will somehow suddenly start seeing xx MB blocks just because the limit is raised.
Tidak ada komentar:
Posting Komentar