Submitted by GreyArt, also found by WatchPug
While there is no loss of funds, removing an operator will cause the cache functionality to be permanently broken. If there was a function that had a modifier which requires the cache to be synced before the function can be called, it would not be callable as well.
The underlying issue is how the bytes32 operator is removed from the array when removeOperator() is called. Its value gets deleted (set to 0x0), but isnt taken out of the array.
For ease of reading, we use abbreviated strings like 0xA, 0xB for bytes32 and address types.
Instead of doing an element deletion, it should be replaced with the last element, then have the last element popped in removeOperator().
maximebrugel (Nested) commented:
alcueca (judge) commented:
