Post-launch README polish — gated on ligate-devnet-1 actually being live at rpc.ligate.io.
Changes
- Badge row (~line 3): swap
[](#status) for a green "devnet live" variant linking at the chain's v0.1.0-devnet release.
- Prose (~line 101): "Pre-devnet.
ligate-devnet-1 is targeted for Q2 2026. Tracking issue: ligate-chain#112." → "Devnet live. ligate-devnet-1 is serving at https://rpc.ligate.io. CLI tested against chain release v0.1.0-devnet."
- Install example (~line 18) currently references
v0.0.1-devnet as the example tag — should reference the actual v0.1.0-devnet release tag once it's tagged on the cli repo too.
Why post-launch only
Badge accuracy: partners seeing "Devnet live" expect a working chain at rpc.ligate.io. We flip when it's actually serving.
Coordinate with
Same flip in lockstep across the trio:
ligate-io/ligate-chain — README line 16 (badge) + line 93 (prose).ligate-io/ligate-js — README line 3 (badge).
Trigger
ligate-io/ligate-chain#237 acceptance: chain has produced 24-48h of stable blocks at rpc.ligate.io.
Post-launch README polish — gated on
ligate-devnet-1actually being live atrpc.ligate.io.Changes
[](#status)for a green "devnet live" variant linking at the chain'sv0.1.0-devnetrelease.ligate-devnet-1is targeted for Q2 2026. Tracking issue:ligate-chain#112." → "Devnet live.ligate-devnet-1is serving athttps://rpc.ligate.io. CLI tested against chain releasev0.1.0-devnet."v0.0.1-devnetas the example tag — should reference the actualv0.1.0-devnetrelease tag once it's tagged on the cli repo too.Why post-launch only
Badge accuracy: partners seeing "Devnet live" expect a working chain at
rpc.ligate.io. We flip when it's actually serving.Coordinate with
Same flip in lockstep across the trio:
ligate-io/ligate-chain— README line 16 (badge) + line 93 (prose).ligate-io/ligate-js— README line 3 (badge).Trigger
ligate-io/ligate-chain#237acceptance: chain has produced 24-48h of stable blocks atrpc.ligate.io.