Geyser, while a great tool, does not provide an ergonomic end-to-end solution for developers to get a full picture of the data created from their programs or desired accounts. While useful for certain use cases, developers in the Solana ecosystem need a simple, yet malleable tool for retrieving live and historical data.
Please see the following RFP that outlines a request to create an open source indexer framework. The Solana Foundation lays out a list of proposed solutions, but the technology used to build the indexer will be decided during grant negotiation by the grantee and the Solana Foundation.
Logistics
Take note of the application deadline (10/04/2024). The maximum grant amount is currently earmarked to $100k in USD-equivalent locked SOL. The final grantee will work with the Solana Foundation to decide on the final terms of the agreement, including negotiation of rigorous but attainable milestones.
Ground Rules
This thread can be used for comments, questions, praise, and / or criticism, and is intended to be an open forum for any prospective responders. This thread is also an experiment in increasing the transparency through which RFPs are fielded by the Solana ecosystem too, so please be mindful that we’re all here to learn and grow.
Responses to this RFP are not required to be public (but recommended), but if it is helpful to share notes or combine forces, then please use this thread for such purposes.
The RFP itself doesn’t mention the data sources where the proposed tool should fetch the data from. For me it seems that it should allow integration with existing indexers (or just node RPC) to fetch the data from there, and allow exporting the data about specific accounts directly to developer’s database. Could you please tell if I got the idea of this RFP right, or elaborate a bit more if this is not the case?
Have a related question on system design. Is the goal for this tool to interface with the validator via remote procedure call, or parse the state in /accounts/run and /rocksdb?
The RFP itself doesn’t mention the data sources where the proposed tool should fetch the data from. For me it seems that it should allow integration with existing indexers (or just node RPC) to fetch the data from there, and allow exporting the data about specific accounts directly to developer’s database. Could you please tell if I got the idea of this RFP right, or elaborate a bit more if this is not the case?
This is up to the RFP applicant, but ideally will be a connection to a geyser stream service that RPC providers already offer. If you can do RPC link or geyser, that would be bonus points.
Have a related question on system design. Is the goal for this tool to interface with the validator via remote procedure call , or parse the state in /accounts/run and /rocksdb?
The goal of this RFP is to offer a stack for developers who do not run fullnodes to get realtime (and historical) updates for their program. It is reasonable to say that the access to the data will come from geyser or RCP links that come from RPC providers.