search

semuxproject / semux-core

Semux Core
https://www.semux.org
MIT License
76 stars 31 forks source link

Core: Nodes continue to signal even after the fork has been activated #189

Closed semuxgo closed 5 years ago

semuxgo commented 5 years ago

As reported by @honeycrypto.

In the testnet, the VM fork was activated at block 1500. The signal still exists in block 1501

orogvany commented 5 years ago

see #139

Most forks we've had stop syncing for any non updated clients when going past the activation point, so they are forced to update.

The VM fork continues to allow old clients to sync up until the point of first CREATE/CALL (or at least it did on old testnet), so the old clients would eventually stop syncing, update, but would have already missed the signalling.