Summary
root@windows95:~# FULLNODE_API_INFO="$(cat ~/fr/token):/ip4/127.0.0.1/tcp/1234/http" forest-cli sync wait -w
Status: Synced (0 epochs behind)
Status: Synced (0 epochs behind)
Status: Synced (0 epochs behind)
Status: Synced (0 epochs behind)
Status: Synced (1 epochs behind)
Status: Synced (0 epochs behind)
Status: Synced (0 epochs behind)
Status: Synced (0 epochs behind)
Status: Synced (0 epochs behind)
Status: Synced (0 epochs behind)
Status: Synced (0 epochs behind)
Status: Synced (0 epochs behind)
Status: Synced (1 epochs behind)
Status: Synced (1 epochs behind)
Status: Synced (0 epochs behind)
Status: Synced (0 epochs behind)
Status: Synced (0 epochs behind)
Status: Synced (0 epochs behind)
Status: Synced (0 epochs behind)
Status: Synced (0 epochs behind)
Node Head: Epoch 6194617 ([bafy2bzacecus5tyidt5xapyqpwv7bs7grzj5uixeqs6nlr7ssr7mvaiq4fk4g, ...])
Network Head: Epoch 6194617
Last Update: 2026-07-15T19:48:32.321625894+00:00
Active Sync Tasks: None
Not sure what those are, whether it's an issue in the forest-cli sync wait -w itself or somewhere in the daemon. More serious if the latter, but we should tackle it regardless.
Completion Criteria
Additional Links & Resources
Summary
Not sure what those are, whether it's an issue in the
forest-cli sync wait -witself or somewhere in the daemon. More serious if the latter, but we should tackle it regardless.Completion Criteria
Additional Links & Resources