Bitcoin Unlimited Code Changes
- gandrewstone committed “fix different handling of gt and lt in github md vs standard md in miner.md” within 1 file for a total of 6 additions and 6 deletions. These changes, as stated, smooth out the user interface of the Github MD by changing the user inputs in the client.
- gandrewstone committed “add miner-specific doc for the EC params and pushtx” within 1 file for a total of 58 additions and 8 deletions. These changes were made to produce miner specific code feedback to help educate and inform miners on running Bitcoin Unlimited clients with emergent consensus in mind.
- Peter Tschipper committed “Use Atomic for nLargestBlockSeen” within 4 files for a total of 20 additions and 12 deletions. These changes were made to make the operation “nLargestBlockSeen” atomic. Making an operation atomic means that it is unable to be split into parts. This means that in any other thread, when viewing “nLargestBlockSeen”, you will see either it’s value before or after it’s assignment, but never the intermediary.
- gandrewstone merged 3 commits from “ftrader-bitcoinunlimited:feature/usability_enhancements_for_rpctests_runner” into “BitcoinUnlimited:0.12.1bu”. During the merge, 2 files were changed with a total of 169 additions and 24 deletions. These changes were optimizations for the “rpctests.py test runner “. These enhancements bring several new options into the test runner, including lists of all available tests, and report readouts when tests are finished. This provides users with much more in depth information about their test results, while enhancing and optimizing the testing interface.
Bitcoin Classic Code Changes
- zander committed “Many updates to non-code stuff” within 136 files for a total of 177 additions and 10,316 deletions. These changes were not made to anything Classic code related, but were rather clarifications and optimizations to the user interface. In Tom’s own words: “This updates many files with fixes and clarifications. This removes files that have some time ago moved to the documentation repository. This removes release notes that were not our releases.”
- zander committed “Remove unused and immature benchmark app” within 8 files for a total of 0 additions and 254 deletions. These changes were made to remove an application from the code that served no purpose for the Classic project. This code was originally generated in 2015 by the Bitcoin Core team for their own projects, and has since become technical debt within the Classic project since it’s forking from the bitcoin master branch.
- zander committed “Remove useless line” within 1 file for a total of 0 additions and 1 deletion. This removal was a simple redundancy within the code calling for the client to “use version 1” when there was only 1 version total. This deletion was technical debt control.
- zander committed “Avoid incompatibility with old code” within 1 files for a total of 3 additions and 2 deletions. These changes were optimizations to the code in order to insure that the newer code that Bitcoin Classic is generating, (FlexTrans), remains compatible with older code.
- zander committed “Fixes and cleanups” within 1 file for a total of 8 additions and 13 deletions. These changes optimize various elements of the Classic code, and allow for bug mitigations and general performance increases. One change present in this commit was made for Flex Trans integration. Another set of changes streamlined various lines together, while polishing the codes language and operation.
Bitcoin XT Code Changes
- dgenr8 merged 1 commit from “dagurval:peer-sel-tests” into “bitcoinxt:master”. During the merge, 7 files were changed for a total of 114 additions and 8 deletions. These changes were made to allow a variety of tests to be made available for the peers of Bitcoin XT to run and select.
Bitcoin Core Code Changes
- sipa committed “Squashed ‘src/secp256k1/’ changes from 7a49cac..8225239” within 33 files for a total of 676 additions and 937 deletions. These changes were made for a variety of reasons, including optimizations, parameter adjustments, test updates, and general cleaning. For a full change breakdown, including the various merges it includes, please click the commit link above. Sipa has itemized the changes.
- richardkiss committed “Fix spelling” within 1 file for a total of 1 addition and 1 deletion. This change was made to correct a simple spelling error where the word “Pairs” was written as “Paris”.
- iaanwj merged 1 commit from “sipa:failedtxid” into “bitcoin:master”. During this merge, 1 file was changed with a total of 4 additions and 4 deletions. This change was made to guarantee that even if a new transaction is rejected as it attempts to add itself to the memory pool, it will still return the transaction ID to the client.
Some News From The Bitcoin Ecosystem
Deadalnix raised a proposal this week to the Bitcoin Unlimited community on the bitco.in forums. Following the updates from Bitcoin Classic and their new transaction format “FlexTrans”, Deadalnix proposed that the Bitcoin Unlimited client should adopt a similar, newer transaction format, but with a twist. His proposed format would bear close resemblance to Flex Trans, and wouldn’t differ significantly in its binary format from the current transaction format, but would have its signature script for each input replaced with witness data. This proposal, BUIP37, essentially blends Core’s brain child Segregated Witness with Flex Trans. This combination of innovative transaction formats is one of the first major proposals put forth by a developer that meets the “Bigger Blocks” and “Small Blocks” camps in the middle. If this proposal were to be accepted, and implemented, Core backers may yet find some common ground with the Bitcoin Unlimited project.
The atmosphere of the Bitcoin ecosystem has been a bit hostile as of late, and this has generated no shortage of controversy all across the network. Truly, the community has never seemed more divided and adversarial than it does today. But even in times of turmoil, there are individuals to be found who can help us to laugh and poke fun at ourselves. Enter Bitcoin Ocho. Styling themselves the answer to all of Bitcoin’s block size problems, Bitcoin Ocho is setting off to increase the block size to 8 times its current limit, hence the numeric name. Bitcoin Ocho has all the subtlety of Donald Trump in their style of trolling, and since arriving on the scene they have been active and loud! If you would like to keep up with the shenanigans of Bitcoin Ocho, see the links below for the Twitter and the Github repository for the magical Ocho code that is yet to come. Their Github should go live when the team makes their first commits.