Drey Actuaries coordinate operations over the Nostr protocol, with each Drey Actuary running their own private client and relays built-in. Nostr was selected because of the client / relay architecture and eventual private asynchronous communication. Drey Actuaries operating their own private relays can tune their relays to accept messages from other Drey Actuaries as the medium for conducting communications for actuary operations, co-ordination on voting, cryptographic threshold signature and verifiable random function protocols, as well as in future accepting communications from other clients that Drey Actuaries will offer services to, like providing account balance information, etc.
Initiative / goal
Nostr enables Drey to minimize communication protocol sprawl by limiting all communication between components, clients, servers to using Nostr only.
Hypothesis
The end result will be that adding any new additional components to the architecture should be streamlined by having one 'go to' communication medium.
Acceptance criteria and must have scope
All comms between components go over Nostr as Nostr events.
Stakeholders
This is core capability/technology, affecting all stakeholders ini engineering.
Description
Drey Actuaries coordinate operations over the Nostr protocol, with each Drey Actuary running their own private client and relays built-in. Nostr was selected because of the client / relay architecture and eventual private asynchronous communication. Drey Actuaries operating their own private relays can tune their relays to accept messages from other Drey Actuaries as the medium for conducting communications for actuary operations, co-ordination on voting, cryptographic threshold signature and verifiable random function protocols, as well as in future accepting communications from other clients that Drey Actuaries will offer services to, like providing account balance information, etc.
Initiative / goal
Nostr enables Drey to minimize communication protocol sprawl by limiting all communication between components, clients, servers to using Nostr only.
Hypothesis
The end result will be that adding any new additional components to the architecture should be streamlined by having one 'go to' communication medium.
Acceptance criteria and must have scope
All comms between components go over Nostr as Nostr events.
Stakeholders
This is core capability/technology, affecting all stakeholders ini engineering.
Timeline
TBC