nspcc-dev / nspcc-dev/neofs-node
Why Alphabet nodes vote for the validators on their startup?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 38
- Forks
- 51
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 38
Description
What I have read:
- https://github.com/nspcc-dev/neofs-node/pull/170
- https://docs.neo.org/docs/en-us/basic/governance.html
- https://github.com/nspcc-dev/neofs-node/issues/2311
- https://github.com/nspcc-dev/neofs-node/pull/2363
The question: why do we need it? What is the purpose of such voting? Why can't it be done on network start (e.g. in neofs-amd as a separate step)?
It makes the alphabet contracts to be the winners of the voting and get more GAS. But it really needs to be done once on network startup and once every time IR is changed. Initial voting can be done in neofs-adm (or any managing procedure), and all the following can be done externally or by the IR's control service.
Where am I wrong?
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 cmd/neofs-adm/internal/modules/morph/initialize.go around lines 81-89, then read the referenced governance documentation, PRs, and issue. Compare the startup and recurring voting responsibilities; done means a maintainer-backed decision or design is recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- blockchain, go
- Domain
- blockchain, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100