OpenZeppelin / OpenZeppelin/compact-contracts
Check `system_version` in env-up
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 55
- Forks
- 29
- Avg merge
- 5d 7h
- Merged PRs (30d)
- 25
Description
There should be a check that the system_version from the local-env's pinned node matches the actual node it reaches through env-up. If a foreign node is on 9944, the health check appears fine and it diverts attention away from where the problem actually resides
Contributor 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.
Research direction
Start by locating the env-up entry point and the local-env configuration that defines the pinned system_version. Trace how env-up reaches the node on port 9944 and how its health check currently determines success. Done means the check compares the pinned and reached node versions and exposes a mismatch instead of reporting a foreign node as healthy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100