Skip to content
Scribe Network
Branch: master
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.
build-aux/m4
contrib
depends
doc
qa
scribe-docs
share
src
.gitattributes
.gitignore
.travis.yml
CONTRIBUTING.md
COPYING
INSTALL
Makefile.am
README.md
autogen.sh
build.md
configure.ac
libscribeconsensus.pc.in

README.md

Scribe Core staging tree 0.12.2

http://scribe.network | Block Explorer | Announcement | Discord | Twitter | Telegram

About Scribe

SCRIBE offers highly secured, anonymous transactions across the world. SCRIBE supports Masternodes with a superb block reward. Features as Private Send and Instant Send make SCRIBE a future-oriented currency on the market. SCRIBE uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Scribe Core is the name of the open source software which enables the use of this currency. Scribe Core is based on the newest Dash codebase and is its own currency.

For more information, as well as an immediately useable, binary version of the Scribe Core software, see http://scribe.network

Scribe Specifications

Specification Value
PoW Algorithm Lyra2REv2
Block Time Average 90 seconds
Block Reward 8 SCRIBE
Block Reward Distribution 40% to Masternodes, 60% to Miners initially, ramping up to 65% Masternodes, 35% miners
Masternode Collateral 1000 SCRIBE
Estimated Supply 32.7 Mio.
Difficulty Retargeting Every block
Difficulty Algorithm Dark Gravity Wave v3

License

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

You can’t perform that action at this time.