When Kleros try to show a question with RPC they need to find it in the logs.
If we don't mind breaking the question struct api we should be able to squeeze 16 bytes worth into unused space without adding storage. Alternatively we could tack it on the end and keep the API at the cost of extra gas. Look into L2 gas pricing and see if this is worth optimizing.
16 bytes should be enough for all chains but ideally this should wrap around if it goes over rather than erroring out.
When Kleros try to show a question with RPC they need to find it in the logs.
If we don't mind breaking the question struct api we should be able to squeeze 16 bytes worth into unused space without adding storage. Alternatively we could tack it on the end and keep the API at the cost of extra gas. Look into L2 gas pricing and see if this is worth optimizing.
16 bytes should be enough for all chains but ideally this should wrap around if it goes over rather than erroring out.