Notification Standard (Advanced)
The Notification Standard (Advanced) delves deeper into the architecture and specifications of notifications within the NeoCast protocol, aiming for modularity and extensibility. Here's a breakdown of the advanced notification components:
Verification:
Verification ensures the validity of the notification.
It checks the sender, source, and the authenticity of the payload content.
Identity:
Notification Identity Payload is a standard way to send notification payloads to NeoCast Nodes for processing.
These payloads can be stored in multiple ways (storage-independent behavior).
Identity ensures that NeoCast Nodes can understand and construct the notification payload from the data.
Payload:
Each notification sent to the protocol is a JSON payload containing various data about the notification.
This JSON payload is what makes the NeoCast Protocol payload content-independent.
It allows for expansion to different types of notifications based on community needs and protocol development.
Content:
Notification Content Markdown standardizes content markdown, creating a styling and formatting standard.
This ensures consistency in how notification content is presented to users.
In essence, the advanced notification standard provides the foundation for creating a modular and extensible notification system that can be used across various platforms, including web3 protocols, smart contracts, dApps, backends, and more. These notifications are tied to user wallet addresses, indexed by NeoCast Nodes, and can be queried and displayed by various crypto frontends, such as wallets, dApps, and mobile apps. This architecture allows for secure and customizable communication in the Web3 environment while accommodating future developments and community-driven needs.
Last updated