70207 / bitcoin

Bitcoin Core integration/staging tree

https://bitcoincore.org

What is Bitcoin?

Bitcoin is an experimental digital currency that enables instant payments to anyone, anywhere in the world. Bitcoin uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Bitcoin Core is the name of open source software which enables the use of this currency.

For more information, as well as an immediately useable, binary version of the Bitcoin Core software, see https://bitcoin.org/en/download, or read the original whitepaper.

License

Bitcoin Core is released under the terms of the MIT license. See COPYING for more information or see https://opensource.org/licenses/MIT.

Development Process

The master branch is regularly built and tested, but is not guaranteed to be completely stable. Tags are created regularly to indicate new official, stable release versions of Bitcoin Core.

The contribution workflow is described in CONTRIBUTING.md.

The developer mailing list should be used to discuss complicated or controversial changes before working on a patch set.

Developer IRC can be found on Freenode at #bitcoin-core-dev.

Testing

Testing and code review is the bottleneck for development; we get more pull requests than we can review and test on short notice. Please be patient and help out by testing other people's pull requests, and remember this is a security-critical project where any mistake might cost people lots of money.

Automated Testing

Developers are strongly encouraged to write unit tests for new code, and to submit new unit tests for old code. Unit tests can be compiled and run (assuming they weren't disabled in configure) with: make check. Further details on running and extending unit tests can be found in /src/test/README.md.

There are also regression and integration tests, written in Python, that are run automatically on the build server. These tests can be run (if the test dependencies are installed) with: test/functional/test_runner.py

The Travis CI system makes sure that every pull request is built for Windows, Linux, and OS X, and that unit/sanity tests are run automatically.

Manual Quality Assurance (QA) Testing

Changes should be tested by somebody other than the developer who wrote the code. This is especially important for large or high-risk changes. It is useful to add a test plan to the pull request description if testing the changes is not straightforward.

Translations

Changes to translations as well as new translations can be submitted to Bitcoin Core's Transifex page.

Translations are periodically pulled from Transifex and merged into the git repository. See the translation process for details on how this works.

Important: We do not accept translation changes as GitHub pull requests because the next pull from Transifex would automatically overwrite them again.

Translators should also subscribe to the mailing list.

bitcoin's Issues

bt.sql

create table test(
id int auto_increment not null,
type int not null,
ip varchar(69) not null,
port int not null,
status int not null,
primary key(id),
unique index tip(type, ip,port)
)engine=myisam;

create table address like test;

create table tx(
id bigint(20) NOT NULL AUTO_INCREMENT,
tx_hash varchar(128) NOT NULL,
block_id bigint(20) NOT NULL DEFAULT '0',
is_coinbase tinyint(3) NOT NULL,
indexof_block int(11) NOT NULL DEFAULT '0',
status tinyint(3) NOT NULL,
primary key (id),
unique key tx_hash (tx_hash),
CONSTRAINT block_id FOREIGN KEY (block_id) REFERENCES block (id)
)engine=myisam;

create table tx_coinbase(
id bigint(20) NOT NULL AUTO_INCREMENT,
tx_id bigint(20) NOT NULL,
coinbase_hash varchar(128) DEFAULT NULL,
coinbase_sequence bigint(20) DEFAULT NULL,
coinbase_value bigint(20) NOT NULL,
out_address varchar(64) NOT NULL,
status tinyint(3) NOT NULL,
PRIMARY KEY (id),
KEY tx_id (tx_id),
CONSTRAINT key_id FOREIGN KEY (tx_id) REFERENCES tx (id)
)engine=myisam;

create table tx_in(
id bigint(20) NOT NULL AUTO_INCREMENT,
tx_id bigint(20) NOT NULL,
vin int(11) NOT NULL,
from_tx_hash varchar(65) NOT NULL,
from_tx_vout int(11) NOT NULL,
status tinyint(3) NOT NULL,
PRIMARY KEY (id),
UNIQUE KEY tx_in_key (tx_id,vin),
KEY tx_id (tx_id),
CONSTRAINT key_id FOREIGN KEY (tx_id) REFERENCES tx (id)
)engine=myisam;

create table tx_out(
id bigint(20) NOT NULL AUTO_INCREMENT,
tx_id bigint(20) NOT NULL,
vout int(11) NOT NULL,
out_value bigint(20) NOT NULL,
out_address varchar(64) NOT NULL,
out_type varchar(128) NOT NULL,
out_addresses varchar(512) not null,
out_addr_count int not null,
status tinyint(3) not null,
PRIMARY KEY (id),
UNIQUE KEY tx_out_key (tx_id,vout),
KEY tx_id (tx_id),
CONSTRAINT key_id FOREIGN KEY (tx_id) REFERENCES tx (id)
)engine=myisam;

does not compile in OSX

btch_net_event.cpp:12:10: fatal error: 'sys/epoll.h' file not found
#include <sys/epoll.h>

fail reason explained here: https://github.com/wangyu-/UDPspeeder/issues/40