INNOVATIVE and DECENTRALIZED crypto currency that have the bases (fast, secure and anonymous transactions, low fees) to become the best digital payment asset for buying/selling goods and service around the world. SUC will also be the starting point around which we will create a complex system of tools and services for ecommerce, trading and crypto world.
Anonymized transactions using coin mixing technology. 1-Second-Transactions. Network stability with masternodes, each is secured with a collateral of 1.000 SUC.
For further information visit us at succoin.org
• PoW Algorithm: NeoScrypt
• Premine: (#1 Block) 1,000,000 SUC
• Type: POW + Masternode
• Block Time: 120 Seconds
• PoW Max Coin Output/Supply: 30,350,000
• Masternode Requirements: 1,000 SUC
• Maturity: 101 Confirmations
| Blocks | Reward | Reward Distribution | |
|---|---|---|---|
| Minner | Masternode | ||
| 1 - 64800 | 10 SUC | 20% | 80% |
| 64801 - 129600 | 15 SUC | 30% | 70% |
| 129601 - 262800 | 20 SUC | 40% | 60% |
| 262801 - 525600 | 10 SUC | 40% | 60% |
| after 525601 | -10% / year* | 40% | 60% |
SUC Core is released under the terms of the MIT license. See COPYING for more information or see https://opensource.org/licenses/MIT.
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 Vivo Core.
The contribution workflow is described in CONTRIBUTING.md.
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.
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.
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