SubQuery is committed to decentralizing web3 infrastructure by offering decentralized public Remote Procedure Call (RPC) services. These services are powered by a global network of independent RPC providers, ensuring a trustless and resilient system. Developers can access these public RPC endpoints to interact seamlessly with supported blockchain networks.
We are excited to announce that our next public RPC will be determined through community input. We invite you to suggest any RPC network you’d like to see supported by commenting on this forum post. On 11.59pm Sunday, January 19th, 2025 (UTC), we’ll compile all suggestions and initiate a community vote on our Snapshot platform.
To kickstart the discussion, here are some networks we’re considering:
Avail
Celo
Gnosis
Fantom
Fuse
IoTeX
Mantle
Scroll
Your participation is crucial in shaping the future of decentralized infrastructure. Please share your suggestions and preferences in the comments below.
For more information about our decentralized RPC services, visit our official page.
Note: The voting process will commence on January 20th, 2025 (UTC) via our Snapshot platform. Please ensure your suggestions are submitted before this date.
Hi, here is my suggestion, (with the help of Chat GPT) about why the Flux Network is an Ideal RPC Provider for SubQuery:
Before starting, you can note that Flux is totally decentralized, and runs more than 4000 dApps, and is backed by approximatively 14 000 nodes securising the network:
1. Decentralized and Scalable Infrastructure
Flux Network’s decentralized cloud infrastructure perfectly aligns with SubQuery’s requirements for RPC providers to have accessible and resilient hardware. With its global network of nodes, Flux offers:
Scalability: Flux’s dynamic node system can scale computational resources up or down to handle varying levels of RPC traffic, minimizing operational risks associated with infrastructure over- or under-utilization.
2. Robust Support for Hardware and Maintenance
Flux Network nodes already meet and exceed the hardware and maintenance requirements outlined for SubQuery RPC providers:
Hardware Requirements: Flux nodes are highly capable of running the necessary services, including RPC Node and Coordinator Services, on diverse infrastructure setups, from self-hosted systems to cloud-based deployments.
Operational Readiness: Flux nodes are equipped with monitoring and alert systems, enabling node operators to proactively address disk size, compute power, and other maintenance needs—critical for handling high ingress traffic and reindexing tasks.
3. Proven Expertise in Node Management
Flux’s technical community is experienced in provisioning servers, managing nodes, and handling advanced networking tasks. This aligns well with the SubQuery requirement for RPC Providers to have a technically proficient user base.
Junior Developer Accessibility: Flux’s ecosystem and tooling lower the barrier to entry for new node operators, allowing even junior developers to run nodes efficiently.
Advanced Networking Management: Experienced Flux operators can optimize performance through clustering, monitoring, and advanced configurations, ensuring seamless RPC service delivery.
4. Incentive Alignment and Staking
Flux’s ecosystem operates with economic incentives similar to SubQuery’s staking model. Flux node operators are already accustomed to staking Flux tokens (FLUX) and maintaining infrastructure for rewards, making the transition to staking and managing SubQuery tokens (SQT) straightforward.
Shared Design Philosophy: Flux’s reward-driven model ensures that node operators have “skin in the game,” just as SubQuery’s staking requirements aim to secure long-term commitment.
5. Seamless Integration with SubQuery
Flux Network’s infrastructure and ethos are primed for SubQuery integration:
Existing RPC Operations: Many Flux node operators already manage RPC services for other use cases. These existing endpoints could be quickly connected to the SubQuery Network, streamlining onboarding and reducing setup time.
Cross-Network Interoperability: Flux supports multiple blockchain ecosystems, allowing it to handle diverse RPC requirements as SubQuery expands its supported networks.
6. Mitigating Risks for RPC Providers
Flux’s operational model helps address some of the common risks for RPC providers:
Infrastructure Investment Risk: Flux’s scalable model enables operators to adjust their hardware investments based on demand, minimizing upfront costs. Its native ecosystem also provides opportunities to monetize computational resources beyond SubQuery RPC services.
Customer Acquisition: Flux’s established reputation within the web3 community positions it to attract developers and users. Additionally, Flux’s community-driven approach promotes active participation in forums and collaborations, building a solid reputation and encouraging customer trust.
Summary
By leveraging its decentralized infrastructure, technical expertise, and strong community, Flux Network is exceptionally well-positioned to meet SubQuery’s requirements for RPC providers. Flux can provide:
High-performance, reliable RPC services with decentralized resilience.
Scalability to support traffic growth and diverse blockchain networks.
A collaborative ecosystem to enhance SubQuery’s network reach and value.
Flux and SubQuery share a common goal of advancing decentralized web3 infrastructure, making this partnership a natural fit.
let’s consider adding Solana indexing. Solana offers high throughput, low costs and a growing ecosystem, making it a valuable addition that can attract more developers and expand our user base.
I hope this message finds you well. I wanted to suggest that we consider adding Solana indexing support to SubQuery. Solana is considered one of the best blockchains for several reasons:
High Throughput: Solana can handle thousands of transactions per second, making it one of the fastest blockchains available.
Low Transaction Costs: The cost per transaction is extremely low, which is a significant advantage for users and developers.
Growing Ecosystem: Solana’s ecosystem is rapidly expanding with a multitude of decentralized applications, NFTs, and DeFi projects.
Strong Developer Community: There’s a vibrant and active developer community that continues to innovate on the Solana platform.
Scalability: Solana’s architecture is designed for scalability without compromising on decentralization or security.
By supporting Solana, we could attract more developers and projects looking for efficient data solutions. This integration would enhance our offering and broaden our user base.
I suggest we add Solana indexing support to SubQuery. Solana is known for its high throughput, low transaction costs, and rapidly growing ecosystem with numerous DeFi and NFT projects. Supporting Solana will attract more developers and expand our user base, enhancing our platform’s capabilities and reach.
I hope this message finds you well. I wanted to suggest that we consider adding Solana indexing support to SubQuery. Solana’s rapid growth and high throughput make it a valuable addition to our platform. By supporting Solana, we could attract more developers and projects looking for efficient data solutions. This integration would enhance our offering and broaden our user base.
SubQuery is a powerful platform that allows developers to transform and query data from the blockchain. It currently supports indexing for a variety of blockchain protocols. To further enhance the capabilities and expand the reach of SubQuery, we propose adding indexing support for the Solana blockchain.
Solana is one of the fastest-growing blockchains, known for its high throughput and low transaction costs. With an increasing number of developers building on the Solana ecosystem, there is a growing demand for efficient data indexing and querying solutions to support decentralized applications. By integrating Solana into SubQuery, we can provide developers with the tools they need to build robust and efficient applications on Solana.
