INCIDENT 033 | Lag in chain index sync

[Christian-MK]

Trigger

• ⬛ suspected malware infections
• ⬛ access violations
• ✔️ anomalous system behaviors
• ⬛ human errors
• ⬛ unauthorized access attempts

Date

2024-05-01

Summary

COOP was unable to query the Plutus chain index due to the chain index sync falling behind mainnet.

Status

Under Review

Assessment

The lag in chain index sync resulted in a missed publication at 1600 UTC. However, once the Plutus chain index caught up and was re-synced, the Orcfax team was able to publish manually to mainnet at 1621 UTC.

Additional Notes

The plutus-chain index remains a recognized risk to the quality of the oracle solution offered by Orcfax and has been the subject of a technical overhaul in the project for the past five months. Once the dependency has been removed publishing should become more reliable.

Technical improvements

The plutus-chain-index will be replaced with Orcfax V1.

We are investigating:

1. How the new solution can be made more reliable based on the lessons learned with the plutus-chain-index.

Documentation improvements

N/A