AceD
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github readd broken files Oct 18, 2018
.tx readd broken files Oct 18, 2018
build-aux/m4 readd broken files Oct 18, 2018
contrib readd broken files Oct 18, 2018
depends readd broken files Oct 18, 2018
dist rename Oct 26, 2018
doc add docs Oct 26, 2018
docker readd broken files Oct 18, 2018
polis-docs readd broken files Oct 18, 2018
qa readd broken files Oct 18, 2018
share readd broken files Oct 18, 2018
src rename Oct 26, 2018
.gitattributes readd broken files Oct 18, 2018
.gitignore readd broken files Oct 18, 2018
.travis.yml readd broken files Oct 18, 2018
CMakeLists.txt readd broken files Oct 18, 2018
CONTRIBUTING.md readd broken files Oct 18, 2018
COPYING readd broken files Oct 18, 2018
INSTALL.md readd broken files Oct 18, 2018
Makefile.am readd broken files Oct 18, 2018
README.md readd broken files Oct 18, 2018
autogen.sh readd broken files Oct 18, 2018
configure.ac some small checks for new nodes Oct 22, 2018
dpi36.background.tiff readd broken files Oct 18, 2018
dpi72.background.tiff readd broken files Oct 18, 2018
libacedconsensus.pc rename Oct 26, 2018
libacedconsensus.pc.in readd broken files Oct 18, 2018

README.md

AceD

ACED Core integration/staging tree

Build Status

http://www.acedpay.org

  • Copyright (c) 2009-2015 Bitcoin Developers
  • Copyright (c) 2014-2017 Dash Developers
  • Copyright (c) 2017-2018 AceD Developers

What is AceD?

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

For more information, as well as an immediately useable, binary version of the AceD Core software, see https://www.acedpay.org/Find-aced/.

License

AceD 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 meant to be stable. Development is normally done in separate branches. Tags are created to indicate new official, stable release versions of AceD Core.

The contribution workflow is described in CONTRIBUTING.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 of the RPC interface, written in Python, that are run automatically on the build server. These tests can be run (if the test dependencies are installed) with: qa/pull-tester/rpc-tests.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 AceD 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 follow the forum.