nspcc-dev / nspcc-dev/neofs-node
ir: Use Neo Go protocol config validation in local consensus launch mode
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 38
- Forks
- 51
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 38
Description
currently IR validates blockchain config by itself
as @AnnaShaleva mentioned in comment, Neo Go lib provides https://pkg.go.dev/github.com/nspcc-dev/neo-go@v0.104.0/pkg/config#ProtocolConfiguration.Validate that performs similar checks
we cannot reuse this checker easily cuz its errors are tied to the Neo Go config format while IR has its own. Specific error system can help
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 reading pkg/innerring/config.go and the linked Neo Go ProtocolConfiguration.Validate documentation, then compare the existing checks and error formats. Establish the intended validation and error boundary for local consensus launch mode; done means overlapping protocol checks are covered without coupling IR's config errors to Neo Go's format.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain, distributed-systems
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100