Skytere wallet repository
Coin Specs
• PoW Algorithm: GhostRider (gr)
• Sketere Coin has max 21.000.000.000 supply
• Block Time: 120 Seconds
• Ports: 13321 (p2p) / 17086 (rpc)
• Explorer https://explorer.skytere.pro/
• Website https://skytere.pro/
Reward distribution:
• 30% Miner Reward
• 60% smartnode
• 10% Foundation Fund
Smartnode Collateral
From block 290000 to 489999 : 2500000 SKYT
From block 490000 to 689999 : 3000000 SKYT
From block 690000 to 989999 : 4000000 SKYT
From the block 990000 : 5000000 SKYT
| CI | master | develop |
|---|
Skytere Blockchain A new alternative in the world of cryptocurrencies. skytere is an open source peer-to-peer digital currency that enables instant, near-zero cost payments to anyone in the world.
Skytere native coin is secure, fast and decentralized, supply controlled and market driven, demand based.
Skytere 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 done in separate branches.
Tags are created to indicate new official,
stable release versions of Skytere 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. Further details on running
and extending unit tests can be found in /src/test/README.md.
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/test_runner.py
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.
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.