btchd/btchd

BitcoinHD Core integration/staging tree

BitcoinHD Core integration/staging tree

https://btchd.org

The Crypto Currency System Based on CPoC.

Pay Tribute to Cryptocurrency Pioneers Bitcoin and Burst!

About BitcoinHD

• BitcoinHD is a new type of crypto currency based on Proof of Capacity.
• BitcoinHD uses an upgraded version of cPOC mining (Conditioned Proof of Capacity), with a perfect economic model and consensus algorithm.
• BitcoinHD uses hard disk as the participant of consensus, which reduces power consumption.
• BitcoinHD mining lowers the entry barriers, and makes the coin generation process more decentralized, secure and reliable.
• Compared with POW mining, cPOC mining saves energy, consumes much less power, has lower noise, no heat, and is anti-ASIC. cPOC-mining-based BitcoinHD can realize the original intention of Satoshi Nakamoto ---- everyone can become a miner.
• Lowered the cost of credit, increased the strength and breadth of consensus, and improved the security of the consensus architecture

For more information, as well as an immediately useable, binary version of the BitcoinHD Core software, see https://btchd.org/#wallet, or read the original whitepaper.

License

BitcoinHD 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 BitcoinHD Core.

The contribution workflow is described in CONTRIBUTING.md and useful hints for developers can be found in doc/developer-notes.md.

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 macOS, 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

The BitcoinHD Core base on Bitcoin Core and shares resources with it.

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.

btchd's Issues

OmniCore require txindex

-omni dependency -txindex.

“Generate Bind Data” at the bottom missing

Hi,guys! “Generate Bind Data” at the bottom of the wallet is missing?how to bind for pool mining now?thx

"GLIBC_2.27 not found" on run ./bin/btchdd

Expected behavior

Run ./bin/btchdd on CentOS 7.8.

Actual behavior

Got /lib64/libm.so.6: version GLIBC_2.27 not found error.

To reproduce

Always.

System information

uname -a: 4.14.0-1.el7.elrepo.x86_64 #1 SMP Sun Nov 12 20:21:04 EST 2017 x86_64 x86_64 x86_64 GNU/Linux

cat /etc/redhat-release: CentOS Linux release 7.8.2003 (Core)

I try use contrib/devtools/symbol-check.py ./bin/btchdd found symbol powf from unsupported version GLIBC_2.27.

change BHD website to bhd.one

change BHD website to bhd.one

兼容China文件的升级 进展怎么样了啊？

Is your feature request related to a problem? Please describe.

Describe the solution you'd like

Describe alternatives you've considered

Additional context

lost funds after pointing to pool

After pledging funds to pool i've lost them all
they are not showing in frozen
and there is no transaction

did i just lost 119 BHD forever?
Expected behavior
pledged funds should be in frozen

Actual behavior
coins are not in frozen or in wallet

System information
BitcoinHD Core wersion v1.4.3.0-7fe720529 (64-bit)
windows 10

make: *** [all-recursive] Error 1

libbitcoin_consensus.a(libbitcoin_consensus_a-hash.o): In function PocLegacy::GeneratePlotterId(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)': /root/btchd/src/hash.cpp:258: undefined reference to crypto::curve25519_kengen(unsigned char*, unsigned char*, unsigned char*)'
libbitcoin_consensus.a(libbitcoin_consensus_a-hash.o): In function PocLegacy::Sign(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, unsigned char const*, unsigned char*, unsigned char*)': /root/btchd/src/hash.cpp:280: undefined reference to crypto::curve25519_kengen(unsigned char*, unsigned char*, unsigned char*)'
/root/btchd/src/hash.cpp:284: undefined reference to crypto::curve25519_kengen(unsigned char*, unsigned char*, unsigned char*)' /root/btchd/src/hash.cpp:286: undefined reference to crypto::curve25519_sign(unsigned char*, unsigned char const*, unsigned char const*, unsigned char const*)'
libbitcoin_consensus.a(libbitcoin_consensus_a-hash.o): In function PocLegacy::Verify(unsigned char const*, unsigned char const*, unsigned char const*)': /root/btchd/src/hash.cpp:298: undefined reference to crypto::curve25519_verify(unsigned char*, unsigned char const*, unsigned char const*, unsigned char const*)'
collect2: error: ld returned 1 exit status
Makefile:3969: recipe for target 'test/test_btchd' failed
make[2]: *** [test/test_btchd] Error 1
make[2]: Leaving directory '/root/btchd/src'
Makefile:9666: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/root/btchd/src'
Makefile:753: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1

Named wallet loses a character

Wanting to open a named wallet ends up opening a wallet with one character less in the name (and creating it anew actually).

Expected behavior

After creating the wallet "first" I expect to not be offered to open a wallet named "irst".

Actual behavior

The app reads the directories of wallets and drops the first character.

To reproduce

Create a new wallet, give it a name, close the program, try to open the wallet.

System information

Ubuntu, SSD, CPU, ext4 harddrive.>

How to overcome:
To actually open a named wallet I have created two directories
"_first" and "first", then it does show it right

Cannot sign messages

Expected behavior

Generate signature

Actual behavior

Error message (translated):
The entered address is not linked to any key. Please verify address and try again.
(Could not switch software to english version, pls. aslo see screenshot.)

To reproduce

Fresh install of latest version, new encrypted wallet, chain is in sync
File/sign message/get address from addr. book/insert some text to sign/press button "sign message" -> error above

Do I miss something? Need to sign messages for https://foxypool.io/

System information

BitcoinHD Core Version v1.4.3.0-7fe720529 (64-Bit) from guthub
running on Win7pro ServicePack 1

can you recommand a multi-miner proxy to me ?

i want to miner BHD,BRUST at the same time .
as i know there exsist a proxy, named ddproxy. however , i was using linux , which is not dependent on .netframe work

Trying to restore wallet backup

Want to restore my wallet backup on windows.

Where is the location to the wallet.dat so I can put my backup back in.

Cannot pledge (point to): insufficient balance

When trying to pledge an amount (using the link-to send option), the indicated balance in the client is 0.00000 which mismatches that actual balance in the overview.
As a result, it is not possible to pledge any amount since it will complain about insufficient balance.

Expected behavior

Available balance should be used and pledging should be possible.

Actual behavior

Balance in the point-to screen (bottom right) is 0.0000 and pledging results in an error "The amount exceeds your balance"

To reproduce

1. Have a positive balance
2. Go to Send
3. Select "point-to"
4. Attempt to make a pledge transaction < available balance+fees

System information

BitcoinHD Core version v1.4.3.0-7fe720529 (64-bit)
Windows Server 2008 R2
Xeon L5640 (x2)
RAID disk array (SAS)