Bistar V2.5 ( Bitcoin Core 0.12 based )
Switch branches/tags
Nothing to show
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.
.tx
build-aux/m4
contrib
depends
doc
qa
share
src
.gitattributes
.gitignore
.travis.yml
CONTRIBUTING.md
COPYING
INSTALL
Makefile.am
README.md
autogen.sh
configure.ac
libbitcoinconsensus.pc.in

README.md

Bitstar

https://bitstarcoin.com

Recommended but not mandatory wallet update, focussed on barterdex compatibility.

note: wallet.dat is incompatible with V2.0.x.x version due to Berkeley DB Library version used.

What is Bitstar?

Bitstar is a decentralised digital currency with near-instant transaction speeds and negligible transaction fees built upon Proof of Stake 3.0 as introduced by the Bitstar development team.

Bitstar takes Bitstar to the next level by building upon Bitcoin Core 0.12 to offer performance enhancements, wider compatibility with third party services and a more advanced base.

For downloads vist: https://github.com/bitstar/bitstarV2.5/releases

License

Bitstar is released under the terms of the MIT license. See COPYING for more information or see https://opensource.org/licenses/MIT.

Development Process

The Bitstar 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 Bitstar.

The contribution workflow is described in CONTRIBUTING.md.

The best place to get started is to join the Development channel on Gitter: https://gitter.im/Bitstar\_Hub/Development

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 with: qa/pull-tester/rpc-tests.py

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.