Removing Key Duplicates

Specific Example Walkthrough

Important Note:

Before proceeding, we suggest checking with DAO contributors to help ensure correct procedures are followed.

1. Preparation:
• Ensure you have not sent a transaction recently and there are no pending transactions.
• Open the Node Operators Registry contract page on Etherscan: Node Operators Registry Contract.
• Confirm that the contract address corresponds to the Node Operators Registry contract from the documentation.
2. Connect Wallet:
• Make sure your wallet is connected to the relevant network (eg mainnet) and the correct account (the desired node operator registry address) is selected.
• Connect your wallet to Etherscan.
3. Initiate Key Removal:
• Expand the section 3. removeSigningKeys() on the Etherscan page.
• Fill in method arguments based on the keys you whish to remove:
• _operator_id:
• _index
• _amount
• Double-check the values and press the 'Write' button.
4. Transaction Confirmation:
• The site will prompt you to sign the transaction in your wallet. Verify all details and proceed to sign.
• Notify DAO contributors once you have sent the transaction to double check the results.
5. Confirmation and Follow-up:
• Please contact DAO contributors to clarify any points or if you have any doubts.
• This transaction will reorganize the keys in the contract.
6. Post-Action Checks:
• After the removal, the following steps will be taken:
• Wait for cache update at Lido Operator Dashboard and ensure the desired changes are reflected.

If something goes wrong:

• In the worst case scenario, it might be necessary to remove all keys above the currently used keys amount, but this may result in a significant gas cost.

Additional Recommendations:

• Wait for the key submitter page backend to update (every 30 mins on mainnet version) to verify that there are no duplicates and no invalid keys before submitting motions.
• Utilize the CLI tool to double-check for duplicates and invalid keys.