Using a batch call, this Referendum aims to cancel proposals that have been approved by the community but have failed to enact on time due to UI misconfiguration.
Namely, as we started to navigate OpenGov, it was brought to our attention that a misinterpretation of the parameter after, which is NOT an absolute block number but a delay expressed in blocks, implied that after approval, these referenda would take years to enact.
Among others, Referenda: 4, 5, 6, 7, 9, 10, 11, currently sitting in the scheduler, are expected to be approved from 1025-1100 days from now.
However, as the teams have already resubmitted their proposals with the updated parameters (see referenda history of various tracks), I am bringing forward the following call to cancel the proposals and avoid any complications in the future.
after parameter, which is a delay in blocks, not an absolute block number.Using a batch call, this Referendum aims to cancel proposals that have been approved by the community but have failed to enact on time due to UI misconfiguration.
Namely, as we started to navigate OpenGov, it was brought to our attention that a misinterpretation of the parameter after, which is NOT an absolute block number but a delay expressed in blocks, implied that after approval, these referenda would take years to enact.
Among others, Referenda: 4, 5, 6, 7, 9, 10, 11, currently sitting in the scheduler, are expected to be approved from 1025-1100 days from now.
However, as the teams have already resubmitted their proposals with the updated parameters (see referenda history of various tracks), I am bringing forward the following call to cancel the proposals and avoid any complications in the future.