Dragan Z
@roberto-bayardo do we know what else is needed from your side to close the work on this issue?
We might want to consider if this should be a P1, based on internal chats we had during planning. @sebastianst @roberto-bayardo - let's discuss it on the Kick-off call.
As agreed on the ENG staff meeting, I'm assigning this to @protolambda as lead implementer that will own this side of work for Granite hardfork.
We should check with @blmalone about his approach for this check.
just to increase visibility, I'm sharing a document with the current document for this implementation: https://www.notion.so/oplabs/Genesis-validation-update-f453b1b676d440efb0ac43adc05cab2f - we are thinking that approach 2 is what we will do to get...
@GrapeBaBa - hey, wanted to check about your plans to continue work on this issue, since it would be great to close the remaining work?
@salindne can you address the latest comments we had, after our first round of reviews for this PR? 🙏
we can just close this issue, we can keep track in the hackmd or create a new issue, if we need to.
@emhane can you review this and let me know if you think something is missing from the suggested scope we have in the issue?
I like what @Inphi share with us on slack and I think it can be used a starting point for the scoping document for auditors: **MT-Cannon is our next iteration...