You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
SHI 245f2d092b Add a missed chainTxData 2 anni fa
.github Starwels start 2 anni fa
.tx Rename all 2 anni fa
build-aux/m4 Rename all 2 anni fa
contrib main - > Starwels MAI 2 anni fa
depends Merge branch 'refs/heads/0.15.1' into 0.15 2 anni fa
doc main - > Starwels MAI 2 anni fa
share Starwels Ai - > Start 2 anni fa
src Add a missed chainTxData 2 anni fa
test main - > Starwels MAI 2 anni fa
.gitattributes Separate protocol versioning from clientversion 6 anni fa
.gitignore Rename all 2 anni fa
.travis.yml Starwels start 2 anni fa Rename all 2 anni fa
COPYING Rename all 2 anni fa Rename all 2 anni fa Rename all 2 anni fa Rename all 2 anni fa Rename all 2 anni fa Starwels start 2 anni fa Rename all 2 anni fa

Starwels integration/staging tree

Build Status

What is Starwels?

Starwels is an experimental digital currency that enables instant payments to anyone, anywhere in the world. Starwels uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Starwels 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 Starwels software, see, or read the original whitepaper.


Starwels is released under the terms of the MIT license. See COPYING for more information or see

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 Starwels.

The contribution workflow is described in

The developer mailing list should be used to discuss complicated or controversial changes before working on a patch set.

Developer IRC can be found on Freenode at #starwels-dev.


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/

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/

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.


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.