bitwise
7f2d7e5248
If the daemon doesn't start syncing add a few addnode lines to the core command - -addnode=... The containers network interface use the host-netwrok; Make sure the provider doesn't block port 34329 |
||
|---|---|---|
| build-aux/m4 | ||
| contrib | ||
| depends | ||
| doc | ||
| share | ||
| src | ||
| test | ||
| .gitattributes | ||
| .gitignore | ||
| .travis.yml | ||
| autogen.sh | ||
| configure.ac | ||
| COPYING | ||
| docker-compose.yml | ||
| Dockerfile | ||
| libbitcoinconsensus.pc.in | ||
| Makefile.am | ||
| README.md | ||
eCoinCore integration/staging tree
This is the Canada eCoin Volume 2 desktop wallet client.
What is eCoinCore?
eCoinCore is an experimental digital currency client software that enables instant payments to anyone, anywhere in the world. eCoinCore uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. eCoinCore 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 eCoinCore software, see https://canadaecoin.site
License
eCoinCore is a compilation of the Bitcoin and Viacoin projects. https://github.com/bitcoin/bitcoin https://github.com/viacoin/viacoin
eCoinCore 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 eCoinCore.
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 Discord channels can be found at https://discord.gg/whZ8gB5 Developer Keybase channels can be found at https://keybase.io/team/canadaecoin Developer IRC channels can be found at #canadaecoin on freenode.
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'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.