2.4. Appendix¶
2.4.1. Delivery Service¶
A Delivery Service is an RPC endpoint where a client can deliver its message (see API).
The delivery service
checks whether the message satisfies the recipient’s spam policy (see ProfileExtension)
decrypts the envelope, adds a postmark, and stores the message encrypted for the recipient until the recipient picks it up.
if supported, notifies the receiver that there is a new message.
Delivery service nodes can be operated as a service or self-sovereign by the user. The protocol explicitly allows (see user profile) a user to point to multiple delivery services so that if one is not available, another can be used. However, delivery service nodes can also act as gateways to other protocols, services, or applications.
2.4.1.1. Gateway to other service¶
If a delivery service works as a gateway to another protocol or service, it must implement the API to receive dm3 messages. However, how it then processes the messages and delivers them to the ecosystem to which it is acting as a gateway is completely up to it and depends only on the service or protocol to which it is connecting.
A gateway can also provide multiple delivery service nodes as primary and fallback services.
2.4.2. Cross Chain Applications¶
Although the dm3 protocol is fundamentally designed to use ENS as a central registry, the protocol can also be implemented on other chains. Name services similar to ENS can be used as a local registry in the ecosystem of this chain. For the entire dm3 ecosystem, this local registry can be directly integrated via CCIP (Cross Chain Interoperability Protocol) (and vice versa) so that interoperability can be established. A complementary extension will further simplify the handling of names of such local registries by automatic mapping of top-level domains (see top-level alias at protocol extensions).
2.4.3. RPC Error Codes¶
Default error codes are specified in the JSON-RPC specification.
Error code |
Error text |
Description |
|---|---|---|
-32600 |
Invalid Request |
The JSON sent is not a valid Request object. |
-32601 |
Method not found |
The method does not exist / is not available. |
-32602 |
Invalid params |
Invalid method parameter(s). |
-32603 |
Internal error |
Internal JSON-RPC error. |
-32700 |
Parse error |
Invalid JSON was received by the server. An error occurred on the server while parsing the JSON text. |