Skip to content

Releases: syscoin/syscoin

Syscoin v4.4.0rc7 Testnet Only

02 Sep 18:10
db9ae1f
Compare
Choose a tag to compare
Pre-release

For users of MacOS running on M1/M2 chips & users of ARM linux & users of aarch64 linux :
Please disable sysgeth when running the arm64 version of darwin or linux binaries.
To disable sysgeth, add the following line to your syscoin.conf

Syscoin v4.4.0rc6 Testnet Only

30 Aug 16:49
0d7b165
Compare
Choose a tag to compare
Pre-release

For users of MacOS running on M1/M2 chips & users of ARM linux & users of aarch64 linux :
Please disable sysgeth when running the arm64 version of darwin or linux binaries.
To disable sysgeth, add the following line to your syscoin.conf

Syscoin v4.4.0rc5 Testnet Only

25 Aug 07:15
6fb7ad4
Compare
Choose a tag to compare
Pre-release

For users of MacOS running on M1/M2 chips & users of ARM linux & users of aarch64 linux :
Please disable sysgeth when running the arm64 version of darwin or linux binaries.
To disable sysgeth, add the following line to your syscoin.conf

Syscoin v4.4.0rc4 Testnet Only

17 Aug 02:01
b660efd
Compare
Choose a tag to compare
Pre-release

For users of MacOS running on M1/M2 chips & users of ARM linux & users of aarch64 linux :
Please disable sysgeth when running the arm64 version of darwin or linux binaries.
To disable sysgeth, add the following line to your syscoin.conf

Syscoin v4.4.0rc3 Testnet Only

13 Aug 17:18
Compare
Choose a tag to compare
Pre-release

For users of MacOS running on M1/M2 chips & users of ARM linux & users of aarch64 linux :
Please disable sysgeth when running the arm64 version of darwin or linux binaries.
To disable sysgeth, add the following line to your syscoin.conf

zmqpubnevm=

Syscoin v4.4.0rc2 Testnet Only

11 Aug 17:55
Compare
Choose a tag to compare
Pre-release

For users of MacOS running on M1/M2 chips & users of ARM linux & users of aarch64 linux :
Please disable sysgeth when running the arm64 version of darwin or linux binaries.
To disable sysgeth, add the following line to your syscoin.conf

zmqpubnevm=

Syscoin v4.4.0rc1. Testnet Only

14 Jul 17:49
Compare
Choose a tag to compare
Pre-release
v4.4.0rc1

Syscoin v4.3.0 NEVM

24 Nov 15:58
Compare
Choose a tag to compare

Official block height for NEVM fork is on block 1317500

this is an explorer https://blockbook.elint.services/blocks you can follow for Syscoin blocks.

Masternodes can upgrade prior to the block and we will transition miner's and ensure everything is operational both miners and masternodes prior to enabling exchanges/services and regular users. You may install by simply running the new version of code overtop of their existing install. Reindex should happen automatically which will download and sync the chain from genesis.

If one does not want to run Geth for NEVM part of the network you can define zmqpubnevm as an empty string which will skip running Geth and not validate EVM blocks.

See release notes for more: https://syscoincore.org/en/releases/4.3.0/

Full Changelog: v4.2.2...dev-4.x

What's Changed

NEVM explorer: https://explorer.syscoin.org/
Ethstats: https://ethstats.syscoin.org/

Masternodes: Please update your sentinel to the latest https://github.com/syscoin/sentinel

Syscoin 4.3.0rc3 Testnet Release

27 Oct 02:29
Compare
Choose a tag to compare
Pre-release

This release builds upon RC2 but fixes windows sysgeth issues. Also fixed intermittent issues of starting/stopping and reorgs with NEVM.

Syscoin 4.3.0rc2 Testnet Release

27 Sep 20:19
Compare
Choose a tag to compare
Pre-release

Syscoin NEVM testnet RC2, this is not intended to be a final release or run on mainnet. We are testing on our official testnet, migration happening on block 840000, this is an explorer https://sys-explorer.tk/blocks you can follow for Syscoin blocks. More info to follow for NEVM explorers, faucets etc. Once we migrate to the new block, masternodes can upgrade by simply running the new version of code overtop of their existing install. No reindex should be necessary.

If one does not want to run Geth for NEVM part of the network you can define zmqpubnevm as an empty string which will skip running Geth and not validate EVM blocks.

Other useful links:
https://ethstats.tanenbaum.io/
https://bridge-testnet.syscoin.org/
Web3 endpoint: https://rpc.tanenbaum.io
Network ID: 5700
Network name: NEVM Tanenbaum

Development links:
Internal bridge contracts: https://github.com/syscoin/sysethereum-contracts/tree/dev-4.2.0
Reference dapp to utilize bridge using web3/pali/metamask: https://github.com/syscoin/sysethereum-dapp/tree/testnet (live at https://bridge-testnet.syscoin.org/)
Entry point into c++ syscoin mint funtion (burn on evm and mint as syscoin SYSX SPT): https://github.com/syscoin/syscoin/blob/dev-4.x/src/services/assetconsensus.cpp#L24
Geth fork running alongside Syscoin Core: https://github.com/syscoin/go-ethereum
Solidity opsysblockhash commit: syscoin/solidity@773f0cc

Mining:
You can mine by adding configuration to syscoin.conf (or by specifying them as command line parameters) which will get passed to Geth running internally (process name 'sysgeth'):
gethcommandline=--mine
gethcommandline=--miner.etherbase=0xe600696eb0555c93f2c391a1406726cee239091d
gethcommandline=--miner.gaslimit=25000000

Gas limit is optional, by default it is at 8000000 (8m gas limit). NEVM runs with EIP1559 enabled. Change '0xe600696eb0555c93f2c391a1406726cee239091d' with your NEVM address. The rest of the mining process remains the same.

Functionally when you mine, a ZMQ message will be sent to the local geth running configured in NEVM mode to respond to a new block packaging up transactions in the geth txpool. This will put the block into the Syscoin block alongside the transaction root, receipt root and block hash of the NEVM block into the Syscoin block header. The Syscoin block will be propagated through Syscoin nodes which will validate the NEVM block by extracting the NEVM block and passing the data to geth (via ZMQ) to deserialize the block and validate it. If the NEVM execution on the block is invalid, the Syscoin block will be flagged as invalid by the validating node. If the block is valid, the geth node will import and store the block into its state. Connects and Disconnects of blocks are handled this way and so Syscoin block validity depends on NEVM block validity.

Enjoy!