ObolNetwork / ObolNetwork/charon-distributed-validator-node
Add execution client RPC URL flag to charon for SAFE signatures in lock files
Open
Nobody has claimed this yet.
protocol
- Dominant language
- Shell
- Stars
- 91
- Forks
- 235
- Avg merge
- 1h 42m
- Merged PRs (30d)
- 1
Description
🎯 Problem to be solved
We have not added the charon flag for an EL to this repo. Meaning the first cluster using a SAFE as an operator address with this setup will encounter verification issues.
🧪 Tests
👐 Additional acceptance criteria
❌ Out of Scope
Contributor guide
No contributing guide indexed for this repository
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
The issue does not name files or tests. Start by locating the docker-compose and Shell configuration that passes flags to charon, then determine how an execution-client RPC URL should be supplied for SAFE signature verification in lock files. Done means the flag is available in this repository and the verification scenario works.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, shell
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100