QA Report

[c4-bot-4]

See the markdown file with the details of this report here.

[ElliotFriedman]

You can't lift the pause by updating the pause duration because you can't execute or propose transactions while the contract is paused.

Once paused, the only way to unpause is to wait it out and let the contract unpause.

[c4-judge]

GalloDaSballo marked the issue as grade-c

[gesha17]

Hello @GalloDaSballo,

The sponsor's comment is a valid one:

You can't lift the pause by updating the pause duration because you can't execute or propose transactions while the contract is paused.

Once paused, the only way to unpause is to wait it out and let the contract unpause.

That was a logical mistake on my part, I don't know why I wrote that, must have been tired. But the rest of the submission is valid. There will be a duration that the protocol will remain without the protection of the pauser guardian.

Especially considering the recent sophisticated attack on Radiant, which involved using malware on the victims computers to compromise the signer keys, this should be a valid concern. The report 137 from the validation repo should be duped with this one.

[GalloDaSballo]

The pause guarantees that a "circuit break" happens
This is a one off event and must be acted upon
Per the EDGECASES document we know that based on the trust on spells vs guardian, config could be set differently

I believe this shows a scenario in which the owners incorrectly interact with the protocol as they should use the pause as a means to take other actions