mirror of
https://github.com/nspcc-dev/neofs-node.git
synced 2026-03-01 04:29:10 +00:00
Why Alphabet nodes vote for the validators on their startup? #1047
Labels
No labels
I1
I2
I3
I4
S0
S1
S2
S3
S4
U0
U1
U2
U3
U4
blocked
bug
config
dependencies
discussion
documentation
enhancement
enhancement
epic
feature
go
good first issue
help wanted
neofs-adm
neofs-cli
neofs-cli
neofs-cli
neofs-ir
neofs-lens
neofs-storage
neofs-storage
performance
question
security
task
test
windows
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nspcc-dev/neofs-node#1047
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @notimetoname on GitHub (Jun 19, 2023).
What I have read:
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-amdas 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?
@roman-khimov commented on GitHub (Jun 20, 2023):
It's not a big problem, the GAS cost is rather low and you don't restart nodes often. Then #2365 solves the main part of it and still leaves this behavior as a mechanism for IR change. Control/adm may be nice, but just require more effort for a very little gain.
@notimetoname commented on GitHub (Jun 21, 2023):
My main question is about that config value in general. Is it possible and is it more convenient to remove it at all and do such things another way? Should it be an app configuration?