The Platinum [PLATINUM] Blockchain is an experimental smart contract platform protocol that enables instant payments to anyone, anywhere in the world in a private, secure manner. Platinum [PLATINUM] uses peer-to-peer blockchain technology developed by Bitcoin to operate with no central authority: managing transactions, execution of contracts, and issuing money are carried out collectively by the network. Platinum [PLATINUM] is the name of open source software which enables the use of this protocol.
Platinum uses libsecp256k1,
libgmp,
Boost1.63,
OR Boost1.57,
Openssl1.02k,
Berkeley DB 6.2.23,
QT5.8 to compile
Block Spacing: 5 Minutes Stake Minimum Age: 15 Confirmations (PoS-v3) | 30 Minutes (PoS-v2)
Port: 10255 RPC Port: 10257
!!! Strongly recommended to use binary mxe instead of compiling from sources, because problems are possible. http://pkg.mxe.cc/
-
git clone https://github.com/payplatinum/platinum/
-
cd platinum/src
-
sudo make -f makefile.unix # Headless
(optional)
-
strip Platinumd
-
sudo cp Platinumd /usr/local/bin
Platinum [PLATINUM] 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 regularly built and tested, but is not guaranteed to be
completely stable. Tags are created
regularly to indicate new official, stable release versions of Platinum [PLATINUM].
The contribution workflow is described in CONTRIBUTING.md.
The developer mailing list should be used to discuss complicated or controversial changes before working on a patch set.
Developer Slack can be found at http://platinumteam.slack.com.
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.
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.