Explorer wallet notification system
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 11
- Forks
- 26
- Avg merge
- 11h 58m
- Merged PRs (30d)
- 16
Description
**Summary**
Currently, users rely on the Telegram bot to stay updated with their orchestrator's operations. While functional, this method lacks flexibility and native Web3 integration. To enhance the user experience and align with decentralized principles, we propose integrating Web3-native notification services.
### **Proposed Solution**
Integrate one or more of the following Web3 notification platforms to deliver real-time updates directly to users' wallets or preferred decentralized communication channels:
- [Web3Inbox](https://web3inbox.com/) by WalletConnect
- [Push Protocol (formerly EPNS)](https://push.org/)
- [XMTP](https://xmtp.org/)
Additionally we could use browser notifications to also provide updates when people visit the explorer. Or go for a mobile app.
### **Benefits**
- **Decentralized and permissionless communication**
- **Improved UX:** Users can receive updates in their wallet apps or Web3 inboxes.
- **Greater flexibility:** Notifications can be customized by users based on specific events (e.g., missed rounds, reward calls, penalties).
- **Future-proofing:** Keeps the system aligned with the broader shift toward decentralized, wallet-native experiences.
### **Potential Use Cases**
- Reward distribution notifications
- Missed rounds or performance issues
- Governance updates or proposals
- On-chain parameter changes
### **Implementation Notes**
- Use wallet addresses as unique identifiers for notification routing.
- Allow opt-in/opt-out settings for different types of notifications.
- Consider offering a unified settings panel in the user dashboard.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are identified in the issue. First compare Web3Inbox, Push Protocol, and XMTP, then determine which notification channels and explorer settings are in scope. Done should include a selected integration, opt-in/opt-out controls, wallet-based routing, and notifications for the listed event types.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- blockchain, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100