github ubiq/go-ubiq v5.1.0
v5.1.0 - Ramen 🍜

latest releases: v7.0.0, v6.0.0, v5.4.0...
3 years ago

Summary

All services which run Ubiq nodes are encouraged to upgrade but this is considered an optional upgrade as there are no hard fork changes. Fusion wallet will be updated to point to the latest version and you will automatically be prompted to upgrade.

Gubiq 5.1 is based on the v1.10.3 release of the upstream Go-Ethereum project and contains around 474 commits merged since the Gubiq 5.0 release that we made in February.

This release has been in testing for over a month internally with no issues.

This release also incorporates UIP 9. UIP 9 has been introduced in a backwards compatible way and brings us greater Dapp compatibility and resolves a LOT of minor issues (because developers assume Chain ID = Network ID) that we have had to debug and fix over the years.

For more information, see our blog post: https://blog.ubiqsmart.com/announcing-gubiq-5-1-e4c5a9982073

Changes

UIP 9 — Change NetworkID to match ChainID

Currently Ubiq’s networkId is 88, while chainId is 8. This should not be problematic, however much of Ethereum’s ecosystem was built with the assumption these values would match (instead of actually following the specification). To make it easier for these Dapps and wallets to properly support Ubiq (without us having to patch/fork each one separately), the networkId is changed to 8 to match the current chainId.
This has been implemented in a manner that allows for a window of time in which clients accept connections from peers reporting both the old and the new networkId (88 and 8 respectively).

This does NOT require a hardfork due to not touching consensus, however the window of time in which both networkIds.
At a later stage networkId 88 will be fully deprecated.

State snapshot system

In this release, the new snapshot mechanism is enabled by default. Snapshots provide O(1) access to state during EVM execution and also serve as the backbone of the snap sync and state pruning features. Note: should you run into any issues with snapshots, they can still be disabled using the --snapshot=false command-line flag.

Snap sync

This is a new sync mode, which is a replacement for ‘fast sync’. In snap sync, the node downloads Ubiq state data much more efficiently than fast sync ever could. With snap sync, we can also finally provide a progress indicator for the state download. Since this is a new feature, and few peers will support snap sync initially, snap sync is not yet enabled by default.

eth/66 protocol

Gubiq now supports eth protocol version 66, which adds request IDs.

Checksums

$ shasum -a 256 *
f2ae7bac0dda1205cf313b761706cbb53f8f0a289c88e23c1a77ab66267f5d62  gubiq-darwin-10.12-amd64
59f32c7e9847fa8f516779b740b9963f8ad4e0f24991f2c9378fc10c5812e9bd  gubiq-linux-amd64
bfc7a66f5964dc1507ca32d4e4bcccc7cf30eb7b0ad8e1c0dc50a429caea9e47  gubiq-linux-arm-7
f67bdd8de30408e23955995b7a82528e1cb696f1ed87c1b756521e9e65e2585a  gubiq-linux-arm64
2c13cbb4994ad77b0465346d6a8565368aa15134a26ea946c65d0ae8ef7b7da5  gubiq-windows-4.0-amd64.exe

Don't miss a new go-ubiq release

NewReleases is sending notifications on new releases.