nspcc-dev / nspcc-dev/neofs-node
Track committee change events in SN
Open
Nobody has claimed this yet.
enhancement
I4
neofs-storage
S3
U4
- Dominant language
- Go
- Stars
- 38
- Forks
- 51
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 38
Description
Refs. #3954, CommitteeChanged event is available from NEO contract since Cockatrice (https://github.com/nspcc-dev/neo-go/pull/3351 and https://github.com/nspcc-dev/neo-go/pull/3892)
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 with issue #3954 and the referenced neo-go pull requests to understand the CommitteeChanged event and how it is exposed. Then locate the SN event-tracking path; the work is done when committee changes from this event are tracked consistently in SN.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain, distributed-systems
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100