Aywa Platform Core
Branch: master
Clone or download
user
user version changed
	modified:   configure.ac
	modified:   src/clientversion.h
	modified:   src/qt/forms/masternodelist.ui
Latest commit 5f498e0 Jan 5, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.tx Initial commit Oct 23, 2018
aywa-docs Initial commit Oct 23, 2018
build-aux/m4
contrib added mutex to hash counter, minor improvements Nov 3, 2018
depends Added checkpoints Jan 5, 2019
doc
qa Initial commit Oct 23, 2018
share Initial commit Oct 23, 2018
src version changed Jan 5, 2019
.gitattributes Initial commit Oct 23, 2018
.gitignore .gitignore edited online with Bitbucket Nov 18, 2018
.travis.yml Initial commit Oct 23, 2018
CONTRIBUTING.md Initial commit Oct 23, 2018
COPYING COPYING edited online with Bitbucket Oct 23, 2018
INSTALL Initial commit Oct 23, 2018
IdeaMiningRules.md Update IdeaMiningRules.md Dec 22, 2018
Makefile.am Initial commit Oct 23, 2018
README.md Update README.md Dec 6, 2018
autogen.sh Initial commit Oct 23, 2018
configure.ac version changed Jan 5, 2019
libaywaconsensus.pc.in

README.md

AywaCore

Aywa is Decentralized Communication and 🎁 Rewards Platform with 🖥 CPU-only mining algo, based on hash algo YesPower, Groestl and Keccak🔐. Aywa uses new Time Gravity Wave algo for difficulty 📊 adjustment and different cost of Masternodes.

Enjoy Aywa built-in IdeaMining. Many proposals already sends rewards🎁🎁🎁 their owners. Needs some AYWA to submit your proposal? No problem! Just press "Start Mining" 🔲 button at your AywaCore Overview Page.

More information is on our page: www.getaywa.org.

If required information was not found you can ask questions at the AywaCore built-in messanger.

AywaCore Download

Look at some AywaCore features:

Overview Page

www.getaywa.org

Proposal Creation  www.getaywa.org

Voting Process

www.getaywa.org

Messages and Public Channels

www.getaywa.org www.getaywa.org

Reward for Proposal  www.getaywa.org

License

Aywa 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 Aywa 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

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 and Linux, OS X, and that unit and sanity tests are automatically run.

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 Aywa Core's Issues 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.