BSHA3 is an experimental blockchain based on Bitcoin. Almost all instances of SHA256, a prominent algorithm throughout Bitcoin, are replaced with SHA3-256.
Its roadmap is to have extreme parity with Bitcoin and Bitcoin Core, with upstream merges accounting for the bulk of its future changes. The issue tracker may be used for discussion and review of upcoming Bitcoin Core pull requests, as well as code issues.
It has an identical difficulty adjustment and halving functions as Bitcoin in its present form.
Its genesis block has a timestamp (nTime) of 1540053565.
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://bitcoincore.org/en/download/, or read the original whitepaper.
BSHA3 is released under the terms of the MIT license. See COPYING for more information or see https://opensource.org/licenses/MIT.
Download either the source code, or a pre-built release.
To build from source, run:
./autogen.sh
./configure --disable-bench
make
The resulting binaries will be created in src/, with the GUI wallet in subdirectory src/qt/.
Components -
bsha3d- Daemon (Syncs and validates blocks and transactions)bsha3-cli- RPC Client (Runs commands on the daemon)bsha3-tx- Transaction Builderbsha3-qt- GUI Wallet (Standalone, can be used for mining and sending)
GUI -
To start, double-click the program. To stop, close the program.
CLI (Command Line Interface) -
To start, run ./bsha3d in a terminal window. Then run ./bsha3-cli getblockchaininfo in another. You should see the block height and other output. Run ./bsha3-cli help for more commands.
To stop bsha3d cleanly, you should run ./bsha3-cli stop.
GUI -
You will need to visit the debug console to use these commands. It is located at Help -> Debug Window on the titlebar.
To start, run command - setgenerate true <num_cpu_cores>
To stop, run command - setgenerate false
CLI -
To start, first run - ./bsha3d
Then, in a separate terminal, run - ./bsha3-cli setgenerate true <num_cpu_cores>
You are now mining.
To stop mining, run - ./bsha3-cli setgenerate false
To stop bsha3d cleanly, run - ./bsha3-cli stop
Create a wallet backup right away. There are two ways to do this:
-
Use
bsha3-cli dumpwallet <output_filename>to create a txt file containing yourxprv(master private key) and its addresses. From thisxprv, you can generate all private keys & addresses that your wallet file will ever contain. -
Copy
$DATADIR/wallets/wallet.datto a safe destination.
Your datadir is in the following folder for each operating system:
- Windows 10 -
C:\Documents and Settings\<username>\Application Data\BSHA3 - Windows 7 -
C:\Users\<username>\AppData\Roaming\BSHA3 - Mac -
~/Library/Application Support/BSHA3 - Unix -
~/.bsha3
The following text is directly from Bitcoin Core.
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 following text is directly from Bitcoin Core.
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.
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.
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.
The following text is directly from Bitcoin Core.
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.