daoleno
@daoleno
Exploring the idea of an open-source crypto data terminal, built by the community for the community. For deep on-chain insights, what are the non-negotiable features? Beyond dashboards & explorers, what analytics & alerts are crucial?
6 replies
8 recasts
88 reactions
David (d/acc)
@promptrotator.eth
how are you sourcing the data? I think replicating gmgn is a great idea, but some archive nodes are like 10tb+
1 reply
0 recast
0 reaction
daoleno
@daoleno
Yes, this is precisely why it should be an open-source project. For analytic data, users should be able to choose: 1. Retention duration 2. Blockchain chains to include 3. Specific data types to index and store Regarding archive data, self-hosted nodes offer a practical solution. Based on my recent check, a reth base network archive node requires approximately 6 TB storage – prohibitively expensive in cloud environments and difficult to maintain synchronization, but significantly cheaper and easier to manage on home servers. Looking ahead, I see two potential solutions: 1. Union API Solution: A hosted API for users who prefer not to run archive nodes/indexers, though this would require significant infrastructure costs 2. Preferred Distributed Approach: Enabling syncing of processed data between nodes through our gateway registry. This would: ▪ Eliminate redundant data indexing ▪ Maintain data sovereignty ▪ Create a decentralized network effect
1 reply
0 recast
3 reactions