Background
The ICF Ecosystem Growth Delegations tranche is an application-only part of the ATOM delegation program designed to advance key ecosystem initiatives and support critical infrastructure. Targeted RFPs allow the program to identify a specific need, define service standards, and invite qualified operators to propose how they would deliver it.
Why this service matters
A PebbleDB snapshot is a packaged copy of Cosmos Hub node data created using the PebbleDB database backend. It allows operators to start or recover a node directly on PebbleDB. PebbleDB can improve database performance and reduce storage requirements, helping lower the resources needed to operate a Cosmos Hub node.
In a recent survey asking validators which tooling improvements would provide the most value, PebbleDB snapshots were the top-requested enhancement. During the latest Cosmos Hub upgrade, operators also requested access to current PebbleDB snapshots while syncing and recovering nodes. Together, these signals demonstrate a clear need for a dependable PebbleDB snapshot service.
Many infrastructure services are provided voluntarily by validators, and several community operators already publish PebbleDB snapshots. Those contributions remain valuable, but voluntary availability does not guarantee a consistent publication schedule, automated restoration testing, dedicated download capacity, documentation, or outage communication.
This RFP is not intended to replace community providers or sponsor every existing service. It will select one provider to operate a sponsored PebbleDB snapshot service under the standards below. Community-operated snapshots can continue to provide additional options and redundancy.
Required scope
The selected provider must:
- Publish regularly. Publish a new
cosmoshub-4PebbleDB snapshot every 12 hours. - Keep snapshots minimal. Retain minimal block history, with the goal of keeping snapshots as small as possible.
- Use standard packaging. Publish snapshots as
tar.zstortar.lz4archives compatible with the current stable version ofzstdorlz4. Include the chain ID, PebbleDB backend, block height, and UTC creation time in each filename. - Test before publishing. Automatically restore each snapshot, start the node, confirm that the chain is
cosmoshub-4, validate application state, and verify that the node begins syncing. - Keep two snapshots available. Keep the two latest verified snapshots available. Remove the oldest only after its replacement has been validated and published.
- Reserve Cosmos Hub download capacity. Reserve at least 1 Gbps exclusively for Cosmos Hub (
cosmoshub-4) snapshot downloads. Support HTTP range requests for parallel and resumable downloads. - Publish operator instructions. Document how to find, download, verify, extract, and start a node from the snapshot, including compatible software and database settings.
- Publish checksums. Publish a SHA-256 checksum beside each archive in machine-readable metadata or a
.sha256file. - Provide clear attribution. Present the service as “Cosmos Hub Snapshots, provided by [Operator Name].”
- Communicate outages. Notify the service contact within 12 hours of detecting an outage affecting access to current verified snapshots. Include the known impact and an estimated restoration time when available.
What to include in your proposal
Proposals should include:
- Whether your team can meet every service requirement above.
- Any requirements your team cannot meet, with an explanation of the limitations.
- The setup work, infrastructure, and ongoing maintenance needed to operate the service.
- The expected time needed to make the service available.
- Relevant experience operating Cosmos Hub infrastructure, publishing blockchain snapshots, or running comparable production services.
- The additional ATOM delegation amount required to provide the service, above any default-tranche delegation for which the applicant qualifies.
One provider will be selected. Applicants must submit their proposal, including the proposed additional delegation amount, privately through the Ecosystem Growth Delegation application form.
For this RFP, applicants should propose only the additional ATOM delegation needed to operate the service, rather than their total combined delegation. Any delegation awarded through this RFP will be provided in addition to any default-tranche delegation for which the selected provider qualifies.
Proposals will be evaluated based on technical fit, ability to meet the service requirements, operational experience, implementation feasibility, expected service quality, launch timing, and the proposed additional delegation amount.
How to apply
Submit the standard Ecosystem Growth Delegation application form and reference “Cosmos Hub PebbleDB snapshots” in the project title or project description.
For context on the broader program, read the ICF delegation program framework announcement.