Cardano Notification Protocol (CNP)

[Proposal setup] Proposal title

Please provide your proposal title

Cardano Notification Protocol (CNP)

[Proposal Summary] Budget Information

Enter the amount of funding you are requesting in ADA

100000

[Proposal Summary] Time

Please specify how many months you expect your project to last

4

[Proposal Summary] Translation Information

Please indicate if your proposal has been auto-translated

No

Original Language

en

[Proposal Summary] Problem Statement

What is the problem you want to solve?

Cardano lacks a unified notification system. Users miss critical events; developers must build custom solutions, leading to poor UX and wasted resources.

[Proposal Summary] Project Dependencies

Does your project have any dependencies on other organizations, technical or otherwise?

No

Describe any dependencies or write 'No dependencies'

No outside dependancies

[Proposal Summary] Project Open Source

Will your project's outputs be fully open source?

Yes

License and Additional Information

Core components — integration specs, APIs, and indexer layer — will be open-sourced under MIT License. Public GitHub repo from launch for transparency and community input. Future expansion of open-sourced parts may be considered based on adoption.

[Theme Selection] Theme

Please choose the most relevant theme and tag related to the outcomes of your proposal.

Developer Tools

[Campaign Category] Category Questions

Describe what makes your idea innovative compared to what has been previously funded (whether by you or others).

Cardano currently has no open, standardized, and reusable notification framework. While other chains have push services, none exist on Cardano that allow any protocol to integrate easily via an open spec and contribute event adapters. CNP provides a pluggable, multi-channel system with wallet-level verification, privacy controls, and community-driven expansion enabling a shared infrastructure that benefits the entire ecosystem.

Describe what your prototype or MVP will demonstrate, and where it can be accessed.

The MVP will demonstrate a fully functional Cardano notification layer detecting on-chain events (transfers, DeFi activity) and delivering them through Telegram, Discord, and potentially a browser extension. It will include a public GitHub with integration standards, open APIs, and at least 2 live protocol integrations. All code and documentation will be available for anyone to adopt, test, or extend.

Describe realistic measures of success, ideally with on-chain metrics.

• 3+ on-chain event types supported in MVP.
• 2+ delivery channels live at beta launch.
• 2+ protocol integrations as notification channels.
• 1+ community-contributed adapter added to GitHub within 3 months.
• 100+ subscribed wallets within 3 months of beta, measurable via unique wallet subscription registrations (on-chain opt-ins).

[Your Project and Solution] Solution

Please describe your proposed solution and how it addresses the problem

We will build the Cardano Notification Protocol (CNP) — a unified, open, and modular real-time notification system for the Cardano ecosystem.

CNP will give users wallet-level push alerts for important blockchain and protocol activity, while giving developers an easy, standardized way to send trusted, verifiable alerts.

The system will:

• Track on-chain events such as ADA/token transfers, stake rewards, and DeFi protocol activity (e.g., liquidations, position changes).
• Enable protocol channels so verified projects can send signed JSON payloads for off-chain or mixed events like DAO votes, governance proposals, or maintenance notices.
• Deliver alerts via multiple channels at launch: Telegram bot, Discord bot, and browser extension with history (mobile app planned later).
• Be fully open spec so any project can integrate via GitHub, following published event schemas and integration guides.
• Include a contribution framework with example adapters, public review, and community-driven expansion.

By standardizing notifications, CNP will reduce duplicated development effort, increase user retention, and give every Cardano user the same high-quality real-time experience seen in other ecosystems.

[Your Project and Solution] Impact

Please define the positive impact your project will have on the wider Cardano community

The absence of a unified notification layer in Cardano is a friction point for both users and developers.

For users: Missed transactions, governance events, or protocol changes lead to poor experience, financial loss, and disengagement.

For developers: Every team building a wallet, DeFi app, or DAO must either forgo notifications or create bespoke solutions from scratch.

CNP’s positive impact:

• Ecosystem-wide enablement: Any dApp, wallet, or DAO can integrate real-time alerts without building its own system.
• Standardization: One schema for all Cardano notifications, improving cross-platform compatibility.
• User growth & retention: Timely, trusted alerts keep users active and engaged.
• Open collaboration: Specs and integration layer are open source, encouraging protocol self-integration and community contributions.

[Your Project and Solution] Capabilities & Feasibility

What is your capability to deliver your project with high levels of trust and accountability? How do you intend to validate if your approach is feasible?

Our team has over two years of experience building in the Cardano ecosystem, with a proven track record of delivering independent, production-grade systems without external funding. We developed the Cardano DEX Aggregator entirely in-house, integrating multiple Cardano DEXs into a unified interface, alongside a Telegram-based transaction monitoring bot, both requiring advanced indexing, protocol API integrations, and real-time data delivery.

• Technical Expertise: Demonstrated ability to design and implement high-performance indexers, event detection engines, and multi-channel delivery systems (bots, extensions, APIs) that meet production standards.
• Independent Track Record: Previous systems, including the DEX Aggregator and transaction bot, were built entirely without Catalyst or external funding, proving our ability to deliver complex, real-time infrastructure.
• Feasibility Validation: The CNP project will begin with a focused specification phase to define event categories, payload formats, and delivery standards, ensuring technical alignment and ease of adoption before full build-out.

This combination of independent delivery history, deep technical capability, and a phased, open-standards approach ensures we can deliver the CNP MVP within budget, on time, and ready for community adoption.

[Milestones] Project Milestones

Milestone Title

Notification Standard & System Specification

Milestone Outputs

• Define Cardano Notification Standard: event types, payload formats, delivery protocols.
• Create category specs (on-chain, governance, DeFi).
• Identify initial manual integrations.
• Draft architecture spec for indexers, triggers, and delivery.
• GitHub repo with README & structure.

Acceptance Criteria

• Technical specification for the Cardano Notification Protocol (CNP) architecture documented and published on GitHub.
• Integration standards for first event categories (on-chain transfers, stake rewards, and initial DeFi actions) clearly defined, including required data points and payload formats.
• GitHub repo live with initial schema definitions

Evidence of Completion

• Public GitHub link to the technical specification and integration standards.
• Public GitHub repo showing initial schema files, README, and structure.
• Documented list of initial protocols selected for integration.

Delivery Month

1

Cost

30000

Progress

30 %

Milestone Title

Core Event Engine & First Protocol Integrations

Milestone Outputs

• Backend event detection layer capable of monitoring key on-chain events (UTXO changes, ADA/token transfers).
• Implementation of notification delivery system for at least 1 channel.
• First protocol integration completed using the published standard.
• Reference integration published in GitHub demonstrating end-to-end event detection and delivery

Acceptance Criteria

• Backend event detection layer implemented to monitor key on-chain activities (UTXO changes, ADA/token transfers).
• Basic integration with the first protocol category completed (DEX or lending), following the published standard.
• Internal testing completed to confirm accuracy of event triggers and delivery across supported channels.

Evidence of Completion

• Public GitHub repo updated with backend code for event detection and delivery.
• Live demo or test environment link showing functional event detection and delivery for at least one protocol.
• Documentation in GitHub describing setup, usage, and first integration example

Delivery Month

2

Cost

30000

Progress

60 %

Milestone Title

Expand Protocol Coverage & User Interface

Milestone Outputs

• Integrations for at least two additional protocols.
• Web-based, mobile-friendly subscription management UI for selecting event types and delivery channels.
• Privacy and filtering controls (category, severity, quiet hours).
• Updated GitHub documentation for new integrations and UI usage.

Acceptance Criteria

• At least two new protocols producing notifications via the standard.
• Subscription management UI deployed and tested on both desktop and mobile.
• Privacy and filtering settings functional across delivery channels.
• GitHub updated with integration code and documentation.

Evidence of Completion

• GitHub repo updated with new protocol integration code and documentation.
• Screenshots or demo video of UI in operation.
• Short internal review confirming UI usability and filtering feature functionality.

Delivery Month

3

Cost

25000

Progress

90 %

Milestone Title

Public Beta Launch & Community Outreach

Milestone Outputs

• Public beta of the CNP platform deployed and accessible to any Cardano wallet user.
• Outreach conducted to protocols for self-integration.
• Public feedback collection process in place.
• Finalized public documentation and GitHub reference implementations.

Acceptance Criteria

• Beta version online, publicly accessible, and functional for multiple event types.
• Feedback collection active for anyone to give feedback and suggestions.
• Documentation complete and publicly available in GitHub

Evidence of Completion

• Public beta URL and GitHub documentation link
• Internal report summarizing beta findings and next steps.

Delivery Month

4

Cost

15000

Progress

100 %

[Final Pitch] Budget & Costs

Please provide a cost breakdown of the proposed work and resources

Total Requested: 100,000 ADA

Breakdown:

• Indexer setup & core event detection: 20,000 ADA
• Protocol channels system (API + signing): 15,000 ADA
• Delivery channels (Telegram, Discord, Extension): 20,000 ADA
• CLI tool: 5,000 ADA
• Open contribution framework + documentation: 12,000 ADA
• Security, rate limiting, abuse prevention: 8,000 ADA
• Testing, QA, community beta: 10,000 ADA
• Project management & coordination: 10,000 ADA
• Contingency: 5,000 ADA

[Final Pitch] Value for Money

How does the cost of the project represent value for the Cardano ecosystem?

This project delivers a reusable, open-source notification infrastructure that benefits the entire Cardano ecosystem. By building a shared standard and core event engine, we remove the need for each protocol to build and maintain its own notification system — saving developer time and resources.

The system will be free to integrate for any project, ensuring wide adoption and ecosystem growth. With minimal recurring costs, the initial investment creates a long-lasting, public good that improves user engagement, retention, and ecosystem reliability.

[Required Acknowledgements] Consent & Confirmation

Terms and Conditions:

Yes