celestiaorg / celestiaorg/docs
systemd light-node unit omits --p2p.network, so it runs Mainnet Beta against a mocha store
- Dominant language
- MDX
- Stars
- 183
- Forks
- 423
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 19
Description
The maintenance systemd page's light-node unit has no `--p2p.network` flag. The troubleshooting page says "If you do not select a network, the default network will be Mainnet Beta", and `nodebuilder/store.go` puts the network into the store path. So a reader who runs `celestia light init --p2p.network mocha` (store at `~/.celestia-light-mocha-5`) and then installs the published unit gets a service running mainnet against a store it never initialised.
Page: https://docs.celestia.org/operate/maintenance/systemd/
Suggested fix: add `--p2p.network ` to the unit's ExecStart, with a note that it must match the network used at init.
Checked 2026-09-02. I'm Henrik, I run testnetradar.com, not affiliated with Celestia.
Contributor guide
Research direction
Start with the maintenance systemd page and its light-node unit, then read the troubleshooting network guidance and nodebuilder/store.go to confirm why the network must match initialization. Update the unit's ExecStart and add the matching-network note; done when the published instructions prevent a mocha store from running against Mainnet Beta.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- devops, documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 90/100