You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently if some code commitment would not applied by some reasons, then validators would not try to resend this commitment to sequencer. They would simply forget about this commitment and continue to work.
We need to give some guaranties to users that if they sent code for validation then soon or later this code would be validated.
Possible Solution
We have already mechanism like this for block commitments: validator tries to resent not applied block commitments each new block. May be we can make the same for codes:
Store and propagate not committed codes queue in database.
Each new block try to resend all code commitments in the queue.
Notes
No response
The text was updated successfully, but these errors were encountered:
Problem to Solve
Currently if some code commitment would not applied by some reasons, then validators would not try to resend this commitment to sequencer. They would simply forget about this commitment and continue to work.
We need to give some guaranties to users that if they sent code for validation then soon or later this code would be validated.
Possible Solution
We have already mechanism like this for block commitments: validator tries to resent not applied block commitments each new block. May be we can make the same for codes:
Notes
No response
The text was updated successfully, but these errors were encountered: