TL;DR
- Ekko lets teams describe onchain moments in plain English and review the trigger logic.
- Teams can resolve affected wallets, accounts, users, and cohorts before delivery.
- Messages can route through the channels users, operators, and support already check.
Important
If you only do one thing: describe a missed notification moment, confirm the parsed trigger logic, and choose who should receive the message.
What You Can Do Today
Ekko’s first release focuses on fast time-to-first-useful-message:
- Create message plans using natural language and review what Ekko understood.
- Use supported wallet and contract activity as factual trigger context.
- Route governed notifications when conditions are met.
Getting Started
- Create your account: https://app.ekko.zone/signup
- Describe a message moment like: Notify affected users when a supported contract event changes their position
- Choose the affected audience and reachable delivery channels
Documentation
Start with the docs hub on the landing site:
https://ekko.zone/docs
Feedback
If you hit an edge case or want a feature, tell us what you were trying to do and what you expected to happen. That context is what makes the product better.