Network Identity Store¶

Purpose¶

The Network Identity Store (NIS) engine stores information associated with known external identities (of peers, topics, domains, and engines), such as advertised addresses and local metadata. The information stored can come from various sources, such as local configuration, P2P protocols (e.g. peer sampling, clustering, pub/sub), other engines, or user input.

In case of peer identities, it stores known addresses along with local routing and transport preferences, latency measurements, trust metric and trust zone (e.g. local, remote).

State¶

IdentityStore¶

--8<-- "./types/identity_store.md:purpose"

--8<-- "./types/identity_store.md:type"

Messages received¶

LookupIdentityRequest¶

--8<-- "id_store/messages/lookup_identity_request.md:purpose"

--8<-- "id_store/messages/lookup_identity_request.md:type"

UpdateIdentityRequest¶

--8<-- "id_store/messages/update_identity_request.md:purpose"

--8<-- "id_store/messages/update_identity_request.md:type"

Notifications sent¶

IdentityUpdated¶

--8<-- "id_store/notifications/identity_updated.md:purpose"

--8<-- "id_store/notifications/identity_updated.md:type"

Message flow¶

sequenceDiagram

--8<-- "id_store/messages/lookup_identity_request.md:sequence"

--8<-- "id_store/messages/update_identity_request.md:sequence"