Emergency rotation of compromised Chorus One oracle

Standing by to vote as soon as the vote is published.

Thanks @ChorusOne for explaining the measures taken - changing to a new machine.
It isn’t very reassuring though that the hot wallet could be leaked. You mention “at a point in the past” - kind of suggesting that it was because of circumstances that are not in effect currently. Nevertheless, if you don’t know how it happened, how can you know it won’t happen again or that these circumstances aren’t present now? Would you mind detailing the measures you are taking so the new key won’t be vulnerable? What if it’s the developer’s machine that is compromised?

I don’t doubt you will take the best possible course of action, but transparency in these circumstances is very much appreciated :slight_smile:

4 Likes