Syscoin

Syscoin Core Developer Portal

Welcome to the Syscoin Core developer portal. You'll find comprehensive guides and documentation to help you start working with Syscoin as quickly as possible, as well as support if you get stuck.

Get Started

Syscoin 4.1.2 Upgrade Guide

Upgrade/Installation Guide:

Back up FIRST!

  1. Base on your OS, locate your wallet.dat within your Data Folder. This file contains your private key information so please back up this file before proceeding.

    • For Windows, the Data Folder is located at
      %APPDATA%\Syscoin
      or
      C:\Users\YourUserName\Appdata\Roaming\Syscoin

    • For Linux, the Data Folder is located at
      ~/.syscoin

    • For MacOS, the Data Folder is located at
      ~/Library/Application Support/Syscoin

  2. Copy the wallet.dat to somewhere safe

  3. Ensure syscoind is not running before proceeding!

Windows

On Windows, please download the latest version here: https://github.com/syscoin/syscoin/releases

If you prefer an installer, use "win64-setup"
If you prefer a zipped standalone version, use "win64zip"
If you previously used the installer for installing 4.0.3, you'll need to uninstall 4.0.3 first.
If you can't locate the uninstaller, go to Settings -> Apps & Features and locate Syscoin Core and click on Uninstall.
The uninstallation process will remove previous software, not your wallet data.

After Syscoin 4.0.x is uninstalled, please proceed to installing 4.1.2 normally.

Linux + MacOS

On Linux and MacOS, you can choose to use the pre-built binary (.dmg for MacOS) or build from source code:
https://github.com/syscoin/syscoin/releases

Compiling from source code

If you ran 4.0.3 before, please do the following first before checking out the latest code:
https://github.com/syscoin/syscoin/releases

cd ~/syscoin
git checkout v4.0.3
sudo make uninstall
make clean

This uninstall the 4.0.3 binaries from /usr/local/bin and then clean up the repo
Proceed as usual after

git checkout v4.1.2
./autogen.sh
./configure
make
sudo make install

Linux: Using Pre-built Binaries

Download the binary

wget https://github.com/syscoin/syscoin/releases/download/v4.1.2/syscoin-4.1.2-x86_64-linux-gnu.tar.gz

Check the shasum of the file (It shouldu say OK)

echo "7b1faf2f920ab459e9582510ceb5d8c61975cdd0b8d436371301c04b37dd7907 syscoin-4.1.2-x86_64-linux-gnu.tar.gz" | sha256sum -c

Unzip the file

tar xf syscoin-4.1.2-x86_64-linux-gnu.tar.gz

Install the binaries to /usr/local/bin

sudo install -m 0755 -o root -g root -t /usr/local/bin syscoin-4.1.2/bin/*

Masternodes

Masternode Install/upgrade guide can be found here:
https://github.com/syscoin/Masternode-Install-Script

Troubleshooting

1. geth_sync_status stuck

If getblockchaininfo shows that geth_sync_status stuck at waiting, check if the following processes are running:

sysgeth.nod
sysrelayer.nod
  • If sysrelayer.nod is not running, please find the Installation Folder for Syscoin Core
    default path is as the following
    Windows: C:\Program Files\Syscoin
    MacOS: /Applications/Syscoin-Qt.app/Contents/MacOS/
    Linux: /usr/local/bin
    Check if a file named scrypt.node exists in your Installation Folder. If yes, remove this file and restart Syscoin

  • If sysrelayer.nod is running, please give Geth some times to sync (~30 minutes). If it's still not synced, please delete the geth data directory from your Data Folder and try again. The default path is at the following:
    Windows: %appdata%\Syscoin\geth
    MacOS: ~/Library/Application Support/Syscoin/geth
    Linux: ~/.syscoin/geth

2. Blocks not syncing due to no peer

If the block is not syncing, and you see an empty peer list, please launch the console and enter the following command:
addnode 52.203.169.241 onetry

3. Transaction not being received / Blockchain not synced

Check if you're still on 4.0.3. If you are, please upgrade to 4.1.2 (see above) and the issue the following command once the node is up
syscoin-cli reconsiderblock 544454cae7e82aca8ca5cfb942b9f64d484bd7b8300d47bb90fd2c50f9134eff

Updated 12 days ago

Syscoin 4.1.2 Upgrade Guide


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.