mirror of
https://github.com/nspcc-dev/neofs-node.git
synced 2026-03-01 04:29:10 +00:00
Add Notary Actor to the morph Client's context #1011
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#1011
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 @AnnaShaleva on GitHub (Apr 20, 2023).
Is your feature request related to a problem? Please describe.
Notary actor is used by both storage node and IR node to send notary requests (ref. #2310). However, new actor is created each time the request need to be sent, which is awful.
Describe the solution you'd like
We need to create a single Notary actor once per morph client initialisation like it is done for RPC actor. However, Notary actor always contains committee multisignature account (either dummy or real, depends on IR/SN choice). Thus, we should track committee update events and create new Notary actor each time committee is changing.
Describe alternatives you've considered
https://github.com/neo-project/neo/issues/2763 would be very helpful, if implemented. Another option is to add some callback to Neo contract as we now have CN inside the IR node. And finally, we can always track committee members by polling.
Don't forget to add labels!
enhancement