During the latest reward tree generation we noticed that Fireeyes has not yet upgraded to smartnode v1.7.1 (released December 5), because they submitted a merkle tree root based on rewards tree v1, instead of v2. That’s why I decided to have a quick look at how the rest of the oDAO is doing.
I looked at the RocketNetworkBalances smart contract. oDAO nodes count up all the ETH in the protocol that belongs to rETH and submit the result there every ~21 hours in order to update the rETH exchange rate. During the latest update, Consensys reported the totalETH to be 173797548491634763613513 (Consensys Submit Balances Transaction), while other nodes (outside of Fireeyes) reported 173797548491634763611383 (for example: Nimbus Submit Balance Transaction). This indicates that Consensys is running an outdated version of the smartnode software as well, which calculates the ETH balance differently.
Furthermore, I noticed that the last transaction from the Etherscan oDAO node was 6 days and 8 hours ago. Since then, there have been 15 opportunities for oDAO nodes to participate in reaching consensus: 7 submit balances, 7 submit prices and 1 submit reward snapshot. Given that it takes more than half of the nodes to submit to reach consensus, it is incredibly unlikely for the Etherscan node to miss out on 15 straight opportunities while performing well ( 0.5**15 = 0.00003051757). This seems to indicate that either the Etherscan node has gone offline during the last week or is experiencing significant performance issues.
It appears that both Fireeyes and Consensys have not yet updated to Smartnode v1.7.1. Etherscan may be offline or experiencing performance issues. I didn’t find any irregularities with the remaining oDAO nodes.
- Can you confirm that you were not running Smartnode v1.7.1 at the time of tree generation/the last balance submission?
- If so, why didn’t you upgrade to it when it was communicated that: “Oracle DAO members must update to this version before Rewards Interval 4, on December 22nd”
- Can you tell us how you handle smartnode upgrades. Who is tracking new releases and how? Who is responsible for upgrading?
- Assuming you did not upgrade to v1.7.1 in time, what did you learn from this incident and how are you looking to avoid it in the future?
- What is your process for monitoring your node to ensure it is online and performing its duties?
- Are you aware of any current or recent issues with your node? If so, when did you notice and what have you done to rectify them?
- If there was an incident, what did you learn and how are you looking to avoid it in the future?