Make the DFO Protocol resilient
Open
@eflumerf is already working on this.
Since Apr 15, 2026.
- #486 by @copilot-swe-agent — closed without merging
- Dominant language
- C++
- Stars
- 3
- Forks
- 5
- Avg merge
- 4h 42m
- Merged PRs (30d)
- 6
Description
One of the items identified in the Application Framework Review Workshop was that the DFO is a single-point-of-failure in the system. We should revise the DFO protocol so that multiple DFOs can be run in concert, and they achieve consensus about each decision in some manner (preferably with very low latency). The chosen pattern could then be extended to other vulnerable points in the system (such as the MLT).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.