This is a forked version of
bitcoin/bitcoin. It branches off of v31.1 and applies a series of eCash-related patches. eCash forks Bitcoin mainnet at height 973728.
Release tags are published to https://releases.ecash.com.
Verify a download before
running it:
gh attestation verify L1-ecash-bitcoin-.zip --repo ecash-com/bitcoin
## eCash build instructions (example uses ubuntu LTS (24.04))
Install build dependencies:
```git cmake build-essential libsqlite3-dev libboost-all-dev libzmq3-dev pkgconf```
Build:
cmake -B build -DBUILD_GUI=OFF -DBUILD_BENCH=OFF -DBUILD_FUZZ_BINARY=OFF -DBUILD_GUI_TESTS=OFF -DBUILD_TESTS=OFF -DENABLE_IPC=OFF -DWITH_ZMQ=ON -DBUILD_UTIL=ON cmake --build build -j $(nproc)
## Data directories & config files:
// Windows: C:\Users\Username\AppData\Local\eCash // macOS: ~/Library/Application Support/eCash // Unix-like: ~/.ecash
Config file name: `ecash.conf`
## Ports
Ports differ from Bitcoin Core so the two can run side by side.
P2P RPC
mainnet 8533 8532 testnet3 18533 18532 testnet4 48533 48532 signet 38533 38532 regtest 18644 18643
Ports for incoming Tor connections are the P2P port plus one.
## Network magic
Each network uses its own message start bytes, so a node will not connect
to Bitcoin Core peers.
mainnet 0xeca5dcb7 testnet3 0xeca5b114 testnet4 0xeca5b124 regtest 0xeca5b134 signet derived from the signet challenge
---
Bitcoin Core integration/staging tree
=====================================
https://bitcoincore.org
For an immediately usable, binary version of the Bitcoin Core software, see
https://bitcoincore.org/en/download/.
What is Bitcoin Core?
---------------------
Bitcoin Core connects to the Bitcoin peer-to-peer network to download and fully
validate blocks and transactions. It also includes a wallet and graphical user
interface, which can be optionally built.
Further information about Bitcoin Core is available in the [doc folder](/doc).
License
-------
Bitcoin Core is released under the terms of the MIT license. See [COPYING](COPYING) for more
information or see https://opensource.org/license/MIT.
Development Process
-------------------
The `master` branch is regularly built (see `doc/build-*.md` for instructions) and tested, but it is not guaranteed to be
completely stable. [Tags](https://github.com/bitcoin/bitcoin/tags) are created
regularly from release branches to indicate new official, stable release versions of Bitcoin Core.
The https://github.com/bitcoin-core/gui repository is used exclusively for the
development of the GUI. Its master branch is identical in all monotree
repositories. Release branches and tags do not exist, so please do not fork
that repository unless it is for development reasons.
The contribution workflow is described in [CONTRIBUTING.md](CONTRIBUTING.md)
and useful hints for developers can be found in [doc/developer-notes.md](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](src/test/README.md) for new code, and to
submit new unit tests for old code. Unit tests can be compiled and run
(assuming they weren't disabled during the generation of the build system) with: `ctest`. Further details on running
and extending unit tests can be found in [/src/test/README.md](/src/test/README.md).
There are also [regression and integration tests](/test), written
in Python.
These tests can be run (if the [test dependencies](/test) are installed) with: `build/test/functional/test_runner.py`
(assuming `build` is your build directory).
The CI (Continuous Integration) systems make sure that every pull request is tested on Windows, Linux, and macOS.
The CI must pass on all commits before merge to avoid unrelated CI failures on new pull requests.
### 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](https://explore.transifex.com/bitcoin/bitcoin/).
Translations are periodically pulled from Transifex and merged into the git repository. See the
[translation process](doc/translation_process.md) 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.