Optimism (OP) Centralizes Fault-Proof System

This is what the OP Foundation did with the Optimism fault-proofs a while back. Two months ago, the OP Foundation decentralized its sequencer

Optimism (OP) has encountered a setback in its efforts to decentralize its fault-proof system. Following community-driven audits, critical vulnerabilities were discovered, prompting the team to temporarily centralize the system.

After decentralizing its sequencer two months ago, OP Foundation encountered vulnerabilities during audits. To address these issues swiftly, the team has reverted to a centralized fault-proof system.

Optimism encountered 12 bugs during audits, prompting a hard fork on September 10. However, the reset has not undergone formal audits, raising concerns among some community members.

Optimism (OP) encountered a problem during its efforts to decentralize its fault-proof system. Following audits conducted by the community, critical vulnerabilities were discovered, prompting the team to temporarily centralize the system.

In August, the OP Foundation decentralized its sequencer, allowing testers and auditors to thoroughly examine the code for vulnerabilities.

However, on August 16, the team announced that it would be reverting to a centralized fault-proof system, following critical vulnerabilities discovered during the community-driven audit.

To address these issues promptly, the team decided to centralize their fault-proof system while they worked on resolving the problems. This measure is intended to be temporary.

Auditors discovered a total of 12 bugs, ranging in severity from low to high. Two severe issues were encountered:

– An error in memory management within the fault-proof system could allow attackers to take control of the system's virtual machine and execute code.

– A vulnerability permitted attackers to manipulate the system by providing a modified version of valid outputs, disrupting the dispute resolution process.

Three medium-severity issues were also identified. One involved the PreimageOracle, which could cause the system to replace correct data with false information.

Another issue, related to the LPP Challenge Period, rendered efforts to counter false claims insufficient, potentially leading to penalties for honest users.

Finally, an issue concerning timing allowed attackers to skip the waiting period and insert false data into the system.

The remaining seven issues centered on instruction implementation and memory verification.

To address these vulnerabilities, the foundation is preparing a hard fork, named “Granite,” which is scheduled for September 10. Notably, the reset has not been formally audited.

Despite this, the team stated that the change poses low risk based on their internal security review.

(OPUSDT)

Ce qui précède est le contenu détaillé de. pour plus d'informations, suivez d'autres articles connexes sur le site Web de PHP en chinois!