Add Notary Actor to the morph Client's context #1011

Open
opened 2025-12-28 17:21:29 +00:00 by sami · 0 comments
Owner

Originally created by @AnnaShaleva on GitHub (Apr 20, 2023).

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!

  • component label: morph Client
  • issue type: enhancement
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! - component label: morph Client - issue type: `enhancement`
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nspcc-dev/neofs-node#1011
No description provided.