[BTC-dev] The Bitcoin Foundation: STATE OF BITCOIN ADDRESS
modsix at gmail.com
Tue Sep 1 04:44:52 UTC 2015
-----BEGIN PGP SIGNED MESSAGE-----
..::[ The Bitcoin Foundation: STATE OF BITCOIN ADDRESS ]::..
[ Date: 2015.08.29 ]
[ Co-Chairs: mod6 [R.01] && ben_vulpes [R.02] ]
It is with great honor and privilege that The Bitcoin Foundation embraces
this opportunity to address the public on the state of current progress,
obstacles and continuing steps in our mission.
During the month of August, most activity centered around testing the rotor
with candidate bitcoin-v0_5_4-TEST2 and generating & signing vpatches with
`V', the new version control system implemented by asciilifeform [R.03].
[ Submitted Patches ]:
This month there were a hand full of patches that were submitted to the
btc-dev mailing list [R.04], two of which were mission-critical and merit
a review here.
0x010: On August 1st, continued tx spam attacks to the blockchain were
initiated. The result of which rendered BDB to exhaust all of its database
locks once again. When The Foundation undertook the task of de-crufting
the Reference Implementation, there was initially a problem with a minimum
of 10`000 locks whereby the R.I. would wedge at block 252`450 [R.05]. At
which time the limit was quadrupled to 40`000 locks to safely bypass the
To eradicate this issue the following values were set:
max_locks = 2737000
max_objects = 1119200
max_lockers = 1119200
asciilifeform submitted the patch [R.06] and it has since been applied to
candidate bitcoin-v0_5_4-TEST2 for continued testing.
0x011: The `rotor' [R.07], submitted on July 27th was undergoing testing
when trinque [R.08] noticed a small hiccup in the included rotor.sh BDB
configuration parameters which yielded a failure to complete the Reference
Implementation compilation. The patch [R.09] adds the following flag to
the BDB configuration parameter list: --host=x86_64-linux
This patch was not directly applied to bitcoin-v0_5_4-TEST2, but to the
unreleased rotor-TEST2.sh [R.0A] build script by mod6; this build script
will most likely be published to the btc-dev list at a later date.
[ bitcoin-v0_5_4-TEST2 Test Archive ]:
With regard to the tx spam attack in the beginning of August, the former
candidate TEST1 has been rendered obsolete. A new test build, which
has `asciilifeform_maxint_locks_corrected.patch' [R.06] applied, has been
An email was communicated to the btc-dev mailing list with the new TEST2
bundle [R.0C] and signature attached.
[ v0.5.4-TEST2 w/rotor ]:
With the advent of the `rotor', which by recipe is suggested to build a
`stator' [R.07]; mod6 created the aforementioned script [R.0A] that will
instead build the latest test bundle with `rotor': bitcoin-v0_5_4-TEST2
The Bitcoin Foundation is still looking for anyone who would like to test
the building of bitcoin-v0_5_4-TEST2 with the rotor and achieve a full
sync of the blockchain.
Throughout the month of August, a number of people successfully built
bitcoin-v0_5_4-TEST2 with rotor via mod6's script [R.0A] or with `stator'
on the following systems:
Full blockchain sync was achieved on Debian 6 and Gentoo thus far.
All others simply just need to test the full sync process.
As a note, the rotor is pre-configured to run on Linux with x86_64
architecture `out-of-the-box'; however, can be configured [on your own]
to run on arbitrary architecture types.
The Bitcoin Foundataion would like to support i386/i686 going forward for
anyone who might still be using this classic architecture. mod6 has
created several yet unreleased patches to the rotor.sh build script and the
buildroot .config file to achieve this. Thus far, mod6 was successful
in building and running bitcoin-v0_5_4-TEST2 with `rotor' on an Ubuntu
10.04 i686 environment; however, is still looking for additional testers
with this architecture to replicate his initial success before patch
publication to the btc-dev mailing list. If you have a clean i386/i686
physical environment or virtual machine and would like to help with this
testing, please contact mod6 on #bitcoin-assets.
[ V ]:
asciilifeform implemented a new wot-based source control and patching
system called `V' [R.0D]. Some examples of `V' tool usage here [R.0E].
Mr. Popescu provides us with an eloquent submission and description of
V-genesis and the paradigm shift of V [R.0F] [R.10].
[ rel1 vpatches signed (bitcoin-v0_5_3_1-RELEASE) ]:
mod6 & asciilifeform generated and signed all of the vpatches that
produce the [rel1] bitcoin-v0_5_3_1-RELEASE from the original
genesis.vpatch [R.11] [R.12].
[ rel2 vpatches signed (bitcoin-v0_5_4-TEST2) ]:
mod6 & asciilifeform generated and signed all of the vpatches that
produce the [rel2] bitcoin-v0_5_4-TEST2 from the rel1 [v0.5.3.1]
codebase [R.11] [R.12].
0x02] Complications and Obstacles
0x03] Continuing Steps
[ Continued testing of v0.5.4-TEST2 w/rotor ]:
Manual testing and automated testing of bitcoin-v0_5_4-TEST2 thus far has
been going very well. We've been able to build and run `TEST2' on seven
different platforms for x86_64 and on one for i686. We need to achieve
full sync on five of those seven still. [See above section 0x01:
v0.5.4-TEST2 w/rotor]. This work will be on-going. We're getting closer!
The Bitcoin Foundation would like to personally thank the following people
for their hard work testing this past month [in order by fingerprint]:
Further performance tests against the latest candidate are a must: NMON,
valgrind and igprof.
New doxygen source code browser files should be generated to contain
patches up through the most recently applied
[ `V' Testing ]:
Testing for `V' will continue into September with the current version: v99
[R.0D] and vdiff.sh [R.1B].
[ Updated Documentation ]:
With the `V' now in-hand, mod6 will begin to update all pertinent
documentation previously released with updates for V.
The summer months have been as busy as ever. It feels like it's starting
to come together.
The Bitcoin Foundation would like to bestow our sincerest thanks and
gratitude to the contributors and community for its support and insight.
[ References ]:
[R.01]: 027A 8D7C 0FB8 A166 4372 0F40 7217 05A8 B71E ADAF
[R.02]: 4F79 0794 2CA8 B89B 01E2 5A76 2AFA 1A9F D2D0 31DA
[R.03]: 1721 5D11 8B72 3950 7FAF ED98 B982 28A0 01AB FFC7
[R.08]: FC66 C0C5 D98C 42A1 D4A9 8B6B 42F9 985A FAB9 53C4
[R.13]: 1559 34BD D16E 8EAF 4493 CB9C B36A E984 9D96 1AC9
[R.14]: 27C3 CE9A 2085 1312 F086 268C 27AF 7532 1F24 89E8
[R.15]: 6160 E1CA C8A3 C529 66FD 7699 8A73 6F0E 2FB7 B452
[R.16]: 6ACE 36E7 86F3 9A4A DC45 06DE 0FF2 943D A179 E169
[R.17]: E662 5CC1 4638 C4CA 4046 94E9 1657 4992 9F9A 6BDD
[R.18]: EA0F AD90 985B 3025 576A 5061 454B 0FC0 BC07 B87E
[R.19]: F28E 0095 843B 91CB 22E7 D655 3358 8BE0 8B23 2B13
[R.1A]: FDF6 3798 C83A 7B13 75F7 2468 E335 8571 3E18 4252
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (FreeBSD)
-----END PGP SIGNATURE-----
More information about the BTC-dev