Rung 1. Hello swarm
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- distributed-systems, machine-learning
Research direction
Read RFC 0001, especially the rung 1 pass criteria and “What every rung publishes,” then review the linked sub-issues #12–#18 and #25 to understand the work that makes up this milestone. The milestone is done when two or three machines, including a Mac, exchange DiLoCo updates over rust-libp2p, loss falls, workers agree after each sync, and the required artifacts are published; the issue says work has not started.
Written by the indexing model from the issue text.
Description
Rung 1. Hello swarm of the milestone ladder in RFC 0001.
What happens: Two or three machines, including a Mac, exchange DiLoCo updates over a rust-libp2p link.
Done when: Loss falls, workers agree after each sync, and the log is public (full pass criteria in RFC 0001). Every rung also publishes config and pins, dataset manifests, the full log, kept checkpoints, a ledger file and a short report (RFC 0001, "What every rung publishes").
Work
- #12 MPS and ROCm in ofl doctor
- #13 bandwidth in ofl doctor
- #14 hardware matrix
- #15 device keypair and signed report
- #16 RFC 0002 node packaging
- #17 rust-libp2p peer
- #18 two-peer integration test
- #25 bootstrap relay runbook
More sub-issues are linked as they are filed. Track progress on the roadmap.
Status: not started. Nothing has been trained yet.
Agent: omp / claude-opus-5-5
- Dominant language
- Python
- Stars
- 1
- Forks
- 2
- Avg merge
- 2h 4m
- Merged PRs (30d)
- 23
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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.
More from OpenFrontierLabs/openfrontier
-
agent-authored area/evals good first issue help wanted layer/8-outputs type/feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
OpenFrontierLabs/openfrontier#26 ·
Maintainers usually reply within 1 day
-
agent-authored area/docs good first issue help wanted layer/7-hosting type/docs
Difficulty 3/5 1-2 days Newbie friendliness 77/100
OpenFrontierLabs/openfrontier#25 ·
Maintainers usually reply within 1 day
-
agent-authored area/web good first issue help wanted layer/6-console type/feature
Difficulty 3/5 1-2 days Newbie friendliness 68/100
OpenFrontierLabs/openfrontier#24 ·
Maintainers usually reply within 1 day
-
Add hash and licence fields for every entry in `manifests/datasets.toml`, checked by `ofl check`Possibly taken @Neeraj111010 claimed this 1 day ago. Openagent-authored area/data area/python good first issue help wanted layer/5-storage type/feature
Difficulty 3/5 1-2 days Newbie friendliness 76/100
OpenFrontierLabs/openfrontier#23 · 1 comment ·
Maintainers usually reply within 1 day
-
agent-authored area/data good first issue help wanted layer/5-storage type/feature
Difficulty 4/5 3-5 days Newbie friendliness 62/100
OpenFrontierLabs/openfrontier#22 ·
Maintainers usually reply within 1 day
All issues in OpenFrontierLabs/openfrontier
Similar issues
-
Email validation accepts a trailing newlinePossibly taken @marcello-pichini claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
dbt-labs/spark-utils#51 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
bug frontend
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
vendrabuck/HERD#1419 ·
Maintainers usually reply within 1 day