|
2 | 2 |
|
3 | 3 | This document outlines major changes between releases. |
4 | 4 |
|
| 5 | +## 0.4.2 "Mutualization" (2 Sep 2025) |
| 6 | + |
| 7 | +A couple of ZK-based DKG rounds passed on TestNet, hence it may be safely |
| 8 | +enabled on MainNet. This version reschedules NeoXDKG, NeoXAMEV and NeoXEthSig |
| 9 | +forks to enable them earlier than planned initially. This version also adds an |
| 10 | +availability check for DKG-related files on node bootstrap. |
| 11 | + |
| 12 | +This version is fully compatible with v0.4.1 and does not require node |
| 13 | +resynchronization. For TestNet nodes no configuration changes are required on |
| 14 | +upgrade (comparing to v0.4.1). For MainNet nodes the DB reinitialization is |
| 15 | +required with the updated genesis configuration since `NeoXEthSig`, `NeoXDKG` |
| 16 | +and `NeoXAMEV` forks are rescheduled. Follow the instructions below to upgrade |
| 17 | +your node from v0.4.1 to v0.4.2: |
| 18 | + |
| 19 | +1. Download new binary and new genesis configuration file from the release page. |
| 20 | +2. Gracefully stop the node. |
| 21 | +3. Replace the old binary with the new binary. |
| 22 | +4. For MainNet nodes only: don't remove DB; reinitialize DB using new binary and |
| 23 | + new genesis configuration file with the following command: |
| 24 | + ``` |
| 25 | + ./geth init --datadir ./node-datadir ./config/genesis.json |
| 26 | + ``` |
| 27 | +5. Start the node. |
| 28 | + |
| 29 | +Behaviour changes: |
| 30 | + * NeoXDKG, NeoXAMEV and NeoXEthSig forks of MainNet are rescheduled to 3623040, |
| 31 | + 3689280 and 3689280 blocks correspondingly (#512) |
| 32 | + * reschedule NeoXDKG fork for PrivNet setups (#502) |
| 33 | + |
| 34 | +Improvements: |
| 35 | + * check DKG-related files are available on node startup (#503) |
| 36 | + * remove compatibility code from system contracts (#506) |
| 37 | + * update ZK-PrivNet documentation (#511) |
| 38 | + |
5 | 39 | ## 0.4.1 "Liberalization" (19 Aug 2025) |
6 | 40 |
|
7 | 41 | This patch-release supports recovery from out-of-date or lost anti-MEV keystore |
|
0 commit comments