Context
Dither currently relies on centralized backend services (API, indexer, database) to serve content. This means users depend on these services being available to access the messages. A "light client" would allow direct access to the AtomOne chain, making Dither truly decentralized.
Design goals
- Query transactions from Eclesia Indexer, either through GraphQL or edge function
- Minimal or no FE framework, keep third-party dependencies to a minimum
- The indexer client layer should be separate from the UI, making it reusable for other interfaces like a future
dither-cli
- No backend required - the client should work entirely from the browser
- Lightweight and fast - small bundle size, quick load times
Scope
- Fetch and display messages through Eclesia
- Wallet-based interactions through Adena
- Support core interactions: posting, replying, following, liking, and reposting
Context
Dither currently relies on centralized backend services (API, indexer, database) to serve content. This means users depend on these services being available to access the messages. A "light client" would allow direct access to the AtomOne chain, making Dither truly decentralized.
Design goals
dither-cliScope