Skip to content

Releases: blockchain-sierra/sierra

Sierra Core release v3.0.0

05 Jun 18:24
@sierracoin-team sierracoin-team
v3.0.0.0
8abf540
Compare
Choose a tag to compare
Sierra Core release v3.0.0 Latest
Latest

What's New?

Sierra 2.x:

  • was based on unsupported code
  • reached end of life

Sierra 3.x:

  • based on stable Dash 0.14 codebase
  • skein PoW used for bootstrap
  • PoS minting implemented (based on few PoS coins)
  • fixed few PoS code bugs (miner crashes and deadlocks)
  • added orphan PoS block automatic recovery (no more lost coins)
  • DevFee and SPOW payments added
  • PrivateSend is currently disabled
  • Governance payments are currently disabled
  • DIP3 blockchain-based deterministic masternode lists
  • LLMQ (long-living masternode quorums) support
  • LLMQ-based InstantSend (instant confirmation of almost all transactions)
  • LLMQ-based ChainLocks (51% attack blockchain protection)
  • Dash API compatible, lot of applications can be easily ported
  • binary releases for Windows (32bit/64bit, both ZIP and Installer)
  • binary releases for Mac (64bit DMG)
  • binary releases for Linux variants (Intel i686, Intel x86_64, ARM gnueabihf, ARM aarch64)

Masternode installation

If you use some masternode hosting platform, make sure that it supports DIP3, particularly, masternodeblsprivkey configuration option. Ask your service provider if it supports Dash-style DIP3 masternodes and how to configure them.

More info on masternode upgrades:

Masternode install script

After you rented a VPS with Ubuntu (versions 16.04, 17.10 or 18.04 are supported), you should have an IPv4 address and root password. Connect to the server (use putty, kitty or other ssh client on Windows) as root@IP with the password given. Then copy/paste the following commands:

wget -N https://github.com/blockchain-sierra/sierra/raw/master/contrib/masternodes/sierracoin_masternode_install.sh
sudo bash sierracoin_masternode_install.sh

The script will ask you to provide BLS private (secret) key. It can be generated for you automatically. If you upgrade an existing masternode, you should copy/paste your existing private key when asked to preserve masternode configuration. Final info screen will show you the BLS public key (if autogenerated). Save it for later to enable DIP3 masternode configuration when activated on blockchain.

What is DIP3

Here is a concise good explanation of DIP3 masternode advantages: https://organicdesign.nz/Masternode

As of mid 2019 the masternodes use DIP-3 protocol which removes the possibility of an operator voting (by splitting up the keys per role). It also gives the operator the freedom to manage the server without requiring the owner to be involved (for things like IP address changes) without requiring the owner to issue a command to start the MN back up. There is now no need for any configuration on the owner's side at all apart from the signing of a message created by the operator. Also, it makes reward payment more flexible by including a mechanism at the protocol level for MN operators to be paid directly from the reward at a rate pre-negotiated with the owner (so the operator receives their fees automatically in a trustless way instead of having to invoice the owner). DIP-3 means also that you don't need the dash-core wallet, you can use anything that can sign, there's also a stand-alone script for signing anyway, so you can now use any wallet like exodus etc for your collateral. Even a full paper wallet can be used now because you only need to use the key if you change your MN operator and the payouts can now be sent automatically at protocol level to your daily spending wallet. And finally the other relevant change is that the randomness has been removed from the top 10% of the payment queue, which means that all nodes will be paid on an exact schedule.

Assets 12
Loading