ZUBX sign letter of intent to develop on Syscoin Platform

Infographic by community member @Caner.

Caner’s proposal was one of the winning Community mini-proposals; he made this great Syscoin 3.0 infographic:

In the media

In case you missed it:

Partnership with Peer Mountain:

Syscoin review in Hindi

Masternode Governance Proposals

Every 43800 blocks (30.4 days) a superblock is generated by the Syscoin protocol, minting a maximum of 168630 Syscoin to be distributed amongst winning proposal. This superblock will be block 131400, and will be mined sometime on August 3th 2018 EST.

There are a lot of interesting proposals for this superblock, and they can be found here: https://syscoin.community/masternode-proposal

Keep in mind Voting closes 3 days or 3 (days)x 24 ( hours) x 60 ( minutes/blocks) = 4320 blocks before the superblock, in this case: 131400 - 4320= 127080 is the block that the voting closes.

SCMT Twitter account

For all the official and latest news releases please follow us for all the latest community news via our SCMT Twitter account, as well as hot-off-the-press Syscoin and BCF updates. The Syscoin team will also share our posts via their official social networking channels, to help spread the word.

Technical Updates

Syscoin 3.0.6 is released and it’s highly advised and mandatory to upgrade for general wallet users. You can find SYSCOIN QT 3.0.6 here. As stated above, upgrading to Syscoin QT 3.0.6 is mandatory and highly advised by the Syscoin core development team. Instructions for the mandatory upgrade for QT 3.0.6 can be found here:

Step 1: Login to the vps

Step 2.1: If you used Justin's script, run this command and choose 'y' to upgrade

bash <(curl -sL https://raw.githubusercontent.com/einalex/syscoin-scripts/master/masternode.sh)

Step 2.2: If you used BCNF's manual guide instead, run these commands in vps:

~/syscoin/src/syscoin-cli stop cd ~/syscoin



git checkout master && git pull



./autogen.sh



./configure



make -j$(nproc) -pipe



~/syscoin/src/syscoind



cd ~/syscoin/src/sentinel



git checkout master



git pull

You do NOT have to press the start button after updating the node. Pressing that button will reset your qualification time and make you wait for |masternodes| * 2.6 / 60 hours for rewards.

Masternodes

At time of publishing there are ~1231 masternodes online.

Masternode daily reward calculation: 37411.2 SYS per day divided across the number of active masternodes (Currently ~1231).

‘Seniority’ will get you +3% ROI on your block reward for every 4 months running your MN. For example, after the first 4 months, you will get 25.98 + 3% = 26.77 rewards per block.

Latest release wallet for creating/managing masternodes is QT 3.0.6. Latest release for Sentinel is 1.1.1.

Checking masternodes

You can check your nodes with your server console on your server (e.g. Putty). Checking the status of your masternode(s) via the server console is always the most accurate way to do so. So if you doubt on QT, check on VPS.

There is a slight differentiation in comments for people who used the Justin Silver script and people who manually installed and update their VPS.

If you used the script to install and update your VPS, use the following lines to run useful commands (via Putty):

Checking your client version: syscli getinfo

Checking your masternode sync status: syscli mnsync status

Checking your masternode status: syscli masternode status

Checking the # of masternodes active: syscli masternode count

Checking the uptime of your masternode:

syscoin-cli masternodelist activeseconds | grep [your IP address]

If you manually install and update your VPS, use the following lines to run useful commands (via Putty):

Checking your client version: syscoin-cli getinfo

Checking your masternode sync status: syscoin-cli mnsync status

Checking your masternode status: syscoin-cli masternode status

Checking the uptime of your masternode:

/syscoin/src/syscoin-cli masternodelist activeseconds | grep [your VPSIP address]

If you have any problems with checking the status or other masternode related issues. Please reach out to the community with the ‘Masternodes’ Channel on Slack.

For more information visit Syscoin.org