This is v1.10.1 of the Smartnode.
It is a medium priority update for node operators Lighthouse or Lodestar, for anyone that generates their own rewards trees (including the Oracle DAO), and for anyone that wants to expose their Prometheus API port.
For everyone else, it is a low priority.
To upgrade, follow the Smartnode upgrade instructions.
Client Updates
- Updated Lighthouse to v4.3.0.
- NOTE: This version of Lighthouse has an important change - it will now only connect to two subnets on the Beacon Chain total, rather than one subnet per validator. This will considerably reduce its bandwidth usage but may result in slightly reduced block rewards for users with a large number of validators. To force it to subscribe to all subnets again, add the
--subscribe-all-subnetsto the "Additional BN Flags" field in theservice configTUI.
- NOTE: This version of Lighthouse has an important change - it will now only connect to two subnets on the Beacon Chain total, rather than one subnet per validator. This will considerably reduce its bandwidth usage but may result in slightly reduced block rewards for users with a large number of validators. To force it to subscribe to all subnets again, add the
- Updated Lodestar to v1.10.0.
Important Dates
- If already opted into Rolling Records, users (including the Oracle DAO) should update to v1.10.1 or later by epoch 225614 (August 31, 2023 05:29:59 AM UTC) to ensure that the records are properly created (see the Bug Fixes section below).
Smartnode Changes
rocketpool node sendnow accepts an arbitrary token address as the token-to-send instead of justrpl,fsrpl,eth, orrethso you can use it to safely move tokens that are currently in your node wallet directly via the CLI.
Bug Fixes
-
Finalized minipools are now correctly subtracted from the number of
stakingminipools in Grafana. -
Fixed a bug that prevented the Smartnode from starting when exposing Prometheus's HTTP port was enabled.
- Thanks to @0xfornax for this fix!
-
Rolling records will now use the proper starting slot when creating new records for subsequent intervals after reporting if one or more of the new interval's first slots were missing.
- The Smartnode will now invalidate checkpoint files that were made using previous Smartnode versions without this fix. Upon upgrading, it will invalidate any checkpoint files you may have already generated from v1.10.0 and start building a new record from the beginning of the interval. This is expected.
Misc Changes
- Added an Oracle Dao duty to report prices to the Base L2 chain.