-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
83109e9
commit 3a7abe2
Showing
1 changed file
with
18 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1,18 @@ | ||
# PRISM Mediator | ||
# PRISM Mediator | ||
|
||
Mediators play a critical role in self-sovereign identity wallets, particularly in the context of mobile devices, because mobile devices don’t typically have static IP addresses and might be offline or even turned off, which can make it difficult to establish direct connections between different parties in the ecosystem and ensure DIDComm message delivery. As a result, the mediator must relay, store, and forward messages between parties. | ||
|
||
Definitions of mediator and relays as per [RFC 0046](https://github.com/hyperledger/aries-rfcs/tree/main/concepts/0046-mediators-and-relays#summary) are outlined below: | ||
|
||
A `mediator` is a participant in agent-to-agent message delivery that must be modeled by the sender. It has its own keys and will deliver messages only after decrypting an outer envelope to reveal a forward request. Many types of mediators may exist, but two important ones should be widely understood, as they commonly manifest in DID Docs: | ||
|
||
- A service that hosts many cloud agents at a single endpoint to provide herd privacy (an "agency") is a mediator. | ||
- A cloud-based agent that routes between/among the edges of a sovereign domain is a mediator. | ||
|
||
A `relay` is an entity that passes along agent-to-agent messages, but that can be ignored when the sender considers encryption choices. It does not decrypt anything. Relays can be used to change the transport for a message (e.g., accept an HTTP POST, then turn around and emit an email; accept a Bluetooth transmission, then turn around and emit something in a message queue). Mix networks like TOR are an important type of relay. | ||
|
||
In self-sovereign identity infrastructure, a mediator can act as an intermediary between the user’s device and other entities in the ecosystem, such as issuers and verifiers. For example, when a user requests a credential from an issuer, the mediator can mediate or relay the requests between the user and the issuer. When the user presents a credential to a verifier, the mediator can again act as an intermediary that mediates or relays the requests between the user and the verifier. Using a mediator and relays, self-sovereign identity wallets can ensure that all transactions are securely communicated between the various parties. At the same time, users have full control over their data and identities. Mediators, relays, and self-sovereign identity wallets can provide high security and trust while ensuring the system is scalable and efficient. | ||
|
||
Prism Mediator is a critical component of the Atala Prism self-sovereign identity solution. Without a centralized authority, it enables secure communication between different entities in the Atala Prism ecosystem, such as users, issuers, and verifiers. | ||
|
||
For a detailed overview of `mediators` and `relays` refer to the [RFC0046: Mediators and Relays](https://github.com/hyperledger/aries-rfcs/tree/main/concepts/0046-mediators-and-relays). |