Notification Standard

Notification Standard: Basic and Advanced

In the world of Web3, notifications are crucial for communication, and the NeoCast notification protocol ensures that the experience is both imperative and customizable. Notifications are divided into two parts: Basic and Advanced.

Notification Standard (Basic): This covers all the fundamental requirements for sending notifications.

Notification Standard (Advanced): This section delves into the composability of the NeoCast notification protocol, how it works, how it can be expanded, and more.

Composable Blocks of Notifications: Every notification within NeoCast is composed of four blocks:

  1. Verification: This includes a proof to verify if the sender is the rightful entity to send the notification.

  2. Identity: Identity contains information about the payload, which is discussed in detail later in the document.

  3. Payload: Payload is the core of the notification, carrying essential data.

  4. Content: Content encompasses the actual message of the notification.

Here's a brief overview of key components:

  • verificationProof: This is a proof mechanism to verify if the sender has the authority to send the notification.

  • identity: Identity contains information about the payload. More details will be provided in later sections of the documentation.

  • sender: This refers to the entity attempting to send the notification.

  • source: Source indicates where the notification is coming from.

  • recipient: This is the address to which the sender is trying to send the notification.

These components work together to ensure that notifications are secure, verifiable, and effectively delivered to the intended recipients in the Web3 environment.

Last updated