diff --git a/docs/bg/subquery_network/2024.md b/docs/bg/subquery_network/2024.md new file mode 100644 index 00000000000..412a1f34fc1 --- /dev/null +++ b/docs/bg/subquery_network/2024.md @@ -0,0 +1,62 @@ +# 2024 in Review: SubQuery’s Top 5 Milestones + +As we look back on 2024, we’re proud to call it a major “year of firsts” for us here at SubQuery. This year was filled with groundbreaking achievements, major launches, and remarkable community growth. The year has flown by but it also feels so long ago that we had our TGE, CEX Listing and SubQuery Network mainnet launch - all on the same day! + +Let’s celebrate some of the key milestones that made 2024 unforgettable. + +## 1. Mainnet Launch + +After an extremely successful Public Sale on 30 January 2024, selling out of SubQuery’s native token (SQT) in less than 2 hours, we worked very hard to launch the SubQuery Network mainnet on 23 February 2024. Powered by SQT and launched on Base, immediately users could consume and/or index data from over 150 networks ([now over 270 networks](https://subquery.network/networks)). + +Almost 1 year on and we have: + +- 46 globally distributed and highly skilled Node Operators servicing the network +- More than 330 million SQT staked and delegated in the Network +- Serving more than 50 million RPC requests every day +- An overall average APY of 22.28% and much higher for Node Operators (94.66%) + +## 2. SQT Token Generation Event + +Combined with the Mainnet launch, we ambitiously chose to do our TGE and day one CEX listing with Bybit on the same day (23 February 2024) as well. The SubQuery Token (SQT) is designed as a utility token that powers the SubQuery Network, providing an incentive for participation, as well as serving as a medium of exchange for transactions within the SubQuery Network. Consumers of data commit SQT in exchange for RPC queries or indexed data from our globally distributed Node Operators. + +Today, you can acquire SQT through any of these centralised exchange: + +- [Bybit](https://www.bybit.com/en/trade/spot/SQT/USDT) +- [Gate.io](https://www.gate.io/trade/SQT_USDT) +- [Crypto.com](https://crypto.com/exchange/trade/SQT_USD) +- [MEXC](https://www.mexc.com/exchange/SQT_USDT) + +SQT is on a number of DEX Pools however most liquidity is on Uniswap. + +- [Uniswap Pool on Ethereum](https://app.uniswap.org/explore/tokens/ethereum/0x09395a2A58DB45db0da254c7EAa5AC469D8bDc85) +- [Unsiwap Pool on Base](https://app.uniswap.org/explore/tokens/base/0x858c50c3af1913b0e849afdb74617388a1a5340d) + +## 3. Expansion into Decentralised RPCs + +This vision was announced at the end of 2023 but really came to fruition in 2024. We expanded our network capabilities by introducing support for Remote Procedure Call (RPC) services. This was the first step of expanding away from just a data indexer to a major decentralised infrastructure network, allowing us to support a more accessible, interoperable, and developer-friendly web3 ecosystem. + +Now serving RPC requests on 20+ networks, [get your decentralised RPCs from the SubQuery Network today](https://subquery.network/rpc/list/). + +### 4\. Launching Artificial Intelligence Tools + +SubQuery took its first steps into the AI space by launching decentralised AI inference model hosting on the SubQuery Network plus a new developer SDK called the AI App Framework. This massively expands the tools and services that we can offer to web3 builders across, all under one roof. + +The AI App Framework allows you to build, deploy, and run production AI apps on the SubQuery Network in a trusted and decentralised environment. AI apps are self-contained and easily scalable AI agents that you can use to power your intelligent applications. They are sandboxed to a trusted runner and can be easily distributed and scaled horizontally across the SubQuery Network. + +[Start building AI Apps today!](https://academy.subquery.network/ai/welcome.html) + +## 5. SubQuery Rebranding + +As we expanded into the Artificial Intelligence space, we felt a new look was warranted to match our new pursuit. So we rebranded to a complete new look with sleek chromatic details and a flower/root narrative. + +The flower and root theme symbolises SubQuery’s commitment to fostering innovation and growth within the blockchain community. The roots represent the deep, stable, and reliable infrastructure that SubQuery provides, while the flowers symbolise the diverse and vibrant dApps that developers can create with the help of this infrastructure. + +[Check out the new look](https://subquery.network/). + +## Looking Ahead to 2025 + +While 2024 was full of exciting milestones, we know this is just the beginning. With a stronger community, enhanced technology, and bold new goals, we’re ready to scale even greater heights in 2025. With our most recent [2024 roadmap](https://blog.subquery.network/subquery-releases-network-roadmap-for-2024/?lng=en) almost fully accomplished, stay tuned for a new version packed with ambitious plans. + +Thank you to everyone—developers, partners, and community members—who helped make this year possible. + +Here’s to many more firsts ahead! \ No newline at end of file diff --git a/docs/bg/subquery_network/about.md b/docs/bg/subquery_network/about.md new file mode 100644 index 00000000000..1699165773b --- /dev/null +++ b/docs/bg/subquery_network/about.md @@ -0,0 +1,47 @@ +# About Us + +Our mission is to innovate Web3 infrastructure so builders can decentralise the next generation of applications - without compromise. + +Pioneering fast, flexible, and scalable decentralised infrastructure, we power Web3's transition to an open, efficient and user-centric future.Join us on our journey to build the future of web3 infrastructure. + +[Join our Discord Community](https://discord.com/invite/subquery) + +## Core team + +SubQuery has a deep bench of highly skilled talent of engineers, customer service, and operations personnel.Headquartered in Singapore, we have key representation in New Zealand, Lisbon, and Sydney. + +### Ian He - CTO and Co-Founder + +Ian forged his interest in blockchain during his tenure as the Technical Team Lead for Centrality where he led the development of core components of CENNZnet. Ian also led a team that won 2nd place in the world's first Substrate/Polkadot Hackathon in 2019. Prior to this, Ian obtained significant experience working on large-scale infrastructure working for Alipay and Yihaodian.com. + +### Scott Twiname - Principal Dev of SDK + +Scott has a large wealth of experience in blockchain development. He started out learning about blockchain in his own time and eventually got the opportunity to apply his knowledge as a senior developer at Sylo. He has worked on all facets of blockchain development from smart contracts, dapps, decentralised technologies and wallet integration for various networks including Bitcoin, Ethereum, Tezos and CENNZnet. + +### Marta Adamczyk - Head of Business Development + +Marta is a huge tech advocate, Web3 enthusiast and IT-meetup addict. She helps SubQuery customers develop and scale their projects by delivering technical consultancy, developer-oriented content and technical education. Former product evangelist, frontend developer, digital marketer, educator and sales manager with corporate and start-up experience. + +### Brittany Seales - Head of Marketing + +Brittany has a background in chemistry but since then she became the closest point of contact with SubQuery customers and helped ensure that every SubQuery customer gets an excellent on-boarding experience. Naturally Brittany is heavily integrated with the community and content marketing and has since taken over this area. Sadly, no amount of interaction with successful blockchain projects has give her the ability to pick a winning NFT! + +### James Bayly - Advisor + +Well-versed across the business, from product engineering to being the face of SubQuery, James is also a serial entrepreneur leading several tech companies. When he’s not in Berlin sipping cocktails, you’ll find him hiking up the Routeburn Track in New Zealand. + +## Our Manifesto + +In the new era of Web3, true power isn't bought – it's built with innovation and vision. +We are SubQuery, not just a company, but a revolution. Our mission: to lead the charge in decentralising the future. +We're pioneering an infrastructure that's fast, flexible, scalable – ready to power tomorrow's Web3 world. Crafting an open, efficient, and user-centric digital landscape. +For the visionaries, the forward-thinkers, the builders of tomorrow – SubQuery is your platform. +Join us in this journey. With SubQuery, it's not just about building for today, but architecting a decentralised, inclusive future. Let's shape the future of Web3, together. + +## About SubQuery + +SubQuery Network is innovating in web3 infrastructure with tools that empower builders to decentralise without compromise. SubQuery’s infrastructure network offers everything from data indexers, RPCs and AI agents - all fully decentralised and production ready. + +Our fast, flexible, and open data indexer supercharges thousands of dApps on nearly 300 networks. Our Sharded Data Node will provide breakthroughs in the RPC industry and our AI App framework makes building AI apps easier than ever before. We pioneer the web3 revolution for visionaries and forward-thinkers. We’re not just a company — we’re a movement driving an inclusive and decentralised web3 era, together. + +[Linktree](https://linktr.ee/subquerynetwork) | [Website](https://subquery.network) | [Discord](https://discord.com/invite/subquery) | [Telegram](https://t.me/subquerynetworkcommunity) | [Twitter](https://twitter.com/subquerynetwork) | [Blog](https://blog.subquery.network/?lng=en) | [Medium](https://medium.com/@subquery) | [LinkedIn](https://www.linkedin.com/company/subquery) | [YouTube](https://www.youtube.com/c/SubQueryNetwork) \ No newline at end of file diff --git a/docs/bg/subquery_network/community.md b/docs/bg/subquery_network/community.md new file mode 100644 index 00000000000..59c4aaeb078 --- /dev/null +++ b/docs/bg/subquery_network/community.md @@ -0,0 +1,178 @@ +# SubQuery Network Community + +The key focus of the [SubQuery Foundation](./governance/foundation.md) and community is to ensure that there is enough support that anyone, from an expert blockchain team to a new hobbyist developer, can build their own Project. Together we can pave the way to a more decentralised future! + +## Connecting with others + +Discord is our main community for talking about SubQuery and learning more. You can join with [this link here](https://discord.com/invite/subquery). People most interested in the SubQuery Network will want to join `#network-general`, and Indexers or Delegators should join `#network-indexer-chat` or `#network-delegator-chat` respectively. + +When the conversation is deeper and requires more thought, we move the conversation to [our Forum](https://forum.subquery.network/). Here you will find longer topics, a history of all announcements to Network, and deeper conversation about the direction of the network. Feel free to join and start posting at [forum.subquery.network](https://forum.subquery.network/)! + +### Join the Node Operator community + +If you're a Node Operator on the Network, we strongly suggest that you keep up with the latest news, announcements, and tips by joining the following Discord channels: + +- `#network-announcements` +- `#network-general` +- `#network-services-release` +- `#network-indexer-announcements` +- `#network-indexer-general` + +## Contributing to Codebases + +SubQuery is open source and open to the community, if you want to contribute (e.g. add a feature, fix a bug, suggest an improvement, or even just fix a typo in our documentation), please review our [contributing guide](../miscellaneous/contributing.md). + +The following codebases are where you can find code for all the contracts, applications, and backend SubQuery projects. We're looking forward to seeing your contributions! + +### `network-app` + +dApp for indexers, consumers and delegators interact with SubQuery Network. + + + +### `network-airdrop-app` + +dApp for users to interact with the SubQuery airdrop contract. + + + +### `network-contracts` + +Contracts for SubQuery Network. + + + +You can find smart contract addresses for all network contracts here in [GitHub](https://github.com/subquery/network-contracts/blob/develop/publish/mainnet.json) + +### `network-app-backend` + +SubQuery project for the backend of the SubQuery App. + + + +### `network-airdrop-app-backend` + +SubQuery project for the backend of the SubQuery Airdrop App. + + + +### `network-swap-app-backend` + +SubQuery project for the backend of the SubQuery Swap App. + + + +### `network-indexer-services` + +Services that Indexers run to connect and serve data to the SubQuery Network. + + + +### `network-clients` + +Client SDKs for SubQuery Network. + + + +### `subquery-component-library` + +React UI component library for SubQuery dApps. + + + +## Community Tools + +There are a number of community built tools that you can use to help your SubQuery Network experience. Feel free to contribute your own. + +:::warning +Please note that none of these tools have been endorsed by the SubQuery team and descriptions have been written by third parties. This section is open for contribution by all. + +Please research and use at your own risk +::: + +### SQTScan + +[SQTScan](https://sqtscan.com/?ref=blog.subquery.network) is a ***community-owned application*** designed specifically to help expert users such as Node Operators and Delegators to gain a deeper understanding of historical rewards on the SubQuery Network and optimise their participation. + +SQT Scan helps expert users (Node Operators and Delegators) with: + +1. **Education:** Understand how their rewards are calculated and how they should make decisions +2. **Compare Opportunities:** Decide which projects to deploy based on historical rewards +3. **Compare Others:** Compare their APY with other Node Operators, overall and by project, to see how they're performing relatively +4. **APY Maximisation:** Identify ways to increase their APY + +If you would like to add your support, suggest improvements or new features, or even contribute code, it is welcomed! + +Links + +- [SQTSCan](https://sqtscan.com) +- [Github](https://github.com/HuberTRoy/subquery-sqtscan) + +### Indexer Monitoring Tools (by web3cdn.network) + +Five products: +1. **Toolkit:** A toolkit contains everything you need to index, monitor and properly access from any device +2. **Telegram Uptime Bot:** Eagle Eye is a bot which will provide you live updates in Telegram on the uptime of your indexer +3. **UpdateHunter** +4. **Snapshots** +5. **Snapshots Toolkit** + +Toolkit Features: + +- Extended monitoring of all indexer parameters, sync time, balances, issues. Metrics also support Alerting rules +- Flags problems that have arisen through monitoring and help you to not miss rewards. +- Makes your indexer and infrastructure secure +- Ease of updating without the risk of changing important parameters +- Secured access to dangerous zone with your own VPN, Access from mobile devices to monitoring, and internal services in any time. +- Very easy installation and user error protection + +Eagle Eye Telegram Bot Notifications: + +- Provide reports on your indexer's uptime - help you to know about an errors in advance and not lose funds. +- If your indexer is offline +- If your project is somehow unavailable +- If you do not have enough funds +- If your certificate is about to expire +- And more + +UpdateHunter: + + - A tool that notifies you when a project is updated or a new project is created, providing complete documentation to enable fast and secure upgrades. + - It scans the blockchain and alerts an indexer via a Telegram channel about updates, automati­cally generating instructions and SQL queries. + - The bot integrates with GitHub, posting documentation updates to a public repository. + + Snapshots: + + - Service generates daily snapshots for all active projects + - This service is ideal if your indexer: + - Is newly deployed and you want to avoid ~1 month of downtime for project synchronization + - Has experienced data loss (corrupted disk, hardware failures, or software issues) + + Snapshots Toolkit: + + - Open Source toolkit for an own snapshot generator. With this repository indexer can generate its own snapshots. + +Links + +- [Toolkit Github](https://toolkit.subquery.dev/) +- [Eagle Eye Telegram Bot](https://eagleeye.subquery.dev/) +- [UpdateHunter](https://eagleeye.subquery.dev/updates) +- [Snapshots](https://snapshots.subquery.dev/) +- [Snapshots Toolkit](https://snapshots.subquery.dev/toolkit) + +### Kepler Network Dashboard (by DappLooker) + +To monitor the progress and performance of the Kepler Network, DappLooker has created a dashboard that displays the following key metrics: + +- Active Indexers / Delegators: The number of Indexers and Delegators who are actively participating in the Kepler Network. +- Weekly Indexer Stake / Delegation: The amount of kSQT that Indexers and Delegators have staked on the Kepler Network in the past week. +- Weekly Rewards: The amount of kSQT that Indexers have earned as rewards for serving data requests on the Kepler Network in the past week. +- Stake Distribution: The distribution of kSQT stakes between Indexers and Delegators on the Kepler Network. + +To make the data more accessible and user-friendly, DappLooker has also made the SubQuery Kepler data publicly available for everyone. This means that anyone can create custom dashboards tailored to their needs using the indexed data from the Kepler Network. + +Links + +- [Dashboard](https://dapplooker.com/dashboard/subquery-kepler-network-dashboard-577) +- [Indexed Dataset](https://analytics.dapplooker.com/browse/2/schema/subquery_kepler) +- [Announcement Article](https://blog.dapplooker.com/dapplooker-integrates-subquery-kepler-network-to-provide-analytics-and-dashboard-solution-to-web3-fb0c5aeea899) diff --git a/docs/bg/subquery_network/faq.md b/docs/bg/subquery_network/faq.md new file mode 100644 index 00000000000..a298d22efe5 --- /dev/null +++ b/docs/bg/subquery_network/faq.md @@ -0,0 +1,78 @@ +# Frequently Asked Questions + +FAQs for specific network participants: + +- [Node Operators](./node_operators/setup/faq.md) +- [Consumers](./consumers/faq.md) + +## Proof-of-indexing + +[Proof Of Index](./introduction/proof-of-index.md) + +## How do you ensure indexed data accuracy? + +Ensured by [Proof Of Index](./introduction/proof-of-index.md) + +## Are there a list of RPC providers that can provide support for \_\_\_ chain? + +SubQuery Network is decentralised, so we can't say what individual node operators would decide to serve you, nor can we say what infrastructure the node operators use and where it is hosted + +## What is the integration and deployment timeline for RPCs? + +SubQuery team can enable the RPC in a few days depending on how long an archive node on your network would take to sync. + +## Where is your/provider's infra hosted? + +Depends on the provider, SubQuery don't dictate this. But SubQuery gateway encourages competition to provide high performance, low latency, and geographically decentralised services. Most providers are running on their own bare metal for cost considerations + +## Is there a testnet environment? + +Yes, be sure to check https://dev.thechaindata.com/ + +## Is there a meaning behind SubQuery's name? + +The name "SubQuery" refers to its function in the blockchain ecosystem. A subquery is essentially a query within another query, allowing users to access data more efficiently. It is a powerful tool for indexing and querying blockchain data. + +## What was the first network that SubQuery first supported? + +SubQuery initially supported the Polkadot network, focusing on indexing and querying data for the Polkadot and its parachains. + +## How many networks do SubQuery support now? + +As of now, SubQuery supports multiple networks, including Polkadot, Kusama, Ethereum, and many others, expanding its reach to a wide array of blockchain ecosystems. + +## How does SubQuery improve blockchain data access? + +SubQuery enhances blockchain data access by providing an indexing layer that aggregates and organizes data from blockchain networks. This allows developers and applications to quickly retrieve and interact with data in a structured and efficient manner. + +## How does SubQuery differ from traditional block explorers? + +Traditional block explorers allow users to explore blockchain data in a static, non-queryable format. SubQuery, on the other hand, provides dynamic and customizable data querying, giving developers the ability to filter, process, and retrieve data in real-time for their applications. + +## What programming languages does SubQuery support? + +SubQuery primarily supports JavaScript and TypeScript for building queries and processing data. Developers can use these languages to define the structure and logic for data retrieval from supported networks. + +## Is SubQuery open-source? + +Yes, SubQuery is open-source. It encourages developers to contribute to its growth and use its tools to build decentralized applications (dApps) more efficiently. The source code is available on GitHub. + +## What are the main use cases for SubQuery? + +SubQuery is used for various purposes, such as: + +- Building decentralized applications (dApps) that need to access blockchain data. +- Indexing and querying blockchain data for analysis and reporting. +- Creating custom data solutions for blockchain ecosystems and decentralized finance (DeFi) platforms. + +## Can I deploy SubQuery on my own infrastructure? + +Yes, SubQuery can be deployed on your own infrastructure, whether on-premise or in the cloud. It offers flexibility to users who want complete control over their indexing and querying solutions. + +## How does SubQuery handle data updates and changes? + +SubQuery continuously updates its data by monitoring blockchain events in real-time. This ensures that the indexed data is always up to date, and any changes to the blockchain are reflected immediately in the data queries. + +## How can I get started with SubQuery? + +To get started with SubQuery, you can visit their official documentation, which provides step-by-step guides on setting up a project, writing queries, and deploying them on supported networks. The community also offers support through forums and Discord. diff --git a/docs/bg/subquery_network/infra-changes.md b/docs/bg/subquery_network/infra-changes.md new file mode 100644 index 00000000000..b30b5fa306d --- /dev/null +++ b/docs/bg/subquery_network/infra-changes.md @@ -0,0 +1,109 @@ +# Redefining Web3: SubQuery Network’s Bold Infrastructure Evolution + +Back in December 2023, we announced the evolution of SubQuery, in which we aim to transition from simply indexing web3 data to pioneering a complete web3 infrastructure revolution. + +Over the last year, as we’ve been building out our data indexing service and network, we realised our network is in a prime position to address broader centralisation issues throughout the web3 infrastructure landscape. + +Our mission has expanded, and so has the opportunity space we’re going to be working in. + +Read on to learn about the challenges we’re taking on and the next steps we’re taking to play a bigger role in decentralising the future. + +### The Web3 Infrastructure Landscape + +Web3 middleware services like indexers, RPCs, oracles and storage services are pivotal in blockchain dApp development. In fact, the utilisation of these middleware services is what sets apart successful, large-scale, production dApps - they accelerate performance and can scale to thousands of users, while providing a superior developer experience to bring in more users, TVL, and value. Indexers and RPCs shoulder the heavy lifting, standing as mission-critical services that underpin the functionality and efficiency of web3 applications. + +![](https://lh7-us.googleusercontent.com/2lbQyLR4fxrgV2dTqljyFV6bECXrfq3anA2k_qM6gJuWdSN01dHrVjIFU6OZeFXXJv57dwaXNQ6_lKdGtLK9YDWr0EdS7yDDv0BwZfFXT_j6aw-iu7bDxIS5ZkgliPD2mY_l5kbJXGKEqI6OWuZIEwk) + +**The current segregated web3 infrastructure landscape** + +Data indexers (like SubQuery) speed up data retrieval, enhancing performance and response times for users. They also simplify data by transforming raw blockchain information into more digestible formats, facilitating efficient development and a smooth user experience. + +Meanwhile, RPCs are pivotal for communication between blockchain nodes and external entities, facilitating data retrieval, smart contract interactions, and transaction submissions. Under the hood of your favourite dApp, tens of requests are passing through RPC providers to query and submit transactions to the network. + +While these middleware services are integral to a successful dApp, there is a significant issue that needs to be addressed. + +### Web3’s Dirty Little Secret + +There is a hidden truth behind the mask of “decentralisation” most of these middleware services wear. The reality is that many leading dApps have a significant reliance on centralised middleware components. This centralisation poses a substantial threat to the envisioned unstoppability of a web3 future, at any given moment, a single entity can undermine supposedly decentralised applications. + +Nowhere is this more apparent with RPC providers, and to a lesser extent, data indexers. These crucial services distinguish the scalable, reliable, and polished dApps from rudimentary applications that go without. But due to historical challenges in the process of decentralisation, for a long time, this has been a compromise most apps have accepted. + +The call for decentralised alternatives to these pivotal middleware services is essential for the foundation of the next generation of dApps to build upon. We need to decentralise these services, without compromise. + +### SubQuery Network Evolution Revealed + +At the start we set out to create a viable decentralised solution to the data indexing problem. + +Web3 developers face great difficulties aggregating and organising data to power dApps, and SubQuery has helped thousands of developers building the world's best and biggest networks, dApps, and analytics tools by providing fast and performant data indexing. + +In 2022 we launched Kepler Network, a pre-mainnet release that enabled us to bootstrap the network sustainably by bringing onboard proficient indexers and projects. The success of Kepler lead to the realisation that the ecosystem we’ve built could bring benefits for more than just decentralised data indexing, but for middleware infrastructure as a whole. The key components of the network we have built and deployed - reward and pricing rails, service verification tools, and dispute resolution processes - are valuable for others verticals. + +Knowing that the SubQuery Network could give our existing community of top node runners a solution to trustlessly receive rewards for running data indexing infrastructure, why couldn’t it work for those other services, for other parts of the dApp tech stack? + +We realised the full potential of the SubQuery Network mainnet should not be limited to just data indexing; its fundamental contracts, tools, and reward flows enable it to be so much more. By harnessing the power of the existing participants and mechanisms, the SubQuery Network is ready to extend to various infrastructure verticals. It dawned on us that there is a massive opportunity ahead of us when we think holistically about the entire developer experience. + +> With the launch of mainnet, the SubQuery Network will emerge as a solution to _decentralise everything_, revolutionising the entire developer experience in web3. + +![](https://lh7-us.googleusercontent.com/fXK85pf2n1zTFAsbxyhYKk4I_negGP3mNvXP_vE-_k-ppDlNQeCUPc-iKG7b2HjaeBaisWhkdDqPL8SoQb0QHW6eHI4-5Bra1GK7hrfIhzx9SW1SWgVJ9Nces5Vfza3fwYNug_nduW_8HJ-XB8eZwig) + +**The vision for SubQuery Network to encompass key web3 infrastructure components in a completely decentralised manner** + +### Starting with RPCs + +Our next step that we have completed is to decentralise the biggest infrastructure component for dApps - _Remote Procedure Call_ or RPC services. + +RPC services are still the main interface to the blockchain, under the hood of your favourite dApp, dozens of requests are passing through RPC providers to query and submit transactions to the network. They are the most critical part of the ecosystem, when one has an outage, [the effects reverberate across the industry](https://decrypt.co/47846/ethereum-backbone-infura-suffers-major-damage?ref=blog.subquery.network). + +Since SubQuery relies on performant and scalable RPCs to maximise our indexing speed, we already work extremely closely with RPC providers. On our quest to index over [115+ chains and counting](https://subquery.network/networks?ref=blog.subquery.network), we’ve discovered that the RPC ecosystem is very fractured: some ecosystems have excellent support, and some don’t, and that makes delivering an excellent indexing experience across all chains difficult. + +Across many smaller emergent networks, amateur RPC services operate to provide RPCs to various developers building on the network. These RPCs are usually run (at a loss) by the core network foundation team, and perhaps a collection of validators (for staking advertising purposes). Unfortunately for cost reasons, these RPCs are usually heavily pruned and rate limited, and have no upsell options for unrestricted access. As a result, dApp developers will often run a private RPC endpoint for their own use. This is expensive, frustrating, poses high barriers to entry, and results in no redundancy for dApp developers. + +For more established networks, one or more commercial providers may come and offer a freemium service, where there is a free plan/public endpoint, and a paid upsell to higher scale access. This serves dApp developers well, but the law of economies of scale dictate that networks tend towards a small number of hyperscale RPC providers who centralise the network and cause major outages that affect thousands of dApps when they go offline. They also extract huge economic value from a network and send that directly to big private cloud companies and VCs. + +We have built an alternative to these two dangerous equilibriums, and help decentralise everything.The SubQuery Network provides an open market for both data indexers and RPC providers and their consumers that: + +- Maintains low barriers of entry: Any node operator can join as a provider for any service on any network. +- Incentivises performance and cost: Node operators are automatically rewarded with requests based on these metrics, driving these values across the network. +- Encourages constant expansion to new chains: Node operators are free to onboard new chains and projects for first mover advantage, constantly expanding the network. + +### Enhancing RPCs - SubQuery’s Data Node + +The performance limitations of data indexers and many other applications have long been limited by the RPC endpoint. Developers have long focussed on building nodes to ensure efficient validation to ensure the safety of the network. As a result of this sacrifice, RPCs are extremely costly and they’re not at all optimised for querying. + +This is compounded by the rise of L2 chains where, with higher throughput, the query performance and cost are major outstanding issues to address. With limited querying capabilities, many don’t support complex querying languages or operations, making it inefficient to retrieve specific data. + +We have delivered the SubQuery Data Node, an enhanced and heavily-forked RPC node that is perfectly optimised for querying, especially on endpoints like `eth_getLog`, and the ability to filter transactions in a single API call. + +The Data Node is open source, allowing people to contribute, extend, or fork the implementation in any way. It supports leading layer-2s and other EVM networks initially, and they are optimised to run on the SubQuery Network in a decentralised way. + +Working together, the SubQuery Indexer and SubQuery Data Node provides the most performant indexing performance possible and in a completely decentralised way thanks to the SubQuery Network. + +Our node runners are able to run these data nodes on the network, bringing powerful and cost-effective RPC access to all, cementing SubQuery’s position as the fastest decentralised data indexer in web3. + +### Democratising RPCs - SubQuery’s Sharded Data Node + +In the final stage of our RPC journey, SubQuery will work to democratise RPCs (and solve [EIP-4444](https://eips.ethereum.org/EIPS/eip-4444?ref=blog.subquery.network)) in the process by delivering the Sharded Data Node, which will make RPCs cheaper to run and operate by node providers. + +In the last few months we’ve spoken with many RPC providers in the ecosystem. In many networks (in particular Cosmos), small scale RPC services operate to provide RPCs to various developers building on the network. Unfortunately for cost reasons, these RPCs are usually heavily pruned and rate limited and have no upsell options for unrestricted access. + +One of the key reasons for this is the sheer size of the node - an Ethereum archive requires about ~12 TB on Geth, an Osmosis archive is at least the same. This is an incredible cost that limits these nodes to large centralised infrastructure providers. + +SubQuery recognises that in order to decentralised RPCs correctly, you need to be able to make running these nodes easier and more accessible to everyday users. Currently the storage is made smaller by “pruning” data, which is intentionally discarding older information while cryptographically confirming that the recent data that is valid. This works fine for writing transactions, but means that indexers and other services are unable to query old data. + +SubQuery will extend its Data Node to support sharding, that is making each Data Node smaller by splitting up block ranges between node operators. Since SubQuery’s Data Node only runs within the boundaries of a specific block range, it does not need to constantly sync new data, allowing it to optimise further for query performance rather than validation and verification. + +The SubQuery Sharded node won’t just shard historical data, but also shard the historical state within the node. By itself, this won’t change much, but these sharded nodes will be optimised to run on the network, and the network will be designed to combine all these shards to expose a single unified endpoint that appears to cover the entire historical state of the chain. Developers will benefit from the entire historical state of the given network, and node operators will benefit from significantly lower running costs, creating a more cost efficient network. + +This is a revolutionary step forward for the RPC industry, and a potential solution to one of the great challenges facing older and larger blockchains with their state bloat size. This solution has the potential to help scale Ethereum, solve [EIP-4444](https://eips.ethereum.org/EIPS/eip-4444?ref=blog.subquery.network), and greatly support proliferation of Layer-2’s and rollups, while further democratising and decentralising the SubQuery Network. + +### Summary + +The future of SubQuery is not simply indexing web3 data, but pioneering a complete web3 infrastructure revolution. web3 middleware services like indexers and RPC providers are pivotal in blockchain dApp development, but there is a hidden truth behind the mask of “decentralisation” most of these middleware services wear. The reality is a significant reliance on centralised middleware components, which poses a substantial threat to the envisioned unstoppability of a web3 future. + +Our mission has expanded, and so has the opportunity space we’re going to be working in. We need to decentralise these services, without compromise. We’ve already delivered breakthroughs in decentralised data indexing, but our next steps will focus on enhancing the performance of RPCs with the SubQuery Data Node, and then to bring RPCs to the masses, with SubQuery’s Sharded Data Nodes. These steps together, will help unlock the next level of performance increases in web3. + +No other team today is better equipped at working to provide a holistic approach to solving this problem. In summary, our vision goes beyond data indexing; it's about revolutionising how data and infrastructure services are organised and accessed. + +Pioneering fast, flexible, and scalable decentralised infrastructure, we will help power web3's transition to an open, efficient and user-centric future. Join us in this journey. With SubQuery, it's not just about building for today, but architecting a decentralised, inclusive future. + +_Let's shape the future of web3, together._ \ No newline at end of file diff --git a/docs/bg/subquery_network/welcome.md b/docs/bg/subquery_network/welcome.md new file mode 100644 index 00000000000..53c14ae9c38 --- /dev/null +++ b/docs/bg/subquery_network/welcome.md @@ -0,0 +1,283 @@ +--- +footer: false +lastUpdated: false +contributors: false +editLink: false +photoSwipe: false +--- + + +
+
+
+ SubQuery Network + + The SubQuery Network is the most scalable, reliable, and unified data infrastructure network. 1,000s of decentralised Indexers and RPC providers simplify the data layer for a myriad of applications and use cases. + +
+
+
+ +
+
+ + + One network, all your web3 data needs + +
+ +
+ + {{ item.title }} + {{ item.subtitle }} + + {{ content }} + + + + + + +
+ +
+ Anyone can participate + + There’s a role for everyone in the network, from highly technical + developers to those with some experience and blockchain beginners. Find + out how you can participate and be rewarded. + +
+
+ + {{ anyone.name }} + + {{ anyone.description }} + + + + +
+
+ + +
+ Get Started with the Network Today + Our decentralised network is live and vibrant +
+ + + {{ item.title }} + + {{ item.desc }} + + + +
+
+ + +
+
+ + diff --git a/docs/de/subquery_network/2024.md b/docs/de/subquery_network/2024.md new file mode 100644 index 00000000000..cea4a68d051 --- /dev/null +++ b/docs/de/subquery_network/2024.md @@ -0,0 +1,62 @@ +# 2024 in Review: SubQuery’s Top 5 Milestones + +As we look back on 2024, we’re proud to call it a major “year of firsts” for us here at SubQuery. This year was filled with groundbreaking achievements, major launches, and remarkable community growth. The year has flown by but it also feels so long ago that we had our TGE, CEX Listing and SubQuery Network mainnet launch - all on the same day! + +Let’s celebrate some of the key milestones that made 2024 unforgettable. + +## 1. Mainnet Launch + +After an extremely successful Public Sale on 30 January 2024, selling out of SubQuery’s native token (SQT) in less than 2 hours, we worked very hard to launch the SubQuery Network mainnet on 23 February 2024. Powered by SQT and launched on Base, immediately users could consume and/or index data from over 150 networks ([now over 270 networks](https://subquery.network/networks)). + +Almost 1 year on and we have: + +- 46 globally distributed and highly skilled Node Operators servicing the network +- More than 330 million SQT staked and delegated in the Network +- Serving more than 50 million RPC requests every day +- An overall average APY of 22.28% and much higher for Node Operators (94.66%) + +## 2. SQT Token Generation Event + +Combined with the Mainnet launch, we ambitiously chose to do our TGE and day one CEX listing with Bybit on the same day (23 February 2024) as well. Das SubQuery-Token (SQT) ist als Utility-Token konzipiert, das das SubQuery-Netzwerk antreibt, einen Anreiz zur Teilnahme bietet und als Tauschmittel für Transaktionen innerhalb des SubQuery-Netzwerks dient. Consumers of data commit SQT in exchange for RPC queries or indexed data from our globally distributed Node Operators. + +Today, you can acquire SQT through any of these centralised exchange: + +- [Bybit](https://www.bybit.com/en/trade/spot/SQT/USDT) +- [Gate.io](https://www.gate.io/trade/SQT_USDT) +- [Crypto.com](https://crypto.com/exchange/trade/SQT_USD) +- [MEXC](https://www.mexc.com/exchange/SQT_USDT) + +SQT is on a number of DEX Pools however most liquidity is on Uniswap. + +- [Uniswap Pool on Ethereum](https://app.uniswap.org/explore/tokens/ethereum/0x09395a2A58DB45db0da254c7EAa5AC469D8bDc85) +- [Unsiwap Pool on Base](https://app.uniswap.org/explore/tokens/base/0x858c50c3af1913b0e849afdb74617388a1a5340d) + +## 3. Expansion into Decentralised RPCs + +This vision was announced at the end of 2023 but really came to fruition in 2024. We expanded our network capabilities by introducing support for Remote Procedure Call (RPC) services. This was the first step of expanding away from just a data indexer to a major decentralised infrastructure network, allowing us to support a more accessible, interoperable, and developer-friendly web3 ecosystem. + +Now serving RPC requests on 20+ networks, [get your decentralised RPCs from the SubQuery Network today](https://subquery.network/rpc/list/). + +### 4\. Launching Artificial Intelligence Tools + +SubQuery took its first steps into the AI space by launching decentralised AI inference model hosting on the SubQuery Network plus a new developer SDK called the AI App Framework. This massively expands the tools and services that we can offer to web3 builders across, all under one roof. + +The AI App Framework allows you to build, deploy, and run production AI apps on the SubQuery Network in a trusted and decentralised environment. AI apps are self-contained and easily scalable AI agents that you can use to power your intelligent applications. They are sandboxed to a trusted runner and can be easily distributed and scaled horizontally across the SubQuery Network. + +[Start building AI Apps today!](https://academy.subquery.network/ai/welcome.html) + +## 5. SubQuery Rebranding + +As we expanded into the Artificial Intelligence space, we felt a new look was warranted to match our new pursuit. So we rebranded to a complete new look with sleek chromatic details and a flower/root narrative. + +The flower and root theme symbolises SubQuery’s commitment to fostering innovation and growth within the blockchain community. The roots represent the deep, stable, and reliable infrastructure that SubQuery provides, while the flowers symbolise the diverse and vibrant dApps that developers can create with the help of this infrastructure. + +[Check out the new look](https://subquery.network/). + +## Looking Ahead to 2025 + +While 2024 was full of exciting milestones, we know this is just the beginning. With a stronger community, enhanced technology, and bold new goals, we’re ready to scale even greater heights in 2025. With our most recent [2024 roadmap](https://blog.subquery.network/subquery-releases-network-roadmap-for-2024/?lng=en) almost fully accomplished, stay tuned for a new version packed with ambitious plans. + +Thank you to everyone—developers, partners, and community members—who helped make this year possible. + +Here’s to many more firsts ahead! \ No newline at end of file diff --git a/docs/de/subquery_network/about.md b/docs/de/subquery_network/about.md new file mode 100644 index 00000000000..1699165773b --- /dev/null +++ b/docs/de/subquery_network/about.md @@ -0,0 +1,47 @@ +# About Us + +Our mission is to innovate Web3 infrastructure so builders can decentralise the next generation of applications - without compromise. + +Pioneering fast, flexible, and scalable decentralised infrastructure, we power Web3's transition to an open, efficient and user-centric future.Join us on our journey to build the future of web3 infrastructure. + +[Join our Discord Community](https://discord.com/invite/subquery) + +## Core team + +SubQuery has a deep bench of highly skilled talent of engineers, customer service, and operations personnel.Headquartered in Singapore, we have key representation in New Zealand, Lisbon, and Sydney. + +### Ian He - CTO and Co-Founder + +Ian forged his interest in blockchain during his tenure as the Technical Team Lead for Centrality where he led the development of core components of CENNZnet. Ian also led a team that won 2nd place in the world's first Substrate/Polkadot Hackathon in 2019. Prior to this, Ian obtained significant experience working on large-scale infrastructure working for Alipay and Yihaodian.com. + +### Scott Twiname - Principal Dev of SDK + +Scott has a large wealth of experience in blockchain development. He started out learning about blockchain in his own time and eventually got the opportunity to apply his knowledge as a senior developer at Sylo. He has worked on all facets of blockchain development from smart contracts, dapps, decentralised technologies and wallet integration for various networks including Bitcoin, Ethereum, Tezos and CENNZnet. + +### Marta Adamczyk - Head of Business Development + +Marta is a huge tech advocate, Web3 enthusiast and IT-meetup addict. She helps SubQuery customers develop and scale their projects by delivering technical consultancy, developer-oriented content and technical education. Former product evangelist, frontend developer, digital marketer, educator and sales manager with corporate and start-up experience. + +### Brittany Seales - Head of Marketing + +Brittany has a background in chemistry but since then she became the closest point of contact with SubQuery customers and helped ensure that every SubQuery customer gets an excellent on-boarding experience. Naturally Brittany is heavily integrated with the community and content marketing and has since taken over this area. Sadly, no amount of interaction with successful blockchain projects has give her the ability to pick a winning NFT! + +### James Bayly - Advisor + +Well-versed across the business, from product engineering to being the face of SubQuery, James is also a serial entrepreneur leading several tech companies. When he’s not in Berlin sipping cocktails, you’ll find him hiking up the Routeburn Track in New Zealand. + +## Our Manifesto + +In the new era of Web3, true power isn't bought – it's built with innovation and vision. +We are SubQuery, not just a company, but a revolution. Our mission: to lead the charge in decentralising the future. +We're pioneering an infrastructure that's fast, flexible, scalable – ready to power tomorrow's Web3 world. Crafting an open, efficient, and user-centric digital landscape. +For the visionaries, the forward-thinkers, the builders of tomorrow – SubQuery is your platform. +Join us in this journey. With SubQuery, it's not just about building for today, but architecting a decentralised, inclusive future. Let's shape the future of Web3, together. + +## About SubQuery + +SubQuery Network is innovating in web3 infrastructure with tools that empower builders to decentralise without compromise. SubQuery’s infrastructure network offers everything from data indexers, RPCs and AI agents - all fully decentralised and production ready. + +Our fast, flexible, and open data indexer supercharges thousands of dApps on nearly 300 networks. Our Sharded Data Node will provide breakthroughs in the RPC industry and our AI App framework makes building AI apps easier than ever before. We pioneer the web3 revolution for visionaries and forward-thinkers. We’re not just a company — we’re a movement driving an inclusive and decentralised web3 era, together. + +[Linktree](https://linktr.ee/subquerynetwork) | [Website](https://subquery.network) | [Discord](https://discord.com/invite/subquery) | [Telegram](https://t.me/subquerynetworkcommunity) | [Twitter](https://twitter.com/subquerynetwork) | [Blog](https://blog.subquery.network/?lng=en) | [Medium](https://medium.com/@subquery) | [LinkedIn](https://www.linkedin.com/company/subquery) | [YouTube](https://www.youtube.com/c/SubQueryNetwork) \ No newline at end of file diff --git a/docs/de/subquery_network/community.md b/docs/de/subquery_network/community.md new file mode 100644 index 00000000000..59c4aaeb078 --- /dev/null +++ b/docs/de/subquery_network/community.md @@ -0,0 +1,178 @@ +# SubQuery Network Community + +The key focus of the [SubQuery Foundation](./governance/foundation.md) and community is to ensure that there is enough support that anyone, from an expert blockchain team to a new hobbyist developer, can build their own Project. Together we can pave the way to a more decentralised future! + +## Connecting with others + +Discord is our main community for talking about SubQuery and learning more. You can join with [this link here](https://discord.com/invite/subquery). People most interested in the SubQuery Network will want to join `#network-general`, and Indexers or Delegators should join `#network-indexer-chat` or `#network-delegator-chat` respectively. + +When the conversation is deeper and requires more thought, we move the conversation to [our Forum](https://forum.subquery.network/). Here you will find longer topics, a history of all announcements to Network, and deeper conversation about the direction of the network. Feel free to join and start posting at [forum.subquery.network](https://forum.subquery.network/)! + +### Join the Node Operator community + +If you're a Node Operator on the Network, we strongly suggest that you keep up with the latest news, announcements, and tips by joining the following Discord channels: + +- `#network-announcements` +- `#network-general` +- `#network-services-release` +- `#network-indexer-announcements` +- `#network-indexer-general` + +## Contributing to Codebases + +SubQuery is open source and open to the community, if you want to contribute (e.g. add a feature, fix a bug, suggest an improvement, or even just fix a typo in our documentation), please review our [contributing guide](../miscellaneous/contributing.md). + +The following codebases are where you can find code for all the contracts, applications, and backend SubQuery projects. We're looking forward to seeing your contributions! + +### `network-app` + +dApp for indexers, consumers and delegators interact with SubQuery Network. + + + +### `network-airdrop-app` + +dApp for users to interact with the SubQuery airdrop contract. + + + +### `network-contracts` + +Contracts for SubQuery Network. + + + +You can find smart contract addresses for all network contracts here in [GitHub](https://github.com/subquery/network-contracts/blob/develop/publish/mainnet.json) + +### `network-app-backend` + +SubQuery project for the backend of the SubQuery App. + + + +### `network-airdrop-app-backend` + +SubQuery project for the backend of the SubQuery Airdrop App. + + + +### `network-swap-app-backend` + +SubQuery project for the backend of the SubQuery Swap App. + + + +### `network-indexer-services` + +Services that Indexers run to connect and serve data to the SubQuery Network. + + + +### `network-clients` + +Client SDKs for SubQuery Network. + + + +### `subquery-component-library` + +React UI component library for SubQuery dApps. + + + +## Community Tools + +There are a number of community built tools that you can use to help your SubQuery Network experience. Feel free to contribute your own. + +:::warning +Please note that none of these tools have been endorsed by the SubQuery team and descriptions have been written by third parties. This section is open for contribution by all. + +Please research and use at your own risk +::: + +### SQTScan + +[SQTScan](https://sqtscan.com/?ref=blog.subquery.network) is a ***community-owned application*** designed specifically to help expert users such as Node Operators and Delegators to gain a deeper understanding of historical rewards on the SubQuery Network and optimise their participation. + +SQT Scan helps expert users (Node Operators and Delegators) with: + +1. **Education:** Understand how their rewards are calculated and how they should make decisions +2. **Compare Opportunities:** Decide which projects to deploy based on historical rewards +3. **Compare Others:** Compare their APY with other Node Operators, overall and by project, to see how they're performing relatively +4. **APY Maximisation:** Identify ways to increase their APY + +If you would like to add your support, suggest improvements or new features, or even contribute code, it is welcomed! + +Links + +- [SQTSCan](https://sqtscan.com) +- [Github](https://github.com/HuberTRoy/subquery-sqtscan) + +### Indexer Monitoring Tools (by web3cdn.network) + +Five products: +1. **Toolkit:** A toolkit contains everything you need to index, monitor and properly access from any device +2. **Telegram Uptime Bot:** Eagle Eye is a bot which will provide you live updates in Telegram on the uptime of your indexer +3. **UpdateHunter** +4. **Snapshots** +5. **Snapshots Toolkit** + +Toolkit Features: + +- Extended monitoring of all indexer parameters, sync time, balances, issues. Metrics also support Alerting rules +- Flags problems that have arisen through monitoring and help you to not miss rewards. +- Makes your indexer and infrastructure secure +- Ease of updating without the risk of changing important parameters +- Secured access to dangerous zone with your own VPN, Access from mobile devices to monitoring, and internal services in any time. +- Very easy installation and user error protection + +Eagle Eye Telegram Bot Notifications: + +- Provide reports on your indexer's uptime - help you to know about an errors in advance and not lose funds. +- If your indexer is offline +- If your project is somehow unavailable +- If you do not have enough funds +- If your certificate is about to expire +- And more + +UpdateHunter: + + - A tool that notifies you when a project is updated or a new project is created, providing complete documentation to enable fast and secure upgrades. + - It scans the blockchain and alerts an indexer via a Telegram channel about updates, automati­cally generating instructions and SQL queries. + - The bot integrates with GitHub, posting documentation updates to a public repository. + + Snapshots: + + - Service generates daily snapshots for all active projects + - This service is ideal if your indexer: + - Is newly deployed and you want to avoid ~1 month of downtime for project synchronization + - Has experienced data loss (corrupted disk, hardware failures, or software issues) + + Snapshots Toolkit: + + - Open Source toolkit for an own snapshot generator. With this repository indexer can generate its own snapshots. + +Links + +- [Toolkit Github](https://toolkit.subquery.dev/) +- [Eagle Eye Telegram Bot](https://eagleeye.subquery.dev/) +- [UpdateHunter](https://eagleeye.subquery.dev/updates) +- [Snapshots](https://snapshots.subquery.dev/) +- [Snapshots Toolkit](https://snapshots.subquery.dev/toolkit) + +### Kepler Network Dashboard (by DappLooker) + +To monitor the progress and performance of the Kepler Network, DappLooker has created a dashboard that displays the following key metrics: + +- Active Indexers / Delegators: The number of Indexers and Delegators who are actively participating in the Kepler Network. +- Weekly Indexer Stake / Delegation: The amount of kSQT that Indexers and Delegators have staked on the Kepler Network in the past week. +- Weekly Rewards: The amount of kSQT that Indexers have earned as rewards for serving data requests on the Kepler Network in the past week. +- Stake Distribution: The distribution of kSQT stakes between Indexers and Delegators on the Kepler Network. + +To make the data more accessible and user-friendly, DappLooker has also made the SubQuery Kepler data publicly available for everyone. This means that anyone can create custom dashboards tailored to their needs using the indexed data from the Kepler Network. + +Links + +- [Dashboard](https://dapplooker.com/dashboard/subquery-kepler-network-dashboard-577) +- [Indexed Dataset](https://analytics.dapplooker.com/browse/2/schema/subquery_kepler) +- [Announcement Article](https://blog.dapplooker.com/dapplooker-integrates-subquery-kepler-network-to-provide-analytics-and-dashboard-solution-to-web3-fb0c5aeea899) diff --git a/docs/de/subquery_network/faq.md b/docs/de/subquery_network/faq.md new file mode 100644 index 00000000000..a298d22efe5 --- /dev/null +++ b/docs/de/subquery_network/faq.md @@ -0,0 +1,78 @@ +# Frequently Asked Questions + +FAQs for specific network participants: + +- [Node Operators](./node_operators/setup/faq.md) +- [Consumers](./consumers/faq.md) + +## Proof-of-indexing + +[Proof Of Index](./introduction/proof-of-index.md) + +## How do you ensure indexed data accuracy? + +Ensured by [Proof Of Index](./introduction/proof-of-index.md) + +## Are there a list of RPC providers that can provide support for \_\_\_ chain? + +SubQuery Network is decentralised, so we can't say what individual node operators would decide to serve you, nor can we say what infrastructure the node operators use and where it is hosted + +## What is the integration and deployment timeline for RPCs? + +SubQuery team can enable the RPC in a few days depending on how long an archive node on your network would take to sync. + +## Where is your/provider's infra hosted? + +Depends on the provider, SubQuery don't dictate this. But SubQuery gateway encourages competition to provide high performance, low latency, and geographically decentralised services. Most providers are running on their own bare metal for cost considerations + +## Is there a testnet environment? + +Yes, be sure to check https://dev.thechaindata.com/ + +## Is there a meaning behind SubQuery's name? + +The name "SubQuery" refers to its function in the blockchain ecosystem. A subquery is essentially a query within another query, allowing users to access data more efficiently. It is a powerful tool for indexing and querying blockchain data. + +## What was the first network that SubQuery first supported? + +SubQuery initially supported the Polkadot network, focusing on indexing and querying data for the Polkadot and its parachains. + +## How many networks do SubQuery support now? + +As of now, SubQuery supports multiple networks, including Polkadot, Kusama, Ethereum, and many others, expanding its reach to a wide array of blockchain ecosystems. + +## How does SubQuery improve blockchain data access? + +SubQuery enhances blockchain data access by providing an indexing layer that aggregates and organizes data from blockchain networks. This allows developers and applications to quickly retrieve and interact with data in a structured and efficient manner. + +## How does SubQuery differ from traditional block explorers? + +Traditional block explorers allow users to explore blockchain data in a static, non-queryable format. SubQuery, on the other hand, provides dynamic and customizable data querying, giving developers the ability to filter, process, and retrieve data in real-time for their applications. + +## What programming languages does SubQuery support? + +SubQuery primarily supports JavaScript and TypeScript for building queries and processing data. Developers can use these languages to define the structure and logic for data retrieval from supported networks. + +## Is SubQuery open-source? + +Yes, SubQuery is open-source. It encourages developers to contribute to its growth and use its tools to build decentralized applications (dApps) more efficiently. The source code is available on GitHub. + +## What are the main use cases for SubQuery? + +SubQuery is used for various purposes, such as: + +- Building decentralized applications (dApps) that need to access blockchain data. +- Indexing and querying blockchain data for analysis and reporting. +- Creating custom data solutions for blockchain ecosystems and decentralized finance (DeFi) platforms. + +## Can I deploy SubQuery on my own infrastructure? + +Yes, SubQuery can be deployed on your own infrastructure, whether on-premise or in the cloud. It offers flexibility to users who want complete control over their indexing and querying solutions. + +## How does SubQuery handle data updates and changes? + +SubQuery continuously updates its data by monitoring blockchain events in real-time. This ensures that the indexed data is always up to date, and any changes to the blockchain are reflected immediately in the data queries. + +## How can I get started with SubQuery? + +To get started with SubQuery, you can visit their official documentation, which provides step-by-step guides on setting up a project, writing queries, and deploying them on supported networks. The community also offers support through forums and Discord. diff --git a/docs/de/subquery_network/infra-changes.md b/docs/de/subquery_network/infra-changes.md new file mode 100644 index 00000000000..b30b5fa306d --- /dev/null +++ b/docs/de/subquery_network/infra-changes.md @@ -0,0 +1,109 @@ +# Redefining Web3: SubQuery Network’s Bold Infrastructure Evolution + +Back in December 2023, we announced the evolution of SubQuery, in which we aim to transition from simply indexing web3 data to pioneering a complete web3 infrastructure revolution. + +Over the last year, as we’ve been building out our data indexing service and network, we realised our network is in a prime position to address broader centralisation issues throughout the web3 infrastructure landscape. + +Our mission has expanded, and so has the opportunity space we’re going to be working in. + +Read on to learn about the challenges we’re taking on and the next steps we’re taking to play a bigger role in decentralising the future. + +### The Web3 Infrastructure Landscape + +Web3 middleware services like indexers, RPCs, oracles and storage services are pivotal in blockchain dApp development. In fact, the utilisation of these middleware services is what sets apart successful, large-scale, production dApps - they accelerate performance and can scale to thousands of users, while providing a superior developer experience to bring in more users, TVL, and value. Indexers and RPCs shoulder the heavy lifting, standing as mission-critical services that underpin the functionality and efficiency of web3 applications. + +![](https://lh7-us.googleusercontent.com/2lbQyLR4fxrgV2dTqljyFV6bECXrfq3anA2k_qM6gJuWdSN01dHrVjIFU6OZeFXXJv57dwaXNQ6_lKdGtLK9YDWr0EdS7yDDv0BwZfFXT_j6aw-iu7bDxIS5ZkgliPD2mY_l5kbJXGKEqI6OWuZIEwk) + +**The current segregated web3 infrastructure landscape** + +Data indexers (like SubQuery) speed up data retrieval, enhancing performance and response times for users. They also simplify data by transforming raw blockchain information into more digestible formats, facilitating efficient development and a smooth user experience. + +Meanwhile, RPCs are pivotal for communication between blockchain nodes and external entities, facilitating data retrieval, smart contract interactions, and transaction submissions. Under the hood of your favourite dApp, tens of requests are passing through RPC providers to query and submit transactions to the network. + +While these middleware services are integral to a successful dApp, there is a significant issue that needs to be addressed. + +### Web3’s Dirty Little Secret + +There is a hidden truth behind the mask of “decentralisation” most of these middleware services wear. The reality is that many leading dApps have a significant reliance on centralised middleware components. This centralisation poses a substantial threat to the envisioned unstoppability of a web3 future, at any given moment, a single entity can undermine supposedly decentralised applications. + +Nowhere is this more apparent with RPC providers, and to a lesser extent, data indexers. These crucial services distinguish the scalable, reliable, and polished dApps from rudimentary applications that go without. But due to historical challenges in the process of decentralisation, for a long time, this has been a compromise most apps have accepted. + +The call for decentralised alternatives to these pivotal middleware services is essential for the foundation of the next generation of dApps to build upon. We need to decentralise these services, without compromise. + +### SubQuery Network Evolution Revealed + +At the start we set out to create a viable decentralised solution to the data indexing problem. + +Web3 developers face great difficulties aggregating and organising data to power dApps, and SubQuery has helped thousands of developers building the world's best and biggest networks, dApps, and analytics tools by providing fast and performant data indexing. + +In 2022 we launched Kepler Network, a pre-mainnet release that enabled us to bootstrap the network sustainably by bringing onboard proficient indexers and projects. The success of Kepler lead to the realisation that the ecosystem we’ve built could bring benefits for more than just decentralised data indexing, but for middleware infrastructure as a whole. The key components of the network we have built and deployed - reward and pricing rails, service verification tools, and dispute resolution processes - are valuable for others verticals. + +Knowing that the SubQuery Network could give our existing community of top node runners a solution to trustlessly receive rewards for running data indexing infrastructure, why couldn’t it work for those other services, for other parts of the dApp tech stack? + +We realised the full potential of the SubQuery Network mainnet should not be limited to just data indexing; its fundamental contracts, tools, and reward flows enable it to be so much more. By harnessing the power of the existing participants and mechanisms, the SubQuery Network is ready to extend to various infrastructure verticals. It dawned on us that there is a massive opportunity ahead of us when we think holistically about the entire developer experience. + +> With the launch of mainnet, the SubQuery Network will emerge as a solution to _decentralise everything_, revolutionising the entire developer experience in web3. + +![](https://lh7-us.googleusercontent.com/fXK85pf2n1zTFAsbxyhYKk4I_negGP3mNvXP_vE-_k-ppDlNQeCUPc-iKG7b2HjaeBaisWhkdDqPL8SoQb0QHW6eHI4-5Bra1GK7hrfIhzx9SW1SWgVJ9Nces5Vfza3fwYNug_nduW_8HJ-XB8eZwig) + +**The vision for SubQuery Network to encompass key web3 infrastructure components in a completely decentralised manner** + +### Starting with RPCs + +Our next step that we have completed is to decentralise the biggest infrastructure component for dApps - _Remote Procedure Call_ or RPC services. + +RPC services are still the main interface to the blockchain, under the hood of your favourite dApp, dozens of requests are passing through RPC providers to query and submit transactions to the network. They are the most critical part of the ecosystem, when one has an outage, [the effects reverberate across the industry](https://decrypt.co/47846/ethereum-backbone-infura-suffers-major-damage?ref=blog.subquery.network). + +Since SubQuery relies on performant and scalable RPCs to maximise our indexing speed, we already work extremely closely with RPC providers. On our quest to index over [115+ chains and counting](https://subquery.network/networks?ref=blog.subquery.network), we’ve discovered that the RPC ecosystem is very fractured: some ecosystems have excellent support, and some don’t, and that makes delivering an excellent indexing experience across all chains difficult. + +Across many smaller emergent networks, amateur RPC services operate to provide RPCs to various developers building on the network. These RPCs are usually run (at a loss) by the core network foundation team, and perhaps a collection of validators (for staking advertising purposes). Unfortunately for cost reasons, these RPCs are usually heavily pruned and rate limited, and have no upsell options for unrestricted access. As a result, dApp developers will often run a private RPC endpoint for their own use. This is expensive, frustrating, poses high barriers to entry, and results in no redundancy for dApp developers. + +For more established networks, one or more commercial providers may come and offer a freemium service, where there is a free plan/public endpoint, and a paid upsell to higher scale access. This serves dApp developers well, but the law of economies of scale dictate that networks tend towards a small number of hyperscale RPC providers who centralise the network and cause major outages that affect thousands of dApps when they go offline. They also extract huge economic value from a network and send that directly to big private cloud companies and VCs. + +We have built an alternative to these two dangerous equilibriums, and help decentralise everything.The SubQuery Network provides an open market for both data indexers and RPC providers and their consumers that: + +- Maintains low barriers of entry: Any node operator can join as a provider for any service on any network. +- Incentivises performance and cost: Node operators are automatically rewarded with requests based on these metrics, driving these values across the network. +- Encourages constant expansion to new chains: Node operators are free to onboard new chains and projects for first mover advantage, constantly expanding the network. + +### Enhancing RPCs - SubQuery’s Data Node + +The performance limitations of data indexers and many other applications have long been limited by the RPC endpoint. Developers have long focussed on building nodes to ensure efficient validation to ensure the safety of the network. As a result of this sacrifice, RPCs are extremely costly and they’re not at all optimised for querying. + +This is compounded by the rise of L2 chains where, with higher throughput, the query performance and cost are major outstanding issues to address. With limited querying capabilities, many don’t support complex querying languages or operations, making it inefficient to retrieve specific data. + +We have delivered the SubQuery Data Node, an enhanced and heavily-forked RPC node that is perfectly optimised for querying, especially on endpoints like `eth_getLog`, and the ability to filter transactions in a single API call. + +The Data Node is open source, allowing people to contribute, extend, or fork the implementation in any way. It supports leading layer-2s and other EVM networks initially, and they are optimised to run on the SubQuery Network in a decentralised way. + +Working together, the SubQuery Indexer and SubQuery Data Node provides the most performant indexing performance possible and in a completely decentralised way thanks to the SubQuery Network. + +Our node runners are able to run these data nodes on the network, bringing powerful and cost-effective RPC access to all, cementing SubQuery’s position as the fastest decentralised data indexer in web3. + +### Democratising RPCs - SubQuery’s Sharded Data Node + +In the final stage of our RPC journey, SubQuery will work to democratise RPCs (and solve [EIP-4444](https://eips.ethereum.org/EIPS/eip-4444?ref=blog.subquery.network)) in the process by delivering the Sharded Data Node, which will make RPCs cheaper to run and operate by node providers. + +In the last few months we’ve spoken with many RPC providers in the ecosystem. In many networks (in particular Cosmos), small scale RPC services operate to provide RPCs to various developers building on the network. Unfortunately for cost reasons, these RPCs are usually heavily pruned and rate limited and have no upsell options for unrestricted access. + +One of the key reasons for this is the sheer size of the node - an Ethereum archive requires about ~12 TB on Geth, an Osmosis archive is at least the same. This is an incredible cost that limits these nodes to large centralised infrastructure providers. + +SubQuery recognises that in order to decentralised RPCs correctly, you need to be able to make running these nodes easier and more accessible to everyday users. Currently the storage is made smaller by “pruning” data, which is intentionally discarding older information while cryptographically confirming that the recent data that is valid. This works fine for writing transactions, but means that indexers and other services are unable to query old data. + +SubQuery will extend its Data Node to support sharding, that is making each Data Node smaller by splitting up block ranges between node operators. Since SubQuery’s Data Node only runs within the boundaries of a specific block range, it does not need to constantly sync new data, allowing it to optimise further for query performance rather than validation and verification. + +The SubQuery Sharded node won’t just shard historical data, but also shard the historical state within the node. By itself, this won’t change much, but these sharded nodes will be optimised to run on the network, and the network will be designed to combine all these shards to expose a single unified endpoint that appears to cover the entire historical state of the chain. Developers will benefit from the entire historical state of the given network, and node operators will benefit from significantly lower running costs, creating a more cost efficient network. + +This is a revolutionary step forward for the RPC industry, and a potential solution to one of the great challenges facing older and larger blockchains with their state bloat size. This solution has the potential to help scale Ethereum, solve [EIP-4444](https://eips.ethereum.org/EIPS/eip-4444?ref=blog.subquery.network), and greatly support proliferation of Layer-2’s and rollups, while further democratising and decentralising the SubQuery Network. + +### Summary + +The future of SubQuery is not simply indexing web3 data, but pioneering a complete web3 infrastructure revolution. web3 middleware services like indexers and RPC providers are pivotal in blockchain dApp development, but there is a hidden truth behind the mask of “decentralisation” most of these middleware services wear. The reality is a significant reliance on centralised middleware components, which poses a substantial threat to the envisioned unstoppability of a web3 future. + +Our mission has expanded, and so has the opportunity space we’re going to be working in. We need to decentralise these services, without compromise. We’ve already delivered breakthroughs in decentralised data indexing, but our next steps will focus on enhancing the performance of RPCs with the SubQuery Data Node, and then to bring RPCs to the masses, with SubQuery’s Sharded Data Nodes. These steps together, will help unlock the next level of performance increases in web3. + +No other team today is better equipped at working to provide a holistic approach to solving this problem. In summary, our vision goes beyond data indexing; it's about revolutionising how data and infrastructure services are organised and accessed. + +Pioneering fast, flexible, and scalable decentralised infrastructure, we will help power web3's transition to an open, efficient and user-centric future. Join us in this journey. With SubQuery, it's not just about building for today, but architecting a decentralised, inclusive future. + +_Let's shape the future of web3, together._ \ No newline at end of file diff --git a/docs/de/subquery_network/welcome.md b/docs/de/subquery_network/welcome.md new file mode 100644 index 00000000000..53c14ae9c38 --- /dev/null +++ b/docs/de/subquery_network/welcome.md @@ -0,0 +1,283 @@ +--- +footer: false +lastUpdated: false +contributors: false +editLink: false +photoSwipe: false +--- + + +
+
+
+ SubQuery Network + + The SubQuery Network is the most scalable, reliable, and unified data infrastructure network. 1,000s of decentralised Indexers and RPC providers simplify the data layer for a myriad of applications and use cases. + +
+
+
+ +
+
+ + + One network, all your web3 data needs + +
+ +
+ + {{ item.title }} + {{ item.subtitle }} + + {{ content }} + + + + + + +
+ +
+ Anyone can participate + + There’s a role for everyone in the network, from highly technical + developers to those with some experience and blockchain beginners. Find + out how you can participate and be rewarded. + +
+
+ + {{ anyone.name }} + + {{ anyone.description }} + + + + +
+
+ + +
+ Get Started with the Network Today + Our decentralised network is live and vibrant +
+ + + {{ item.title }} + + {{ item.desc }} + + + +
+
+ + +
+
+ + diff --git a/docs/es/subquery_network/2024.md b/docs/es/subquery_network/2024.md new file mode 100644 index 00000000000..1fa294e025c --- /dev/null +++ b/docs/es/subquery_network/2024.md @@ -0,0 +1,62 @@ +# 2024 in Review: SubQuery’s Top 5 Milestones + +As we look back on 2024, we’re proud to call it a major “year of firsts” for us here at SubQuery. This year was filled with groundbreaking achievements, major launches, and remarkable community growth. The year has flown by but it also feels so long ago that we had our TGE, CEX Listing and SubQuery Network mainnet launch - all on the same day! + +Let’s celebrate some of the key milestones that made 2024 unforgettable. + +## 1. Mainnet Launch + +After an extremely successful Public Sale on 30 January 2024, selling out of SubQuery’s native token (SQT) in less than 2 hours, we worked very hard to launch the SubQuery Network mainnet on 23 February 2024. Powered by SQT and launched on Base, immediately users could consume and/or index data from over 150 networks ([now over 270 networks](https://subquery.network/networks)). + +Almost 1 year on and we have: + +- 46 globally distributed and highly skilled Node Operators servicing the network +- More than 330 million SQT staked and delegated in the Network +- Serving more than 50 million RPC requests every day +- An overall average APY of 22.28% and much higher for Node Operators (94.66%) + +## 2. SQT Token Generation Event + +Combined with the Mainnet launch, we ambitiously chose to do our TGE and day one CEX listing with Bybit on the same day (23 February 2024) as well. SubQuery Token (SQT) está diseñado como un token de utilidad que potencia la SubQuery Network, proporcionando un incentivo para la participación, así como servir como medio de intercambio para transacciones dentro de SubQuery Network. Consumers of data commit SQT in exchange for RPC queries or indexed data from our globally distributed Node Operators. + +Today, you can acquire SQT through any of these centralised exchange: + +- [Bybit](https://www.bybit.com/en/trade/spot/SQT/USDT) +- [Gate.io](https://www.gate.io/trade/SQT_USDT) +- [Crypto.com](https://crypto.com/exchange/trade/SQT_USD) +- [MEXC](https://www.mexc.com/exchange/SQT_USDT) + +SQT is on a number of DEX Pools however most liquidity is on Uniswap. + +- [Uniswap Pool on Ethereum](https://app.uniswap.org/explore/tokens/ethereum/0x09395a2A58DB45db0da254c7EAa5AC469D8bDc85) +- [Unsiwap Pool on Base](https://app.uniswap.org/explore/tokens/base/0x858c50c3af1913b0e849afdb74617388a1a5340d) + +## 3. Expansion into Decentralised RPCs + +This vision was announced at the end of 2023 but really came to fruition in 2024. We expanded our network capabilities by introducing support for Remote Procedure Call (RPC) services. This was the first step of expanding away from just a data indexer to a major decentralised infrastructure network, allowing us to support a more accessible, interoperable, and developer-friendly web3 ecosystem. + +Now serving RPC requests on 20+ networks, [get your decentralised RPCs from the SubQuery Network today](https://subquery.network/rpc/list/). + +### 4\. Launching Artificial Intelligence Tools + +SubQuery took its first steps into the AI space by launching decentralised AI inference model hosting on the SubQuery Network plus a new developer SDK called the AI App Framework. This massively expands the tools and services that we can offer to web3 builders across, all under one roof. + +The AI App Framework allows you to build, deploy, and run production AI apps on the SubQuery Network in a trusted and decentralised environment. AI apps are self-contained and easily scalable AI agents that you can use to power your intelligent applications. They are sandboxed to a trusted runner and can be easily distributed and scaled horizontally across the SubQuery Network. + +[Start building AI Apps today!](https://academy.subquery.network/ai/welcome.html) + +## 5. SubQuery Rebranding + +As we expanded into the Artificial Intelligence space, we felt a new look was warranted to match our new pursuit. So we rebranded to a complete new look with sleek chromatic details and a flower/root narrative. + +The flower and root theme symbolises SubQuery’s commitment to fostering innovation and growth within the blockchain community. The roots represent the deep, stable, and reliable infrastructure that SubQuery provides, while the flowers symbolise the diverse and vibrant dApps that developers can create with the help of this infrastructure. + +[Check out the new look](https://subquery.network/). + +## Looking Ahead to 2025 + +While 2024 was full of exciting milestones, we know this is just the beginning. With a stronger community, enhanced technology, and bold new goals, we’re ready to scale even greater heights in 2025. With our most recent [2024 roadmap](https://blog.subquery.network/subquery-releases-network-roadmap-for-2024/?lng=en) almost fully accomplished, stay tuned for a new version packed with ambitious plans. + +Thank you to everyone—developers, partners, and community members—who helped make this year possible. + +Here’s to many more firsts ahead! \ No newline at end of file diff --git a/docs/es/subquery_network/about.md b/docs/es/subquery_network/about.md new file mode 100644 index 00000000000..1699165773b --- /dev/null +++ b/docs/es/subquery_network/about.md @@ -0,0 +1,47 @@ +# About Us + +Our mission is to innovate Web3 infrastructure so builders can decentralise the next generation of applications - without compromise. + +Pioneering fast, flexible, and scalable decentralised infrastructure, we power Web3's transition to an open, efficient and user-centric future.Join us on our journey to build the future of web3 infrastructure. + +[Join our Discord Community](https://discord.com/invite/subquery) + +## Core team + +SubQuery has a deep bench of highly skilled talent of engineers, customer service, and operations personnel.Headquartered in Singapore, we have key representation in New Zealand, Lisbon, and Sydney. + +### Ian He - CTO and Co-Founder + +Ian forged his interest in blockchain during his tenure as the Technical Team Lead for Centrality where he led the development of core components of CENNZnet. Ian also led a team that won 2nd place in the world's first Substrate/Polkadot Hackathon in 2019. Prior to this, Ian obtained significant experience working on large-scale infrastructure working for Alipay and Yihaodian.com. + +### Scott Twiname - Principal Dev of SDK + +Scott has a large wealth of experience in blockchain development. He started out learning about blockchain in his own time and eventually got the opportunity to apply his knowledge as a senior developer at Sylo. He has worked on all facets of blockchain development from smart contracts, dapps, decentralised technologies and wallet integration for various networks including Bitcoin, Ethereum, Tezos and CENNZnet. + +### Marta Adamczyk - Head of Business Development + +Marta is a huge tech advocate, Web3 enthusiast and IT-meetup addict. She helps SubQuery customers develop and scale their projects by delivering technical consultancy, developer-oriented content and technical education. Former product evangelist, frontend developer, digital marketer, educator and sales manager with corporate and start-up experience. + +### Brittany Seales - Head of Marketing + +Brittany has a background in chemistry but since then she became the closest point of contact with SubQuery customers and helped ensure that every SubQuery customer gets an excellent on-boarding experience. Naturally Brittany is heavily integrated with the community and content marketing and has since taken over this area. Sadly, no amount of interaction with successful blockchain projects has give her the ability to pick a winning NFT! + +### James Bayly - Advisor + +Well-versed across the business, from product engineering to being the face of SubQuery, James is also a serial entrepreneur leading several tech companies. When he’s not in Berlin sipping cocktails, you’ll find him hiking up the Routeburn Track in New Zealand. + +## Our Manifesto + +In the new era of Web3, true power isn't bought – it's built with innovation and vision. +We are SubQuery, not just a company, but a revolution. Our mission: to lead the charge in decentralising the future. +We're pioneering an infrastructure that's fast, flexible, scalable – ready to power tomorrow's Web3 world. Crafting an open, efficient, and user-centric digital landscape. +For the visionaries, the forward-thinkers, the builders of tomorrow – SubQuery is your platform. +Join us in this journey. With SubQuery, it's not just about building for today, but architecting a decentralised, inclusive future. Let's shape the future of Web3, together. + +## About SubQuery + +SubQuery Network is innovating in web3 infrastructure with tools that empower builders to decentralise without compromise. SubQuery’s infrastructure network offers everything from data indexers, RPCs and AI agents - all fully decentralised and production ready. + +Our fast, flexible, and open data indexer supercharges thousands of dApps on nearly 300 networks. Our Sharded Data Node will provide breakthroughs in the RPC industry and our AI App framework makes building AI apps easier than ever before. We pioneer the web3 revolution for visionaries and forward-thinkers. We’re not just a company — we’re a movement driving an inclusive and decentralised web3 era, together. + +[Linktree](https://linktr.ee/subquerynetwork) | [Website](https://subquery.network) | [Discord](https://discord.com/invite/subquery) | [Telegram](https://t.me/subquerynetworkcommunity) | [Twitter](https://twitter.com/subquerynetwork) | [Blog](https://blog.subquery.network/?lng=en) | [Medium](https://medium.com/@subquery) | [LinkedIn](https://www.linkedin.com/company/subquery) | [YouTube](https://www.youtube.com/c/SubQueryNetwork) \ No newline at end of file diff --git a/docs/es/subquery_network/community.md b/docs/es/subquery_network/community.md new file mode 100644 index 00000000000..59c4aaeb078 --- /dev/null +++ b/docs/es/subquery_network/community.md @@ -0,0 +1,178 @@ +# SubQuery Network Community + +The key focus of the [SubQuery Foundation](./governance/foundation.md) and community is to ensure that there is enough support that anyone, from an expert blockchain team to a new hobbyist developer, can build their own Project. Together we can pave the way to a more decentralised future! + +## Connecting with others + +Discord is our main community for talking about SubQuery and learning more. You can join with [this link here](https://discord.com/invite/subquery). People most interested in the SubQuery Network will want to join `#network-general`, and Indexers or Delegators should join `#network-indexer-chat` or `#network-delegator-chat` respectively. + +When the conversation is deeper and requires more thought, we move the conversation to [our Forum](https://forum.subquery.network/). Here you will find longer topics, a history of all announcements to Network, and deeper conversation about the direction of the network. Feel free to join and start posting at [forum.subquery.network](https://forum.subquery.network/)! + +### Join the Node Operator community + +If you're a Node Operator on the Network, we strongly suggest that you keep up with the latest news, announcements, and tips by joining the following Discord channels: + +- `#network-announcements` +- `#network-general` +- `#network-services-release` +- `#network-indexer-announcements` +- `#network-indexer-general` + +## Contributing to Codebases + +SubQuery is open source and open to the community, if you want to contribute (e.g. add a feature, fix a bug, suggest an improvement, or even just fix a typo in our documentation), please review our [contributing guide](../miscellaneous/contributing.md). + +The following codebases are where you can find code for all the contracts, applications, and backend SubQuery projects. We're looking forward to seeing your contributions! + +### `network-app` + +dApp for indexers, consumers and delegators interact with SubQuery Network. + + + +### `network-airdrop-app` + +dApp for users to interact with the SubQuery airdrop contract. + + + +### `network-contracts` + +Contracts for SubQuery Network. + + + +You can find smart contract addresses for all network contracts here in [GitHub](https://github.com/subquery/network-contracts/blob/develop/publish/mainnet.json) + +### `network-app-backend` + +SubQuery project for the backend of the SubQuery App. + + + +### `network-airdrop-app-backend` + +SubQuery project for the backend of the SubQuery Airdrop App. + + + +### `network-swap-app-backend` + +SubQuery project for the backend of the SubQuery Swap App. + + + +### `network-indexer-services` + +Services that Indexers run to connect and serve data to the SubQuery Network. + + + +### `network-clients` + +Client SDKs for SubQuery Network. + + + +### `subquery-component-library` + +React UI component library for SubQuery dApps. + + + +## Community Tools + +There are a number of community built tools that you can use to help your SubQuery Network experience. Feel free to contribute your own. + +:::warning +Please note that none of these tools have been endorsed by the SubQuery team and descriptions have been written by third parties. This section is open for contribution by all. + +Please research and use at your own risk +::: + +### SQTScan + +[SQTScan](https://sqtscan.com/?ref=blog.subquery.network) is a ***community-owned application*** designed specifically to help expert users such as Node Operators and Delegators to gain a deeper understanding of historical rewards on the SubQuery Network and optimise their participation. + +SQT Scan helps expert users (Node Operators and Delegators) with: + +1. **Education:** Understand how their rewards are calculated and how they should make decisions +2. **Compare Opportunities:** Decide which projects to deploy based on historical rewards +3. **Compare Others:** Compare their APY with other Node Operators, overall and by project, to see how they're performing relatively +4. **APY Maximisation:** Identify ways to increase their APY + +If you would like to add your support, suggest improvements or new features, or even contribute code, it is welcomed! + +Links + +- [SQTSCan](https://sqtscan.com) +- [Github](https://github.com/HuberTRoy/subquery-sqtscan) + +### Indexer Monitoring Tools (by web3cdn.network) + +Five products: +1. **Toolkit:** A toolkit contains everything you need to index, monitor and properly access from any device +2. **Telegram Uptime Bot:** Eagle Eye is a bot which will provide you live updates in Telegram on the uptime of your indexer +3. **UpdateHunter** +4. **Snapshots** +5. **Snapshots Toolkit** + +Toolkit Features: + +- Extended monitoring of all indexer parameters, sync time, balances, issues. Metrics also support Alerting rules +- Flags problems that have arisen through monitoring and help you to not miss rewards. +- Makes your indexer and infrastructure secure +- Ease of updating without the risk of changing important parameters +- Secured access to dangerous zone with your own VPN, Access from mobile devices to monitoring, and internal services in any time. +- Very easy installation and user error protection + +Eagle Eye Telegram Bot Notifications: + +- Provide reports on your indexer's uptime - help you to know about an errors in advance and not lose funds. +- If your indexer is offline +- If your project is somehow unavailable +- If you do not have enough funds +- If your certificate is about to expire +- And more + +UpdateHunter: + + - A tool that notifies you when a project is updated or a new project is created, providing complete documentation to enable fast and secure upgrades. + - It scans the blockchain and alerts an indexer via a Telegram channel about updates, automati­cally generating instructions and SQL queries. + - The bot integrates with GitHub, posting documentation updates to a public repository. + + Snapshots: + + - Service generates daily snapshots for all active projects + - This service is ideal if your indexer: + - Is newly deployed and you want to avoid ~1 month of downtime for project synchronization + - Has experienced data loss (corrupted disk, hardware failures, or software issues) + + Snapshots Toolkit: + + - Open Source toolkit for an own snapshot generator. With this repository indexer can generate its own snapshots. + +Links + +- [Toolkit Github](https://toolkit.subquery.dev/) +- [Eagle Eye Telegram Bot](https://eagleeye.subquery.dev/) +- [UpdateHunter](https://eagleeye.subquery.dev/updates) +- [Snapshots](https://snapshots.subquery.dev/) +- [Snapshots Toolkit](https://snapshots.subquery.dev/toolkit) + +### Kepler Network Dashboard (by DappLooker) + +To monitor the progress and performance of the Kepler Network, DappLooker has created a dashboard that displays the following key metrics: + +- Active Indexers / Delegators: The number of Indexers and Delegators who are actively participating in the Kepler Network. +- Weekly Indexer Stake / Delegation: The amount of kSQT that Indexers and Delegators have staked on the Kepler Network in the past week. +- Weekly Rewards: The amount of kSQT that Indexers have earned as rewards for serving data requests on the Kepler Network in the past week. +- Stake Distribution: The distribution of kSQT stakes between Indexers and Delegators on the Kepler Network. + +To make the data more accessible and user-friendly, DappLooker has also made the SubQuery Kepler data publicly available for everyone. This means that anyone can create custom dashboards tailored to their needs using the indexed data from the Kepler Network. + +Links + +- [Dashboard](https://dapplooker.com/dashboard/subquery-kepler-network-dashboard-577) +- [Indexed Dataset](https://analytics.dapplooker.com/browse/2/schema/subquery_kepler) +- [Announcement Article](https://blog.dapplooker.com/dapplooker-integrates-subquery-kepler-network-to-provide-analytics-and-dashboard-solution-to-web3-fb0c5aeea899) diff --git a/docs/es/subquery_network/faq.md b/docs/es/subquery_network/faq.md new file mode 100644 index 00000000000..a298d22efe5 --- /dev/null +++ b/docs/es/subquery_network/faq.md @@ -0,0 +1,78 @@ +# Frequently Asked Questions + +FAQs for specific network participants: + +- [Node Operators](./node_operators/setup/faq.md) +- [Consumers](./consumers/faq.md) + +## Proof-of-indexing + +[Proof Of Index](./introduction/proof-of-index.md) + +## How do you ensure indexed data accuracy? + +Ensured by [Proof Of Index](./introduction/proof-of-index.md) + +## Are there a list of RPC providers that can provide support for \_\_\_ chain? + +SubQuery Network is decentralised, so we can't say what individual node operators would decide to serve you, nor can we say what infrastructure the node operators use and where it is hosted + +## What is the integration and deployment timeline for RPCs? + +SubQuery team can enable the RPC in a few days depending on how long an archive node on your network would take to sync. + +## Where is your/provider's infra hosted? + +Depends on the provider, SubQuery don't dictate this. But SubQuery gateway encourages competition to provide high performance, low latency, and geographically decentralised services. Most providers are running on their own bare metal for cost considerations + +## Is there a testnet environment? + +Yes, be sure to check https://dev.thechaindata.com/ + +## Is there a meaning behind SubQuery's name? + +The name "SubQuery" refers to its function in the blockchain ecosystem. A subquery is essentially a query within another query, allowing users to access data more efficiently. It is a powerful tool for indexing and querying blockchain data. + +## What was the first network that SubQuery first supported? + +SubQuery initially supported the Polkadot network, focusing on indexing and querying data for the Polkadot and its parachains. + +## How many networks do SubQuery support now? + +As of now, SubQuery supports multiple networks, including Polkadot, Kusama, Ethereum, and many others, expanding its reach to a wide array of blockchain ecosystems. + +## How does SubQuery improve blockchain data access? + +SubQuery enhances blockchain data access by providing an indexing layer that aggregates and organizes data from blockchain networks. This allows developers and applications to quickly retrieve and interact with data in a structured and efficient manner. + +## How does SubQuery differ from traditional block explorers? + +Traditional block explorers allow users to explore blockchain data in a static, non-queryable format. SubQuery, on the other hand, provides dynamic and customizable data querying, giving developers the ability to filter, process, and retrieve data in real-time for their applications. + +## What programming languages does SubQuery support? + +SubQuery primarily supports JavaScript and TypeScript for building queries and processing data. Developers can use these languages to define the structure and logic for data retrieval from supported networks. + +## Is SubQuery open-source? + +Yes, SubQuery is open-source. It encourages developers to contribute to its growth and use its tools to build decentralized applications (dApps) more efficiently. The source code is available on GitHub. + +## What are the main use cases for SubQuery? + +SubQuery is used for various purposes, such as: + +- Building decentralized applications (dApps) that need to access blockchain data. +- Indexing and querying blockchain data for analysis and reporting. +- Creating custom data solutions for blockchain ecosystems and decentralized finance (DeFi) platforms. + +## Can I deploy SubQuery on my own infrastructure? + +Yes, SubQuery can be deployed on your own infrastructure, whether on-premise or in the cloud. It offers flexibility to users who want complete control over their indexing and querying solutions. + +## How does SubQuery handle data updates and changes? + +SubQuery continuously updates its data by monitoring blockchain events in real-time. This ensures that the indexed data is always up to date, and any changes to the blockchain are reflected immediately in the data queries. + +## How can I get started with SubQuery? + +To get started with SubQuery, you can visit their official documentation, which provides step-by-step guides on setting up a project, writing queries, and deploying them on supported networks. The community also offers support through forums and Discord. diff --git a/docs/es/subquery_network/infra-changes.md b/docs/es/subquery_network/infra-changes.md new file mode 100644 index 00000000000..b30b5fa306d --- /dev/null +++ b/docs/es/subquery_network/infra-changes.md @@ -0,0 +1,109 @@ +# Redefining Web3: SubQuery Network’s Bold Infrastructure Evolution + +Back in December 2023, we announced the evolution of SubQuery, in which we aim to transition from simply indexing web3 data to pioneering a complete web3 infrastructure revolution. + +Over the last year, as we’ve been building out our data indexing service and network, we realised our network is in a prime position to address broader centralisation issues throughout the web3 infrastructure landscape. + +Our mission has expanded, and so has the opportunity space we’re going to be working in. + +Read on to learn about the challenges we’re taking on and the next steps we’re taking to play a bigger role in decentralising the future. + +### The Web3 Infrastructure Landscape + +Web3 middleware services like indexers, RPCs, oracles and storage services are pivotal in blockchain dApp development. In fact, the utilisation of these middleware services is what sets apart successful, large-scale, production dApps - they accelerate performance and can scale to thousands of users, while providing a superior developer experience to bring in more users, TVL, and value. Indexers and RPCs shoulder the heavy lifting, standing as mission-critical services that underpin the functionality and efficiency of web3 applications. + +![](https://lh7-us.googleusercontent.com/2lbQyLR4fxrgV2dTqljyFV6bECXrfq3anA2k_qM6gJuWdSN01dHrVjIFU6OZeFXXJv57dwaXNQ6_lKdGtLK9YDWr0EdS7yDDv0BwZfFXT_j6aw-iu7bDxIS5ZkgliPD2mY_l5kbJXGKEqI6OWuZIEwk) + +**The current segregated web3 infrastructure landscape** + +Data indexers (like SubQuery) speed up data retrieval, enhancing performance and response times for users. They also simplify data by transforming raw blockchain information into more digestible formats, facilitating efficient development and a smooth user experience. + +Meanwhile, RPCs are pivotal for communication between blockchain nodes and external entities, facilitating data retrieval, smart contract interactions, and transaction submissions. Under the hood of your favourite dApp, tens of requests are passing through RPC providers to query and submit transactions to the network. + +While these middleware services are integral to a successful dApp, there is a significant issue that needs to be addressed. + +### Web3’s Dirty Little Secret + +There is a hidden truth behind the mask of “decentralisation” most of these middleware services wear. The reality is that many leading dApps have a significant reliance on centralised middleware components. This centralisation poses a substantial threat to the envisioned unstoppability of a web3 future, at any given moment, a single entity can undermine supposedly decentralised applications. + +Nowhere is this more apparent with RPC providers, and to a lesser extent, data indexers. These crucial services distinguish the scalable, reliable, and polished dApps from rudimentary applications that go without. But due to historical challenges in the process of decentralisation, for a long time, this has been a compromise most apps have accepted. + +The call for decentralised alternatives to these pivotal middleware services is essential for the foundation of the next generation of dApps to build upon. We need to decentralise these services, without compromise. + +### SubQuery Network Evolution Revealed + +At the start we set out to create a viable decentralised solution to the data indexing problem. + +Web3 developers face great difficulties aggregating and organising data to power dApps, and SubQuery has helped thousands of developers building the world's best and biggest networks, dApps, and analytics tools by providing fast and performant data indexing. + +In 2022 we launched Kepler Network, a pre-mainnet release that enabled us to bootstrap the network sustainably by bringing onboard proficient indexers and projects. The success of Kepler lead to the realisation that the ecosystem we’ve built could bring benefits for more than just decentralised data indexing, but for middleware infrastructure as a whole. The key components of the network we have built and deployed - reward and pricing rails, service verification tools, and dispute resolution processes - are valuable for others verticals. + +Knowing that the SubQuery Network could give our existing community of top node runners a solution to trustlessly receive rewards for running data indexing infrastructure, why couldn’t it work for those other services, for other parts of the dApp tech stack? + +We realised the full potential of the SubQuery Network mainnet should not be limited to just data indexing; its fundamental contracts, tools, and reward flows enable it to be so much more. By harnessing the power of the existing participants and mechanisms, the SubQuery Network is ready to extend to various infrastructure verticals. It dawned on us that there is a massive opportunity ahead of us when we think holistically about the entire developer experience. + +> With the launch of mainnet, the SubQuery Network will emerge as a solution to _decentralise everything_, revolutionising the entire developer experience in web3. + +![](https://lh7-us.googleusercontent.com/fXK85pf2n1zTFAsbxyhYKk4I_negGP3mNvXP_vE-_k-ppDlNQeCUPc-iKG7b2HjaeBaisWhkdDqPL8SoQb0QHW6eHI4-5Bra1GK7hrfIhzx9SW1SWgVJ9Nces5Vfza3fwYNug_nduW_8HJ-XB8eZwig) + +**The vision for SubQuery Network to encompass key web3 infrastructure components in a completely decentralised manner** + +### Starting with RPCs + +Our next step that we have completed is to decentralise the biggest infrastructure component for dApps - _Remote Procedure Call_ or RPC services. + +RPC services are still the main interface to the blockchain, under the hood of your favourite dApp, dozens of requests are passing through RPC providers to query and submit transactions to the network. They are the most critical part of the ecosystem, when one has an outage, [the effects reverberate across the industry](https://decrypt.co/47846/ethereum-backbone-infura-suffers-major-damage?ref=blog.subquery.network). + +Since SubQuery relies on performant and scalable RPCs to maximise our indexing speed, we already work extremely closely with RPC providers. On our quest to index over [115+ chains and counting](https://subquery.network/networks?ref=blog.subquery.network), we’ve discovered that the RPC ecosystem is very fractured: some ecosystems have excellent support, and some don’t, and that makes delivering an excellent indexing experience across all chains difficult. + +Across many smaller emergent networks, amateur RPC services operate to provide RPCs to various developers building on the network. These RPCs are usually run (at a loss) by the core network foundation team, and perhaps a collection of validators (for staking advertising purposes). Unfortunately for cost reasons, these RPCs are usually heavily pruned and rate limited, and have no upsell options for unrestricted access. As a result, dApp developers will often run a private RPC endpoint for their own use. This is expensive, frustrating, poses high barriers to entry, and results in no redundancy for dApp developers. + +For more established networks, one or more commercial providers may come and offer a freemium service, where there is a free plan/public endpoint, and a paid upsell to higher scale access. This serves dApp developers well, but the law of economies of scale dictate that networks tend towards a small number of hyperscale RPC providers who centralise the network and cause major outages that affect thousands of dApps when they go offline. They also extract huge economic value from a network and send that directly to big private cloud companies and VCs. + +We have built an alternative to these two dangerous equilibriums, and help decentralise everything.The SubQuery Network provides an open market for both data indexers and RPC providers and their consumers that: + +- Maintains low barriers of entry: Any node operator can join as a provider for any service on any network. +- Incentivises performance and cost: Node operators are automatically rewarded with requests based on these metrics, driving these values across the network. +- Encourages constant expansion to new chains: Node operators are free to onboard new chains and projects for first mover advantage, constantly expanding the network. + +### Enhancing RPCs - SubQuery’s Data Node + +The performance limitations of data indexers and many other applications have long been limited by the RPC endpoint. Developers have long focussed on building nodes to ensure efficient validation to ensure the safety of the network. As a result of this sacrifice, RPCs are extremely costly and they’re not at all optimised for querying. + +This is compounded by the rise of L2 chains where, with higher throughput, the query performance and cost are major outstanding issues to address. With limited querying capabilities, many don’t support complex querying languages or operations, making it inefficient to retrieve specific data. + +We have delivered the SubQuery Data Node, an enhanced and heavily-forked RPC node that is perfectly optimised for querying, especially on endpoints like `eth_getLog`, and the ability to filter transactions in a single API call. + +The Data Node is open source, allowing people to contribute, extend, or fork the implementation in any way. It supports leading layer-2s and other EVM networks initially, and they are optimised to run on the SubQuery Network in a decentralised way. + +Working together, the SubQuery Indexer and SubQuery Data Node provides the most performant indexing performance possible and in a completely decentralised way thanks to the SubQuery Network. + +Our node runners are able to run these data nodes on the network, bringing powerful and cost-effective RPC access to all, cementing SubQuery’s position as the fastest decentralised data indexer in web3. + +### Democratising RPCs - SubQuery’s Sharded Data Node + +In the final stage of our RPC journey, SubQuery will work to democratise RPCs (and solve [EIP-4444](https://eips.ethereum.org/EIPS/eip-4444?ref=blog.subquery.network)) in the process by delivering the Sharded Data Node, which will make RPCs cheaper to run and operate by node providers. + +In the last few months we’ve spoken with many RPC providers in the ecosystem. In many networks (in particular Cosmos), small scale RPC services operate to provide RPCs to various developers building on the network. Unfortunately for cost reasons, these RPCs are usually heavily pruned and rate limited and have no upsell options for unrestricted access. + +One of the key reasons for this is the sheer size of the node - an Ethereum archive requires about ~12 TB on Geth, an Osmosis archive is at least the same. This is an incredible cost that limits these nodes to large centralised infrastructure providers. + +SubQuery recognises that in order to decentralised RPCs correctly, you need to be able to make running these nodes easier and more accessible to everyday users. Currently the storage is made smaller by “pruning” data, which is intentionally discarding older information while cryptographically confirming that the recent data that is valid. This works fine for writing transactions, but means that indexers and other services are unable to query old data. + +SubQuery will extend its Data Node to support sharding, that is making each Data Node smaller by splitting up block ranges between node operators. Since SubQuery’s Data Node only runs within the boundaries of a specific block range, it does not need to constantly sync new data, allowing it to optimise further for query performance rather than validation and verification. + +The SubQuery Sharded node won’t just shard historical data, but also shard the historical state within the node. By itself, this won’t change much, but these sharded nodes will be optimised to run on the network, and the network will be designed to combine all these shards to expose a single unified endpoint that appears to cover the entire historical state of the chain. Developers will benefit from the entire historical state of the given network, and node operators will benefit from significantly lower running costs, creating a more cost efficient network. + +This is a revolutionary step forward for the RPC industry, and a potential solution to one of the great challenges facing older and larger blockchains with their state bloat size. This solution has the potential to help scale Ethereum, solve [EIP-4444](https://eips.ethereum.org/EIPS/eip-4444?ref=blog.subquery.network), and greatly support proliferation of Layer-2’s and rollups, while further democratising and decentralising the SubQuery Network. + +### Summary + +The future of SubQuery is not simply indexing web3 data, but pioneering a complete web3 infrastructure revolution. web3 middleware services like indexers and RPC providers are pivotal in blockchain dApp development, but there is a hidden truth behind the mask of “decentralisation” most of these middleware services wear. The reality is a significant reliance on centralised middleware components, which poses a substantial threat to the envisioned unstoppability of a web3 future. + +Our mission has expanded, and so has the opportunity space we’re going to be working in. We need to decentralise these services, without compromise. We’ve already delivered breakthroughs in decentralised data indexing, but our next steps will focus on enhancing the performance of RPCs with the SubQuery Data Node, and then to bring RPCs to the masses, with SubQuery’s Sharded Data Nodes. These steps together, will help unlock the next level of performance increases in web3. + +No other team today is better equipped at working to provide a holistic approach to solving this problem. In summary, our vision goes beyond data indexing; it's about revolutionising how data and infrastructure services are organised and accessed. + +Pioneering fast, flexible, and scalable decentralised infrastructure, we will help power web3's transition to an open, efficient and user-centric future. Join us in this journey. With SubQuery, it's not just about building for today, but architecting a decentralised, inclusive future. + +_Let's shape the future of web3, together._ \ No newline at end of file diff --git a/docs/es/subquery_network/welcome.md b/docs/es/subquery_network/welcome.md new file mode 100644 index 00000000000..53c14ae9c38 --- /dev/null +++ b/docs/es/subquery_network/welcome.md @@ -0,0 +1,283 @@ +--- +footer: false +lastUpdated: false +contributors: false +editLink: false +photoSwipe: false +--- + + +
+
+
+ SubQuery Network + + The SubQuery Network is the most scalable, reliable, and unified data infrastructure network. 1,000s of decentralised Indexers and RPC providers simplify the data layer for a myriad of applications and use cases. + +
+
+
+ +
+
+ + + One network, all your web3 data needs + +
+ +
+ + {{ item.title }} + {{ item.subtitle }} + + {{ content }} + + + + + + +
+ +
+ Anyone can participate + + There’s a role for everyone in the network, from highly technical + developers to those with some experience and blockchain beginners. Find + out how you can participate and be rewarded. + +
+
+ + {{ anyone.name }} + + {{ anyone.description }} + + + + +
+
+ + +
+ Get Started with the Network Today + Our decentralised network is live and vibrant +
+ + + {{ item.title }} + + {{ item.desc }} + + + +
+
+ + +
+
+ + diff --git a/docs/fr/subquery_network/2024.md b/docs/fr/subquery_network/2024.md new file mode 100644 index 00000000000..412a1f34fc1 --- /dev/null +++ b/docs/fr/subquery_network/2024.md @@ -0,0 +1,62 @@ +# 2024 in Review: SubQuery’s Top 5 Milestones + +As we look back on 2024, we’re proud to call it a major “year of firsts” for us here at SubQuery. This year was filled with groundbreaking achievements, major launches, and remarkable community growth. The year has flown by but it also feels so long ago that we had our TGE, CEX Listing and SubQuery Network mainnet launch - all on the same day! + +Let’s celebrate some of the key milestones that made 2024 unforgettable. + +## 1. Mainnet Launch + +After an extremely successful Public Sale on 30 January 2024, selling out of SubQuery’s native token (SQT) in less than 2 hours, we worked very hard to launch the SubQuery Network mainnet on 23 February 2024. Powered by SQT and launched on Base, immediately users could consume and/or index data from over 150 networks ([now over 270 networks](https://subquery.network/networks)). + +Almost 1 year on and we have: + +- 46 globally distributed and highly skilled Node Operators servicing the network +- More than 330 million SQT staked and delegated in the Network +- Serving more than 50 million RPC requests every day +- An overall average APY of 22.28% and much higher for Node Operators (94.66%) + +## 2. SQT Token Generation Event + +Combined with the Mainnet launch, we ambitiously chose to do our TGE and day one CEX listing with Bybit on the same day (23 February 2024) as well. The SubQuery Token (SQT) is designed as a utility token that powers the SubQuery Network, providing an incentive for participation, as well as serving as a medium of exchange for transactions within the SubQuery Network. Consumers of data commit SQT in exchange for RPC queries or indexed data from our globally distributed Node Operators. + +Today, you can acquire SQT through any of these centralised exchange: + +- [Bybit](https://www.bybit.com/en/trade/spot/SQT/USDT) +- [Gate.io](https://www.gate.io/trade/SQT_USDT) +- [Crypto.com](https://crypto.com/exchange/trade/SQT_USD) +- [MEXC](https://www.mexc.com/exchange/SQT_USDT) + +SQT is on a number of DEX Pools however most liquidity is on Uniswap. + +- [Uniswap Pool on Ethereum](https://app.uniswap.org/explore/tokens/ethereum/0x09395a2A58DB45db0da254c7EAa5AC469D8bDc85) +- [Unsiwap Pool on Base](https://app.uniswap.org/explore/tokens/base/0x858c50c3af1913b0e849afdb74617388a1a5340d) + +## 3. Expansion into Decentralised RPCs + +This vision was announced at the end of 2023 but really came to fruition in 2024. We expanded our network capabilities by introducing support for Remote Procedure Call (RPC) services. This was the first step of expanding away from just a data indexer to a major decentralised infrastructure network, allowing us to support a more accessible, interoperable, and developer-friendly web3 ecosystem. + +Now serving RPC requests on 20+ networks, [get your decentralised RPCs from the SubQuery Network today](https://subquery.network/rpc/list/). + +### 4\. Launching Artificial Intelligence Tools + +SubQuery took its first steps into the AI space by launching decentralised AI inference model hosting on the SubQuery Network plus a new developer SDK called the AI App Framework. This massively expands the tools and services that we can offer to web3 builders across, all under one roof. + +The AI App Framework allows you to build, deploy, and run production AI apps on the SubQuery Network in a trusted and decentralised environment. AI apps are self-contained and easily scalable AI agents that you can use to power your intelligent applications. They are sandboxed to a trusted runner and can be easily distributed and scaled horizontally across the SubQuery Network. + +[Start building AI Apps today!](https://academy.subquery.network/ai/welcome.html) + +## 5. SubQuery Rebranding + +As we expanded into the Artificial Intelligence space, we felt a new look was warranted to match our new pursuit. So we rebranded to a complete new look with sleek chromatic details and a flower/root narrative. + +The flower and root theme symbolises SubQuery’s commitment to fostering innovation and growth within the blockchain community. The roots represent the deep, stable, and reliable infrastructure that SubQuery provides, while the flowers symbolise the diverse and vibrant dApps that developers can create with the help of this infrastructure. + +[Check out the new look](https://subquery.network/). + +## Looking Ahead to 2025 + +While 2024 was full of exciting milestones, we know this is just the beginning. With a stronger community, enhanced technology, and bold new goals, we’re ready to scale even greater heights in 2025. With our most recent [2024 roadmap](https://blog.subquery.network/subquery-releases-network-roadmap-for-2024/?lng=en) almost fully accomplished, stay tuned for a new version packed with ambitious plans. + +Thank you to everyone—developers, partners, and community members—who helped make this year possible. + +Here’s to many more firsts ahead! \ No newline at end of file diff --git a/docs/fr/subquery_network/about.md b/docs/fr/subquery_network/about.md new file mode 100644 index 00000000000..1699165773b --- /dev/null +++ b/docs/fr/subquery_network/about.md @@ -0,0 +1,47 @@ +# About Us + +Our mission is to innovate Web3 infrastructure so builders can decentralise the next generation of applications - without compromise. + +Pioneering fast, flexible, and scalable decentralised infrastructure, we power Web3's transition to an open, efficient and user-centric future.Join us on our journey to build the future of web3 infrastructure. + +[Join our Discord Community](https://discord.com/invite/subquery) + +## Core team + +SubQuery has a deep bench of highly skilled talent of engineers, customer service, and operations personnel.Headquartered in Singapore, we have key representation in New Zealand, Lisbon, and Sydney. + +### Ian He - CTO and Co-Founder + +Ian forged his interest in blockchain during his tenure as the Technical Team Lead for Centrality where he led the development of core components of CENNZnet. Ian also led a team that won 2nd place in the world's first Substrate/Polkadot Hackathon in 2019. Prior to this, Ian obtained significant experience working on large-scale infrastructure working for Alipay and Yihaodian.com. + +### Scott Twiname - Principal Dev of SDK + +Scott has a large wealth of experience in blockchain development. He started out learning about blockchain in his own time and eventually got the opportunity to apply his knowledge as a senior developer at Sylo. He has worked on all facets of blockchain development from smart contracts, dapps, decentralised technologies and wallet integration for various networks including Bitcoin, Ethereum, Tezos and CENNZnet. + +### Marta Adamczyk - Head of Business Development + +Marta is a huge tech advocate, Web3 enthusiast and IT-meetup addict. She helps SubQuery customers develop and scale their projects by delivering technical consultancy, developer-oriented content and technical education. Former product evangelist, frontend developer, digital marketer, educator and sales manager with corporate and start-up experience. + +### Brittany Seales - Head of Marketing + +Brittany has a background in chemistry but since then she became the closest point of contact with SubQuery customers and helped ensure that every SubQuery customer gets an excellent on-boarding experience. Naturally Brittany is heavily integrated with the community and content marketing and has since taken over this area. Sadly, no amount of interaction with successful blockchain projects has give her the ability to pick a winning NFT! + +### James Bayly - Advisor + +Well-versed across the business, from product engineering to being the face of SubQuery, James is also a serial entrepreneur leading several tech companies. When he’s not in Berlin sipping cocktails, you’ll find him hiking up the Routeburn Track in New Zealand. + +## Our Manifesto + +In the new era of Web3, true power isn't bought – it's built with innovation and vision. +We are SubQuery, not just a company, but a revolution. Our mission: to lead the charge in decentralising the future. +We're pioneering an infrastructure that's fast, flexible, scalable – ready to power tomorrow's Web3 world. Crafting an open, efficient, and user-centric digital landscape. +For the visionaries, the forward-thinkers, the builders of tomorrow – SubQuery is your platform. +Join us in this journey. With SubQuery, it's not just about building for today, but architecting a decentralised, inclusive future. Let's shape the future of Web3, together. + +## About SubQuery + +SubQuery Network is innovating in web3 infrastructure with tools that empower builders to decentralise without compromise. SubQuery’s infrastructure network offers everything from data indexers, RPCs and AI agents - all fully decentralised and production ready. + +Our fast, flexible, and open data indexer supercharges thousands of dApps on nearly 300 networks. Our Sharded Data Node will provide breakthroughs in the RPC industry and our AI App framework makes building AI apps easier than ever before. We pioneer the web3 revolution for visionaries and forward-thinkers. We’re not just a company — we’re a movement driving an inclusive and decentralised web3 era, together. + +[Linktree](https://linktr.ee/subquerynetwork) | [Website](https://subquery.network) | [Discord](https://discord.com/invite/subquery) | [Telegram](https://t.me/subquerynetworkcommunity) | [Twitter](https://twitter.com/subquerynetwork) | [Blog](https://blog.subquery.network/?lng=en) | [Medium](https://medium.com/@subquery) | [LinkedIn](https://www.linkedin.com/company/subquery) | [YouTube](https://www.youtube.com/c/SubQueryNetwork) \ No newline at end of file diff --git a/docs/fr/subquery_network/community.md b/docs/fr/subquery_network/community.md new file mode 100644 index 00000000000..59c4aaeb078 --- /dev/null +++ b/docs/fr/subquery_network/community.md @@ -0,0 +1,178 @@ +# SubQuery Network Community + +The key focus of the [SubQuery Foundation](./governance/foundation.md) and community is to ensure that there is enough support that anyone, from an expert blockchain team to a new hobbyist developer, can build their own Project. Together we can pave the way to a more decentralised future! + +## Connecting with others + +Discord is our main community for talking about SubQuery and learning more. You can join with [this link here](https://discord.com/invite/subquery). People most interested in the SubQuery Network will want to join `#network-general`, and Indexers or Delegators should join `#network-indexer-chat` or `#network-delegator-chat` respectively. + +When the conversation is deeper and requires more thought, we move the conversation to [our Forum](https://forum.subquery.network/). Here you will find longer topics, a history of all announcements to Network, and deeper conversation about the direction of the network. Feel free to join and start posting at [forum.subquery.network](https://forum.subquery.network/)! + +### Join the Node Operator community + +If you're a Node Operator on the Network, we strongly suggest that you keep up with the latest news, announcements, and tips by joining the following Discord channels: + +- `#network-announcements` +- `#network-general` +- `#network-services-release` +- `#network-indexer-announcements` +- `#network-indexer-general` + +## Contributing to Codebases + +SubQuery is open source and open to the community, if you want to contribute (e.g. add a feature, fix a bug, suggest an improvement, or even just fix a typo in our documentation), please review our [contributing guide](../miscellaneous/contributing.md). + +The following codebases are where you can find code for all the contracts, applications, and backend SubQuery projects. We're looking forward to seeing your contributions! + +### `network-app` + +dApp for indexers, consumers and delegators interact with SubQuery Network. + + + +### `network-airdrop-app` + +dApp for users to interact with the SubQuery airdrop contract. + + + +### `network-contracts` + +Contracts for SubQuery Network. + + + +You can find smart contract addresses for all network contracts here in [GitHub](https://github.com/subquery/network-contracts/blob/develop/publish/mainnet.json) + +### `network-app-backend` + +SubQuery project for the backend of the SubQuery App. + + + +### `network-airdrop-app-backend` + +SubQuery project for the backend of the SubQuery Airdrop App. + + + +### `network-swap-app-backend` + +SubQuery project for the backend of the SubQuery Swap App. + + + +### `network-indexer-services` + +Services that Indexers run to connect and serve data to the SubQuery Network. + + + +### `network-clients` + +Client SDKs for SubQuery Network. + + + +### `subquery-component-library` + +React UI component library for SubQuery dApps. + + + +## Community Tools + +There are a number of community built tools that you can use to help your SubQuery Network experience. Feel free to contribute your own. + +:::warning +Please note that none of these tools have been endorsed by the SubQuery team and descriptions have been written by third parties. This section is open for contribution by all. + +Please research and use at your own risk +::: + +### SQTScan + +[SQTScan](https://sqtscan.com/?ref=blog.subquery.network) is a ***community-owned application*** designed specifically to help expert users such as Node Operators and Delegators to gain a deeper understanding of historical rewards on the SubQuery Network and optimise their participation. + +SQT Scan helps expert users (Node Operators and Delegators) with: + +1. **Education:** Understand how their rewards are calculated and how they should make decisions +2. **Compare Opportunities:** Decide which projects to deploy based on historical rewards +3. **Compare Others:** Compare their APY with other Node Operators, overall and by project, to see how they're performing relatively +4. **APY Maximisation:** Identify ways to increase their APY + +If you would like to add your support, suggest improvements or new features, or even contribute code, it is welcomed! + +Links + +- [SQTSCan](https://sqtscan.com) +- [Github](https://github.com/HuberTRoy/subquery-sqtscan) + +### Indexer Monitoring Tools (by web3cdn.network) + +Five products: +1. **Toolkit:** A toolkit contains everything you need to index, monitor and properly access from any device +2. **Telegram Uptime Bot:** Eagle Eye is a bot which will provide you live updates in Telegram on the uptime of your indexer +3. **UpdateHunter** +4. **Snapshots** +5. **Snapshots Toolkit** + +Toolkit Features: + +- Extended monitoring of all indexer parameters, sync time, balances, issues. Metrics also support Alerting rules +- Flags problems that have arisen through monitoring and help you to not miss rewards. +- Makes your indexer and infrastructure secure +- Ease of updating without the risk of changing important parameters +- Secured access to dangerous zone with your own VPN, Access from mobile devices to monitoring, and internal services in any time. +- Very easy installation and user error protection + +Eagle Eye Telegram Bot Notifications: + +- Provide reports on your indexer's uptime - help you to know about an errors in advance and not lose funds. +- If your indexer is offline +- If your project is somehow unavailable +- If you do not have enough funds +- If your certificate is about to expire +- And more + +UpdateHunter: + + - A tool that notifies you when a project is updated or a new project is created, providing complete documentation to enable fast and secure upgrades. + - It scans the blockchain and alerts an indexer via a Telegram channel about updates, automati­cally generating instructions and SQL queries. + - The bot integrates with GitHub, posting documentation updates to a public repository. + + Snapshots: + + - Service generates daily snapshots for all active projects + - This service is ideal if your indexer: + - Is newly deployed and you want to avoid ~1 month of downtime for project synchronization + - Has experienced data loss (corrupted disk, hardware failures, or software issues) + + Snapshots Toolkit: + + - Open Source toolkit for an own snapshot generator. With this repository indexer can generate its own snapshots. + +Links + +- [Toolkit Github](https://toolkit.subquery.dev/) +- [Eagle Eye Telegram Bot](https://eagleeye.subquery.dev/) +- [UpdateHunter](https://eagleeye.subquery.dev/updates) +- [Snapshots](https://snapshots.subquery.dev/) +- [Snapshots Toolkit](https://snapshots.subquery.dev/toolkit) + +### Kepler Network Dashboard (by DappLooker) + +To monitor the progress and performance of the Kepler Network, DappLooker has created a dashboard that displays the following key metrics: + +- Active Indexers / Delegators: The number of Indexers and Delegators who are actively participating in the Kepler Network. +- Weekly Indexer Stake / Delegation: The amount of kSQT that Indexers and Delegators have staked on the Kepler Network in the past week. +- Weekly Rewards: The amount of kSQT that Indexers have earned as rewards for serving data requests on the Kepler Network in the past week. +- Stake Distribution: The distribution of kSQT stakes between Indexers and Delegators on the Kepler Network. + +To make the data more accessible and user-friendly, DappLooker has also made the SubQuery Kepler data publicly available for everyone. This means that anyone can create custom dashboards tailored to their needs using the indexed data from the Kepler Network. + +Links + +- [Dashboard](https://dapplooker.com/dashboard/subquery-kepler-network-dashboard-577) +- [Indexed Dataset](https://analytics.dapplooker.com/browse/2/schema/subquery_kepler) +- [Announcement Article](https://blog.dapplooker.com/dapplooker-integrates-subquery-kepler-network-to-provide-analytics-and-dashboard-solution-to-web3-fb0c5aeea899) diff --git a/docs/fr/subquery_network/faq.md b/docs/fr/subquery_network/faq.md new file mode 100644 index 00000000000..a298d22efe5 --- /dev/null +++ b/docs/fr/subquery_network/faq.md @@ -0,0 +1,78 @@ +# Frequently Asked Questions + +FAQs for specific network participants: + +- [Node Operators](./node_operators/setup/faq.md) +- [Consumers](./consumers/faq.md) + +## Proof-of-indexing + +[Proof Of Index](./introduction/proof-of-index.md) + +## How do you ensure indexed data accuracy? + +Ensured by [Proof Of Index](./introduction/proof-of-index.md) + +## Are there a list of RPC providers that can provide support for \_\_\_ chain? + +SubQuery Network is decentralised, so we can't say what individual node operators would decide to serve you, nor can we say what infrastructure the node operators use and where it is hosted + +## What is the integration and deployment timeline for RPCs? + +SubQuery team can enable the RPC in a few days depending on how long an archive node on your network would take to sync. + +## Where is your/provider's infra hosted? + +Depends on the provider, SubQuery don't dictate this. But SubQuery gateway encourages competition to provide high performance, low latency, and geographically decentralised services. Most providers are running on their own bare metal for cost considerations + +## Is there a testnet environment? + +Yes, be sure to check https://dev.thechaindata.com/ + +## Is there a meaning behind SubQuery's name? + +The name "SubQuery" refers to its function in the blockchain ecosystem. A subquery is essentially a query within another query, allowing users to access data more efficiently. It is a powerful tool for indexing and querying blockchain data. + +## What was the first network that SubQuery first supported? + +SubQuery initially supported the Polkadot network, focusing on indexing and querying data for the Polkadot and its parachains. + +## How many networks do SubQuery support now? + +As of now, SubQuery supports multiple networks, including Polkadot, Kusama, Ethereum, and many others, expanding its reach to a wide array of blockchain ecosystems. + +## How does SubQuery improve blockchain data access? + +SubQuery enhances blockchain data access by providing an indexing layer that aggregates and organizes data from blockchain networks. This allows developers and applications to quickly retrieve and interact with data in a structured and efficient manner. + +## How does SubQuery differ from traditional block explorers? + +Traditional block explorers allow users to explore blockchain data in a static, non-queryable format. SubQuery, on the other hand, provides dynamic and customizable data querying, giving developers the ability to filter, process, and retrieve data in real-time for their applications. + +## What programming languages does SubQuery support? + +SubQuery primarily supports JavaScript and TypeScript for building queries and processing data. Developers can use these languages to define the structure and logic for data retrieval from supported networks. + +## Is SubQuery open-source? + +Yes, SubQuery is open-source. It encourages developers to contribute to its growth and use its tools to build decentralized applications (dApps) more efficiently. The source code is available on GitHub. + +## What are the main use cases for SubQuery? + +SubQuery is used for various purposes, such as: + +- Building decentralized applications (dApps) that need to access blockchain data. +- Indexing and querying blockchain data for analysis and reporting. +- Creating custom data solutions for blockchain ecosystems and decentralized finance (DeFi) platforms. + +## Can I deploy SubQuery on my own infrastructure? + +Yes, SubQuery can be deployed on your own infrastructure, whether on-premise or in the cloud. It offers flexibility to users who want complete control over their indexing and querying solutions. + +## How does SubQuery handle data updates and changes? + +SubQuery continuously updates its data by monitoring blockchain events in real-time. This ensures that the indexed data is always up to date, and any changes to the blockchain are reflected immediately in the data queries. + +## How can I get started with SubQuery? + +To get started with SubQuery, you can visit their official documentation, which provides step-by-step guides on setting up a project, writing queries, and deploying them on supported networks. The community also offers support through forums and Discord. diff --git a/docs/fr/subquery_network/infra-changes.md b/docs/fr/subquery_network/infra-changes.md new file mode 100644 index 00000000000..b30b5fa306d --- /dev/null +++ b/docs/fr/subquery_network/infra-changes.md @@ -0,0 +1,109 @@ +# Redefining Web3: SubQuery Network’s Bold Infrastructure Evolution + +Back in December 2023, we announced the evolution of SubQuery, in which we aim to transition from simply indexing web3 data to pioneering a complete web3 infrastructure revolution. + +Over the last year, as we’ve been building out our data indexing service and network, we realised our network is in a prime position to address broader centralisation issues throughout the web3 infrastructure landscape. + +Our mission has expanded, and so has the opportunity space we’re going to be working in. + +Read on to learn about the challenges we’re taking on and the next steps we’re taking to play a bigger role in decentralising the future. + +### The Web3 Infrastructure Landscape + +Web3 middleware services like indexers, RPCs, oracles and storage services are pivotal in blockchain dApp development. In fact, the utilisation of these middleware services is what sets apart successful, large-scale, production dApps - they accelerate performance and can scale to thousands of users, while providing a superior developer experience to bring in more users, TVL, and value. Indexers and RPCs shoulder the heavy lifting, standing as mission-critical services that underpin the functionality and efficiency of web3 applications. + +![](https://lh7-us.googleusercontent.com/2lbQyLR4fxrgV2dTqljyFV6bECXrfq3anA2k_qM6gJuWdSN01dHrVjIFU6OZeFXXJv57dwaXNQ6_lKdGtLK9YDWr0EdS7yDDv0BwZfFXT_j6aw-iu7bDxIS5ZkgliPD2mY_l5kbJXGKEqI6OWuZIEwk) + +**The current segregated web3 infrastructure landscape** + +Data indexers (like SubQuery) speed up data retrieval, enhancing performance and response times for users. They also simplify data by transforming raw blockchain information into more digestible formats, facilitating efficient development and a smooth user experience. + +Meanwhile, RPCs are pivotal for communication between blockchain nodes and external entities, facilitating data retrieval, smart contract interactions, and transaction submissions. Under the hood of your favourite dApp, tens of requests are passing through RPC providers to query and submit transactions to the network. + +While these middleware services are integral to a successful dApp, there is a significant issue that needs to be addressed. + +### Web3’s Dirty Little Secret + +There is a hidden truth behind the mask of “decentralisation” most of these middleware services wear. The reality is that many leading dApps have a significant reliance on centralised middleware components. This centralisation poses a substantial threat to the envisioned unstoppability of a web3 future, at any given moment, a single entity can undermine supposedly decentralised applications. + +Nowhere is this more apparent with RPC providers, and to a lesser extent, data indexers. These crucial services distinguish the scalable, reliable, and polished dApps from rudimentary applications that go without. But due to historical challenges in the process of decentralisation, for a long time, this has been a compromise most apps have accepted. + +The call for decentralised alternatives to these pivotal middleware services is essential for the foundation of the next generation of dApps to build upon. We need to decentralise these services, without compromise. + +### SubQuery Network Evolution Revealed + +At the start we set out to create a viable decentralised solution to the data indexing problem. + +Web3 developers face great difficulties aggregating and organising data to power dApps, and SubQuery has helped thousands of developers building the world's best and biggest networks, dApps, and analytics tools by providing fast and performant data indexing. + +In 2022 we launched Kepler Network, a pre-mainnet release that enabled us to bootstrap the network sustainably by bringing onboard proficient indexers and projects. The success of Kepler lead to the realisation that the ecosystem we’ve built could bring benefits for more than just decentralised data indexing, but for middleware infrastructure as a whole. The key components of the network we have built and deployed - reward and pricing rails, service verification tools, and dispute resolution processes - are valuable for others verticals. + +Knowing that the SubQuery Network could give our existing community of top node runners a solution to trustlessly receive rewards for running data indexing infrastructure, why couldn’t it work for those other services, for other parts of the dApp tech stack? + +We realised the full potential of the SubQuery Network mainnet should not be limited to just data indexing; its fundamental contracts, tools, and reward flows enable it to be so much more. By harnessing the power of the existing participants and mechanisms, the SubQuery Network is ready to extend to various infrastructure verticals. It dawned on us that there is a massive opportunity ahead of us when we think holistically about the entire developer experience. + +> With the launch of mainnet, the SubQuery Network will emerge as a solution to _decentralise everything_, revolutionising the entire developer experience in web3. + +![](https://lh7-us.googleusercontent.com/fXK85pf2n1zTFAsbxyhYKk4I_negGP3mNvXP_vE-_k-ppDlNQeCUPc-iKG7b2HjaeBaisWhkdDqPL8SoQb0QHW6eHI4-5Bra1GK7hrfIhzx9SW1SWgVJ9Nces5Vfza3fwYNug_nduW_8HJ-XB8eZwig) + +**The vision for SubQuery Network to encompass key web3 infrastructure components in a completely decentralised manner** + +### Starting with RPCs + +Our next step that we have completed is to decentralise the biggest infrastructure component for dApps - _Remote Procedure Call_ or RPC services. + +RPC services are still the main interface to the blockchain, under the hood of your favourite dApp, dozens of requests are passing through RPC providers to query and submit transactions to the network. They are the most critical part of the ecosystem, when one has an outage, [the effects reverberate across the industry](https://decrypt.co/47846/ethereum-backbone-infura-suffers-major-damage?ref=blog.subquery.network). + +Since SubQuery relies on performant and scalable RPCs to maximise our indexing speed, we already work extremely closely with RPC providers. On our quest to index over [115+ chains and counting](https://subquery.network/networks?ref=blog.subquery.network), we’ve discovered that the RPC ecosystem is very fractured: some ecosystems have excellent support, and some don’t, and that makes delivering an excellent indexing experience across all chains difficult. + +Across many smaller emergent networks, amateur RPC services operate to provide RPCs to various developers building on the network. These RPCs are usually run (at a loss) by the core network foundation team, and perhaps a collection of validators (for staking advertising purposes). Unfortunately for cost reasons, these RPCs are usually heavily pruned and rate limited, and have no upsell options for unrestricted access. As a result, dApp developers will often run a private RPC endpoint for their own use. This is expensive, frustrating, poses high barriers to entry, and results in no redundancy for dApp developers. + +For more established networks, one or more commercial providers may come and offer a freemium service, where there is a free plan/public endpoint, and a paid upsell to higher scale access. This serves dApp developers well, but the law of economies of scale dictate that networks tend towards a small number of hyperscale RPC providers who centralise the network and cause major outages that affect thousands of dApps when they go offline. They also extract huge economic value from a network and send that directly to big private cloud companies and VCs. + +We have built an alternative to these two dangerous equilibriums, and help decentralise everything.The SubQuery Network provides an open market for both data indexers and RPC providers and their consumers that: + +- Maintains low barriers of entry: Any node operator can join as a provider for any service on any network. +- Incentivises performance and cost: Node operators are automatically rewarded with requests based on these metrics, driving these values across the network. +- Encourages constant expansion to new chains: Node operators are free to onboard new chains and projects for first mover advantage, constantly expanding the network. + +### Enhancing RPCs - SubQuery’s Data Node + +The performance limitations of data indexers and many other applications have long been limited by the RPC endpoint. Developers have long focussed on building nodes to ensure efficient validation to ensure the safety of the network. As a result of this sacrifice, RPCs are extremely costly and they’re not at all optimised for querying. + +This is compounded by the rise of L2 chains where, with higher throughput, the query performance and cost are major outstanding issues to address. With limited querying capabilities, many don’t support complex querying languages or operations, making it inefficient to retrieve specific data. + +We have delivered the SubQuery Data Node, an enhanced and heavily-forked RPC node that is perfectly optimised for querying, especially on endpoints like `eth_getLog`, and the ability to filter transactions in a single API call. + +The Data Node is open source, allowing people to contribute, extend, or fork the implementation in any way. It supports leading layer-2s and other EVM networks initially, and they are optimised to run on the SubQuery Network in a decentralised way. + +Working together, the SubQuery Indexer and SubQuery Data Node provides the most performant indexing performance possible and in a completely decentralised way thanks to the SubQuery Network. + +Our node runners are able to run these data nodes on the network, bringing powerful and cost-effective RPC access to all, cementing SubQuery’s position as the fastest decentralised data indexer in web3. + +### Democratising RPCs - SubQuery’s Sharded Data Node + +In the final stage of our RPC journey, SubQuery will work to democratise RPCs (and solve [EIP-4444](https://eips.ethereum.org/EIPS/eip-4444?ref=blog.subquery.network)) in the process by delivering the Sharded Data Node, which will make RPCs cheaper to run and operate by node providers. + +In the last few months we’ve spoken with many RPC providers in the ecosystem. In many networks (in particular Cosmos), small scale RPC services operate to provide RPCs to various developers building on the network. Unfortunately for cost reasons, these RPCs are usually heavily pruned and rate limited and have no upsell options for unrestricted access. + +One of the key reasons for this is the sheer size of the node - an Ethereum archive requires about ~12 TB on Geth, an Osmosis archive is at least the same. This is an incredible cost that limits these nodes to large centralised infrastructure providers. + +SubQuery recognises that in order to decentralised RPCs correctly, you need to be able to make running these nodes easier and more accessible to everyday users. Currently the storage is made smaller by “pruning” data, which is intentionally discarding older information while cryptographically confirming that the recent data that is valid. This works fine for writing transactions, but means that indexers and other services are unable to query old data. + +SubQuery will extend its Data Node to support sharding, that is making each Data Node smaller by splitting up block ranges between node operators. Since SubQuery’s Data Node only runs within the boundaries of a specific block range, it does not need to constantly sync new data, allowing it to optimise further for query performance rather than validation and verification. + +The SubQuery Sharded node won’t just shard historical data, but also shard the historical state within the node. By itself, this won’t change much, but these sharded nodes will be optimised to run on the network, and the network will be designed to combine all these shards to expose a single unified endpoint that appears to cover the entire historical state of the chain. Developers will benefit from the entire historical state of the given network, and node operators will benefit from significantly lower running costs, creating a more cost efficient network. + +This is a revolutionary step forward for the RPC industry, and a potential solution to one of the great challenges facing older and larger blockchains with their state bloat size. This solution has the potential to help scale Ethereum, solve [EIP-4444](https://eips.ethereum.org/EIPS/eip-4444?ref=blog.subquery.network), and greatly support proliferation of Layer-2’s and rollups, while further democratising and decentralising the SubQuery Network. + +### Summary + +The future of SubQuery is not simply indexing web3 data, but pioneering a complete web3 infrastructure revolution. web3 middleware services like indexers and RPC providers are pivotal in blockchain dApp development, but there is a hidden truth behind the mask of “decentralisation” most of these middleware services wear. The reality is a significant reliance on centralised middleware components, which poses a substantial threat to the envisioned unstoppability of a web3 future. + +Our mission has expanded, and so has the opportunity space we’re going to be working in. We need to decentralise these services, without compromise. We’ve already delivered breakthroughs in decentralised data indexing, but our next steps will focus on enhancing the performance of RPCs with the SubQuery Data Node, and then to bring RPCs to the masses, with SubQuery’s Sharded Data Nodes. These steps together, will help unlock the next level of performance increases in web3. + +No other team today is better equipped at working to provide a holistic approach to solving this problem. In summary, our vision goes beyond data indexing; it's about revolutionising how data and infrastructure services are organised and accessed. + +Pioneering fast, flexible, and scalable decentralised infrastructure, we will help power web3's transition to an open, efficient and user-centric future. Join us in this journey. With SubQuery, it's not just about building for today, but architecting a decentralised, inclusive future. + +_Let's shape the future of web3, together._ \ No newline at end of file diff --git a/docs/fr/subquery_network/welcome.md b/docs/fr/subquery_network/welcome.md new file mode 100644 index 00000000000..53c14ae9c38 --- /dev/null +++ b/docs/fr/subquery_network/welcome.md @@ -0,0 +1,283 @@ +--- +footer: false +lastUpdated: false +contributors: false +editLink: false +photoSwipe: false +--- + + +
+
+
+ SubQuery Network + + The SubQuery Network is the most scalable, reliable, and unified data infrastructure network. 1,000s of decentralised Indexers and RPC providers simplify the data layer for a myriad of applications and use cases. + +
+
+
+ +
+
+ + + One network, all your web3 data needs + +
+ +
+ + {{ item.title }} + {{ item.subtitle }} + + {{ content }} + + + + + + +
+ +
+ Anyone can participate + + There’s a role for everyone in the network, from highly technical + developers to those with some experience and blockchain beginners. Find + out how you can participate and be rewarded. + +
+
+ + {{ anyone.name }} + + {{ anyone.description }} + + + + +
+
+ + +
+ Get Started with the Network Today + Our decentralised network is live and vibrant +
+ + + {{ item.title }} + + {{ item.desc }} + + + +
+
+ + +
+
+ + diff --git a/docs/id/subquery_network/2024.md b/docs/id/subquery_network/2024.md new file mode 100644 index 00000000000..dfe086f16d3 --- /dev/null +++ b/docs/id/subquery_network/2024.md @@ -0,0 +1,62 @@ +# 2024 in Review: SubQuery’s Top 5 Milestones + +As we look back on 2024, we’re proud to call it a major “year of firsts” for us here at SubQuery. This year was filled with groundbreaking achievements, major launches, and remarkable community growth. The year has flown by but it also feels so long ago that we had our TGE, CEX Listing and SubQuery Network mainnet launch - all on the same day! + +Let’s celebrate some of the key milestones that made 2024 unforgettable. + +## 1. Mainnet Launch + +After an extremely successful Public Sale on 30 January 2024, selling out of SubQuery’s native token (SQT) in less than 2 hours, we worked very hard to launch the SubQuery Network mainnet on 23 February 2024. Powered by SQT and launched on Base, immediately users could consume and/or index data from over 150 networks ([now over 270 networks](https://subquery.network/networks)). + +Almost 1 year on and we have: + +- 46 globally distributed and highly skilled Node Operators servicing the network +- More than 330 million SQT staked and delegated in the Network +- Serving more than 50 million RPC requests every day +- An overall average APY of 22.28% and much higher for Node Operators (94.66%) + +## 2. SQT Token Generation Event + +Combined with the Mainnet launch, we ambitiously chose to do our TGE and day one CEX listing with Bybit on the same day (23 February 2024) as well. Seperti yang diuraikan dalam Whitepaper, SQT dimaksudkan untuk menjadi token yang menggerakkan Jaringan SubQuery, memberikan insentif untuk partisipasi, serta berfungsi sebagai media pertukaran untuk transaksi dalam Jaringan SubQuery. Consumers of data commit SQT in exchange for RPC queries or indexed data from our globally distributed Node Operators. + +Today, you can acquire SQT through any of these centralised exchange: + +- [Bybit](https://www.bybit.com/en/trade/spot/SQT/USDT) +- [Gate.io](https://www.gate.io/trade/SQT_USDT) +- [Crypto.com](https://crypto.com/exchange/trade/SQT_USD) +- [MEXC](https://www.mexc.com/exchange/SQT_USDT) + +SQT is on a number of DEX Pools however most liquidity is on Uniswap. + +- [Uniswap Pool on Ethereum](https://app.uniswap.org/explore/tokens/ethereum/0x09395a2A58DB45db0da254c7EAa5AC469D8bDc85) +- [Unsiwap Pool on Base](https://app.uniswap.org/explore/tokens/base/0x858c50c3af1913b0e849afdb74617388a1a5340d) + +## 3. Expansion into Decentralised RPCs + +This vision was announced at the end of 2023 but really came to fruition in 2024. We expanded our network capabilities by introducing support for Remote Procedure Call (RPC) services. This was the first step of expanding away from just a data indexer to a major decentralised infrastructure network, allowing us to support a more accessible, interoperable, and developer-friendly web3 ecosystem. + +Now serving RPC requests on 20+ networks, [get your decentralised RPCs from the SubQuery Network today](https://subquery.network/rpc/list/). + +### 4\. Launching Artificial Intelligence Tools + +SubQuery took its first steps into the AI space by launching decentralised AI inference model hosting on the SubQuery Network plus a new developer SDK called the AI App Framework. This massively expands the tools and services that we can offer to web3 builders across, all under one roof. + +The AI App Framework allows you to build, deploy, and run production AI apps on the SubQuery Network in a trusted and decentralised environment. AI apps are self-contained and easily scalable AI agents that you can use to power your intelligent applications. They are sandboxed to a trusted runner and can be easily distributed and scaled horizontally across the SubQuery Network. + +[Start building AI Apps today!](https://academy.subquery.network/ai/welcome.html) + +## 5. SubQuery Rebranding + +As we expanded into the Artificial Intelligence space, we felt a new look was warranted to match our new pursuit. So we rebranded to a complete new look with sleek chromatic details and a flower/root narrative. + +The flower and root theme symbolises SubQuery’s commitment to fostering innovation and growth within the blockchain community. The roots represent the deep, stable, and reliable infrastructure that SubQuery provides, while the flowers symbolise the diverse and vibrant dApps that developers can create with the help of this infrastructure. + +[Check out the new look](https://subquery.network/). + +## Looking Ahead to 2025 + +While 2024 was full of exciting milestones, we know this is just the beginning. With a stronger community, enhanced technology, and bold new goals, we’re ready to scale even greater heights in 2025. With our most recent [2024 roadmap](https://blog.subquery.network/subquery-releases-network-roadmap-for-2024/?lng=en) almost fully accomplished, stay tuned for a new version packed with ambitious plans. + +Thank you to everyone—developers, partners, and community members—who helped make this year possible. + +Here’s to many more firsts ahead! \ No newline at end of file diff --git a/docs/id/subquery_network/about.md b/docs/id/subquery_network/about.md new file mode 100644 index 00000000000..1699165773b --- /dev/null +++ b/docs/id/subquery_network/about.md @@ -0,0 +1,47 @@ +# About Us + +Our mission is to innovate Web3 infrastructure so builders can decentralise the next generation of applications - without compromise. + +Pioneering fast, flexible, and scalable decentralised infrastructure, we power Web3's transition to an open, efficient and user-centric future.Join us on our journey to build the future of web3 infrastructure. + +[Join our Discord Community](https://discord.com/invite/subquery) + +## Core team + +SubQuery has a deep bench of highly skilled talent of engineers, customer service, and operations personnel.Headquartered in Singapore, we have key representation in New Zealand, Lisbon, and Sydney. + +### Ian He - CTO and Co-Founder + +Ian forged his interest in blockchain during his tenure as the Technical Team Lead for Centrality where he led the development of core components of CENNZnet. Ian also led a team that won 2nd place in the world's first Substrate/Polkadot Hackathon in 2019. Prior to this, Ian obtained significant experience working on large-scale infrastructure working for Alipay and Yihaodian.com. + +### Scott Twiname - Principal Dev of SDK + +Scott has a large wealth of experience in blockchain development. He started out learning about blockchain in his own time and eventually got the opportunity to apply his knowledge as a senior developer at Sylo. He has worked on all facets of blockchain development from smart contracts, dapps, decentralised technologies and wallet integration for various networks including Bitcoin, Ethereum, Tezos and CENNZnet. + +### Marta Adamczyk - Head of Business Development + +Marta is a huge tech advocate, Web3 enthusiast and IT-meetup addict. She helps SubQuery customers develop and scale their projects by delivering technical consultancy, developer-oriented content and technical education. Former product evangelist, frontend developer, digital marketer, educator and sales manager with corporate and start-up experience. + +### Brittany Seales - Head of Marketing + +Brittany has a background in chemistry but since then she became the closest point of contact with SubQuery customers and helped ensure that every SubQuery customer gets an excellent on-boarding experience. Naturally Brittany is heavily integrated with the community and content marketing and has since taken over this area. Sadly, no amount of interaction with successful blockchain projects has give her the ability to pick a winning NFT! + +### James Bayly - Advisor + +Well-versed across the business, from product engineering to being the face of SubQuery, James is also a serial entrepreneur leading several tech companies. When he’s not in Berlin sipping cocktails, you’ll find him hiking up the Routeburn Track in New Zealand. + +## Our Manifesto + +In the new era of Web3, true power isn't bought – it's built with innovation and vision. +We are SubQuery, not just a company, but a revolution. Our mission: to lead the charge in decentralising the future. +We're pioneering an infrastructure that's fast, flexible, scalable – ready to power tomorrow's Web3 world. Crafting an open, efficient, and user-centric digital landscape. +For the visionaries, the forward-thinkers, the builders of tomorrow – SubQuery is your platform. +Join us in this journey. With SubQuery, it's not just about building for today, but architecting a decentralised, inclusive future. Let's shape the future of Web3, together. + +## About SubQuery + +SubQuery Network is innovating in web3 infrastructure with tools that empower builders to decentralise without compromise. SubQuery’s infrastructure network offers everything from data indexers, RPCs and AI agents - all fully decentralised and production ready. + +Our fast, flexible, and open data indexer supercharges thousands of dApps on nearly 300 networks. Our Sharded Data Node will provide breakthroughs in the RPC industry and our AI App framework makes building AI apps easier than ever before. We pioneer the web3 revolution for visionaries and forward-thinkers. We’re not just a company — we’re a movement driving an inclusive and decentralised web3 era, together. + +[Linktree](https://linktr.ee/subquerynetwork) | [Website](https://subquery.network) | [Discord](https://discord.com/invite/subquery) | [Telegram](https://t.me/subquerynetworkcommunity) | [Twitter](https://twitter.com/subquerynetwork) | [Blog](https://blog.subquery.network/?lng=en) | [Medium](https://medium.com/@subquery) | [LinkedIn](https://www.linkedin.com/company/subquery) | [YouTube](https://www.youtube.com/c/SubQueryNetwork) \ No newline at end of file diff --git a/docs/id/subquery_network/community.md b/docs/id/subquery_network/community.md new file mode 100644 index 00000000000..59c4aaeb078 --- /dev/null +++ b/docs/id/subquery_network/community.md @@ -0,0 +1,178 @@ +# SubQuery Network Community + +The key focus of the [SubQuery Foundation](./governance/foundation.md) and community is to ensure that there is enough support that anyone, from an expert blockchain team to a new hobbyist developer, can build their own Project. Together we can pave the way to a more decentralised future! + +## Connecting with others + +Discord is our main community for talking about SubQuery and learning more. You can join with [this link here](https://discord.com/invite/subquery). People most interested in the SubQuery Network will want to join `#network-general`, and Indexers or Delegators should join `#network-indexer-chat` or `#network-delegator-chat` respectively. + +When the conversation is deeper and requires more thought, we move the conversation to [our Forum](https://forum.subquery.network/). Here you will find longer topics, a history of all announcements to Network, and deeper conversation about the direction of the network. Feel free to join and start posting at [forum.subquery.network](https://forum.subquery.network/)! + +### Join the Node Operator community + +If you're a Node Operator on the Network, we strongly suggest that you keep up with the latest news, announcements, and tips by joining the following Discord channels: + +- `#network-announcements` +- `#network-general` +- `#network-services-release` +- `#network-indexer-announcements` +- `#network-indexer-general` + +## Contributing to Codebases + +SubQuery is open source and open to the community, if you want to contribute (e.g. add a feature, fix a bug, suggest an improvement, or even just fix a typo in our documentation), please review our [contributing guide](../miscellaneous/contributing.md). + +The following codebases are where you can find code for all the contracts, applications, and backend SubQuery projects. We're looking forward to seeing your contributions! + +### `network-app` + +dApp for indexers, consumers and delegators interact with SubQuery Network. + + + +### `network-airdrop-app` + +dApp for users to interact with the SubQuery airdrop contract. + + + +### `network-contracts` + +Contracts for SubQuery Network. + + + +You can find smart contract addresses for all network contracts here in [GitHub](https://github.com/subquery/network-contracts/blob/develop/publish/mainnet.json) + +### `network-app-backend` + +SubQuery project for the backend of the SubQuery App. + + + +### `network-airdrop-app-backend` + +SubQuery project for the backend of the SubQuery Airdrop App. + + + +### `network-swap-app-backend` + +SubQuery project for the backend of the SubQuery Swap App. + + + +### `network-indexer-services` + +Services that Indexers run to connect and serve data to the SubQuery Network. + + + +### `network-clients` + +Client SDKs for SubQuery Network. + + + +### `subquery-component-library` + +React UI component library for SubQuery dApps. + + + +## Community Tools + +There are a number of community built tools that you can use to help your SubQuery Network experience. Feel free to contribute your own. + +:::warning +Please note that none of these tools have been endorsed by the SubQuery team and descriptions have been written by third parties. This section is open for contribution by all. + +Please research and use at your own risk +::: + +### SQTScan + +[SQTScan](https://sqtscan.com/?ref=blog.subquery.network) is a ***community-owned application*** designed specifically to help expert users such as Node Operators and Delegators to gain a deeper understanding of historical rewards on the SubQuery Network and optimise their participation. + +SQT Scan helps expert users (Node Operators and Delegators) with: + +1. **Education:** Understand how their rewards are calculated and how they should make decisions +2. **Compare Opportunities:** Decide which projects to deploy based on historical rewards +3. **Compare Others:** Compare their APY with other Node Operators, overall and by project, to see how they're performing relatively +4. **APY Maximisation:** Identify ways to increase their APY + +If you would like to add your support, suggest improvements or new features, or even contribute code, it is welcomed! + +Links + +- [SQTSCan](https://sqtscan.com) +- [Github](https://github.com/HuberTRoy/subquery-sqtscan) + +### Indexer Monitoring Tools (by web3cdn.network) + +Five products: +1. **Toolkit:** A toolkit contains everything you need to index, monitor and properly access from any device +2. **Telegram Uptime Bot:** Eagle Eye is a bot which will provide you live updates in Telegram on the uptime of your indexer +3. **UpdateHunter** +4. **Snapshots** +5. **Snapshots Toolkit** + +Toolkit Features: + +- Extended monitoring of all indexer parameters, sync time, balances, issues. Metrics also support Alerting rules +- Flags problems that have arisen through monitoring and help you to not miss rewards. +- Makes your indexer and infrastructure secure +- Ease of updating without the risk of changing important parameters +- Secured access to dangerous zone with your own VPN, Access from mobile devices to monitoring, and internal services in any time. +- Very easy installation and user error protection + +Eagle Eye Telegram Bot Notifications: + +- Provide reports on your indexer's uptime - help you to know about an errors in advance and not lose funds. +- If your indexer is offline +- If your project is somehow unavailable +- If you do not have enough funds +- If your certificate is about to expire +- And more + +UpdateHunter: + + - A tool that notifies you when a project is updated or a new project is created, providing complete documentation to enable fast and secure upgrades. + - It scans the blockchain and alerts an indexer via a Telegram channel about updates, automati­cally generating instructions and SQL queries. + - The bot integrates with GitHub, posting documentation updates to a public repository. + + Snapshots: + + - Service generates daily snapshots for all active projects + - This service is ideal if your indexer: + - Is newly deployed and you want to avoid ~1 month of downtime for project synchronization + - Has experienced data loss (corrupted disk, hardware failures, or software issues) + + Snapshots Toolkit: + + - Open Source toolkit for an own snapshot generator. With this repository indexer can generate its own snapshots. + +Links + +- [Toolkit Github](https://toolkit.subquery.dev/) +- [Eagle Eye Telegram Bot](https://eagleeye.subquery.dev/) +- [UpdateHunter](https://eagleeye.subquery.dev/updates) +- [Snapshots](https://snapshots.subquery.dev/) +- [Snapshots Toolkit](https://snapshots.subquery.dev/toolkit) + +### Kepler Network Dashboard (by DappLooker) + +To monitor the progress and performance of the Kepler Network, DappLooker has created a dashboard that displays the following key metrics: + +- Active Indexers / Delegators: The number of Indexers and Delegators who are actively participating in the Kepler Network. +- Weekly Indexer Stake / Delegation: The amount of kSQT that Indexers and Delegators have staked on the Kepler Network in the past week. +- Weekly Rewards: The amount of kSQT that Indexers have earned as rewards for serving data requests on the Kepler Network in the past week. +- Stake Distribution: The distribution of kSQT stakes between Indexers and Delegators on the Kepler Network. + +To make the data more accessible and user-friendly, DappLooker has also made the SubQuery Kepler data publicly available for everyone. This means that anyone can create custom dashboards tailored to their needs using the indexed data from the Kepler Network. + +Links + +- [Dashboard](https://dapplooker.com/dashboard/subquery-kepler-network-dashboard-577) +- [Indexed Dataset](https://analytics.dapplooker.com/browse/2/schema/subquery_kepler) +- [Announcement Article](https://blog.dapplooker.com/dapplooker-integrates-subquery-kepler-network-to-provide-analytics-and-dashboard-solution-to-web3-fb0c5aeea899) diff --git a/docs/id/subquery_network/faq.md b/docs/id/subquery_network/faq.md new file mode 100644 index 00000000000..a298d22efe5 --- /dev/null +++ b/docs/id/subquery_network/faq.md @@ -0,0 +1,78 @@ +# Frequently Asked Questions + +FAQs for specific network participants: + +- [Node Operators](./node_operators/setup/faq.md) +- [Consumers](./consumers/faq.md) + +## Proof-of-indexing + +[Proof Of Index](./introduction/proof-of-index.md) + +## How do you ensure indexed data accuracy? + +Ensured by [Proof Of Index](./introduction/proof-of-index.md) + +## Are there a list of RPC providers that can provide support for \_\_\_ chain? + +SubQuery Network is decentralised, so we can't say what individual node operators would decide to serve you, nor can we say what infrastructure the node operators use and where it is hosted + +## What is the integration and deployment timeline for RPCs? + +SubQuery team can enable the RPC in a few days depending on how long an archive node on your network would take to sync. + +## Where is your/provider's infra hosted? + +Depends on the provider, SubQuery don't dictate this. But SubQuery gateway encourages competition to provide high performance, low latency, and geographically decentralised services. Most providers are running on their own bare metal for cost considerations + +## Is there a testnet environment? + +Yes, be sure to check https://dev.thechaindata.com/ + +## Is there a meaning behind SubQuery's name? + +The name "SubQuery" refers to its function in the blockchain ecosystem. A subquery is essentially a query within another query, allowing users to access data more efficiently. It is a powerful tool for indexing and querying blockchain data. + +## What was the first network that SubQuery first supported? + +SubQuery initially supported the Polkadot network, focusing on indexing and querying data for the Polkadot and its parachains. + +## How many networks do SubQuery support now? + +As of now, SubQuery supports multiple networks, including Polkadot, Kusama, Ethereum, and many others, expanding its reach to a wide array of blockchain ecosystems. + +## How does SubQuery improve blockchain data access? + +SubQuery enhances blockchain data access by providing an indexing layer that aggregates and organizes data from blockchain networks. This allows developers and applications to quickly retrieve and interact with data in a structured and efficient manner. + +## How does SubQuery differ from traditional block explorers? + +Traditional block explorers allow users to explore blockchain data in a static, non-queryable format. SubQuery, on the other hand, provides dynamic and customizable data querying, giving developers the ability to filter, process, and retrieve data in real-time for their applications. + +## What programming languages does SubQuery support? + +SubQuery primarily supports JavaScript and TypeScript for building queries and processing data. Developers can use these languages to define the structure and logic for data retrieval from supported networks. + +## Is SubQuery open-source? + +Yes, SubQuery is open-source. It encourages developers to contribute to its growth and use its tools to build decentralized applications (dApps) more efficiently. The source code is available on GitHub. + +## What are the main use cases for SubQuery? + +SubQuery is used for various purposes, such as: + +- Building decentralized applications (dApps) that need to access blockchain data. +- Indexing and querying blockchain data for analysis and reporting. +- Creating custom data solutions for blockchain ecosystems and decentralized finance (DeFi) platforms. + +## Can I deploy SubQuery on my own infrastructure? + +Yes, SubQuery can be deployed on your own infrastructure, whether on-premise or in the cloud. It offers flexibility to users who want complete control over their indexing and querying solutions. + +## How does SubQuery handle data updates and changes? + +SubQuery continuously updates its data by monitoring blockchain events in real-time. This ensures that the indexed data is always up to date, and any changes to the blockchain are reflected immediately in the data queries. + +## How can I get started with SubQuery? + +To get started with SubQuery, you can visit their official documentation, which provides step-by-step guides on setting up a project, writing queries, and deploying them on supported networks. The community also offers support through forums and Discord. diff --git a/docs/id/subquery_network/infra-changes.md b/docs/id/subquery_network/infra-changes.md new file mode 100644 index 00000000000..b30b5fa306d --- /dev/null +++ b/docs/id/subquery_network/infra-changes.md @@ -0,0 +1,109 @@ +# Redefining Web3: SubQuery Network’s Bold Infrastructure Evolution + +Back in December 2023, we announced the evolution of SubQuery, in which we aim to transition from simply indexing web3 data to pioneering a complete web3 infrastructure revolution. + +Over the last year, as we’ve been building out our data indexing service and network, we realised our network is in a prime position to address broader centralisation issues throughout the web3 infrastructure landscape. + +Our mission has expanded, and so has the opportunity space we’re going to be working in. + +Read on to learn about the challenges we’re taking on and the next steps we’re taking to play a bigger role in decentralising the future. + +### The Web3 Infrastructure Landscape + +Web3 middleware services like indexers, RPCs, oracles and storage services are pivotal in blockchain dApp development. In fact, the utilisation of these middleware services is what sets apart successful, large-scale, production dApps - they accelerate performance and can scale to thousands of users, while providing a superior developer experience to bring in more users, TVL, and value. Indexers and RPCs shoulder the heavy lifting, standing as mission-critical services that underpin the functionality and efficiency of web3 applications. + +![](https://lh7-us.googleusercontent.com/2lbQyLR4fxrgV2dTqljyFV6bECXrfq3anA2k_qM6gJuWdSN01dHrVjIFU6OZeFXXJv57dwaXNQ6_lKdGtLK9YDWr0EdS7yDDv0BwZfFXT_j6aw-iu7bDxIS5ZkgliPD2mY_l5kbJXGKEqI6OWuZIEwk) + +**The current segregated web3 infrastructure landscape** + +Data indexers (like SubQuery) speed up data retrieval, enhancing performance and response times for users. They also simplify data by transforming raw blockchain information into more digestible formats, facilitating efficient development and a smooth user experience. + +Meanwhile, RPCs are pivotal for communication between blockchain nodes and external entities, facilitating data retrieval, smart contract interactions, and transaction submissions. Under the hood of your favourite dApp, tens of requests are passing through RPC providers to query and submit transactions to the network. + +While these middleware services are integral to a successful dApp, there is a significant issue that needs to be addressed. + +### Web3’s Dirty Little Secret + +There is a hidden truth behind the mask of “decentralisation” most of these middleware services wear. The reality is that many leading dApps have a significant reliance on centralised middleware components. This centralisation poses a substantial threat to the envisioned unstoppability of a web3 future, at any given moment, a single entity can undermine supposedly decentralised applications. + +Nowhere is this more apparent with RPC providers, and to a lesser extent, data indexers. These crucial services distinguish the scalable, reliable, and polished dApps from rudimentary applications that go without. But due to historical challenges in the process of decentralisation, for a long time, this has been a compromise most apps have accepted. + +The call for decentralised alternatives to these pivotal middleware services is essential for the foundation of the next generation of dApps to build upon. We need to decentralise these services, without compromise. + +### SubQuery Network Evolution Revealed + +At the start we set out to create a viable decentralised solution to the data indexing problem. + +Web3 developers face great difficulties aggregating and organising data to power dApps, and SubQuery has helped thousands of developers building the world's best and biggest networks, dApps, and analytics tools by providing fast and performant data indexing. + +In 2022 we launched Kepler Network, a pre-mainnet release that enabled us to bootstrap the network sustainably by bringing onboard proficient indexers and projects. The success of Kepler lead to the realisation that the ecosystem we’ve built could bring benefits for more than just decentralised data indexing, but for middleware infrastructure as a whole. The key components of the network we have built and deployed - reward and pricing rails, service verification tools, and dispute resolution processes - are valuable for others verticals. + +Knowing that the SubQuery Network could give our existing community of top node runners a solution to trustlessly receive rewards for running data indexing infrastructure, why couldn’t it work for those other services, for other parts of the dApp tech stack? + +We realised the full potential of the SubQuery Network mainnet should not be limited to just data indexing; its fundamental contracts, tools, and reward flows enable it to be so much more. By harnessing the power of the existing participants and mechanisms, the SubQuery Network is ready to extend to various infrastructure verticals. It dawned on us that there is a massive opportunity ahead of us when we think holistically about the entire developer experience. + +> With the launch of mainnet, the SubQuery Network will emerge as a solution to _decentralise everything_, revolutionising the entire developer experience in web3. + +![](https://lh7-us.googleusercontent.com/fXK85pf2n1zTFAsbxyhYKk4I_negGP3mNvXP_vE-_k-ppDlNQeCUPc-iKG7b2HjaeBaisWhkdDqPL8SoQb0QHW6eHI4-5Bra1GK7hrfIhzx9SW1SWgVJ9Nces5Vfza3fwYNug_nduW_8HJ-XB8eZwig) + +**The vision for SubQuery Network to encompass key web3 infrastructure components in a completely decentralised manner** + +### Starting with RPCs + +Our next step that we have completed is to decentralise the biggest infrastructure component for dApps - _Remote Procedure Call_ or RPC services. + +RPC services are still the main interface to the blockchain, under the hood of your favourite dApp, dozens of requests are passing through RPC providers to query and submit transactions to the network. They are the most critical part of the ecosystem, when one has an outage, [the effects reverberate across the industry](https://decrypt.co/47846/ethereum-backbone-infura-suffers-major-damage?ref=blog.subquery.network). + +Since SubQuery relies on performant and scalable RPCs to maximise our indexing speed, we already work extremely closely with RPC providers. On our quest to index over [115+ chains and counting](https://subquery.network/networks?ref=blog.subquery.network), we’ve discovered that the RPC ecosystem is very fractured: some ecosystems have excellent support, and some don’t, and that makes delivering an excellent indexing experience across all chains difficult. + +Across many smaller emergent networks, amateur RPC services operate to provide RPCs to various developers building on the network. These RPCs are usually run (at a loss) by the core network foundation team, and perhaps a collection of validators (for staking advertising purposes). Unfortunately for cost reasons, these RPCs are usually heavily pruned and rate limited, and have no upsell options for unrestricted access. As a result, dApp developers will often run a private RPC endpoint for their own use. This is expensive, frustrating, poses high barriers to entry, and results in no redundancy for dApp developers. + +For more established networks, one or more commercial providers may come and offer a freemium service, where there is a free plan/public endpoint, and a paid upsell to higher scale access. This serves dApp developers well, but the law of economies of scale dictate that networks tend towards a small number of hyperscale RPC providers who centralise the network and cause major outages that affect thousands of dApps when they go offline. They also extract huge economic value from a network and send that directly to big private cloud companies and VCs. + +We have built an alternative to these two dangerous equilibriums, and help decentralise everything.The SubQuery Network provides an open market for both data indexers and RPC providers and their consumers that: + +- Maintains low barriers of entry: Any node operator can join as a provider for any service on any network. +- Incentivises performance and cost: Node operators are automatically rewarded with requests based on these metrics, driving these values across the network. +- Encourages constant expansion to new chains: Node operators are free to onboard new chains and projects for first mover advantage, constantly expanding the network. + +### Enhancing RPCs - SubQuery’s Data Node + +The performance limitations of data indexers and many other applications have long been limited by the RPC endpoint. Developers have long focussed on building nodes to ensure efficient validation to ensure the safety of the network. As a result of this sacrifice, RPCs are extremely costly and they’re not at all optimised for querying. + +This is compounded by the rise of L2 chains where, with higher throughput, the query performance and cost are major outstanding issues to address. With limited querying capabilities, many don’t support complex querying languages or operations, making it inefficient to retrieve specific data. + +We have delivered the SubQuery Data Node, an enhanced and heavily-forked RPC node that is perfectly optimised for querying, especially on endpoints like `eth_getLog`, and the ability to filter transactions in a single API call. + +The Data Node is open source, allowing people to contribute, extend, or fork the implementation in any way. It supports leading layer-2s and other EVM networks initially, and they are optimised to run on the SubQuery Network in a decentralised way. + +Working together, the SubQuery Indexer and SubQuery Data Node provides the most performant indexing performance possible and in a completely decentralised way thanks to the SubQuery Network. + +Our node runners are able to run these data nodes on the network, bringing powerful and cost-effective RPC access to all, cementing SubQuery’s position as the fastest decentralised data indexer in web3. + +### Democratising RPCs - SubQuery’s Sharded Data Node + +In the final stage of our RPC journey, SubQuery will work to democratise RPCs (and solve [EIP-4444](https://eips.ethereum.org/EIPS/eip-4444?ref=blog.subquery.network)) in the process by delivering the Sharded Data Node, which will make RPCs cheaper to run and operate by node providers. + +In the last few months we’ve spoken with many RPC providers in the ecosystem. In many networks (in particular Cosmos), small scale RPC services operate to provide RPCs to various developers building on the network. Unfortunately for cost reasons, these RPCs are usually heavily pruned and rate limited and have no upsell options for unrestricted access. + +One of the key reasons for this is the sheer size of the node - an Ethereum archive requires about ~12 TB on Geth, an Osmosis archive is at least the same. This is an incredible cost that limits these nodes to large centralised infrastructure providers. + +SubQuery recognises that in order to decentralised RPCs correctly, you need to be able to make running these nodes easier and more accessible to everyday users. Currently the storage is made smaller by “pruning” data, which is intentionally discarding older information while cryptographically confirming that the recent data that is valid. This works fine for writing transactions, but means that indexers and other services are unable to query old data. + +SubQuery will extend its Data Node to support sharding, that is making each Data Node smaller by splitting up block ranges between node operators. Since SubQuery’s Data Node only runs within the boundaries of a specific block range, it does not need to constantly sync new data, allowing it to optimise further for query performance rather than validation and verification. + +The SubQuery Sharded node won’t just shard historical data, but also shard the historical state within the node. By itself, this won’t change much, but these sharded nodes will be optimised to run on the network, and the network will be designed to combine all these shards to expose a single unified endpoint that appears to cover the entire historical state of the chain. Developers will benefit from the entire historical state of the given network, and node operators will benefit from significantly lower running costs, creating a more cost efficient network. + +This is a revolutionary step forward for the RPC industry, and a potential solution to one of the great challenges facing older and larger blockchains with their state bloat size. This solution has the potential to help scale Ethereum, solve [EIP-4444](https://eips.ethereum.org/EIPS/eip-4444?ref=blog.subquery.network), and greatly support proliferation of Layer-2’s and rollups, while further democratising and decentralising the SubQuery Network. + +### Summary + +The future of SubQuery is not simply indexing web3 data, but pioneering a complete web3 infrastructure revolution. web3 middleware services like indexers and RPC providers are pivotal in blockchain dApp development, but there is a hidden truth behind the mask of “decentralisation” most of these middleware services wear. The reality is a significant reliance on centralised middleware components, which poses a substantial threat to the envisioned unstoppability of a web3 future. + +Our mission has expanded, and so has the opportunity space we’re going to be working in. We need to decentralise these services, without compromise. We’ve already delivered breakthroughs in decentralised data indexing, but our next steps will focus on enhancing the performance of RPCs with the SubQuery Data Node, and then to bring RPCs to the masses, with SubQuery’s Sharded Data Nodes. These steps together, will help unlock the next level of performance increases in web3. + +No other team today is better equipped at working to provide a holistic approach to solving this problem. In summary, our vision goes beyond data indexing; it's about revolutionising how data and infrastructure services are organised and accessed. + +Pioneering fast, flexible, and scalable decentralised infrastructure, we will help power web3's transition to an open, efficient and user-centric future. Join us in this journey. With SubQuery, it's not just about building for today, but architecting a decentralised, inclusive future. + +_Let's shape the future of web3, together._ \ No newline at end of file diff --git a/docs/id/subquery_network/welcome.md b/docs/id/subquery_network/welcome.md new file mode 100644 index 00000000000..53c14ae9c38 --- /dev/null +++ b/docs/id/subquery_network/welcome.md @@ -0,0 +1,283 @@ +--- +footer: false +lastUpdated: false +contributors: false +editLink: false +photoSwipe: false +--- + + +
+
+
+ SubQuery Network + + The SubQuery Network is the most scalable, reliable, and unified data infrastructure network. 1,000s of decentralised Indexers and RPC providers simplify the data layer for a myriad of applications and use cases. + +
+
+
+ +
+
+ + + One network, all your web3 data needs + +
+ +
+ + {{ item.title }} + {{ item.subtitle }} + + {{ content }} + + + + + + +
+ +
+ Anyone can participate + + There’s a role for everyone in the network, from highly technical + developers to those with some experience and blockchain beginners. Find + out how you can participate and be rewarded. + +
+
+ + {{ anyone.name }} + + {{ anyone.description }} + + + + +
+
+ + +
+ Get Started with the Network Today + Our decentralised network is live and vibrant +
+ + + {{ item.title }} + + {{ item.desc }} + + + +
+
+ + +
+
+ + diff --git a/docs/it/subquery_network/2024.md b/docs/it/subquery_network/2024.md new file mode 100644 index 00000000000..412a1f34fc1 --- /dev/null +++ b/docs/it/subquery_network/2024.md @@ -0,0 +1,62 @@ +# 2024 in Review: SubQuery’s Top 5 Milestones + +As we look back on 2024, we’re proud to call it a major “year of firsts” for us here at SubQuery. This year was filled with groundbreaking achievements, major launches, and remarkable community growth. The year has flown by but it also feels so long ago that we had our TGE, CEX Listing and SubQuery Network mainnet launch - all on the same day! + +Let’s celebrate some of the key milestones that made 2024 unforgettable. + +## 1. Mainnet Launch + +After an extremely successful Public Sale on 30 January 2024, selling out of SubQuery’s native token (SQT) in less than 2 hours, we worked very hard to launch the SubQuery Network mainnet on 23 February 2024. Powered by SQT and launched on Base, immediately users could consume and/or index data from over 150 networks ([now over 270 networks](https://subquery.network/networks)). + +Almost 1 year on and we have: + +- 46 globally distributed and highly skilled Node Operators servicing the network +- More than 330 million SQT staked and delegated in the Network +- Serving more than 50 million RPC requests every day +- An overall average APY of 22.28% and much higher for Node Operators (94.66%) + +## 2. SQT Token Generation Event + +Combined with the Mainnet launch, we ambitiously chose to do our TGE and day one CEX listing with Bybit on the same day (23 February 2024) as well. The SubQuery Token (SQT) is designed as a utility token that powers the SubQuery Network, providing an incentive for participation, as well as serving as a medium of exchange for transactions within the SubQuery Network. Consumers of data commit SQT in exchange for RPC queries or indexed data from our globally distributed Node Operators. + +Today, you can acquire SQT through any of these centralised exchange: + +- [Bybit](https://www.bybit.com/en/trade/spot/SQT/USDT) +- [Gate.io](https://www.gate.io/trade/SQT_USDT) +- [Crypto.com](https://crypto.com/exchange/trade/SQT_USD) +- [MEXC](https://www.mexc.com/exchange/SQT_USDT) + +SQT is on a number of DEX Pools however most liquidity is on Uniswap. + +- [Uniswap Pool on Ethereum](https://app.uniswap.org/explore/tokens/ethereum/0x09395a2A58DB45db0da254c7EAa5AC469D8bDc85) +- [Unsiwap Pool on Base](https://app.uniswap.org/explore/tokens/base/0x858c50c3af1913b0e849afdb74617388a1a5340d) + +## 3. Expansion into Decentralised RPCs + +This vision was announced at the end of 2023 but really came to fruition in 2024. We expanded our network capabilities by introducing support for Remote Procedure Call (RPC) services. This was the first step of expanding away from just a data indexer to a major decentralised infrastructure network, allowing us to support a more accessible, interoperable, and developer-friendly web3 ecosystem. + +Now serving RPC requests on 20+ networks, [get your decentralised RPCs from the SubQuery Network today](https://subquery.network/rpc/list/). + +### 4\. Launching Artificial Intelligence Tools + +SubQuery took its first steps into the AI space by launching decentralised AI inference model hosting on the SubQuery Network plus a new developer SDK called the AI App Framework. This massively expands the tools and services that we can offer to web3 builders across, all under one roof. + +The AI App Framework allows you to build, deploy, and run production AI apps on the SubQuery Network in a trusted and decentralised environment. AI apps are self-contained and easily scalable AI agents that you can use to power your intelligent applications. They are sandboxed to a trusted runner and can be easily distributed and scaled horizontally across the SubQuery Network. + +[Start building AI Apps today!](https://academy.subquery.network/ai/welcome.html) + +## 5. SubQuery Rebranding + +As we expanded into the Artificial Intelligence space, we felt a new look was warranted to match our new pursuit. So we rebranded to a complete new look with sleek chromatic details and a flower/root narrative. + +The flower and root theme symbolises SubQuery’s commitment to fostering innovation and growth within the blockchain community. The roots represent the deep, stable, and reliable infrastructure that SubQuery provides, while the flowers symbolise the diverse and vibrant dApps that developers can create with the help of this infrastructure. + +[Check out the new look](https://subquery.network/). + +## Looking Ahead to 2025 + +While 2024 was full of exciting milestones, we know this is just the beginning. With a stronger community, enhanced technology, and bold new goals, we’re ready to scale even greater heights in 2025. With our most recent [2024 roadmap](https://blog.subquery.network/subquery-releases-network-roadmap-for-2024/?lng=en) almost fully accomplished, stay tuned for a new version packed with ambitious plans. + +Thank you to everyone—developers, partners, and community members—who helped make this year possible. + +Here’s to many more firsts ahead! \ No newline at end of file diff --git a/docs/it/subquery_network/about.md b/docs/it/subquery_network/about.md new file mode 100644 index 00000000000..1699165773b --- /dev/null +++ b/docs/it/subquery_network/about.md @@ -0,0 +1,47 @@ +# About Us + +Our mission is to innovate Web3 infrastructure so builders can decentralise the next generation of applications - without compromise. + +Pioneering fast, flexible, and scalable decentralised infrastructure, we power Web3's transition to an open, efficient and user-centric future.Join us on our journey to build the future of web3 infrastructure. + +[Join our Discord Community](https://discord.com/invite/subquery) + +## Core team + +SubQuery has a deep bench of highly skilled talent of engineers, customer service, and operations personnel.Headquartered in Singapore, we have key representation in New Zealand, Lisbon, and Sydney. + +### Ian He - CTO and Co-Founder + +Ian forged his interest in blockchain during his tenure as the Technical Team Lead for Centrality where he led the development of core components of CENNZnet. Ian also led a team that won 2nd place in the world's first Substrate/Polkadot Hackathon in 2019. Prior to this, Ian obtained significant experience working on large-scale infrastructure working for Alipay and Yihaodian.com. + +### Scott Twiname - Principal Dev of SDK + +Scott has a large wealth of experience in blockchain development. He started out learning about blockchain in his own time and eventually got the opportunity to apply his knowledge as a senior developer at Sylo. He has worked on all facets of blockchain development from smart contracts, dapps, decentralised technologies and wallet integration for various networks including Bitcoin, Ethereum, Tezos and CENNZnet. + +### Marta Adamczyk - Head of Business Development + +Marta is a huge tech advocate, Web3 enthusiast and IT-meetup addict. She helps SubQuery customers develop and scale their projects by delivering technical consultancy, developer-oriented content and technical education. Former product evangelist, frontend developer, digital marketer, educator and sales manager with corporate and start-up experience. + +### Brittany Seales - Head of Marketing + +Brittany has a background in chemistry but since then she became the closest point of contact with SubQuery customers and helped ensure that every SubQuery customer gets an excellent on-boarding experience. Naturally Brittany is heavily integrated with the community and content marketing and has since taken over this area. Sadly, no amount of interaction with successful blockchain projects has give her the ability to pick a winning NFT! + +### James Bayly - Advisor + +Well-versed across the business, from product engineering to being the face of SubQuery, James is also a serial entrepreneur leading several tech companies. When he’s not in Berlin sipping cocktails, you’ll find him hiking up the Routeburn Track in New Zealand. + +## Our Manifesto + +In the new era of Web3, true power isn't bought – it's built with innovation and vision. +We are SubQuery, not just a company, but a revolution. Our mission: to lead the charge in decentralising the future. +We're pioneering an infrastructure that's fast, flexible, scalable – ready to power tomorrow's Web3 world. Crafting an open, efficient, and user-centric digital landscape. +For the visionaries, the forward-thinkers, the builders of tomorrow – SubQuery is your platform. +Join us in this journey. With SubQuery, it's not just about building for today, but architecting a decentralised, inclusive future. Let's shape the future of Web3, together. + +## About SubQuery + +SubQuery Network is innovating in web3 infrastructure with tools that empower builders to decentralise without compromise. SubQuery’s infrastructure network offers everything from data indexers, RPCs and AI agents - all fully decentralised and production ready. + +Our fast, flexible, and open data indexer supercharges thousands of dApps on nearly 300 networks. Our Sharded Data Node will provide breakthroughs in the RPC industry and our AI App framework makes building AI apps easier than ever before. We pioneer the web3 revolution for visionaries and forward-thinkers. We’re not just a company — we’re a movement driving an inclusive and decentralised web3 era, together. + +[Linktree](https://linktr.ee/subquerynetwork) | [Website](https://subquery.network) | [Discord](https://discord.com/invite/subquery) | [Telegram](https://t.me/subquerynetworkcommunity) | [Twitter](https://twitter.com/subquerynetwork) | [Blog](https://blog.subquery.network/?lng=en) | [Medium](https://medium.com/@subquery) | [LinkedIn](https://www.linkedin.com/company/subquery) | [YouTube](https://www.youtube.com/c/SubQueryNetwork) \ No newline at end of file diff --git a/docs/it/subquery_network/community.md b/docs/it/subquery_network/community.md new file mode 100644 index 00000000000..59c4aaeb078 --- /dev/null +++ b/docs/it/subquery_network/community.md @@ -0,0 +1,178 @@ +# SubQuery Network Community + +The key focus of the [SubQuery Foundation](./governance/foundation.md) and community is to ensure that there is enough support that anyone, from an expert blockchain team to a new hobbyist developer, can build their own Project. Together we can pave the way to a more decentralised future! + +## Connecting with others + +Discord is our main community for talking about SubQuery and learning more. You can join with [this link here](https://discord.com/invite/subquery). People most interested in the SubQuery Network will want to join `#network-general`, and Indexers or Delegators should join `#network-indexer-chat` or `#network-delegator-chat` respectively. + +When the conversation is deeper and requires more thought, we move the conversation to [our Forum](https://forum.subquery.network/). Here you will find longer topics, a history of all announcements to Network, and deeper conversation about the direction of the network. Feel free to join and start posting at [forum.subquery.network](https://forum.subquery.network/)! + +### Join the Node Operator community + +If you're a Node Operator on the Network, we strongly suggest that you keep up with the latest news, announcements, and tips by joining the following Discord channels: + +- `#network-announcements` +- `#network-general` +- `#network-services-release` +- `#network-indexer-announcements` +- `#network-indexer-general` + +## Contributing to Codebases + +SubQuery is open source and open to the community, if you want to contribute (e.g. add a feature, fix a bug, suggest an improvement, or even just fix a typo in our documentation), please review our [contributing guide](../miscellaneous/contributing.md). + +The following codebases are where you can find code for all the contracts, applications, and backend SubQuery projects. We're looking forward to seeing your contributions! + +### `network-app` + +dApp for indexers, consumers and delegators interact with SubQuery Network. + + + +### `network-airdrop-app` + +dApp for users to interact with the SubQuery airdrop contract. + + + +### `network-contracts` + +Contracts for SubQuery Network. + + + +You can find smart contract addresses for all network contracts here in [GitHub](https://github.com/subquery/network-contracts/blob/develop/publish/mainnet.json) + +### `network-app-backend` + +SubQuery project for the backend of the SubQuery App. + + + +### `network-airdrop-app-backend` + +SubQuery project for the backend of the SubQuery Airdrop App. + + + +### `network-swap-app-backend` + +SubQuery project for the backend of the SubQuery Swap App. + + + +### `network-indexer-services` + +Services that Indexers run to connect and serve data to the SubQuery Network. + + + +### `network-clients` + +Client SDKs for SubQuery Network. + + + +### `subquery-component-library` + +React UI component library for SubQuery dApps. + + + +## Community Tools + +There are a number of community built tools that you can use to help your SubQuery Network experience. Feel free to contribute your own. + +:::warning +Please note that none of these tools have been endorsed by the SubQuery team and descriptions have been written by third parties. This section is open for contribution by all. + +Please research and use at your own risk +::: + +### SQTScan + +[SQTScan](https://sqtscan.com/?ref=blog.subquery.network) is a ***community-owned application*** designed specifically to help expert users such as Node Operators and Delegators to gain a deeper understanding of historical rewards on the SubQuery Network and optimise their participation. + +SQT Scan helps expert users (Node Operators and Delegators) with: + +1. **Education:** Understand how their rewards are calculated and how they should make decisions +2. **Compare Opportunities:** Decide which projects to deploy based on historical rewards +3. **Compare Others:** Compare their APY with other Node Operators, overall and by project, to see how they're performing relatively +4. **APY Maximisation:** Identify ways to increase their APY + +If you would like to add your support, suggest improvements or new features, or even contribute code, it is welcomed! + +Links + +- [SQTSCan](https://sqtscan.com) +- [Github](https://github.com/HuberTRoy/subquery-sqtscan) + +### Indexer Monitoring Tools (by web3cdn.network) + +Five products: +1. **Toolkit:** A toolkit contains everything you need to index, monitor and properly access from any device +2. **Telegram Uptime Bot:** Eagle Eye is a bot which will provide you live updates in Telegram on the uptime of your indexer +3. **UpdateHunter** +4. **Snapshots** +5. **Snapshots Toolkit** + +Toolkit Features: + +- Extended monitoring of all indexer parameters, sync time, balances, issues. Metrics also support Alerting rules +- Flags problems that have arisen through monitoring and help you to not miss rewards. +- Makes your indexer and infrastructure secure +- Ease of updating without the risk of changing important parameters +- Secured access to dangerous zone with your own VPN, Access from mobile devices to monitoring, and internal services in any time. +- Very easy installation and user error protection + +Eagle Eye Telegram Bot Notifications: + +- Provide reports on your indexer's uptime - help you to know about an errors in advance and not lose funds. +- If your indexer is offline +- If your project is somehow unavailable +- If you do not have enough funds +- If your certificate is about to expire +- And more + +UpdateHunter: + + - A tool that notifies you when a project is updated or a new project is created, providing complete documentation to enable fast and secure upgrades. + - It scans the blockchain and alerts an indexer via a Telegram channel about updates, automati­cally generating instructions and SQL queries. + - The bot integrates with GitHub, posting documentation updates to a public repository. + + Snapshots: + + - Service generates daily snapshots for all active projects + - This service is ideal if your indexer: + - Is newly deployed and you want to avoid ~1 month of downtime for project synchronization + - Has experienced data loss (corrupted disk, hardware failures, or software issues) + + Snapshots Toolkit: + + - Open Source toolkit for an own snapshot generator. With this repository indexer can generate its own snapshots. + +Links + +- [Toolkit Github](https://toolkit.subquery.dev/) +- [Eagle Eye Telegram Bot](https://eagleeye.subquery.dev/) +- [UpdateHunter](https://eagleeye.subquery.dev/updates) +- [Snapshots](https://snapshots.subquery.dev/) +- [Snapshots Toolkit](https://snapshots.subquery.dev/toolkit) + +### Kepler Network Dashboard (by DappLooker) + +To monitor the progress and performance of the Kepler Network, DappLooker has created a dashboard that displays the following key metrics: + +- Active Indexers / Delegators: The number of Indexers and Delegators who are actively participating in the Kepler Network. +- Weekly Indexer Stake / Delegation: The amount of kSQT that Indexers and Delegators have staked on the Kepler Network in the past week. +- Weekly Rewards: The amount of kSQT that Indexers have earned as rewards for serving data requests on the Kepler Network in the past week. +- Stake Distribution: The distribution of kSQT stakes between Indexers and Delegators on the Kepler Network. + +To make the data more accessible and user-friendly, DappLooker has also made the SubQuery Kepler data publicly available for everyone. This means that anyone can create custom dashboards tailored to their needs using the indexed data from the Kepler Network. + +Links + +- [Dashboard](https://dapplooker.com/dashboard/subquery-kepler-network-dashboard-577) +- [Indexed Dataset](https://analytics.dapplooker.com/browse/2/schema/subquery_kepler) +- [Announcement Article](https://blog.dapplooker.com/dapplooker-integrates-subquery-kepler-network-to-provide-analytics-and-dashboard-solution-to-web3-fb0c5aeea899) diff --git a/docs/it/subquery_network/faq.md b/docs/it/subquery_network/faq.md new file mode 100644 index 00000000000..a298d22efe5 --- /dev/null +++ b/docs/it/subquery_network/faq.md @@ -0,0 +1,78 @@ +# Frequently Asked Questions + +FAQs for specific network participants: + +- [Node Operators](./node_operators/setup/faq.md) +- [Consumers](./consumers/faq.md) + +## Proof-of-indexing + +[Proof Of Index](./introduction/proof-of-index.md) + +## How do you ensure indexed data accuracy? + +Ensured by [Proof Of Index](./introduction/proof-of-index.md) + +## Are there a list of RPC providers that can provide support for \_\_\_ chain? + +SubQuery Network is decentralised, so we can't say what individual node operators would decide to serve you, nor can we say what infrastructure the node operators use and where it is hosted + +## What is the integration and deployment timeline for RPCs? + +SubQuery team can enable the RPC in a few days depending on how long an archive node on your network would take to sync. + +## Where is your/provider's infra hosted? + +Depends on the provider, SubQuery don't dictate this. But SubQuery gateway encourages competition to provide high performance, low latency, and geographically decentralised services. Most providers are running on their own bare metal for cost considerations + +## Is there a testnet environment? + +Yes, be sure to check https://dev.thechaindata.com/ + +## Is there a meaning behind SubQuery's name? + +The name "SubQuery" refers to its function in the blockchain ecosystem. A subquery is essentially a query within another query, allowing users to access data more efficiently. It is a powerful tool for indexing and querying blockchain data. + +## What was the first network that SubQuery first supported? + +SubQuery initially supported the Polkadot network, focusing on indexing and querying data for the Polkadot and its parachains. + +## How many networks do SubQuery support now? + +As of now, SubQuery supports multiple networks, including Polkadot, Kusama, Ethereum, and many others, expanding its reach to a wide array of blockchain ecosystems. + +## How does SubQuery improve blockchain data access? + +SubQuery enhances blockchain data access by providing an indexing layer that aggregates and organizes data from blockchain networks. This allows developers and applications to quickly retrieve and interact with data in a structured and efficient manner. + +## How does SubQuery differ from traditional block explorers? + +Traditional block explorers allow users to explore blockchain data in a static, non-queryable format. SubQuery, on the other hand, provides dynamic and customizable data querying, giving developers the ability to filter, process, and retrieve data in real-time for their applications. + +## What programming languages does SubQuery support? + +SubQuery primarily supports JavaScript and TypeScript for building queries and processing data. Developers can use these languages to define the structure and logic for data retrieval from supported networks. + +## Is SubQuery open-source? + +Yes, SubQuery is open-source. It encourages developers to contribute to its growth and use its tools to build decentralized applications (dApps) more efficiently. The source code is available on GitHub. + +## What are the main use cases for SubQuery? + +SubQuery is used for various purposes, such as: + +- Building decentralized applications (dApps) that need to access blockchain data. +- Indexing and querying blockchain data for analysis and reporting. +- Creating custom data solutions for blockchain ecosystems and decentralized finance (DeFi) platforms. + +## Can I deploy SubQuery on my own infrastructure? + +Yes, SubQuery can be deployed on your own infrastructure, whether on-premise or in the cloud. It offers flexibility to users who want complete control over their indexing and querying solutions. + +## How does SubQuery handle data updates and changes? + +SubQuery continuously updates its data by monitoring blockchain events in real-time. This ensures that the indexed data is always up to date, and any changes to the blockchain are reflected immediately in the data queries. + +## How can I get started with SubQuery? + +To get started with SubQuery, you can visit their official documentation, which provides step-by-step guides on setting up a project, writing queries, and deploying them on supported networks. The community also offers support through forums and Discord. diff --git a/docs/it/subquery_network/infra-changes.md b/docs/it/subquery_network/infra-changes.md new file mode 100644 index 00000000000..b30b5fa306d --- /dev/null +++ b/docs/it/subquery_network/infra-changes.md @@ -0,0 +1,109 @@ +# Redefining Web3: SubQuery Network’s Bold Infrastructure Evolution + +Back in December 2023, we announced the evolution of SubQuery, in which we aim to transition from simply indexing web3 data to pioneering a complete web3 infrastructure revolution. + +Over the last year, as we’ve been building out our data indexing service and network, we realised our network is in a prime position to address broader centralisation issues throughout the web3 infrastructure landscape. + +Our mission has expanded, and so has the opportunity space we’re going to be working in. + +Read on to learn about the challenges we’re taking on and the next steps we’re taking to play a bigger role in decentralising the future. + +### The Web3 Infrastructure Landscape + +Web3 middleware services like indexers, RPCs, oracles and storage services are pivotal in blockchain dApp development. In fact, the utilisation of these middleware services is what sets apart successful, large-scale, production dApps - they accelerate performance and can scale to thousands of users, while providing a superior developer experience to bring in more users, TVL, and value. Indexers and RPCs shoulder the heavy lifting, standing as mission-critical services that underpin the functionality and efficiency of web3 applications. + +![](https://lh7-us.googleusercontent.com/2lbQyLR4fxrgV2dTqljyFV6bECXrfq3anA2k_qM6gJuWdSN01dHrVjIFU6OZeFXXJv57dwaXNQ6_lKdGtLK9YDWr0EdS7yDDv0BwZfFXT_j6aw-iu7bDxIS5ZkgliPD2mY_l5kbJXGKEqI6OWuZIEwk) + +**The current segregated web3 infrastructure landscape** + +Data indexers (like SubQuery) speed up data retrieval, enhancing performance and response times for users. They also simplify data by transforming raw blockchain information into more digestible formats, facilitating efficient development and a smooth user experience. + +Meanwhile, RPCs are pivotal for communication between blockchain nodes and external entities, facilitating data retrieval, smart contract interactions, and transaction submissions. Under the hood of your favourite dApp, tens of requests are passing through RPC providers to query and submit transactions to the network. + +While these middleware services are integral to a successful dApp, there is a significant issue that needs to be addressed. + +### Web3’s Dirty Little Secret + +There is a hidden truth behind the mask of “decentralisation” most of these middleware services wear. The reality is that many leading dApps have a significant reliance on centralised middleware components. This centralisation poses a substantial threat to the envisioned unstoppability of a web3 future, at any given moment, a single entity can undermine supposedly decentralised applications. + +Nowhere is this more apparent with RPC providers, and to a lesser extent, data indexers. These crucial services distinguish the scalable, reliable, and polished dApps from rudimentary applications that go without. But due to historical challenges in the process of decentralisation, for a long time, this has been a compromise most apps have accepted. + +The call for decentralised alternatives to these pivotal middleware services is essential for the foundation of the next generation of dApps to build upon. We need to decentralise these services, without compromise. + +### SubQuery Network Evolution Revealed + +At the start we set out to create a viable decentralised solution to the data indexing problem. + +Web3 developers face great difficulties aggregating and organising data to power dApps, and SubQuery has helped thousands of developers building the world's best and biggest networks, dApps, and analytics tools by providing fast and performant data indexing. + +In 2022 we launched Kepler Network, a pre-mainnet release that enabled us to bootstrap the network sustainably by bringing onboard proficient indexers and projects. The success of Kepler lead to the realisation that the ecosystem we’ve built could bring benefits for more than just decentralised data indexing, but for middleware infrastructure as a whole. The key components of the network we have built and deployed - reward and pricing rails, service verification tools, and dispute resolution processes - are valuable for others verticals. + +Knowing that the SubQuery Network could give our existing community of top node runners a solution to trustlessly receive rewards for running data indexing infrastructure, why couldn’t it work for those other services, for other parts of the dApp tech stack? + +We realised the full potential of the SubQuery Network mainnet should not be limited to just data indexing; its fundamental contracts, tools, and reward flows enable it to be so much more. By harnessing the power of the existing participants and mechanisms, the SubQuery Network is ready to extend to various infrastructure verticals. It dawned on us that there is a massive opportunity ahead of us when we think holistically about the entire developer experience. + +> With the launch of mainnet, the SubQuery Network will emerge as a solution to _decentralise everything_, revolutionising the entire developer experience in web3. + +![](https://lh7-us.googleusercontent.com/fXK85pf2n1zTFAsbxyhYKk4I_negGP3mNvXP_vE-_k-ppDlNQeCUPc-iKG7b2HjaeBaisWhkdDqPL8SoQb0QHW6eHI4-5Bra1GK7hrfIhzx9SW1SWgVJ9Nces5Vfza3fwYNug_nduW_8HJ-XB8eZwig) + +**The vision for SubQuery Network to encompass key web3 infrastructure components in a completely decentralised manner** + +### Starting with RPCs + +Our next step that we have completed is to decentralise the biggest infrastructure component for dApps - _Remote Procedure Call_ or RPC services. + +RPC services are still the main interface to the blockchain, under the hood of your favourite dApp, dozens of requests are passing through RPC providers to query and submit transactions to the network. They are the most critical part of the ecosystem, when one has an outage, [the effects reverberate across the industry](https://decrypt.co/47846/ethereum-backbone-infura-suffers-major-damage?ref=blog.subquery.network). + +Since SubQuery relies on performant and scalable RPCs to maximise our indexing speed, we already work extremely closely with RPC providers. On our quest to index over [115+ chains and counting](https://subquery.network/networks?ref=blog.subquery.network), we’ve discovered that the RPC ecosystem is very fractured: some ecosystems have excellent support, and some don’t, and that makes delivering an excellent indexing experience across all chains difficult. + +Across many smaller emergent networks, amateur RPC services operate to provide RPCs to various developers building on the network. These RPCs are usually run (at a loss) by the core network foundation team, and perhaps a collection of validators (for staking advertising purposes). Unfortunately for cost reasons, these RPCs are usually heavily pruned and rate limited, and have no upsell options for unrestricted access. As a result, dApp developers will often run a private RPC endpoint for their own use. This is expensive, frustrating, poses high barriers to entry, and results in no redundancy for dApp developers. + +For more established networks, one or more commercial providers may come and offer a freemium service, where there is a free plan/public endpoint, and a paid upsell to higher scale access. This serves dApp developers well, but the law of economies of scale dictate that networks tend towards a small number of hyperscale RPC providers who centralise the network and cause major outages that affect thousands of dApps when they go offline. They also extract huge economic value from a network and send that directly to big private cloud companies and VCs. + +We have built an alternative to these two dangerous equilibriums, and help decentralise everything.The SubQuery Network provides an open market for both data indexers and RPC providers and their consumers that: + +- Maintains low barriers of entry: Any node operator can join as a provider for any service on any network. +- Incentivises performance and cost: Node operators are automatically rewarded with requests based on these metrics, driving these values across the network. +- Encourages constant expansion to new chains: Node operators are free to onboard new chains and projects for first mover advantage, constantly expanding the network. + +### Enhancing RPCs - SubQuery’s Data Node + +The performance limitations of data indexers and many other applications have long been limited by the RPC endpoint. Developers have long focussed on building nodes to ensure efficient validation to ensure the safety of the network. As a result of this sacrifice, RPCs are extremely costly and they’re not at all optimised for querying. + +This is compounded by the rise of L2 chains where, with higher throughput, the query performance and cost are major outstanding issues to address. With limited querying capabilities, many don’t support complex querying languages or operations, making it inefficient to retrieve specific data. + +We have delivered the SubQuery Data Node, an enhanced and heavily-forked RPC node that is perfectly optimised for querying, especially on endpoints like `eth_getLog`, and the ability to filter transactions in a single API call. + +The Data Node is open source, allowing people to contribute, extend, or fork the implementation in any way. It supports leading layer-2s and other EVM networks initially, and they are optimised to run on the SubQuery Network in a decentralised way. + +Working together, the SubQuery Indexer and SubQuery Data Node provides the most performant indexing performance possible and in a completely decentralised way thanks to the SubQuery Network. + +Our node runners are able to run these data nodes on the network, bringing powerful and cost-effective RPC access to all, cementing SubQuery’s position as the fastest decentralised data indexer in web3. + +### Democratising RPCs - SubQuery’s Sharded Data Node + +In the final stage of our RPC journey, SubQuery will work to democratise RPCs (and solve [EIP-4444](https://eips.ethereum.org/EIPS/eip-4444?ref=blog.subquery.network)) in the process by delivering the Sharded Data Node, which will make RPCs cheaper to run and operate by node providers. + +In the last few months we’ve spoken with many RPC providers in the ecosystem. In many networks (in particular Cosmos), small scale RPC services operate to provide RPCs to various developers building on the network. Unfortunately for cost reasons, these RPCs are usually heavily pruned and rate limited and have no upsell options for unrestricted access. + +One of the key reasons for this is the sheer size of the node - an Ethereum archive requires about ~12 TB on Geth, an Osmosis archive is at least the same. This is an incredible cost that limits these nodes to large centralised infrastructure providers. + +SubQuery recognises that in order to decentralised RPCs correctly, you need to be able to make running these nodes easier and more accessible to everyday users. Currently the storage is made smaller by “pruning” data, which is intentionally discarding older information while cryptographically confirming that the recent data that is valid. This works fine for writing transactions, but means that indexers and other services are unable to query old data. + +SubQuery will extend its Data Node to support sharding, that is making each Data Node smaller by splitting up block ranges between node operators. Since SubQuery’s Data Node only runs within the boundaries of a specific block range, it does not need to constantly sync new data, allowing it to optimise further for query performance rather than validation and verification. + +The SubQuery Sharded node won’t just shard historical data, but also shard the historical state within the node. By itself, this won’t change much, but these sharded nodes will be optimised to run on the network, and the network will be designed to combine all these shards to expose a single unified endpoint that appears to cover the entire historical state of the chain. Developers will benefit from the entire historical state of the given network, and node operators will benefit from significantly lower running costs, creating a more cost efficient network. + +This is a revolutionary step forward for the RPC industry, and a potential solution to one of the great challenges facing older and larger blockchains with their state bloat size. This solution has the potential to help scale Ethereum, solve [EIP-4444](https://eips.ethereum.org/EIPS/eip-4444?ref=blog.subquery.network), and greatly support proliferation of Layer-2’s and rollups, while further democratising and decentralising the SubQuery Network. + +### Summary + +The future of SubQuery is not simply indexing web3 data, but pioneering a complete web3 infrastructure revolution. web3 middleware services like indexers and RPC providers are pivotal in blockchain dApp development, but there is a hidden truth behind the mask of “decentralisation” most of these middleware services wear. The reality is a significant reliance on centralised middleware components, which poses a substantial threat to the envisioned unstoppability of a web3 future. + +Our mission has expanded, and so has the opportunity space we’re going to be working in. We need to decentralise these services, without compromise. We’ve already delivered breakthroughs in decentralised data indexing, but our next steps will focus on enhancing the performance of RPCs with the SubQuery Data Node, and then to bring RPCs to the masses, with SubQuery’s Sharded Data Nodes. These steps together, will help unlock the next level of performance increases in web3. + +No other team today is better equipped at working to provide a holistic approach to solving this problem. In summary, our vision goes beyond data indexing; it's about revolutionising how data and infrastructure services are organised and accessed. + +Pioneering fast, flexible, and scalable decentralised infrastructure, we will help power web3's transition to an open, efficient and user-centric future. Join us in this journey. With SubQuery, it's not just about building for today, but architecting a decentralised, inclusive future. + +_Let's shape the future of web3, together._ \ No newline at end of file diff --git a/docs/it/subquery_network/welcome.md b/docs/it/subquery_network/welcome.md new file mode 100644 index 00000000000..53c14ae9c38 --- /dev/null +++ b/docs/it/subquery_network/welcome.md @@ -0,0 +1,283 @@ +--- +footer: false +lastUpdated: false +contributors: false +editLink: false +photoSwipe: false +--- + + +
+
+
+ SubQuery Network + + The SubQuery Network is the most scalable, reliable, and unified data infrastructure network. 1,000s of decentralised Indexers and RPC providers simplify the data layer for a myriad of applications and use cases. + +
+
+
+ +
+
+ + + One network, all your web3 data needs + +
+ +
+ + {{ item.title }} + {{ item.subtitle }} + + {{ content }} + + + + + + +
+ +
+ Anyone can participate + + There’s a role for everyone in the network, from highly technical + developers to those with some experience and blockchain beginners. Find + out how you can participate and be rewarded. + +
+
+ + {{ anyone.name }} + + {{ anyone.description }} + + + + +
+
+ + +
+ Get Started with the Network Today + Our decentralised network is live and vibrant +
+ + + {{ item.title }} + + {{ item.desc }} + + + +
+
+ + +
+
+ + diff --git a/docs/ja/subquery_network/2024.md b/docs/ja/subquery_network/2024.md new file mode 100644 index 00000000000..412a1f34fc1 --- /dev/null +++ b/docs/ja/subquery_network/2024.md @@ -0,0 +1,62 @@ +# 2024 in Review: SubQuery’s Top 5 Milestones + +As we look back on 2024, we’re proud to call it a major “year of firsts” for us here at SubQuery. This year was filled with groundbreaking achievements, major launches, and remarkable community growth. The year has flown by but it also feels so long ago that we had our TGE, CEX Listing and SubQuery Network mainnet launch - all on the same day! + +Let’s celebrate some of the key milestones that made 2024 unforgettable. + +## 1. Mainnet Launch + +After an extremely successful Public Sale on 30 January 2024, selling out of SubQuery’s native token (SQT) in less than 2 hours, we worked very hard to launch the SubQuery Network mainnet on 23 February 2024. Powered by SQT and launched on Base, immediately users could consume and/or index data from over 150 networks ([now over 270 networks](https://subquery.network/networks)). + +Almost 1 year on and we have: + +- 46 globally distributed and highly skilled Node Operators servicing the network +- More than 330 million SQT staked and delegated in the Network +- Serving more than 50 million RPC requests every day +- An overall average APY of 22.28% and much higher for Node Operators (94.66%) + +## 2. SQT Token Generation Event + +Combined with the Mainnet launch, we ambitiously chose to do our TGE and day one CEX listing with Bybit on the same day (23 February 2024) as well. The SubQuery Token (SQT) is designed as a utility token that powers the SubQuery Network, providing an incentive for participation, as well as serving as a medium of exchange for transactions within the SubQuery Network. Consumers of data commit SQT in exchange for RPC queries or indexed data from our globally distributed Node Operators. + +Today, you can acquire SQT through any of these centralised exchange: + +- [Bybit](https://www.bybit.com/en/trade/spot/SQT/USDT) +- [Gate.io](https://www.gate.io/trade/SQT_USDT) +- [Crypto.com](https://crypto.com/exchange/trade/SQT_USD) +- [MEXC](https://www.mexc.com/exchange/SQT_USDT) + +SQT is on a number of DEX Pools however most liquidity is on Uniswap. + +- [Uniswap Pool on Ethereum](https://app.uniswap.org/explore/tokens/ethereum/0x09395a2A58DB45db0da254c7EAa5AC469D8bDc85) +- [Unsiwap Pool on Base](https://app.uniswap.org/explore/tokens/base/0x858c50c3af1913b0e849afdb74617388a1a5340d) + +## 3. Expansion into Decentralised RPCs + +This vision was announced at the end of 2023 but really came to fruition in 2024. We expanded our network capabilities by introducing support for Remote Procedure Call (RPC) services. This was the first step of expanding away from just a data indexer to a major decentralised infrastructure network, allowing us to support a more accessible, interoperable, and developer-friendly web3 ecosystem. + +Now serving RPC requests on 20+ networks, [get your decentralised RPCs from the SubQuery Network today](https://subquery.network/rpc/list/). + +### 4\. Launching Artificial Intelligence Tools + +SubQuery took its first steps into the AI space by launching decentralised AI inference model hosting on the SubQuery Network plus a new developer SDK called the AI App Framework. This massively expands the tools and services that we can offer to web3 builders across, all under one roof. + +The AI App Framework allows you to build, deploy, and run production AI apps on the SubQuery Network in a trusted and decentralised environment. AI apps are self-contained and easily scalable AI agents that you can use to power your intelligent applications. They are sandboxed to a trusted runner and can be easily distributed and scaled horizontally across the SubQuery Network. + +[Start building AI Apps today!](https://academy.subquery.network/ai/welcome.html) + +## 5. SubQuery Rebranding + +As we expanded into the Artificial Intelligence space, we felt a new look was warranted to match our new pursuit. So we rebranded to a complete new look with sleek chromatic details and a flower/root narrative. + +The flower and root theme symbolises SubQuery’s commitment to fostering innovation and growth within the blockchain community. The roots represent the deep, stable, and reliable infrastructure that SubQuery provides, while the flowers symbolise the diverse and vibrant dApps that developers can create with the help of this infrastructure. + +[Check out the new look](https://subquery.network/). + +## Looking Ahead to 2025 + +While 2024 was full of exciting milestones, we know this is just the beginning. With a stronger community, enhanced technology, and bold new goals, we’re ready to scale even greater heights in 2025. With our most recent [2024 roadmap](https://blog.subquery.network/subquery-releases-network-roadmap-for-2024/?lng=en) almost fully accomplished, stay tuned for a new version packed with ambitious plans. + +Thank you to everyone—developers, partners, and community members—who helped make this year possible. + +Here’s to many more firsts ahead! \ No newline at end of file diff --git a/docs/ja/subquery_network/about.md b/docs/ja/subquery_network/about.md new file mode 100644 index 00000000000..1699165773b --- /dev/null +++ b/docs/ja/subquery_network/about.md @@ -0,0 +1,47 @@ +# About Us + +Our mission is to innovate Web3 infrastructure so builders can decentralise the next generation of applications - without compromise. + +Pioneering fast, flexible, and scalable decentralised infrastructure, we power Web3's transition to an open, efficient and user-centric future.Join us on our journey to build the future of web3 infrastructure. + +[Join our Discord Community](https://discord.com/invite/subquery) + +## Core team + +SubQuery has a deep bench of highly skilled talent of engineers, customer service, and operations personnel.Headquartered in Singapore, we have key representation in New Zealand, Lisbon, and Sydney. + +### Ian He - CTO and Co-Founder + +Ian forged his interest in blockchain during his tenure as the Technical Team Lead for Centrality where he led the development of core components of CENNZnet. Ian also led a team that won 2nd place in the world's first Substrate/Polkadot Hackathon in 2019. Prior to this, Ian obtained significant experience working on large-scale infrastructure working for Alipay and Yihaodian.com. + +### Scott Twiname - Principal Dev of SDK + +Scott has a large wealth of experience in blockchain development. He started out learning about blockchain in his own time and eventually got the opportunity to apply his knowledge as a senior developer at Sylo. He has worked on all facets of blockchain development from smart contracts, dapps, decentralised technologies and wallet integration for various networks including Bitcoin, Ethereum, Tezos and CENNZnet. + +### Marta Adamczyk - Head of Business Development + +Marta is a huge tech advocate, Web3 enthusiast and IT-meetup addict. She helps SubQuery customers develop and scale their projects by delivering technical consultancy, developer-oriented content and technical education. Former product evangelist, frontend developer, digital marketer, educator and sales manager with corporate and start-up experience. + +### Brittany Seales - Head of Marketing + +Brittany has a background in chemistry but since then she became the closest point of contact with SubQuery customers and helped ensure that every SubQuery customer gets an excellent on-boarding experience. Naturally Brittany is heavily integrated with the community and content marketing and has since taken over this area. Sadly, no amount of interaction with successful blockchain projects has give her the ability to pick a winning NFT! + +### James Bayly - Advisor + +Well-versed across the business, from product engineering to being the face of SubQuery, James is also a serial entrepreneur leading several tech companies. When he’s not in Berlin sipping cocktails, you’ll find him hiking up the Routeburn Track in New Zealand. + +## Our Manifesto + +In the new era of Web3, true power isn't bought – it's built with innovation and vision. +We are SubQuery, not just a company, but a revolution. Our mission: to lead the charge in decentralising the future. +We're pioneering an infrastructure that's fast, flexible, scalable – ready to power tomorrow's Web3 world. Crafting an open, efficient, and user-centric digital landscape. +For the visionaries, the forward-thinkers, the builders of tomorrow – SubQuery is your platform. +Join us in this journey. With SubQuery, it's not just about building for today, but architecting a decentralised, inclusive future. Let's shape the future of Web3, together. + +## About SubQuery + +SubQuery Network is innovating in web3 infrastructure with tools that empower builders to decentralise without compromise. SubQuery’s infrastructure network offers everything from data indexers, RPCs and AI agents - all fully decentralised and production ready. + +Our fast, flexible, and open data indexer supercharges thousands of dApps on nearly 300 networks. Our Sharded Data Node will provide breakthroughs in the RPC industry and our AI App framework makes building AI apps easier than ever before. We pioneer the web3 revolution for visionaries and forward-thinkers. We’re not just a company — we’re a movement driving an inclusive and decentralised web3 era, together. + +[Linktree](https://linktr.ee/subquerynetwork) | [Website](https://subquery.network) | [Discord](https://discord.com/invite/subquery) | [Telegram](https://t.me/subquerynetworkcommunity) | [Twitter](https://twitter.com/subquerynetwork) | [Blog](https://blog.subquery.network/?lng=en) | [Medium](https://medium.com/@subquery) | [LinkedIn](https://www.linkedin.com/company/subquery) | [YouTube](https://www.youtube.com/c/SubQueryNetwork) \ No newline at end of file diff --git a/docs/ja/subquery_network/community.md b/docs/ja/subquery_network/community.md new file mode 100644 index 00000000000..59c4aaeb078 --- /dev/null +++ b/docs/ja/subquery_network/community.md @@ -0,0 +1,178 @@ +# SubQuery Network Community + +The key focus of the [SubQuery Foundation](./governance/foundation.md) and community is to ensure that there is enough support that anyone, from an expert blockchain team to a new hobbyist developer, can build their own Project. Together we can pave the way to a more decentralised future! + +## Connecting with others + +Discord is our main community for talking about SubQuery and learning more. You can join with [this link here](https://discord.com/invite/subquery). People most interested in the SubQuery Network will want to join `#network-general`, and Indexers or Delegators should join `#network-indexer-chat` or `#network-delegator-chat` respectively. + +When the conversation is deeper and requires more thought, we move the conversation to [our Forum](https://forum.subquery.network/). Here you will find longer topics, a history of all announcements to Network, and deeper conversation about the direction of the network. Feel free to join and start posting at [forum.subquery.network](https://forum.subquery.network/)! + +### Join the Node Operator community + +If you're a Node Operator on the Network, we strongly suggest that you keep up with the latest news, announcements, and tips by joining the following Discord channels: + +- `#network-announcements` +- `#network-general` +- `#network-services-release` +- `#network-indexer-announcements` +- `#network-indexer-general` + +## Contributing to Codebases + +SubQuery is open source and open to the community, if you want to contribute (e.g. add a feature, fix a bug, suggest an improvement, or even just fix a typo in our documentation), please review our [contributing guide](../miscellaneous/contributing.md). + +The following codebases are where you can find code for all the contracts, applications, and backend SubQuery projects. We're looking forward to seeing your contributions! + +### `network-app` + +dApp for indexers, consumers and delegators interact with SubQuery Network. + + + +### `network-airdrop-app` + +dApp for users to interact with the SubQuery airdrop contract. + + + +### `network-contracts` + +Contracts for SubQuery Network. + + + +You can find smart contract addresses for all network contracts here in [GitHub](https://github.com/subquery/network-contracts/blob/develop/publish/mainnet.json) + +### `network-app-backend` + +SubQuery project for the backend of the SubQuery App. + + + +### `network-airdrop-app-backend` + +SubQuery project for the backend of the SubQuery Airdrop App. + + + +### `network-swap-app-backend` + +SubQuery project for the backend of the SubQuery Swap App. + + + +### `network-indexer-services` + +Services that Indexers run to connect and serve data to the SubQuery Network. + + + +### `network-clients` + +Client SDKs for SubQuery Network. + + + +### `subquery-component-library` + +React UI component library for SubQuery dApps. + + + +## Community Tools + +There are a number of community built tools that you can use to help your SubQuery Network experience. Feel free to contribute your own. + +:::warning +Please note that none of these tools have been endorsed by the SubQuery team and descriptions have been written by third parties. This section is open for contribution by all. + +Please research and use at your own risk +::: + +### SQTScan + +[SQTScan](https://sqtscan.com/?ref=blog.subquery.network) is a ***community-owned application*** designed specifically to help expert users such as Node Operators and Delegators to gain a deeper understanding of historical rewards on the SubQuery Network and optimise their participation. + +SQT Scan helps expert users (Node Operators and Delegators) with: + +1. **Education:** Understand how their rewards are calculated and how they should make decisions +2. **Compare Opportunities:** Decide which projects to deploy based on historical rewards +3. **Compare Others:** Compare their APY with other Node Operators, overall and by project, to see how they're performing relatively +4. **APY Maximisation:** Identify ways to increase their APY + +If you would like to add your support, suggest improvements or new features, or even contribute code, it is welcomed! + +Links + +- [SQTSCan](https://sqtscan.com) +- [Github](https://github.com/HuberTRoy/subquery-sqtscan) + +### Indexer Monitoring Tools (by web3cdn.network) + +Five products: +1. **Toolkit:** A toolkit contains everything you need to index, monitor and properly access from any device +2. **Telegram Uptime Bot:** Eagle Eye is a bot which will provide you live updates in Telegram on the uptime of your indexer +3. **UpdateHunter** +4. **Snapshots** +5. **Snapshots Toolkit** + +Toolkit Features: + +- Extended monitoring of all indexer parameters, sync time, balances, issues. Metrics also support Alerting rules +- Flags problems that have arisen through monitoring and help you to not miss rewards. +- Makes your indexer and infrastructure secure +- Ease of updating without the risk of changing important parameters +- Secured access to dangerous zone with your own VPN, Access from mobile devices to monitoring, and internal services in any time. +- Very easy installation and user error protection + +Eagle Eye Telegram Bot Notifications: + +- Provide reports on your indexer's uptime - help you to know about an errors in advance and not lose funds. +- If your indexer is offline +- If your project is somehow unavailable +- If you do not have enough funds +- If your certificate is about to expire +- And more + +UpdateHunter: + + - A tool that notifies you when a project is updated or a new project is created, providing complete documentation to enable fast and secure upgrades. + - It scans the blockchain and alerts an indexer via a Telegram channel about updates, automati­cally generating instructions and SQL queries. + - The bot integrates with GitHub, posting documentation updates to a public repository. + + Snapshots: + + - Service generates daily snapshots for all active projects + - This service is ideal if your indexer: + - Is newly deployed and you want to avoid ~1 month of downtime for project synchronization + - Has experienced data loss (corrupted disk, hardware failures, or software issues) + + Snapshots Toolkit: + + - Open Source toolkit for an own snapshot generator. With this repository indexer can generate its own snapshots. + +Links + +- [Toolkit Github](https://toolkit.subquery.dev/) +- [Eagle Eye Telegram Bot](https://eagleeye.subquery.dev/) +- [UpdateHunter](https://eagleeye.subquery.dev/updates) +- [Snapshots](https://snapshots.subquery.dev/) +- [Snapshots Toolkit](https://snapshots.subquery.dev/toolkit) + +### Kepler Network Dashboard (by DappLooker) + +To monitor the progress and performance of the Kepler Network, DappLooker has created a dashboard that displays the following key metrics: + +- Active Indexers / Delegators: The number of Indexers and Delegators who are actively participating in the Kepler Network. +- Weekly Indexer Stake / Delegation: The amount of kSQT that Indexers and Delegators have staked on the Kepler Network in the past week. +- Weekly Rewards: The amount of kSQT that Indexers have earned as rewards for serving data requests on the Kepler Network in the past week. +- Stake Distribution: The distribution of kSQT stakes between Indexers and Delegators on the Kepler Network. + +To make the data more accessible and user-friendly, DappLooker has also made the SubQuery Kepler data publicly available for everyone. This means that anyone can create custom dashboards tailored to their needs using the indexed data from the Kepler Network. + +Links + +- [Dashboard](https://dapplooker.com/dashboard/subquery-kepler-network-dashboard-577) +- [Indexed Dataset](https://analytics.dapplooker.com/browse/2/schema/subquery_kepler) +- [Announcement Article](https://blog.dapplooker.com/dapplooker-integrates-subquery-kepler-network-to-provide-analytics-and-dashboard-solution-to-web3-fb0c5aeea899) diff --git a/docs/ja/subquery_network/faq.md b/docs/ja/subquery_network/faq.md new file mode 100644 index 00000000000..a298d22efe5 --- /dev/null +++ b/docs/ja/subquery_network/faq.md @@ -0,0 +1,78 @@ +# Frequently Asked Questions + +FAQs for specific network participants: + +- [Node Operators](./node_operators/setup/faq.md) +- [Consumers](./consumers/faq.md) + +## Proof-of-indexing + +[Proof Of Index](./introduction/proof-of-index.md) + +## How do you ensure indexed data accuracy? + +Ensured by [Proof Of Index](./introduction/proof-of-index.md) + +## Are there a list of RPC providers that can provide support for \_\_\_ chain? + +SubQuery Network is decentralised, so we can't say what individual node operators would decide to serve you, nor can we say what infrastructure the node operators use and where it is hosted + +## What is the integration and deployment timeline for RPCs? + +SubQuery team can enable the RPC in a few days depending on how long an archive node on your network would take to sync. + +## Where is your/provider's infra hosted? + +Depends on the provider, SubQuery don't dictate this. But SubQuery gateway encourages competition to provide high performance, low latency, and geographically decentralised services. Most providers are running on their own bare metal for cost considerations + +## Is there a testnet environment? + +Yes, be sure to check https://dev.thechaindata.com/ + +## Is there a meaning behind SubQuery's name? + +The name "SubQuery" refers to its function in the blockchain ecosystem. A subquery is essentially a query within another query, allowing users to access data more efficiently. It is a powerful tool for indexing and querying blockchain data. + +## What was the first network that SubQuery first supported? + +SubQuery initially supported the Polkadot network, focusing on indexing and querying data for the Polkadot and its parachains. + +## How many networks do SubQuery support now? + +As of now, SubQuery supports multiple networks, including Polkadot, Kusama, Ethereum, and many others, expanding its reach to a wide array of blockchain ecosystems. + +## How does SubQuery improve blockchain data access? + +SubQuery enhances blockchain data access by providing an indexing layer that aggregates and organizes data from blockchain networks. This allows developers and applications to quickly retrieve and interact with data in a structured and efficient manner. + +## How does SubQuery differ from traditional block explorers? + +Traditional block explorers allow users to explore blockchain data in a static, non-queryable format. SubQuery, on the other hand, provides dynamic and customizable data querying, giving developers the ability to filter, process, and retrieve data in real-time for their applications. + +## What programming languages does SubQuery support? + +SubQuery primarily supports JavaScript and TypeScript for building queries and processing data. Developers can use these languages to define the structure and logic for data retrieval from supported networks. + +## Is SubQuery open-source? + +Yes, SubQuery is open-source. It encourages developers to contribute to its growth and use its tools to build decentralized applications (dApps) more efficiently. The source code is available on GitHub. + +## What are the main use cases for SubQuery? + +SubQuery is used for various purposes, such as: + +- Building decentralized applications (dApps) that need to access blockchain data. +- Indexing and querying blockchain data for analysis and reporting. +- Creating custom data solutions for blockchain ecosystems and decentralized finance (DeFi) platforms. + +## Can I deploy SubQuery on my own infrastructure? + +Yes, SubQuery can be deployed on your own infrastructure, whether on-premise or in the cloud. It offers flexibility to users who want complete control over their indexing and querying solutions. + +## How does SubQuery handle data updates and changes? + +SubQuery continuously updates its data by monitoring blockchain events in real-time. This ensures that the indexed data is always up to date, and any changes to the blockchain are reflected immediately in the data queries. + +## How can I get started with SubQuery? + +To get started with SubQuery, you can visit their official documentation, which provides step-by-step guides on setting up a project, writing queries, and deploying them on supported networks. The community also offers support through forums and Discord. diff --git a/docs/ja/subquery_network/infra-changes.md b/docs/ja/subquery_network/infra-changes.md new file mode 100644 index 00000000000..b30b5fa306d --- /dev/null +++ b/docs/ja/subquery_network/infra-changes.md @@ -0,0 +1,109 @@ +# Redefining Web3: SubQuery Network’s Bold Infrastructure Evolution + +Back in December 2023, we announced the evolution of SubQuery, in which we aim to transition from simply indexing web3 data to pioneering a complete web3 infrastructure revolution. + +Over the last year, as we’ve been building out our data indexing service and network, we realised our network is in a prime position to address broader centralisation issues throughout the web3 infrastructure landscape. + +Our mission has expanded, and so has the opportunity space we’re going to be working in. + +Read on to learn about the challenges we’re taking on and the next steps we’re taking to play a bigger role in decentralising the future. + +### The Web3 Infrastructure Landscape + +Web3 middleware services like indexers, RPCs, oracles and storage services are pivotal in blockchain dApp development. In fact, the utilisation of these middleware services is what sets apart successful, large-scale, production dApps - they accelerate performance and can scale to thousands of users, while providing a superior developer experience to bring in more users, TVL, and value. Indexers and RPCs shoulder the heavy lifting, standing as mission-critical services that underpin the functionality and efficiency of web3 applications. + +![](https://lh7-us.googleusercontent.com/2lbQyLR4fxrgV2dTqljyFV6bECXrfq3anA2k_qM6gJuWdSN01dHrVjIFU6OZeFXXJv57dwaXNQ6_lKdGtLK9YDWr0EdS7yDDv0BwZfFXT_j6aw-iu7bDxIS5ZkgliPD2mY_l5kbJXGKEqI6OWuZIEwk) + +**The current segregated web3 infrastructure landscape** + +Data indexers (like SubQuery) speed up data retrieval, enhancing performance and response times for users. They also simplify data by transforming raw blockchain information into more digestible formats, facilitating efficient development and a smooth user experience. + +Meanwhile, RPCs are pivotal for communication between blockchain nodes and external entities, facilitating data retrieval, smart contract interactions, and transaction submissions. Under the hood of your favourite dApp, tens of requests are passing through RPC providers to query and submit transactions to the network. + +While these middleware services are integral to a successful dApp, there is a significant issue that needs to be addressed. + +### Web3’s Dirty Little Secret + +There is a hidden truth behind the mask of “decentralisation” most of these middleware services wear. The reality is that many leading dApps have a significant reliance on centralised middleware components. This centralisation poses a substantial threat to the envisioned unstoppability of a web3 future, at any given moment, a single entity can undermine supposedly decentralised applications. + +Nowhere is this more apparent with RPC providers, and to a lesser extent, data indexers. These crucial services distinguish the scalable, reliable, and polished dApps from rudimentary applications that go without. But due to historical challenges in the process of decentralisation, for a long time, this has been a compromise most apps have accepted. + +The call for decentralised alternatives to these pivotal middleware services is essential for the foundation of the next generation of dApps to build upon. We need to decentralise these services, without compromise. + +### SubQuery Network Evolution Revealed + +At the start we set out to create a viable decentralised solution to the data indexing problem. + +Web3 developers face great difficulties aggregating and organising data to power dApps, and SubQuery has helped thousands of developers building the world's best and biggest networks, dApps, and analytics tools by providing fast and performant data indexing. + +In 2022 we launched Kepler Network, a pre-mainnet release that enabled us to bootstrap the network sustainably by bringing onboard proficient indexers and projects. The success of Kepler lead to the realisation that the ecosystem we’ve built could bring benefits for more than just decentralised data indexing, but for middleware infrastructure as a whole. The key components of the network we have built and deployed - reward and pricing rails, service verification tools, and dispute resolution processes - are valuable for others verticals. + +Knowing that the SubQuery Network could give our existing community of top node runners a solution to trustlessly receive rewards for running data indexing infrastructure, why couldn’t it work for those other services, for other parts of the dApp tech stack? + +We realised the full potential of the SubQuery Network mainnet should not be limited to just data indexing; its fundamental contracts, tools, and reward flows enable it to be so much more. By harnessing the power of the existing participants and mechanisms, the SubQuery Network is ready to extend to various infrastructure verticals. It dawned on us that there is a massive opportunity ahead of us when we think holistically about the entire developer experience. + +> With the launch of mainnet, the SubQuery Network will emerge as a solution to _decentralise everything_, revolutionising the entire developer experience in web3. + +![](https://lh7-us.googleusercontent.com/fXK85pf2n1zTFAsbxyhYKk4I_negGP3mNvXP_vE-_k-ppDlNQeCUPc-iKG7b2HjaeBaisWhkdDqPL8SoQb0QHW6eHI4-5Bra1GK7hrfIhzx9SW1SWgVJ9Nces5Vfza3fwYNug_nduW_8HJ-XB8eZwig) + +**The vision for SubQuery Network to encompass key web3 infrastructure components in a completely decentralised manner** + +### Starting with RPCs + +Our next step that we have completed is to decentralise the biggest infrastructure component for dApps - _Remote Procedure Call_ or RPC services. + +RPC services are still the main interface to the blockchain, under the hood of your favourite dApp, dozens of requests are passing through RPC providers to query and submit transactions to the network. They are the most critical part of the ecosystem, when one has an outage, [the effects reverberate across the industry](https://decrypt.co/47846/ethereum-backbone-infura-suffers-major-damage?ref=blog.subquery.network). + +Since SubQuery relies on performant and scalable RPCs to maximise our indexing speed, we already work extremely closely with RPC providers. On our quest to index over [115+ chains and counting](https://subquery.network/networks?ref=blog.subquery.network), we’ve discovered that the RPC ecosystem is very fractured: some ecosystems have excellent support, and some don’t, and that makes delivering an excellent indexing experience across all chains difficult. + +Across many smaller emergent networks, amateur RPC services operate to provide RPCs to various developers building on the network. These RPCs are usually run (at a loss) by the core network foundation team, and perhaps a collection of validators (for staking advertising purposes). Unfortunately for cost reasons, these RPCs are usually heavily pruned and rate limited, and have no upsell options for unrestricted access. As a result, dApp developers will often run a private RPC endpoint for their own use. This is expensive, frustrating, poses high barriers to entry, and results in no redundancy for dApp developers. + +For more established networks, one or more commercial providers may come and offer a freemium service, where there is a free plan/public endpoint, and a paid upsell to higher scale access. This serves dApp developers well, but the law of economies of scale dictate that networks tend towards a small number of hyperscale RPC providers who centralise the network and cause major outages that affect thousands of dApps when they go offline. They also extract huge economic value from a network and send that directly to big private cloud companies and VCs. + +We have built an alternative to these two dangerous equilibriums, and help decentralise everything.The SubQuery Network provides an open market for both data indexers and RPC providers and their consumers that: + +- Maintains low barriers of entry: Any node operator can join as a provider for any service on any network. +- Incentivises performance and cost: Node operators are automatically rewarded with requests based on these metrics, driving these values across the network. +- Encourages constant expansion to new chains: Node operators are free to onboard new chains and projects for first mover advantage, constantly expanding the network. + +### Enhancing RPCs - SubQuery’s Data Node + +The performance limitations of data indexers and many other applications have long been limited by the RPC endpoint. Developers have long focussed on building nodes to ensure efficient validation to ensure the safety of the network. As a result of this sacrifice, RPCs are extremely costly and they’re not at all optimised for querying. + +This is compounded by the rise of L2 chains where, with higher throughput, the query performance and cost are major outstanding issues to address. With limited querying capabilities, many don’t support complex querying languages or operations, making it inefficient to retrieve specific data. + +We have delivered the SubQuery Data Node, an enhanced and heavily-forked RPC node that is perfectly optimised for querying, especially on endpoints like `eth_getLog`, and the ability to filter transactions in a single API call. + +The Data Node is open source, allowing people to contribute, extend, or fork the implementation in any way. It supports leading layer-2s and other EVM networks initially, and they are optimised to run on the SubQuery Network in a decentralised way. + +Working together, the SubQuery Indexer and SubQuery Data Node provides the most performant indexing performance possible and in a completely decentralised way thanks to the SubQuery Network. + +Our node runners are able to run these data nodes on the network, bringing powerful and cost-effective RPC access to all, cementing SubQuery’s position as the fastest decentralised data indexer in web3. + +### Democratising RPCs - SubQuery’s Sharded Data Node + +In the final stage of our RPC journey, SubQuery will work to democratise RPCs (and solve [EIP-4444](https://eips.ethereum.org/EIPS/eip-4444?ref=blog.subquery.network)) in the process by delivering the Sharded Data Node, which will make RPCs cheaper to run and operate by node providers. + +In the last few months we’ve spoken with many RPC providers in the ecosystem. In many networks (in particular Cosmos), small scale RPC services operate to provide RPCs to various developers building on the network. Unfortunately for cost reasons, these RPCs are usually heavily pruned and rate limited and have no upsell options for unrestricted access. + +One of the key reasons for this is the sheer size of the node - an Ethereum archive requires about ~12 TB on Geth, an Osmosis archive is at least the same. This is an incredible cost that limits these nodes to large centralised infrastructure providers. + +SubQuery recognises that in order to decentralised RPCs correctly, you need to be able to make running these nodes easier and more accessible to everyday users. Currently the storage is made smaller by “pruning” data, which is intentionally discarding older information while cryptographically confirming that the recent data that is valid. This works fine for writing transactions, but means that indexers and other services are unable to query old data. + +SubQuery will extend its Data Node to support sharding, that is making each Data Node smaller by splitting up block ranges between node operators. Since SubQuery’s Data Node only runs within the boundaries of a specific block range, it does not need to constantly sync new data, allowing it to optimise further for query performance rather than validation and verification. + +The SubQuery Sharded node won’t just shard historical data, but also shard the historical state within the node. By itself, this won’t change much, but these sharded nodes will be optimised to run on the network, and the network will be designed to combine all these shards to expose a single unified endpoint that appears to cover the entire historical state of the chain. Developers will benefit from the entire historical state of the given network, and node operators will benefit from significantly lower running costs, creating a more cost efficient network. + +This is a revolutionary step forward for the RPC industry, and a potential solution to one of the great challenges facing older and larger blockchains with their state bloat size. This solution has the potential to help scale Ethereum, solve [EIP-4444](https://eips.ethereum.org/EIPS/eip-4444?ref=blog.subquery.network), and greatly support proliferation of Layer-2’s and rollups, while further democratising and decentralising the SubQuery Network. + +### Summary + +The future of SubQuery is not simply indexing web3 data, but pioneering a complete web3 infrastructure revolution. web3 middleware services like indexers and RPC providers are pivotal in blockchain dApp development, but there is a hidden truth behind the mask of “decentralisation” most of these middleware services wear. The reality is a significant reliance on centralised middleware components, which poses a substantial threat to the envisioned unstoppability of a web3 future. + +Our mission has expanded, and so has the opportunity space we’re going to be working in. We need to decentralise these services, without compromise. We’ve already delivered breakthroughs in decentralised data indexing, but our next steps will focus on enhancing the performance of RPCs with the SubQuery Data Node, and then to bring RPCs to the masses, with SubQuery’s Sharded Data Nodes. These steps together, will help unlock the next level of performance increases in web3. + +No other team today is better equipped at working to provide a holistic approach to solving this problem. In summary, our vision goes beyond data indexing; it's about revolutionising how data and infrastructure services are organised and accessed. + +Pioneering fast, flexible, and scalable decentralised infrastructure, we will help power web3's transition to an open, efficient and user-centric future. Join us in this journey. With SubQuery, it's not just about building for today, but architecting a decentralised, inclusive future. + +_Let's shape the future of web3, together._ \ No newline at end of file diff --git a/docs/ja/subquery_network/welcome.md b/docs/ja/subquery_network/welcome.md new file mode 100644 index 00000000000..53c14ae9c38 --- /dev/null +++ b/docs/ja/subquery_network/welcome.md @@ -0,0 +1,283 @@ +--- +footer: false +lastUpdated: false +contributors: false +editLink: false +photoSwipe: false +--- + + +
+
+
+ SubQuery Network + + The SubQuery Network is the most scalable, reliable, and unified data infrastructure network. 1,000s of decentralised Indexers and RPC providers simplify the data layer for a myriad of applications and use cases. + +
+
+
+ +
+
+ + + One network, all your web3 data needs + +
+ +
+ + {{ item.title }} + {{ item.subtitle }} + + {{ content }} + + + + + + +
+ +
+ Anyone can participate + + There’s a role for everyone in the network, from highly technical + developers to those with some experience and blockchain beginners. Find + out how you can participate and be rewarded. + +
+
+ + {{ anyone.name }} + + {{ anyone.description }} + + + + +
+
+ + +
+ Get Started with the Network Today + Our decentralised network is live and vibrant +
+ + + {{ item.title }} + + {{ item.desc }} + + + +
+
+ + +
+
+ + diff --git a/docs/ko/subquery_network/2024.md b/docs/ko/subquery_network/2024.md new file mode 100644 index 00000000000..412a1f34fc1 --- /dev/null +++ b/docs/ko/subquery_network/2024.md @@ -0,0 +1,62 @@ +# 2024 in Review: SubQuery’s Top 5 Milestones + +As we look back on 2024, we’re proud to call it a major “year of firsts” for us here at SubQuery. This year was filled with groundbreaking achievements, major launches, and remarkable community growth. The year has flown by but it also feels so long ago that we had our TGE, CEX Listing and SubQuery Network mainnet launch - all on the same day! + +Let’s celebrate some of the key milestones that made 2024 unforgettable. + +## 1. Mainnet Launch + +After an extremely successful Public Sale on 30 January 2024, selling out of SubQuery’s native token (SQT) in less than 2 hours, we worked very hard to launch the SubQuery Network mainnet on 23 February 2024. Powered by SQT and launched on Base, immediately users could consume and/or index data from over 150 networks ([now over 270 networks](https://subquery.network/networks)). + +Almost 1 year on and we have: + +- 46 globally distributed and highly skilled Node Operators servicing the network +- More than 330 million SQT staked and delegated in the Network +- Serving more than 50 million RPC requests every day +- An overall average APY of 22.28% and much higher for Node Operators (94.66%) + +## 2. SQT Token Generation Event + +Combined with the Mainnet launch, we ambitiously chose to do our TGE and day one CEX listing with Bybit on the same day (23 February 2024) as well. The SubQuery Token (SQT) is designed as a utility token that powers the SubQuery Network, providing an incentive for participation, as well as serving as a medium of exchange for transactions within the SubQuery Network. Consumers of data commit SQT in exchange for RPC queries or indexed data from our globally distributed Node Operators. + +Today, you can acquire SQT through any of these centralised exchange: + +- [Bybit](https://www.bybit.com/en/trade/spot/SQT/USDT) +- [Gate.io](https://www.gate.io/trade/SQT_USDT) +- [Crypto.com](https://crypto.com/exchange/trade/SQT_USD) +- [MEXC](https://www.mexc.com/exchange/SQT_USDT) + +SQT is on a number of DEX Pools however most liquidity is on Uniswap. + +- [Uniswap Pool on Ethereum](https://app.uniswap.org/explore/tokens/ethereum/0x09395a2A58DB45db0da254c7EAa5AC469D8bDc85) +- [Unsiwap Pool on Base](https://app.uniswap.org/explore/tokens/base/0x858c50c3af1913b0e849afdb74617388a1a5340d) + +## 3. Expansion into Decentralised RPCs + +This vision was announced at the end of 2023 but really came to fruition in 2024. We expanded our network capabilities by introducing support for Remote Procedure Call (RPC) services. This was the first step of expanding away from just a data indexer to a major decentralised infrastructure network, allowing us to support a more accessible, interoperable, and developer-friendly web3 ecosystem. + +Now serving RPC requests on 20+ networks, [get your decentralised RPCs from the SubQuery Network today](https://subquery.network/rpc/list/). + +### 4\. Launching Artificial Intelligence Tools + +SubQuery took its first steps into the AI space by launching decentralised AI inference model hosting on the SubQuery Network plus a new developer SDK called the AI App Framework. This massively expands the tools and services that we can offer to web3 builders across, all under one roof. + +The AI App Framework allows you to build, deploy, and run production AI apps on the SubQuery Network in a trusted and decentralised environment. AI apps are self-contained and easily scalable AI agents that you can use to power your intelligent applications. They are sandboxed to a trusted runner and can be easily distributed and scaled horizontally across the SubQuery Network. + +[Start building AI Apps today!](https://academy.subquery.network/ai/welcome.html) + +## 5. SubQuery Rebranding + +As we expanded into the Artificial Intelligence space, we felt a new look was warranted to match our new pursuit. So we rebranded to a complete new look with sleek chromatic details and a flower/root narrative. + +The flower and root theme symbolises SubQuery’s commitment to fostering innovation and growth within the blockchain community. The roots represent the deep, stable, and reliable infrastructure that SubQuery provides, while the flowers symbolise the diverse and vibrant dApps that developers can create with the help of this infrastructure. + +[Check out the new look](https://subquery.network/). + +## Looking Ahead to 2025 + +While 2024 was full of exciting milestones, we know this is just the beginning. With a stronger community, enhanced technology, and bold new goals, we’re ready to scale even greater heights in 2025. With our most recent [2024 roadmap](https://blog.subquery.network/subquery-releases-network-roadmap-for-2024/?lng=en) almost fully accomplished, stay tuned for a new version packed with ambitious plans. + +Thank you to everyone—developers, partners, and community members—who helped make this year possible. + +Here’s to many more firsts ahead! \ No newline at end of file diff --git a/docs/ko/subquery_network/about.md b/docs/ko/subquery_network/about.md new file mode 100644 index 00000000000..1699165773b --- /dev/null +++ b/docs/ko/subquery_network/about.md @@ -0,0 +1,47 @@ +# About Us + +Our mission is to innovate Web3 infrastructure so builders can decentralise the next generation of applications - without compromise. + +Pioneering fast, flexible, and scalable decentralised infrastructure, we power Web3's transition to an open, efficient and user-centric future.Join us on our journey to build the future of web3 infrastructure. + +[Join our Discord Community](https://discord.com/invite/subquery) + +## Core team + +SubQuery has a deep bench of highly skilled talent of engineers, customer service, and operations personnel.Headquartered in Singapore, we have key representation in New Zealand, Lisbon, and Sydney. + +### Ian He - CTO and Co-Founder + +Ian forged his interest in blockchain during his tenure as the Technical Team Lead for Centrality where he led the development of core components of CENNZnet. Ian also led a team that won 2nd place in the world's first Substrate/Polkadot Hackathon in 2019. Prior to this, Ian obtained significant experience working on large-scale infrastructure working for Alipay and Yihaodian.com. + +### Scott Twiname - Principal Dev of SDK + +Scott has a large wealth of experience in blockchain development. He started out learning about blockchain in his own time and eventually got the opportunity to apply his knowledge as a senior developer at Sylo. He has worked on all facets of blockchain development from smart contracts, dapps, decentralised technologies and wallet integration for various networks including Bitcoin, Ethereum, Tezos and CENNZnet. + +### Marta Adamczyk - Head of Business Development + +Marta is a huge tech advocate, Web3 enthusiast and IT-meetup addict. She helps SubQuery customers develop and scale their projects by delivering technical consultancy, developer-oriented content and technical education. Former product evangelist, frontend developer, digital marketer, educator and sales manager with corporate and start-up experience. + +### Brittany Seales - Head of Marketing + +Brittany has a background in chemistry but since then she became the closest point of contact with SubQuery customers and helped ensure that every SubQuery customer gets an excellent on-boarding experience. Naturally Brittany is heavily integrated with the community and content marketing and has since taken over this area. Sadly, no amount of interaction with successful blockchain projects has give her the ability to pick a winning NFT! + +### James Bayly - Advisor + +Well-versed across the business, from product engineering to being the face of SubQuery, James is also a serial entrepreneur leading several tech companies. When he’s not in Berlin sipping cocktails, you’ll find him hiking up the Routeburn Track in New Zealand. + +## Our Manifesto + +In the new era of Web3, true power isn't bought – it's built with innovation and vision. +We are SubQuery, not just a company, but a revolution. Our mission: to lead the charge in decentralising the future. +We're pioneering an infrastructure that's fast, flexible, scalable – ready to power tomorrow's Web3 world. Crafting an open, efficient, and user-centric digital landscape. +For the visionaries, the forward-thinkers, the builders of tomorrow – SubQuery is your platform. +Join us in this journey. With SubQuery, it's not just about building for today, but architecting a decentralised, inclusive future. Let's shape the future of Web3, together. + +## About SubQuery + +SubQuery Network is innovating in web3 infrastructure with tools that empower builders to decentralise without compromise. SubQuery’s infrastructure network offers everything from data indexers, RPCs and AI agents - all fully decentralised and production ready. + +Our fast, flexible, and open data indexer supercharges thousands of dApps on nearly 300 networks. Our Sharded Data Node will provide breakthroughs in the RPC industry and our AI App framework makes building AI apps easier than ever before. We pioneer the web3 revolution for visionaries and forward-thinkers. We’re not just a company — we’re a movement driving an inclusive and decentralised web3 era, together. + +[Linktree](https://linktr.ee/subquerynetwork) | [Website](https://subquery.network) | [Discord](https://discord.com/invite/subquery) | [Telegram](https://t.me/subquerynetworkcommunity) | [Twitter](https://twitter.com/subquerynetwork) | [Blog](https://blog.subquery.network/?lng=en) | [Medium](https://medium.com/@subquery) | [LinkedIn](https://www.linkedin.com/company/subquery) | [YouTube](https://www.youtube.com/c/SubQueryNetwork) \ No newline at end of file diff --git a/docs/ko/subquery_network/community.md b/docs/ko/subquery_network/community.md new file mode 100644 index 00000000000..59c4aaeb078 --- /dev/null +++ b/docs/ko/subquery_network/community.md @@ -0,0 +1,178 @@ +# SubQuery Network Community + +The key focus of the [SubQuery Foundation](./governance/foundation.md) and community is to ensure that there is enough support that anyone, from an expert blockchain team to a new hobbyist developer, can build their own Project. Together we can pave the way to a more decentralised future! + +## Connecting with others + +Discord is our main community for talking about SubQuery and learning more. You can join with [this link here](https://discord.com/invite/subquery). People most interested in the SubQuery Network will want to join `#network-general`, and Indexers or Delegators should join `#network-indexer-chat` or `#network-delegator-chat` respectively. + +When the conversation is deeper and requires more thought, we move the conversation to [our Forum](https://forum.subquery.network/). Here you will find longer topics, a history of all announcements to Network, and deeper conversation about the direction of the network. Feel free to join and start posting at [forum.subquery.network](https://forum.subquery.network/)! + +### Join the Node Operator community + +If you're a Node Operator on the Network, we strongly suggest that you keep up with the latest news, announcements, and tips by joining the following Discord channels: + +- `#network-announcements` +- `#network-general` +- `#network-services-release` +- `#network-indexer-announcements` +- `#network-indexer-general` + +## Contributing to Codebases + +SubQuery is open source and open to the community, if you want to contribute (e.g. add a feature, fix a bug, suggest an improvement, or even just fix a typo in our documentation), please review our [contributing guide](../miscellaneous/contributing.md). + +The following codebases are where you can find code for all the contracts, applications, and backend SubQuery projects. We're looking forward to seeing your contributions! + +### `network-app` + +dApp for indexers, consumers and delegators interact with SubQuery Network. + + + +### `network-airdrop-app` + +dApp for users to interact with the SubQuery airdrop contract. + + + +### `network-contracts` + +Contracts for SubQuery Network. + + + +You can find smart contract addresses for all network contracts here in [GitHub](https://github.com/subquery/network-contracts/blob/develop/publish/mainnet.json) + +### `network-app-backend` + +SubQuery project for the backend of the SubQuery App. + + + +### `network-airdrop-app-backend` + +SubQuery project for the backend of the SubQuery Airdrop App. + + + +### `network-swap-app-backend` + +SubQuery project for the backend of the SubQuery Swap App. + + + +### `network-indexer-services` + +Services that Indexers run to connect and serve data to the SubQuery Network. + + + +### `network-clients` + +Client SDKs for SubQuery Network. + + + +### `subquery-component-library` + +React UI component library for SubQuery dApps. + + + +## Community Tools + +There are a number of community built tools that you can use to help your SubQuery Network experience. Feel free to contribute your own. + +:::warning +Please note that none of these tools have been endorsed by the SubQuery team and descriptions have been written by third parties. This section is open for contribution by all. + +Please research and use at your own risk +::: + +### SQTScan + +[SQTScan](https://sqtscan.com/?ref=blog.subquery.network) is a ***community-owned application*** designed specifically to help expert users such as Node Operators and Delegators to gain a deeper understanding of historical rewards on the SubQuery Network and optimise their participation. + +SQT Scan helps expert users (Node Operators and Delegators) with: + +1. **Education:** Understand how their rewards are calculated and how they should make decisions +2. **Compare Opportunities:** Decide which projects to deploy based on historical rewards +3. **Compare Others:** Compare their APY with other Node Operators, overall and by project, to see how they're performing relatively +4. **APY Maximisation:** Identify ways to increase their APY + +If you would like to add your support, suggest improvements or new features, or even contribute code, it is welcomed! + +Links + +- [SQTSCan](https://sqtscan.com) +- [Github](https://github.com/HuberTRoy/subquery-sqtscan) + +### Indexer Monitoring Tools (by web3cdn.network) + +Five products: +1. **Toolkit:** A toolkit contains everything you need to index, monitor and properly access from any device +2. **Telegram Uptime Bot:** Eagle Eye is a bot which will provide you live updates in Telegram on the uptime of your indexer +3. **UpdateHunter** +4. **Snapshots** +5. **Snapshots Toolkit** + +Toolkit Features: + +- Extended monitoring of all indexer parameters, sync time, balances, issues. Metrics also support Alerting rules +- Flags problems that have arisen through monitoring and help you to not miss rewards. +- Makes your indexer and infrastructure secure +- Ease of updating without the risk of changing important parameters +- Secured access to dangerous zone with your own VPN, Access from mobile devices to monitoring, and internal services in any time. +- Very easy installation and user error protection + +Eagle Eye Telegram Bot Notifications: + +- Provide reports on your indexer's uptime - help you to know about an errors in advance and not lose funds. +- If your indexer is offline +- If your project is somehow unavailable +- If you do not have enough funds +- If your certificate is about to expire +- And more + +UpdateHunter: + + - A tool that notifies you when a project is updated or a new project is created, providing complete documentation to enable fast and secure upgrades. + - It scans the blockchain and alerts an indexer via a Telegram channel about updates, automati­cally generating instructions and SQL queries. + - The bot integrates with GitHub, posting documentation updates to a public repository. + + Snapshots: + + - Service generates daily snapshots for all active projects + - This service is ideal if your indexer: + - Is newly deployed and you want to avoid ~1 month of downtime for project synchronization + - Has experienced data loss (corrupted disk, hardware failures, or software issues) + + Snapshots Toolkit: + + - Open Source toolkit for an own snapshot generator. With this repository indexer can generate its own snapshots. + +Links + +- [Toolkit Github](https://toolkit.subquery.dev/) +- [Eagle Eye Telegram Bot](https://eagleeye.subquery.dev/) +- [UpdateHunter](https://eagleeye.subquery.dev/updates) +- [Snapshots](https://snapshots.subquery.dev/) +- [Snapshots Toolkit](https://snapshots.subquery.dev/toolkit) + +### Kepler Network Dashboard (by DappLooker) + +To monitor the progress and performance of the Kepler Network, DappLooker has created a dashboard that displays the following key metrics: + +- Active Indexers / Delegators: The number of Indexers and Delegators who are actively participating in the Kepler Network. +- Weekly Indexer Stake / Delegation: The amount of kSQT that Indexers and Delegators have staked on the Kepler Network in the past week. +- Weekly Rewards: The amount of kSQT that Indexers have earned as rewards for serving data requests on the Kepler Network in the past week. +- Stake Distribution: The distribution of kSQT stakes between Indexers and Delegators on the Kepler Network. + +To make the data more accessible and user-friendly, DappLooker has also made the SubQuery Kepler data publicly available for everyone. This means that anyone can create custom dashboards tailored to their needs using the indexed data from the Kepler Network. + +Links + +- [Dashboard](https://dapplooker.com/dashboard/subquery-kepler-network-dashboard-577) +- [Indexed Dataset](https://analytics.dapplooker.com/browse/2/schema/subquery_kepler) +- [Announcement Article](https://blog.dapplooker.com/dapplooker-integrates-subquery-kepler-network-to-provide-analytics-and-dashboard-solution-to-web3-fb0c5aeea899) diff --git a/docs/ko/subquery_network/faq.md b/docs/ko/subquery_network/faq.md new file mode 100644 index 00000000000..a298d22efe5 --- /dev/null +++ b/docs/ko/subquery_network/faq.md @@ -0,0 +1,78 @@ +# Frequently Asked Questions + +FAQs for specific network participants: + +- [Node Operators](./node_operators/setup/faq.md) +- [Consumers](./consumers/faq.md) + +## Proof-of-indexing + +[Proof Of Index](./introduction/proof-of-index.md) + +## How do you ensure indexed data accuracy? + +Ensured by [Proof Of Index](./introduction/proof-of-index.md) + +## Are there a list of RPC providers that can provide support for \_\_\_ chain? + +SubQuery Network is decentralised, so we can't say what individual node operators would decide to serve you, nor can we say what infrastructure the node operators use and where it is hosted + +## What is the integration and deployment timeline for RPCs? + +SubQuery team can enable the RPC in a few days depending on how long an archive node on your network would take to sync. + +## Where is your/provider's infra hosted? + +Depends on the provider, SubQuery don't dictate this. But SubQuery gateway encourages competition to provide high performance, low latency, and geographically decentralised services. Most providers are running on their own bare metal for cost considerations + +## Is there a testnet environment? + +Yes, be sure to check https://dev.thechaindata.com/ + +## Is there a meaning behind SubQuery's name? + +The name "SubQuery" refers to its function in the blockchain ecosystem. A subquery is essentially a query within another query, allowing users to access data more efficiently. It is a powerful tool for indexing and querying blockchain data. + +## What was the first network that SubQuery first supported? + +SubQuery initially supported the Polkadot network, focusing on indexing and querying data for the Polkadot and its parachains. + +## How many networks do SubQuery support now? + +As of now, SubQuery supports multiple networks, including Polkadot, Kusama, Ethereum, and many others, expanding its reach to a wide array of blockchain ecosystems. + +## How does SubQuery improve blockchain data access? + +SubQuery enhances blockchain data access by providing an indexing layer that aggregates and organizes data from blockchain networks. This allows developers and applications to quickly retrieve and interact with data in a structured and efficient manner. + +## How does SubQuery differ from traditional block explorers? + +Traditional block explorers allow users to explore blockchain data in a static, non-queryable format. SubQuery, on the other hand, provides dynamic and customizable data querying, giving developers the ability to filter, process, and retrieve data in real-time for their applications. + +## What programming languages does SubQuery support? + +SubQuery primarily supports JavaScript and TypeScript for building queries and processing data. Developers can use these languages to define the structure and logic for data retrieval from supported networks. + +## Is SubQuery open-source? + +Yes, SubQuery is open-source. It encourages developers to contribute to its growth and use its tools to build decentralized applications (dApps) more efficiently. The source code is available on GitHub. + +## What are the main use cases for SubQuery? + +SubQuery is used for various purposes, such as: + +- Building decentralized applications (dApps) that need to access blockchain data. +- Indexing and querying blockchain data for analysis and reporting. +- Creating custom data solutions for blockchain ecosystems and decentralized finance (DeFi) platforms. + +## Can I deploy SubQuery on my own infrastructure? + +Yes, SubQuery can be deployed on your own infrastructure, whether on-premise or in the cloud. It offers flexibility to users who want complete control over their indexing and querying solutions. + +## How does SubQuery handle data updates and changes? + +SubQuery continuously updates its data by monitoring blockchain events in real-time. This ensures that the indexed data is always up to date, and any changes to the blockchain are reflected immediately in the data queries. + +## How can I get started with SubQuery? + +To get started with SubQuery, you can visit their official documentation, which provides step-by-step guides on setting up a project, writing queries, and deploying them on supported networks. The community also offers support through forums and Discord. diff --git a/docs/ko/subquery_network/infra-changes.md b/docs/ko/subquery_network/infra-changes.md new file mode 100644 index 00000000000..b30b5fa306d --- /dev/null +++ b/docs/ko/subquery_network/infra-changes.md @@ -0,0 +1,109 @@ +# Redefining Web3: SubQuery Network’s Bold Infrastructure Evolution + +Back in December 2023, we announced the evolution of SubQuery, in which we aim to transition from simply indexing web3 data to pioneering a complete web3 infrastructure revolution. + +Over the last year, as we’ve been building out our data indexing service and network, we realised our network is in a prime position to address broader centralisation issues throughout the web3 infrastructure landscape. + +Our mission has expanded, and so has the opportunity space we’re going to be working in. + +Read on to learn about the challenges we’re taking on and the next steps we’re taking to play a bigger role in decentralising the future. + +### The Web3 Infrastructure Landscape + +Web3 middleware services like indexers, RPCs, oracles and storage services are pivotal in blockchain dApp development. In fact, the utilisation of these middleware services is what sets apart successful, large-scale, production dApps - they accelerate performance and can scale to thousands of users, while providing a superior developer experience to bring in more users, TVL, and value. Indexers and RPCs shoulder the heavy lifting, standing as mission-critical services that underpin the functionality and efficiency of web3 applications. + +![](https://lh7-us.googleusercontent.com/2lbQyLR4fxrgV2dTqljyFV6bECXrfq3anA2k_qM6gJuWdSN01dHrVjIFU6OZeFXXJv57dwaXNQ6_lKdGtLK9YDWr0EdS7yDDv0BwZfFXT_j6aw-iu7bDxIS5ZkgliPD2mY_l5kbJXGKEqI6OWuZIEwk) + +**The current segregated web3 infrastructure landscape** + +Data indexers (like SubQuery) speed up data retrieval, enhancing performance and response times for users. They also simplify data by transforming raw blockchain information into more digestible formats, facilitating efficient development and a smooth user experience. + +Meanwhile, RPCs are pivotal for communication between blockchain nodes and external entities, facilitating data retrieval, smart contract interactions, and transaction submissions. Under the hood of your favourite dApp, tens of requests are passing through RPC providers to query and submit transactions to the network. + +While these middleware services are integral to a successful dApp, there is a significant issue that needs to be addressed. + +### Web3’s Dirty Little Secret + +There is a hidden truth behind the mask of “decentralisation” most of these middleware services wear. The reality is that many leading dApps have a significant reliance on centralised middleware components. This centralisation poses a substantial threat to the envisioned unstoppability of a web3 future, at any given moment, a single entity can undermine supposedly decentralised applications. + +Nowhere is this more apparent with RPC providers, and to a lesser extent, data indexers. These crucial services distinguish the scalable, reliable, and polished dApps from rudimentary applications that go without. But due to historical challenges in the process of decentralisation, for a long time, this has been a compromise most apps have accepted. + +The call for decentralised alternatives to these pivotal middleware services is essential for the foundation of the next generation of dApps to build upon. We need to decentralise these services, without compromise. + +### SubQuery Network Evolution Revealed + +At the start we set out to create a viable decentralised solution to the data indexing problem. + +Web3 developers face great difficulties aggregating and organising data to power dApps, and SubQuery has helped thousands of developers building the world's best and biggest networks, dApps, and analytics tools by providing fast and performant data indexing. + +In 2022 we launched Kepler Network, a pre-mainnet release that enabled us to bootstrap the network sustainably by bringing onboard proficient indexers and projects. The success of Kepler lead to the realisation that the ecosystem we’ve built could bring benefits for more than just decentralised data indexing, but for middleware infrastructure as a whole. The key components of the network we have built and deployed - reward and pricing rails, service verification tools, and dispute resolution processes - are valuable for others verticals. + +Knowing that the SubQuery Network could give our existing community of top node runners a solution to trustlessly receive rewards for running data indexing infrastructure, why couldn’t it work for those other services, for other parts of the dApp tech stack? + +We realised the full potential of the SubQuery Network mainnet should not be limited to just data indexing; its fundamental contracts, tools, and reward flows enable it to be so much more. By harnessing the power of the existing participants and mechanisms, the SubQuery Network is ready to extend to various infrastructure verticals. It dawned on us that there is a massive opportunity ahead of us when we think holistically about the entire developer experience. + +> With the launch of mainnet, the SubQuery Network will emerge as a solution to _decentralise everything_, revolutionising the entire developer experience in web3. + +![](https://lh7-us.googleusercontent.com/fXK85pf2n1zTFAsbxyhYKk4I_negGP3mNvXP_vE-_k-ppDlNQeCUPc-iKG7b2HjaeBaisWhkdDqPL8SoQb0QHW6eHI4-5Bra1GK7hrfIhzx9SW1SWgVJ9Nces5Vfza3fwYNug_nduW_8HJ-XB8eZwig) + +**The vision for SubQuery Network to encompass key web3 infrastructure components in a completely decentralised manner** + +### Starting with RPCs + +Our next step that we have completed is to decentralise the biggest infrastructure component for dApps - _Remote Procedure Call_ or RPC services. + +RPC services are still the main interface to the blockchain, under the hood of your favourite dApp, dozens of requests are passing through RPC providers to query and submit transactions to the network. They are the most critical part of the ecosystem, when one has an outage, [the effects reverberate across the industry](https://decrypt.co/47846/ethereum-backbone-infura-suffers-major-damage?ref=blog.subquery.network). + +Since SubQuery relies on performant and scalable RPCs to maximise our indexing speed, we already work extremely closely with RPC providers. On our quest to index over [115+ chains and counting](https://subquery.network/networks?ref=blog.subquery.network), we’ve discovered that the RPC ecosystem is very fractured: some ecosystems have excellent support, and some don’t, and that makes delivering an excellent indexing experience across all chains difficult. + +Across many smaller emergent networks, amateur RPC services operate to provide RPCs to various developers building on the network. These RPCs are usually run (at a loss) by the core network foundation team, and perhaps a collection of validators (for staking advertising purposes). Unfortunately for cost reasons, these RPCs are usually heavily pruned and rate limited, and have no upsell options for unrestricted access. As a result, dApp developers will often run a private RPC endpoint for their own use. This is expensive, frustrating, poses high barriers to entry, and results in no redundancy for dApp developers. + +For more established networks, one or more commercial providers may come and offer a freemium service, where there is a free plan/public endpoint, and a paid upsell to higher scale access. This serves dApp developers well, but the law of economies of scale dictate that networks tend towards a small number of hyperscale RPC providers who centralise the network and cause major outages that affect thousands of dApps when they go offline. They also extract huge economic value from a network and send that directly to big private cloud companies and VCs. + +We have built an alternative to these two dangerous equilibriums, and help decentralise everything.The SubQuery Network provides an open market for both data indexers and RPC providers and their consumers that: + +- Maintains low barriers of entry: Any node operator can join as a provider for any service on any network. +- Incentivises performance and cost: Node operators are automatically rewarded with requests based on these metrics, driving these values across the network. +- Encourages constant expansion to new chains: Node operators are free to onboard new chains and projects for first mover advantage, constantly expanding the network. + +### Enhancing RPCs - SubQuery’s Data Node + +The performance limitations of data indexers and many other applications have long been limited by the RPC endpoint. Developers have long focussed on building nodes to ensure efficient validation to ensure the safety of the network. As a result of this sacrifice, RPCs are extremely costly and they’re not at all optimised for querying. + +This is compounded by the rise of L2 chains where, with higher throughput, the query performance and cost are major outstanding issues to address. With limited querying capabilities, many don’t support complex querying languages or operations, making it inefficient to retrieve specific data. + +We have delivered the SubQuery Data Node, an enhanced and heavily-forked RPC node that is perfectly optimised for querying, especially on endpoints like `eth_getLog`, and the ability to filter transactions in a single API call. + +The Data Node is open source, allowing people to contribute, extend, or fork the implementation in any way. It supports leading layer-2s and other EVM networks initially, and they are optimised to run on the SubQuery Network in a decentralised way. + +Working together, the SubQuery Indexer and SubQuery Data Node provides the most performant indexing performance possible and in a completely decentralised way thanks to the SubQuery Network. + +Our node runners are able to run these data nodes on the network, bringing powerful and cost-effective RPC access to all, cementing SubQuery’s position as the fastest decentralised data indexer in web3. + +### Democratising RPCs - SubQuery’s Sharded Data Node + +In the final stage of our RPC journey, SubQuery will work to democratise RPCs (and solve [EIP-4444](https://eips.ethereum.org/EIPS/eip-4444?ref=blog.subquery.network)) in the process by delivering the Sharded Data Node, which will make RPCs cheaper to run and operate by node providers. + +In the last few months we’ve spoken with many RPC providers in the ecosystem. In many networks (in particular Cosmos), small scale RPC services operate to provide RPCs to various developers building on the network. Unfortunately for cost reasons, these RPCs are usually heavily pruned and rate limited and have no upsell options for unrestricted access. + +One of the key reasons for this is the sheer size of the node - an Ethereum archive requires about ~12 TB on Geth, an Osmosis archive is at least the same. This is an incredible cost that limits these nodes to large centralised infrastructure providers. + +SubQuery recognises that in order to decentralised RPCs correctly, you need to be able to make running these nodes easier and more accessible to everyday users. Currently the storage is made smaller by “pruning” data, which is intentionally discarding older information while cryptographically confirming that the recent data that is valid. This works fine for writing transactions, but means that indexers and other services are unable to query old data. + +SubQuery will extend its Data Node to support sharding, that is making each Data Node smaller by splitting up block ranges between node operators. Since SubQuery’s Data Node only runs within the boundaries of a specific block range, it does not need to constantly sync new data, allowing it to optimise further for query performance rather than validation and verification. + +The SubQuery Sharded node won’t just shard historical data, but also shard the historical state within the node. By itself, this won’t change much, but these sharded nodes will be optimised to run on the network, and the network will be designed to combine all these shards to expose a single unified endpoint that appears to cover the entire historical state of the chain. Developers will benefit from the entire historical state of the given network, and node operators will benefit from significantly lower running costs, creating a more cost efficient network. + +This is a revolutionary step forward for the RPC industry, and a potential solution to one of the great challenges facing older and larger blockchains with their state bloat size. This solution has the potential to help scale Ethereum, solve [EIP-4444](https://eips.ethereum.org/EIPS/eip-4444?ref=blog.subquery.network), and greatly support proliferation of Layer-2’s and rollups, while further democratising and decentralising the SubQuery Network. + +### Summary + +The future of SubQuery is not simply indexing web3 data, but pioneering a complete web3 infrastructure revolution. web3 middleware services like indexers and RPC providers are pivotal in blockchain dApp development, but there is a hidden truth behind the mask of “decentralisation” most of these middleware services wear. The reality is a significant reliance on centralised middleware components, which poses a substantial threat to the envisioned unstoppability of a web3 future. + +Our mission has expanded, and so has the opportunity space we’re going to be working in. We need to decentralise these services, without compromise. We’ve already delivered breakthroughs in decentralised data indexing, but our next steps will focus on enhancing the performance of RPCs with the SubQuery Data Node, and then to bring RPCs to the masses, with SubQuery’s Sharded Data Nodes. These steps together, will help unlock the next level of performance increases in web3. + +No other team today is better equipped at working to provide a holistic approach to solving this problem. In summary, our vision goes beyond data indexing; it's about revolutionising how data and infrastructure services are organised and accessed. + +Pioneering fast, flexible, and scalable decentralised infrastructure, we will help power web3's transition to an open, efficient and user-centric future. Join us in this journey. With SubQuery, it's not just about building for today, but architecting a decentralised, inclusive future. + +_Let's shape the future of web3, together._ \ No newline at end of file diff --git a/docs/ko/subquery_network/welcome.md b/docs/ko/subquery_network/welcome.md new file mode 100644 index 00000000000..53c14ae9c38 --- /dev/null +++ b/docs/ko/subquery_network/welcome.md @@ -0,0 +1,283 @@ +--- +footer: false +lastUpdated: false +contributors: false +editLink: false +photoSwipe: false +--- + + +
+
+
+ SubQuery Network + + The SubQuery Network is the most scalable, reliable, and unified data infrastructure network. 1,000s of decentralised Indexers and RPC providers simplify the data layer for a myriad of applications and use cases. + +
+
+
+ +
+
+ + + One network, all your web3 data needs + +
+ +
+ + {{ item.title }} + {{ item.subtitle }} + + {{ content }} + + + + + + +
+ +
+ Anyone can participate + + There’s a role for everyone in the network, from highly technical + developers to those with some experience and blockchain beginners. Find + out how you can participate and be rewarded. + +
+
+ + {{ anyone.name }} + + {{ anyone.description }} + + + + +
+
+ + +
+ Get Started with the Network Today + Our decentralised network is live and vibrant +
+ + + {{ item.title }} + + {{ item.desc }} + + + +
+
+ + +
+
+ + diff --git a/docs/ru/subquery_network/2024.md b/docs/ru/subquery_network/2024.md new file mode 100644 index 00000000000..3c75b053c28 --- /dev/null +++ b/docs/ru/subquery_network/2024.md @@ -0,0 +1,62 @@ +# 2024 in Review: SubQuery’s Top 5 Milestones + +As we look back on 2024, we’re proud to call it a major “year of firsts” for us here at SubQuery. This year was filled with groundbreaking achievements, major launches, and remarkable community growth. The year has flown by but it also feels so long ago that we had our TGE, CEX Listing and SubQuery Network mainnet launch - all on the same day! + +Let’s celebrate some of the key milestones that made 2024 unforgettable. + +## 1. Mainnet Launch + +After an extremely successful Public Sale on 30 January 2024, selling out of SubQuery’s native token (SQT) in less than 2 hours, we worked very hard to launch the SubQuery Network mainnet on 23 February 2024. Powered by SQT and launched on Base, immediately users could consume and/or index data from over 150 networks ([now over 270 networks](https://subquery.network/networks)). + +Almost 1 year on and we have: + +- 46 globally distributed and highly skilled Node Operators servicing the network +- More than 330 million SQT staked and delegated in the Network +- Serving more than 50 million RPC requests every day +- An overall average APY of 22.28% and much higher for Node Operators (94.66%) + +## 2. SQT Token Generation Event + +Combined with the Mainnet launch, we ambitiously chose to do our TGE and day one CEX listing with Bybit on the same day (23 February 2024) as well. Токен SubQuery Token (SQT) разработан как полезный токен, который обеспечивает работу сети SubQuery Network, стимулирует участие в ней, а также служит средством обмена для транзакций в сети SubQuery Network. Consumers of data commit SQT in exchange for RPC queries or indexed data from our globally distributed Node Operators. + +Today, you can acquire SQT through any of these centralised exchange: + +- [Bybit](https://www.bybit.com/en/trade/spot/SQT/USDT) +- [Gate.io](https://www.gate.io/trade/SQT_USDT) +- [Crypto.com](https://crypto.com/exchange/trade/SQT_USD) +- [MEXC](https://www.mexc.com/exchange/SQT_USDT) + +SQT is on a number of DEX Pools however most liquidity is on Uniswap. + +- [Uniswap Pool on Ethereum](https://app.uniswap.org/explore/tokens/ethereum/0x09395a2A58DB45db0da254c7EAa5AC469D8bDc85) +- [Unsiwap Pool on Base](https://app.uniswap.org/explore/tokens/base/0x858c50c3af1913b0e849afdb74617388a1a5340d) + +## 3. Expansion into Decentralised RPCs + +This vision was announced at the end of 2023 but really came to fruition in 2024. We expanded our network capabilities by introducing support for Remote Procedure Call (RPC) services. This was the first step of expanding away from just a data indexer to a major decentralised infrastructure network, allowing us to support a more accessible, interoperable, and developer-friendly web3 ecosystem. + +Now serving RPC requests on 20+ networks, [get your decentralised RPCs from the SubQuery Network today](https://subquery.network/rpc/list/). + +### 4\. Launching Artificial Intelligence Tools + +SubQuery took its first steps into the AI space by launching decentralised AI inference model hosting on the SubQuery Network plus a new developer SDK called the AI App Framework. This massively expands the tools and services that we can offer to web3 builders across, all under one roof. + +The AI App Framework allows you to build, deploy, and run production AI apps on the SubQuery Network in a trusted and decentralised environment. AI apps are self-contained and easily scalable AI agents that you can use to power your intelligent applications. They are sandboxed to a trusted runner and can be easily distributed and scaled horizontally across the SubQuery Network. + +[Start building AI Apps today!](https://academy.subquery.network/ai/welcome.html) + +## 5. SubQuery Rebranding + +As we expanded into the Artificial Intelligence space, we felt a new look was warranted to match our new pursuit. So we rebranded to a complete new look with sleek chromatic details and a flower/root narrative. + +The flower and root theme symbolises SubQuery’s commitment to fostering innovation and growth within the blockchain community. The roots represent the deep, stable, and reliable infrastructure that SubQuery provides, while the flowers symbolise the diverse and vibrant dApps that developers can create with the help of this infrastructure. + +[Check out the new look](https://subquery.network/). + +## Looking Ahead to 2025 + +While 2024 was full of exciting milestones, we know this is just the beginning. With a stronger community, enhanced technology, and bold new goals, we’re ready to scale even greater heights in 2025. With our most recent [2024 roadmap](https://blog.subquery.network/subquery-releases-network-roadmap-for-2024/?lng=en) almost fully accomplished, stay tuned for a new version packed with ambitious plans. + +Thank you to everyone—developers, partners, and community members—who helped make this year possible. + +Here’s to many more firsts ahead! \ No newline at end of file diff --git a/docs/ru/subquery_network/about.md b/docs/ru/subquery_network/about.md new file mode 100644 index 00000000000..1699165773b --- /dev/null +++ b/docs/ru/subquery_network/about.md @@ -0,0 +1,47 @@ +# About Us + +Our mission is to innovate Web3 infrastructure so builders can decentralise the next generation of applications - without compromise. + +Pioneering fast, flexible, and scalable decentralised infrastructure, we power Web3's transition to an open, efficient and user-centric future.Join us on our journey to build the future of web3 infrastructure. + +[Join our Discord Community](https://discord.com/invite/subquery) + +## Core team + +SubQuery has a deep bench of highly skilled talent of engineers, customer service, and operations personnel.Headquartered in Singapore, we have key representation in New Zealand, Lisbon, and Sydney. + +### Ian He - CTO and Co-Founder + +Ian forged his interest in blockchain during his tenure as the Technical Team Lead for Centrality where he led the development of core components of CENNZnet. Ian also led a team that won 2nd place in the world's first Substrate/Polkadot Hackathon in 2019. Prior to this, Ian obtained significant experience working on large-scale infrastructure working for Alipay and Yihaodian.com. + +### Scott Twiname - Principal Dev of SDK + +Scott has a large wealth of experience in blockchain development. He started out learning about blockchain in his own time and eventually got the opportunity to apply his knowledge as a senior developer at Sylo. He has worked on all facets of blockchain development from smart contracts, dapps, decentralised technologies and wallet integration for various networks including Bitcoin, Ethereum, Tezos and CENNZnet. + +### Marta Adamczyk - Head of Business Development + +Marta is a huge tech advocate, Web3 enthusiast and IT-meetup addict. She helps SubQuery customers develop and scale their projects by delivering technical consultancy, developer-oriented content and technical education. Former product evangelist, frontend developer, digital marketer, educator and sales manager with corporate and start-up experience. + +### Brittany Seales - Head of Marketing + +Brittany has a background in chemistry but since then she became the closest point of contact with SubQuery customers and helped ensure that every SubQuery customer gets an excellent on-boarding experience. Naturally Brittany is heavily integrated with the community and content marketing and has since taken over this area. Sadly, no amount of interaction with successful blockchain projects has give her the ability to pick a winning NFT! + +### James Bayly - Advisor + +Well-versed across the business, from product engineering to being the face of SubQuery, James is also a serial entrepreneur leading several tech companies. When he’s not in Berlin sipping cocktails, you’ll find him hiking up the Routeburn Track in New Zealand. + +## Our Manifesto + +In the new era of Web3, true power isn't bought – it's built with innovation and vision. +We are SubQuery, not just a company, but a revolution. Our mission: to lead the charge in decentralising the future. +We're pioneering an infrastructure that's fast, flexible, scalable – ready to power tomorrow's Web3 world. Crafting an open, efficient, and user-centric digital landscape. +For the visionaries, the forward-thinkers, the builders of tomorrow – SubQuery is your platform. +Join us in this journey. With SubQuery, it's not just about building for today, but architecting a decentralised, inclusive future. Let's shape the future of Web3, together. + +## About SubQuery + +SubQuery Network is innovating in web3 infrastructure with tools that empower builders to decentralise without compromise. SubQuery’s infrastructure network offers everything from data indexers, RPCs and AI agents - all fully decentralised and production ready. + +Our fast, flexible, and open data indexer supercharges thousands of dApps on nearly 300 networks. Our Sharded Data Node will provide breakthroughs in the RPC industry and our AI App framework makes building AI apps easier than ever before. We pioneer the web3 revolution for visionaries and forward-thinkers. We’re not just a company — we’re a movement driving an inclusive and decentralised web3 era, together. + +[Linktree](https://linktr.ee/subquerynetwork) | [Website](https://subquery.network) | [Discord](https://discord.com/invite/subquery) | [Telegram](https://t.me/subquerynetworkcommunity) | [Twitter](https://twitter.com/subquerynetwork) | [Blog](https://blog.subquery.network/?lng=en) | [Medium](https://medium.com/@subquery) | [LinkedIn](https://www.linkedin.com/company/subquery) | [YouTube](https://www.youtube.com/c/SubQueryNetwork) \ No newline at end of file diff --git a/docs/ru/subquery_network/community.md b/docs/ru/subquery_network/community.md new file mode 100644 index 00000000000..59c4aaeb078 --- /dev/null +++ b/docs/ru/subquery_network/community.md @@ -0,0 +1,178 @@ +# SubQuery Network Community + +The key focus of the [SubQuery Foundation](./governance/foundation.md) and community is to ensure that there is enough support that anyone, from an expert blockchain team to a new hobbyist developer, can build their own Project. Together we can pave the way to a more decentralised future! + +## Connecting with others + +Discord is our main community for talking about SubQuery and learning more. You can join with [this link here](https://discord.com/invite/subquery). People most interested in the SubQuery Network will want to join `#network-general`, and Indexers or Delegators should join `#network-indexer-chat` or `#network-delegator-chat` respectively. + +When the conversation is deeper and requires more thought, we move the conversation to [our Forum](https://forum.subquery.network/). Here you will find longer topics, a history of all announcements to Network, and deeper conversation about the direction of the network. Feel free to join and start posting at [forum.subquery.network](https://forum.subquery.network/)! + +### Join the Node Operator community + +If you're a Node Operator on the Network, we strongly suggest that you keep up with the latest news, announcements, and tips by joining the following Discord channels: + +- `#network-announcements` +- `#network-general` +- `#network-services-release` +- `#network-indexer-announcements` +- `#network-indexer-general` + +## Contributing to Codebases + +SubQuery is open source and open to the community, if you want to contribute (e.g. add a feature, fix a bug, suggest an improvement, or even just fix a typo in our documentation), please review our [contributing guide](../miscellaneous/contributing.md). + +The following codebases are where you can find code for all the contracts, applications, and backend SubQuery projects. We're looking forward to seeing your contributions! + +### `network-app` + +dApp for indexers, consumers and delegators interact with SubQuery Network. + + + +### `network-airdrop-app` + +dApp for users to interact with the SubQuery airdrop contract. + + + +### `network-contracts` + +Contracts for SubQuery Network. + + + +You can find smart contract addresses for all network contracts here in [GitHub](https://github.com/subquery/network-contracts/blob/develop/publish/mainnet.json) + +### `network-app-backend` + +SubQuery project for the backend of the SubQuery App. + + + +### `network-airdrop-app-backend` + +SubQuery project for the backend of the SubQuery Airdrop App. + + + +### `network-swap-app-backend` + +SubQuery project for the backend of the SubQuery Swap App. + + + +### `network-indexer-services` + +Services that Indexers run to connect and serve data to the SubQuery Network. + + + +### `network-clients` + +Client SDKs for SubQuery Network. + + + +### `subquery-component-library` + +React UI component library for SubQuery dApps. + + + +## Community Tools + +There are a number of community built tools that you can use to help your SubQuery Network experience. Feel free to contribute your own. + +:::warning +Please note that none of these tools have been endorsed by the SubQuery team and descriptions have been written by third parties. This section is open for contribution by all. + +Please research and use at your own risk +::: + +### SQTScan + +[SQTScan](https://sqtscan.com/?ref=blog.subquery.network) is a ***community-owned application*** designed specifically to help expert users such as Node Operators and Delegators to gain a deeper understanding of historical rewards on the SubQuery Network and optimise their participation. + +SQT Scan helps expert users (Node Operators and Delegators) with: + +1. **Education:** Understand how their rewards are calculated and how they should make decisions +2. **Compare Opportunities:** Decide which projects to deploy based on historical rewards +3. **Compare Others:** Compare their APY with other Node Operators, overall and by project, to see how they're performing relatively +4. **APY Maximisation:** Identify ways to increase their APY + +If you would like to add your support, suggest improvements or new features, or even contribute code, it is welcomed! + +Links + +- [SQTSCan](https://sqtscan.com) +- [Github](https://github.com/HuberTRoy/subquery-sqtscan) + +### Indexer Monitoring Tools (by web3cdn.network) + +Five products: +1. **Toolkit:** A toolkit contains everything you need to index, monitor and properly access from any device +2. **Telegram Uptime Bot:** Eagle Eye is a bot which will provide you live updates in Telegram on the uptime of your indexer +3. **UpdateHunter** +4. **Snapshots** +5. **Snapshots Toolkit** + +Toolkit Features: + +- Extended monitoring of all indexer parameters, sync time, balances, issues. Metrics also support Alerting rules +- Flags problems that have arisen through monitoring and help you to not miss rewards. +- Makes your indexer and infrastructure secure +- Ease of updating without the risk of changing important parameters +- Secured access to dangerous zone with your own VPN, Access from mobile devices to monitoring, and internal services in any time. +- Very easy installation and user error protection + +Eagle Eye Telegram Bot Notifications: + +- Provide reports on your indexer's uptime - help you to know about an errors in advance and not lose funds. +- If your indexer is offline +- If your project is somehow unavailable +- If you do not have enough funds +- If your certificate is about to expire +- And more + +UpdateHunter: + + - A tool that notifies you when a project is updated or a new project is created, providing complete documentation to enable fast and secure upgrades. + - It scans the blockchain and alerts an indexer via a Telegram channel about updates, automati­cally generating instructions and SQL queries. + - The bot integrates with GitHub, posting documentation updates to a public repository. + + Snapshots: + + - Service generates daily snapshots for all active projects + - This service is ideal if your indexer: + - Is newly deployed and you want to avoid ~1 month of downtime for project synchronization + - Has experienced data loss (corrupted disk, hardware failures, or software issues) + + Snapshots Toolkit: + + - Open Source toolkit for an own snapshot generator. With this repository indexer can generate its own snapshots. + +Links + +- [Toolkit Github](https://toolkit.subquery.dev/) +- [Eagle Eye Telegram Bot](https://eagleeye.subquery.dev/) +- [UpdateHunter](https://eagleeye.subquery.dev/updates) +- [Snapshots](https://snapshots.subquery.dev/) +- [Snapshots Toolkit](https://snapshots.subquery.dev/toolkit) + +### Kepler Network Dashboard (by DappLooker) + +To monitor the progress and performance of the Kepler Network, DappLooker has created a dashboard that displays the following key metrics: + +- Active Indexers / Delegators: The number of Indexers and Delegators who are actively participating in the Kepler Network. +- Weekly Indexer Stake / Delegation: The amount of kSQT that Indexers and Delegators have staked on the Kepler Network in the past week. +- Weekly Rewards: The amount of kSQT that Indexers have earned as rewards for serving data requests on the Kepler Network in the past week. +- Stake Distribution: The distribution of kSQT stakes between Indexers and Delegators on the Kepler Network. + +To make the data more accessible and user-friendly, DappLooker has also made the SubQuery Kepler data publicly available for everyone. This means that anyone can create custom dashboards tailored to their needs using the indexed data from the Kepler Network. + +Links + +- [Dashboard](https://dapplooker.com/dashboard/subquery-kepler-network-dashboard-577) +- [Indexed Dataset](https://analytics.dapplooker.com/browse/2/schema/subquery_kepler) +- [Announcement Article](https://blog.dapplooker.com/dapplooker-integrates-subquery-kepler-network-to-provide-analytics-and-dashboard-solution-to-web3-fb0c5aeea899) diff --git a/docs/ru/subquery_network/faq.md b/docs/ru/subquery_network/faq.md new file mode 100644 index 00000000000..a298d22efe5 --- /dev/null +++ b/docs/ru/subquery_network/faq.md @@ -0,0 +1,78 @@ +# Frequently Asked Questions + +FAQs for specific network participants: + +- [Node Operators](./node_operators/setup/faq.md) +- [Consumers](./consumers/faq.md) + +## Proof-of-indexing + +[Proof Of Index](./introduction/proof-of-index.md) + +## How do you ensure indexed data accuracy? + +Ensured by [Proof Of Index](./introduction/proof-of-index.md) + +## Are there a list of RPC providers that can provide support for \_\_\_ chain? + +SubQuery Network is decentralised, so we can't say what individual node operators would decide to serve you, nor can we say what infrastructure the node operators use and where it is hosted + +## What is the integration and deployment timeline for RPCs? + +SubQuery team can enable the RPC in a few days depending on how long an archive node on your network would take to sync. + +## Where is your/provider's infra hosted? + +Depends on the provider, SubQuery don't dictate this. But SubQuery gateway encourages competition to provide high performance, low latency, and geographically decentralised services. Most providers are running on their own bare metal for cost considerations + +## Is there a testnet environment? + +Yes, be sure to check https://dev.thechaindata.com/ + +## Is there a meaning behind SubQuery's name? + +The name "SubQuery" refers to its function in the blockchain ecosystem. A subquery is essentially a query within another query, allowing users to access data more efficiently. It is a powerful tool for indexing and querying blockchain data. + +## What was the first network that SubQuery first supported? + +SubQuery initially supported the Polkadot network, focusing on indexing and querying data for the Polkadot and its parachains. + +## How many networks do SubQuery support now? + +As of now, SubQuery supports multiple networks, including Polkadot, Kusama, Ethereum, and many others, expanding its reach to a wide array of blockchain ecosystems. + +## How does SubQuery improve blockchain data access? + +SubQuery enhances blockchain data access by providing an indexing layer that aggregates and organizes data from blockchain networks. This allows developers and applications to quickly retrieve and interact with data in a structured and efficient manner. + +## How does SubQuery differ from traditional block explorers? + +Traditional block explorers allow users to explore blockchain data in a static, non-queryable format. SubQuery, on the other hand, provides dynamic and customizable data querying, giving developers the ability to filter, process, and retrieve data in real-time for their applications. + +## What programming languages does SubQuery support? + +SubQuery primarily supports JavaScript and TypeScript for building queries and processing data. Developers can use these languages to define the structure and logic for data retrieval from supported networks. + +## Is SubQuery open-source? + +Yes, SubQuery is open-source. It encourages developers to contribute to its growth and use its tools to build decentralized applications (dApps) more efficiently. The source code is available on GitHub. + +## What are the main use cases for SubQuery? + +SubQuery is used for various purposes, such as: + +- Building decentralized applications (dApps) that need to access blockchain data. +- Indexing and querying blockchain data for analysis and reporting. +- Creating custom data solutions for blockchain ecosystems and decentralized finance (DeFi) platforms. + +## Can I deploy SubQuery on my own infrastructure? + +Yes, SubQuery can be deployed on your own infrastructure, whether on-premise or in the cloud. It offers flexibility to users who want complete control over their indexing and querying solutions. + +## How does SubQuery handle data updates and changes? + +SubQuery continuously updates its data by monitoring blockchain events in real-time. This ensures that the indexed data is always up to date, and any changes to the blockchain are reflected immediately in the data queries. + +## How can I get started with SubQuery? + +To get started with SubQuery, you can visit their official documentation, which provides step-by-step guides on setting up a project, writing queries, and deploying them on supported networks. The community also offers support through forums and Discord. diff --git a/docs/ru/subquery_network/infra-changes.md b/docs/ru/subquery_network/infra-changes.md new file mode 100644 index 00000000000..b30b5fa306d --- /dev/null +++ b/docs/ru/subquery_network/infra-changes.md @@ -0,0 +1,109 @@ +# Redefining Web3: SubQuery Network’s Bold Infrastructure Evolution + +Back in December 2023, we announced the evolution of SubQuery, in which we aim to transition from simply indexing web3 data to pioneering a complete web3 infrastructure revolution. + +Over the last year, as we’ve been building out our data indexing service and network, we realised our network is in a prime position to address broader centralisation issues throughout the web3 infrastructure landscape. + +Our mission has expanded, and so has the opportunity space we’re going to be working in. + +Read on to learn about the challenges we’re taking on and the next steps we’re taking to play a bigger role in decentralising the future. + +### The Web3 Infrastructure Landscape + +Web3 middleware services like indexers, RPCs, oracles and storage services are pivotal in blockchain dApp development. In fact, the utilisation of these middleware services is what sets apart successful, large-scale, production dApps - they accelerate performance and can scale to thousands of users, while providing a superior developer experience to bring in more users, TVL, and value. Indexers and RPCs shoulder the heavy lifting, standing as mission-critical services that underpin the functionality and efficiency of web3 applications. + +![](https://lh7-us.googleusercontent.com/2lbQyLR4fxrgV2dTqljyFV6bECXrfq3anA2k_qM6gJuWdSN01dHrVjIFU6OZeFXXJv57dwaXNQ6_lKdGtLK9YDWr0EdS7yDDv0BwZfFXT_j6aw-iu7bDxIS5ZkgliPD2mY_l5kbJXGKEqI6OWuZIEwk) + +**The current segregated web3 infrastructure landscape** + +Data indexers (like SubQuery) speed up data retrieval, enhancing performance and response times for users. They also simplify data by transforming raw blockchain information into more digestible formats, facilitating efficient development and a smooth user experience. + +Meanwhile, RPCs are pivotal for communication between blockchain nodes and external entities, facilitating data retrieval, smart contract interactions, and transaction submissions. Under the hood of your favourite dApp, tens of requests are passing through RPC providers to query and submit transactions to the network. + +While these middleware services are integral to a successful dApp, there is a significant issue that needs to be addressed. + +### Web3’s Dirty Little Secret + +There is a hidden truth behind the mask of “decentralisation” most of these middleware services wear. The reality is that many leading dApps have a significant reliance on centralised middleware components. This centralisation poses a substantial threat to the envisioned unstoppability of a web3 future, at any given moment, a single entity can undermine supposedly decentralised applications. + +Nowhere is this more apparent with RPC providers, and to a lesser extent, data indexers. These crucial services distinguish the scalable, reliable, and polished dApps from rudimentary applications that go without. But due to historical challenges in the process of decentralisation, for a long time, this has been a compromise most apps have accepted. + +The call for decentralised alternatives to these pivotal middleware services is essential for the foundation of the next generation of dApps to build upon. We need to decentralise these services, without compromise. + +### SubQuery Network Evolution Revealed + +At the start we set out to create a viable decentralised solution to the data indexing problem. + +Web3 developers face great difficulties aggregating and organising data to power dApps, and SubQuery has helped thousands of developers building the world's best and biggest networks, dApps, and analytics tools by providing fast and performant data indexing. + +In 2022 we launched Kepler Network, a pre-mainnet release that enabled us to bootstrap the network sustainably by bringing onboard proficient indexers and projects. The success of Kepler lead to the realisation that the ecosystem we’ve built could bring benefits for more than just decentralised data indexing, but for middleware infrastructure as a whole. The key components of the network we have built and deployed - reward and pricing rails, service verification tools, and dispute resolution processes - are valuable for others verticals. + +Knowing that the SubQuery Network could give our existing community of top node runners a solution to trustlessly receive rewards for running data indexing infrastructure, why couldn’t it work for those other services, for other parts of the dApp tech stack? + +We realised the full potential of the SubQuery Network mainnet should not be limited to just data indexing; its fundamental contracts, tools, and reward flows enable it to be so much more. By harnessing the power of the existing participants and mechanisms, the SubQuery Network is ready to extend to various infrastructure verticals. It dawned on us that there is a massive opportunity ahead of us when we think holistically about the entire developer experience. + +> With the launch of mainnet, the SubQuery Network will emerge as a solution to _decentralise everything_, revolutionising the entire developer experience in web3. + +![](https://lh7-us.googleusercontent.com/fXK85pf2n1zTFAsbxyhYKk4I_negGP3mNvXP_vE-_k-ppDlNQeCUPc-iKG7b2HjaeBaisWhkdDqPL8SoQb0QHW6eHI4-5Bra1GK7hrfIhzx9SW1SWgVJ9Nces5Vfza3fwYNug_nduW_8HJ-XB8eZwig) + +**The vision for SubQuery Network to encompass key web3 infrastructure components in a completely decentralised manner** + +### Starting with RPCs + +Our next step that we have completed is to decentralise the biggest infrastructure component for dApps - _Remote Procedure Call_ or RPC services. + +RPC services are still the main interface to the blockchain, under the hood of your favourite dApp, dozens of requests are passing through RPC providers to query and submit transactions to the network. They are the most critical part of the ecosystem, when one has an outage, [the effects reverberate across the industry](https://decrypt.co/47846/ethereum-backbone-infura-suffers-major-damage?ref=blog.subquery.network). + +Since SubQuery relies on performant and scalable RPCs to maximise our indexing speed, we already work extremely closely with RPC providers. On our quest to index over [115+ chains and counting](https://subquery.network/networks?ref=blog.subquery.network), we’ve discovered that the RPC ecosystem is very fractured: some ecosystems have excellent support, and some don’t, and that makes delivering an excellent indexing experience across all chains difficult. + +Across many smaller emergent networks, amateur RPC services operate to provide RPCs to various developers building on the network. These RPCs are usually run (at a loss) by the core network foundation team, and perhaps a collection of validators (for staking advertising purposes). Unfortunately for cost reasons, these RPCs are usually heavily pruned and rate limited, and have no upsell options for unrestricted access. As a result, dApp developers will often run a private RPC endpoint for their own use. This is expensive, frustrating, poses high barriers to entry, and results in no redundancy for dApp developers. + +For more established networks, one or more commercial providers may come and offer a freemium service, where there is a free plan/public endpoint, and a paid upsell to higher scale access. This serves dApp developers well, but the law of economies of scale dictate that networks tend towards a small number of hyperscale RPC providers who centralise the network and cause major outages that affect thousands of dApps when they go offline. They also extract huge economic value from a network and send that directly to big private cloud companies and VCs. + +We have built an alternative to these two dangerous equilibriums, and help decentralise everything.The SubQuery Network provides an open market for both data indexers and RPC providers and their consumers that: + +- Maintains low barriers of entry: Any node operator can join as a provider for any service on any network. +- Incentivises performance and cost: Node operators are automatically rewarded with requests based on these metrics, driving these values across the network. +- Encourages constant expansion to new chains: Node operators are free to onboard new chains and projects for first mover advantage, constantly expanding the network. + +### Enhancing RPCs - SubQuery’s Data Node + +The performance limitations of data indexers and many other applications have long been limited by the RPC endpoint. Developers have long focussed on building nodes to ensure efficient validation to ensure the safety of the network. As a result of this sacrifice, RPCs are extremely costly and they’re not at all optimised for querying. + +This is compounded by the rise of L2 chains where, with higher throughput, the query performance and cost are major outstanding issues to address. With limited querying capabilities, many don’t support complex querying languages or operations, making it inefficient to retrieve specific data. + +We have delivered the SubQuery Data Node, an enhanced and heavily-forked RPC node that is perfectly optimised for querying, especially on endpoints like `eth_getLog`, and the ability to filter transactions in a single API call. + +The Data Node is open source, allowing people to contribute, extend, or fork the implementation in any way. It supports leading layer-2s and other EVM networks initially, and they are optimised to run on the SubQuery Network in a decentralised way. + +Working together, the SubQuery Indexer and SubQuery Data Node provides the most performant indexing performance possible and in a completely decentralised way thanks to the SubQuery Network. + +Our node runners are able to run these data nodes on the network, bringing powerful and cost-effective RPC access to all, cementing SubQuery’s position as the fastest decentralised data indexer in web3. + +### Democratising RPCs - SubQuery’s Sharded Data Node + +In the final stage of our RPC journey, SubQuery will work to democratise RPCs (and solve [EIP-4444](https://eips.ethereum.org/EIPS/eip-4444?ref=blog.subquery.network)) in the process by delivering the Sharded Data Node, which will make RPCs cheaper to run and operate by node providers. + +In the last few months we’ve spoken with many RPC providers in the ecosystem. In many networks (in particular Cosmos), small scale RPC services operate to provide RPCs to various developers building on the network. Unfortunately for cost reasons, these RPCs are usually heavily pruned and rate limited and have no upsell options for unrestricted access. + +One of the key reasons for this is the sheer size of the node - an Ethereum archive requires about ~12 TB on Geth, an Osmosis archive is at least the same. This is an incredible cost that limits these nodes to large centralised infrastructure providers. + +SubQuery recognises that in order to decentralised RPCs correctly, you need to be able to make running these nodes easier and more accessible to everyday users. Currently the storage is made smaller by “pruning” data, which is intentionally discarding older information while cryptographically confirming that the recent data that is valid. This works fine for writing transactions, but means that indexers and other services are unable to query old data. + +SubQuery will extend its Data Node to support sharding, that is making each Data Node smaller by splitting up block ranges between node operators. Since SubQuery’s Data Node only runs within the boundaries of a specific block range, it does not need to constantly sync new data, allowing it to optimise further for query performance rather than validation and verification. + +The SubQuery Sharded node won’t just shard historical data, but also shard the historical state within the node. By itself, this won’t change much, but these sharded nodes will be optimised to run on the network, and the network will be designed to combine all these shards to expose a single unified endpoint that appears to cover the entire historical state of the chain. Developers will benefit from the entire historical state of the given network, and node operators will benefit from significantly lower running costs, creating a more cost efficient network. + +This is a revolutionary step forward for the RPC industry, and a potential solution to one of the great challenges facing older and larger blockchains with their state bloat size. This solution has the potential to help scale Ethereum, solve [EIP-4444](https://eips.ethereum.org/EIPS/eip-4444?ref=blog.subquery.network), and greatly support proliferation of Layer-2’s and rollups, while further democratising and decentralising the SubQuery Network. + +### Summary + +The future of SubQuery is not simply indexing web3 data, but pioneering a complete web3 infrastructure revolution. web3 middleware services like indexers and RPC providers are pivotal in blockchain dApp development, but there is a hidden truth behind the mask of “decentralisation” most of these middleware services wear. The reality is a significant reliance on centralised middleware components, which poses a substantial threat to the envisioned unstoppability of a web3 future. + +Our mission has expanded, and so has the opportunity space we’re going to be working in. We need to decentralise these services, without compromise. We’ve already delivered breakthroughs in decentralised data indexing, but our next steps will focus on enhancing the performance of RPCs with the SubQuery Data Node, and then to bring RPCs to the masses, with SubQuery’s Sharded Data Nodes. These steps together, will help unlock the next level of performance increases in web3. + +No other team today is better equipped at working to provide a holistic approach to solving this problem. In summary, our vision goes beyond data indexing; it's about revolutionising how data and infrastructure services are organised and accessed. + +Pioneering fast, flexible, and scalable decentralised infrastructure, we will help power web3's transition to an open, efficient and user-centric future. Join us in this journey. With SubQuery, it's not just about building for today, but architecting a decentralised, inclusive future. + +_Let's shape the future of web3, together._ \ No newline at end of file diff --git a/docs/ru/subquery_network/welcome.md b/docs/ru/subquery_network/welcome.md new file mode 100644 index 00000000000..53c14ae9c38 --- /dev/null +++ b/docs/ru/subquery_network/welcome.md @@ -0,0 +1,283 @@ +--- +footer: false +lastUpdated: false +contributors: false +editLink: false +photoSwipe: false +--- + + +
+
+
+ SubQuery Network + + The SubQuery Network is the most scalable, reliable, and unified data infrastructure network. 1,000s of decentralised Indexers and RPC providers simplify the data layer for a myriad of applications and use cases. + +
+
+
+ +
+
+ + + One network, all your web3 data needs + +
+ +
+ + {{ item.title }} + {{ item.subtitle }} + + {{ content }} + + + + + + +
+ +
+ Anyone can participate + + There’s a role for everyone in the network, from highly technical + developers to those with some experience and blockchain beginners. Find + out how you can participate and be rewarded. + +
+
+ + {{ anyone.name }} + + {{ anyone.description }} + + + + +
+
+ + +
+ Get Started with the Network Today + Our decentralised network is live and vibrant +
+ + + {{ item.title }} + + {{ item.desc }} + + + +
+
+ + +
+
+ + diff --git a/docs/th/subquery_network/2024.md b/docs/th/subquery_network/2024.md new file mode 100644 index 00000000000..412a1f34fc1 --- /dev/null +++ b/docs/th/subquery_network/2024.md @@ -0,0 +1,62 @@ +# 2024 in Review: SubQuery’s Top 5 Milestones + +As we look back on 2024, we’re proud to call it a major “year of firsts” for us here at SubQuery. This year was filled with groundbreaking achievements, major launches, and remarkable community growth. The year has flown by but it also feels so long ago that we had our TGE, CEX Listing and SubQuery Network mainnet launch - all on the same day! + +Let’s celebrate some of the key milestones that made 2024 unforgettable. + +## 1. Mainnet Launch + +After an extremely successful Public Sale on 30 January 2024, selling out of SubQuery’s native token (SQT) in less than 2 hours, we worked very hard to launch the SubQuery Network mainnet on 23 February 2024. Powered by SQT and launched on Base, immediately users could consume and/or index data from over 150 networks ([now over 270 networks](https://subquery.network/networks)). + +Almost 1 year on and we have: + +- 46 globally distributed and highly skilled Node Operators servicing the network +- More than 330 million SQT staked and delegated in the Network +- Serving more than 50 million RPC requests every day +- An overall average APY of 22.28% and much higher for Node Operators (94.66%) + +## 2. SQT Token Generation Event + +Combined with the Mainnet launch, we ambitiously chose to do our TGE and day one CEX listing with Bybit on the same day (23 February 2024) as well. The SubQuery Token (SQT) is designed as a utility token that powers the SubQuery Network, providing an incentive for participation, as well as serving as a medium of exchange for transactions within the SubQuery Network. Consumers of data commit SQT in exchange for RPC queries or indexed data from our globally distributed Node Operators. + +Today, you can acquire SQT through any of these centralised exchange: + +- [Bybit](https://www.bybit.com/en/trade/spot/SQT/USDT) +- [Gate.io](https://www.gate.io/trade/SQT_USDT) +- [Crypto.com](https://crypto.com/exchange/trade/SQT_USD) +- [MEXC](https://www.mexc.com/exchange/SQT_USDT) + +SQT is on a number of DEX Pools however most liquidity is on Uniswap. + +- [Uniswap Pool on Ethereum](https://app.uniswap.org/explore/tokens/ethereum/0x09395a2A58DB45db0da254c7EAa5AC469D8bDc85) +- [Unsiwap Pool on Base](https://app.uniswap.org/explore/tokens/base/0x858c50c3af1913b0e849afdb74617388a1a5340d) + +## 3. Expansion into Decentralised RPCs + +This vision was announced at the end of 2023 but really came to fruition in 2024. We expanded our network capabilities by introducing support for Remote Procedure Call (RPC) services. This was the first step of expanding away from just a data indexer to a major decentralised infrastructure network, allowing us to support a more accessible, interoperable, and developer-friendly web3 ecosystem. + +Now serving RPC requests on 20+ networks, [get your decentralised RPCs from the SubQuery Network today](https://subquery.network/rpc/list/). + +### 4\. Launching Artificial Intelligence Tools + +SubQuery took its first steps into the AI space by launching decentralised AI inference model hosting on the SubQuery Network plus a new developer SDK called the AI App Framework. This massively expands the tools and services that we can offer to web3 builders across, all under one roof. + +The AI App Framework allows you to build, deploy, and run production AI apps on the SubQuery Network in a trusted and decentralised environment. AI apps are self-contained and easily scalable AI agents that you can use to power your intelligent applications. They are sandboxed to a trusted runner and can be easily distributed and scaled horizontally across the SubQuery Network. + +[Start building AI Apps today!](https://academy.subquery.network/ai/welcome.html) + +## 5. SubQuery Rebranding + +As we expanded into the Artificial Intelligence space, we felt a new look was warranted to match our new pursuit. So we rebranded to a complete new look with sleek chromatic details and a flower/root narrative. + +The flower and root theme symbolises SubQuery’s commitment to fostering innovation and growth within the blockchain community. The roots represent the deep, stable, and reliable infrastructure that SubQuery provides, while the flowers symbolise the diverse and vibrant dApps that developers can create with the help of this infrastructure. + +[Check out the new look](https://subquery.network/). + +## Looking Ahead to 2025 + +While 2024 was full of exciting milestones, we know this is just the beginning. With a stronger community, enhanced technology, and bold new goals, we’re ready to scale even greater heights in 2025. With our most recent [2024 roadmap](https://blog.subquery.network/subquery-releases-network-roadmap-for-2024/?lng=en) almost fully accomplished, stay tuned for a new version packed with ambitious plans. + +Thank you to everyone—developers, partners, and community members—who helped make this year possible. + +Here’s to many more firsts ahead! \ No newline at end of file diff --git a/docs/th/subquery_network/about.md b/docs/th/subquery_network/about.md new file mode 100644 index 00000000000..1699165773b --- /dev/null +++ b/docs/th/subquery_network/about.md @@ -0,0 +1,47 @@ +# About Us + +Our mission is to innovate Web3 infrastructure so builders can decentralise the next generation of applications - without compromise. + +Pioneering fast, flexible, and scalable decentralised infrastructure, we power Web3's transition to an open, efficient and user-centric future.Join us on our journey to build the future of web3 infrastructure. + +[Join our Discord Community](https://discord.com/invite/subquery) + +## Core team + +SubQuery has a deep bench of highly skilled talent of engineers, customer service, and operations personnel.Headquartered in Singapore, we have key representation in New Zealand, Lisbon, and Sydney. + +### Ian He - CTO and Co-Founder + +Ian forged his interest in blockchain during his tenure as the Technical Team Lead for Centrality where he led the development of core components of CENNZnet. Ian also led a team that won 2nd place in the world's first Substrate/Polkadot Hackathon in 2019. Prior to this, Ian obtained significant experience working on large-scale infrastructure working for Alipay and Yihaodian.com. + +### Scott Twiname - Principal Dev of SDK + +Scott has a large wealth of experience in blockchain development. He started out learning about blockchain in his own time and eventually got the opportunity to apply his knowledge as a senior developer at Sylo. He has worked on all facets of blockchain development from smart contracts, dapps, decentralised technologies and wallet integration for various networks including Bitcoin, Ethereum, Tezos and CENNZnet. + +### Marta Adamczyk - Head of Business Development + +Marta is a huge tech advocate, Web3 enthusiast and IT-meetup addict. She helps SubQuery customers develop and scale their projects by delivering technical consultancy, developer-oriented content and technical education. Former product evangelist, frontend developer, digital marketer, educator and sales manager with corporate and start-up experience. + +### Brittany Seales - Head of Marketing + +Brittany has a background in chemistry but since then she became the closest point of contact with SubQuery customers and helped ensure that every SubQuery customer gets an excellent on-boarding experience. Naturally Brittany is heavily integrated with the community and content marketing and has since taken over this area. Sadly, no amount of interaction with successful blockchain projects has give her the ability to pick a winning NFT! + +### James Bayly - Advisor + +Well-versed across the business, from product engineering to being the face of SubQuery, James is also a serial entrepreneur leading several tech companies. When he’s not in Berlin sipping cocktails, you’ll find him hiking up the Routeburn Track in New Zealand. + +## Our Manifesto + +In the new era of Web3, true power isn't bought – it's built with innovation and vision. +We are SubQuery, not just a company, but a revolution. Our mission: to lead the charge in decentralising the future. +We're pioneering an infrastructure that's fast, flexible, scalable – ready to power tomorrow's Web3 world. Crafting an open, efficient, and user-centric digital landscape. +For the visionaries, the forward-thinkers, the builders of tomorrow – SubQuery is your platform. +Join us in this journey. With SubQuery, it's not just about building for today, but architecting a decentralised, inclusive future. Let's shape the future of Web3, together. + +## About SubQuery + +SubQuery Network is innovating in web3 infrastructure with tools that empower builders to decentralise without compromise. SubQuery’s infrastructure network offers everything from data indexers, RPCs and AI agents - all fully decentralised and production ready. + +Our fast, flexible, and open data indexer supercharges thousands of dApps on nearly 300 networks. Our Sharded Data Node will provide breakthroughs in the RPC industry and our AI App framework makes building AI apps easier than ever before. We pioneer the web3 revolution for visionaries and forward-thinkers. We’re not just a company — we’re a movement driving an inclusive and decentralised web3 era, together. + +[Linktree](https://linktr.ee/subquerynetwork) | [Website](https://subquery.network) | [Discord](https://discord.com/invite/subquery) | [Telegram](https://t.me/subquerynetworkcommunity) | [Twitter](https://twitter.com/subquerynetwork) | [Blog](https://blog.subquery.network/?lng=en) | [Medium](https://medium.com/@subquery) | [LinkedIn](https://www.linkedin.com/company/subquery) | [YouTube](https://www.youtube.com/c/SubQueryNetwork) \ No newline at end of file diff --git a/docs/th/subquery_network/community.md b/docs/th/subquery_network/community.md new file mode 100644 index 00000000000..59c4aaeb078 --- /dev/null +++ b/docs/th/subquery_network/community.md @@ -0,0 +1,178 @@ +# SubQuery Network Community + +The key focus of the [SubQuery Foundation](./governance/foundation.md) and community is to ensure that there is enough support that anyone, from an expert blockchain team to a new hobbyist developer, can build their own Project. Together we can pave the way to a more decentralised future! + +## Connecting with others + +Discord is our main community for talking about SubQuery and learning more. You can join with [this link here](https://discord.com/invite/subquery). People most interested in the SubQuery Network will want to join `#network-general`, and Indexers or Delegators should join `#network-indexer-chat` or `#network-delegator-chat` respectively. + +When the conversation is deeper and requires more thought, we move the conversation to [our Forum](https://forum.subquery.network/). Here you will find longer topics, a history of all announcements to Network, and deeper conversation about the direction of the network. Feel free to join and start posting at [forum.subquery.network](https://forum.subquery.network/)! + +### Join the Node Operator community + +If you're a Node Operator on the Network, we strongly suggest that you keep up with the latest news, announcements, and tips by joining the following Discord channels: + +- `#network-announcements` +- `#network-general` +- `#network-services-release` +- `#network-indexer-announcements` +- `#network-indexer-general` + +## Contributing to Codebases + +SubQuery is open source and open to the community, if you want to contribute (e.g. add a feature, fix a bug, suggest an improvement, or even just fix a typo in our documentation), please review our [contributing guide](../miscellaneous/contributing.md). + +The following codebases are where you can find code for all the contracts, applications, and backend SubQuery projects. We're looking forward to seeing your contributions! + +### `network-app` + +dApp for indexers, consumers and delegators interact with SubQuery Network. + + + +### `network-airdrop-app` + +dApp for users to interact with the SubQuery airdrop contract. + + + +### `network-contracts` + +Contracts for SubQuery Network. + + + +You can find smart contract addresses for all network contracts here in [GitHub](https://github.com/subquery/network-contracts/blob/develop/publish/mainnet.json) + +### `network-app-backend` + +SubQuery project for the backend of the SubQuery App. + + + +### `network-airdrop-app-backend` + +SubQuery project for the backend of the SubQuery Airdrop App. + + + +### `network-swap-app-backend` + +SubQuery project for the backend of the SubQuery Swap App. + + + +### `network-indexer-services` + +Services that Indexers run to connect and serve data to the SubQuery Network. + + + +### `network-clients` + +Client SDKs for SubQuery Network. + + + +### `subquery-component-library` + +React UI component library for SubQuery dApps. + + + +## Community Tools + +There are a number of community built tools that you can use to help your SubQuery Network experience. Feel free to contribute your own. + +:::warning +Please note that none of these tools have been endorsed by the SubQuery team and descriptions have been written by third parties. This section is open for contribution by all. + +Please research and use at your own risk +::: + +### SQTScan + +[SQTScan](https://sqtscan.com/?ref=blog.subquery.network) is a ***community-owned application*** designed specifically to help expert users such as Node Operators and Delegators to gain a deeper understanding of historical rewards on the SubQuery Network and optimise their participation. + +SQT Scan helps expert users (Node Operators and Delegators) with: + +1. **Education:** Understand how their rewards are calculated and how they should make decisions +2. **Compare Opportunities:** Decide which projects to deploy based on historical rewards +3. **Compare Others:** Compare their APY with other Node Operators, overall and by project, to see how they're performing relatively +4. **APY Maximisation:** Identify ways to increase their APY + +If you would like to add your support, suggest improvements or new features, or even contribute code, it is welcomed! + +Links + +- [SQTSCan](https://sqtscan.com) +- [Github](https://github.com/HuberTRoy/subquery-sqtscan) + +### Indexer Monitoring Tools (by web3cdn.network) + +Five products: +1. **Toolkit:** A toolkit contains everything you need to index, monitor and properly access from any device +2. **Telegram Uptime Bot:** Eagle Eye is a bot which will provide you live updates in Telegram on the uptime of your indexer +3. **UpdateHunter** +4. **Snapshots** +5. **Snapshots Toolkit** + +Toolkit Features: + +- Extended monitoring of all indexer parameters, sync time, balances, issues. Metrics also support Alerting rules +- Flags problems that have arisen through monitoring and help you to not miss rewards. +- Makes your indexer and infrastructure secure +- Ease of updating without the risk of changing important parameters +- Secured access to dangerous zone with your own VPN, Access from mobile devices to monitoring, and internal services in any time. +- Very easy installation and user error protection + +Eagle Eye Telegram Bot Notifications: + +- Provide reports on your indexer's uptime - help you to know about an errors in advance and not lose funds. +- If your indexer is offline +- If your project is somehow unavailable +- If you do not have enough funds +- If your certificate is about to expire +- And more + +UpdateHunter: + + - A tool that notifies you when a project is updated or a new project is created, providing complete documentation to enable fast and secure upgrades. + - It scans the blockchain and alerts an indexer via a Telegram channel about updates, automati­cally generating instructions and SQL queries. + - The bot integrates with GitHub, posting documentation updates to a public repository. + + Snapshots: + + - Service generates daily snapshots for all active projects + - This service is ideal if your indexer: + - Is newly deployed and you want to avoid ~1 month of downtime for project synchronization + - Has experienced data loss (corrupted disk, hardware failures, or software issues) + + Snapshots Toolkit: + + - Open Source toolkit for an own snapshot generator. With this repository indexer can generate its own snapshots. + +Links + +- [Toolkit Github](https://toolkit.subquery.dev/) +- [Eagle Eye Telegram Bot](https://eagleeye.subquery.dev/) +- [UpdateHunter](https://eagleeye.subquery.dev/updates) +- [Snapshots](https://snapshots.subquery.dev/) +- [Snapshots Toolkit](https://snapshots.subquery.dev/toolkit) + +### Kepler Network Dashboard (by DappLooker) + +To monitor the progress and performance of the Kepler Network, DappLooker has created a dashboard that displays the following key metrics: + +- Active Indexers / Delegators: The number of Indexers and Delegators who are actively participating in the Kepler Network. +- Weekly Indexer Stake / Delegation: The amount of kSQT that Indexers and Delegators have staked on the Kepler Network in the past week. +- Weekly Rewards: The amount of kSQT that Indexers have earned as rewards for serving data requests on the Kepler Network in the past week. +- Stake Distribution: The distribution of kSQT stakes between Indexers and Delegators on the Kepler Network. + +To make the data more accessible and user-friendly, DappLooker has also made the SubQuery Kepler data publicly available for everyone. This means that anyone can create custom dashboards tailored to their needs using the indexed data from the Kepler Network. + +Links + +- [Dashboard](https://dapplooker.com/dashboard/subquery-kepler-network-dashboard-577) +- [Indexed Dataset](https://analytics.dapplooker.com/browse/2/schema/subquery_kepler) +- [Announcement Article](https://blog.dapplooker.com/dapplooker-integrates-subquery-kepler-network-to-provide-analytics-and-dashboard-solution-to-web3-fb0c5aeea899) diff --git a/docs/th/subquery_network/faq.md b/docs/th/subquery_network/faq.md new file mode 100644 index 00000000000..a298d22efe5 --- /dev/null +++ b/docs/th/subquery_network/faq.md @@ -0,0 +1,78 @@ +# Frequently Asked Questions + +FAQs for specific network participants: + +- [Node Operators](./node_operators/setup/faq.md) +- [Consumers](./consumers/faq.md) + +## Proof-of-indexing + +[Proof Of Index](./introduction/proof-of-index.md) + +## How do you ensure indexed data accuracy? + +Ensured by [Proof Of Index](./introduction/proof-of-index.md) + +## Are there a list of RPC providers that can provide support for \_\_\_ chain? + +SubQuery Network is decentralised, so we can't say what individual node operators would decide to serve you, nor can we say what infrastructure the node operators use and where it is hosted + +## What is the integration and deployment timeline for RPCs? + +SubQuery team can enable the RPC in a few days depending on how long an archive node on your network would take to sync. + +## Where is your/provider's infra hosted? + +Depends on the provider, SubQuery don't dictate this. But SubQuery gateway encourages competition to provide high performance, low latency, and geographically decentralised services. Most providers are running on their own bare metal for cost considerations + +## Is there a testnet environment? + +Yes, be sure to check https://dev.thechaindata.com/ + +## Is there a meaning behind SubQuery's name? + +The name "SubQuery" refers to its function in the blockchain ecosystem. A subquery is essentially a query within another query, allowing users to access data more efficiently. It is a powerful tool for indexing and querying blockchain data. + +## What was the first network that SubQuery first supported? + +SubQuery initially supported the Polkadot network, focusing on indexing and querying data for the Polkadot and its parachains. + +## How many networks do SubQuery support now? + +As of now, SubQuery supports multiple networks, including Polkadot, Kusama, Ethereum, and many others, expanding its reach to a wide array of blockchain ecosystems. + +## How does SubQuery improve blockchain data access? + +SubQuery enhances blockchain data access by providing an indexing layer that aggregates and organizes data from blockchain networks. This allows developers and applications to quickly retrieve and interact with data in a structured and efficient manner. + +## How does SubQuery differ from traditional block explorers? + +Traditional block explorers allow users to explore blockchain data in a static, non-queryable format. SubQuery, on the other hand, provides dynamic and customizable data querying, giving developers the ability to filter, process, and retrieve data in real-time for their applications. + +## What programming languages does SubQuery support? + +SubQuery primarily supports JavaScript and TypeScript for building queries and processing data. Developers can use these languages to define the structure and logic for data retrieval from supported networks. + +## Is SubQuery open-source? + +Yes, SubQuery is open-source. It encourages developers to contribute to its growth and use its tools to build decentralized applications (dApps) more efficiently. The source code is available on GitHub. + +## What are the main use cases for SubQuery? + +SubQuery is used for various purposes, such as: + +- Building decentralized applications (dApps) that need to access blockchain data. +- Indexing and querying blockchain data for analysis and reporting. +- Creating custom data solutions for blockchain ecosystems and decentralized finance (DeFi) platforms. + +## Can I deploy SubQuery on my own infrastructure? + +Yes, SubQuery can be deployed on your own infrastructure, whether on-premise or in the cloud. It offers flexibility to users who want complete control over their indexing and querying solutions. + +## How does SubQuery handle data updates and changes? + +SubQuery continuously updates its data by monitoring blockchain events in real-time. This ensures that the indexed data is always up to date, and any changes to the blockchain are reflected immediately in the data queries. + +## How can I get started with SubQuery? + +To get started with SubQuery, you can visit their official documentation, which provides step-by-step guides on setting up a project, writing queries, and deploying them on supported networks. The community also offers support through forums and Discord. diff --git a/docs/th/subquery_network/infra-changes.md b/docs/th/subquery_network/infra-changes.md new file mode 100644 index 00000000000..b30b5fa306d --- /dev/null +++ b/docs/th/subquery_network/infra-changes.md @@ -0,0 +1,109 @@ +# Redefining Web3: SubQuery Network’s Bold Infrastructure Evolution + +Back in December 2023, we announced the evolution of SubQuery, in which we aim to transition from simply indexing web3 data to pioneering a complete web3 infrastructure revolution. + +Over the last year, as we’ve been building out our data indexing service and network, we realised our network is in a prime position to address broader centralisation issues throughout the web3 infrastructure landscape. + +Our mission has expanded, and so has the opportunity space we’re going to be working in. + +Read on to learn about the challenges we’re taking on and the next steps we’re taking to play a bigger role in decentralising the future. + +### The Web3 Infrastructure Landscape + +Web3 middleware services like indexers, RPCs, oracles and storage services are pivotal in blockchain dApp development. In fact, the utilisation of these middleware services is what sets apart successful, large-scale, production dApps - they accelerate performance and can scale to thousands of users, while providing a superior developer experience to bring in more users, TVL, and value. Indexers and RPCs shoulder the heavy lifting, standing as mission-critical services that underpin the functionality and efficiency of web3 applications. + +![](https://lh7-us.googleusercontent.com/2lbQyLR4fxrgV2dTqljyFV6bECXrfq3anA2k_qM6gJuWdSN01dHrVjIFU6OZeFXXJv57dwaXNQ6_lKdGtLK9YDWr0EdS7yDDv0BwZfFXT_j6aw-iu7bDxIS5ZkgliPD2mY_l5kbJXGKEqI6OWuZIEwk) + +**The current segregated web3 infrastructure landscape** + +Data indexers (like SubQuery) speed up data retrieval, enhancing performance and response times for users. They also simplify data by transforming raw blockchain information into more digestible formats, facilitating efficient development and a smooth user experience. + +Meanwhile, RPCs are pivotal for communication between blockchain nodes and external entities, facilitating data retrieval, smart contract interactions, and transaction submissions. Under the hood of your favourite dApp, tens of requests are passing through RPC providers to query and submit transactions to the network. + +While these middleware services are integral to a successful dApp, there is a significant issue that needs to be addressed. + +### Web3’s Dirty Little Secret + +There is a hidden truth behind the mask of “decentralisation” most of these middleware services wear. The reality is that many leading dApps have a significant reliance on centralised middleware components. This centralisation poses a substantial threat to the envisioned unstoppability of a web3 future, at any given moment, a single entity can undermine supposedly decentralised applications. + +Nowhere is this more apparent with RPC providers, and to a lesser extent, data indexers. These crucial services distinguish the scalable, reliable, and polished dApps from rudimentary applications that go without. But due to historical challenges in the process of decentralisation, for a long time, this has been a compromise most apps have accepted. + +The call for decentralised alternatives to these pivotal middleware services is essential for the foundation of the next generation of dApps to build upon. We need to decentralise these services, without compromise. + +### SubQuery Network Evolution Revealed + +At the start we set out to create a viable decentralised solution to the data indexing problem. + +Web3 developers face great difficulties aggregating and organising data to power dApps, and SubQuery has helped thousands of developers building the world's best and biggest networks, dApps, and analytics tools by providing fast and performant data indexing. + +In 2022 we launched Kepler Network, a pre-mainnet release that enabled us to bootstrap the network sustainably by bringing onboard proficient indexers and projects. The success of Kepler lead to the realisation that the ecosystem we’ve built could bring benefits for more than just decentralised data indexing, but for middleware infrastructure as a whole. The key components of the network we have built and deployed - reward and pricing rails, service verification tools, and dispute resolution processes - are valuable for others verticals. + +Knowing that the SubQuery Network could give our existing community of top node runners a solution to trustlessly receive rewards for running data indexing infrastructure, why couldn’t it work for those other services, for other parts of the dApp tech stack? + +We realised the full potential of the SubQuery Network mainnet should not be limited to just data indexing; its fundamental contracts, tools, and reward flows enable it to be so much more. By harnessing the power of the existing participants and mechanisms, the SubQuery Network is ready to extend to various infrastructure verticals. It dawned on us that there is a massive opportunity ahead of us when we think holistically about the entire developer experience. + +> With the launch of mainnet, the SubQuery Network will emerge as a solution to _decentralise everything_, revolutionising the entire developer experience in web3. + +![](https://lh7-us.googleusercontent.com/fXK85pf2n1zTFAsbxyhYKk4I_negGP3mNvXP_vE-_k-ppDlNQeCUPc-iKG7b2HjaeBaisWhkdDqPL8SoQb0QHW6eHI4-5Bra1GK7hrfIhzx9SW1SWgVJ9Nces5Vfza3fwYNug_nduW_8HJ-XB8eZwig) + +**The vision for SubQuery Network to encompass key web3 infrastructure components in a completely decentralised manner** + +### Starting with RPCs + +Our next step that we have completed is to decentralise the biggest infrastructure component for dApps - _Remote Procedure Call_ or RPC services. + +RPC services are still the main interface to the blockchain, under the hood of your favourite dApp, dozens of requests are passing through RPC providers to query and submit transactions to the network. They are the most critical part of the ecosystem, when one has an outage, [the effects reverberate across the industry](https://decrypt.co/47846/ethereum-backbone-infura-suffers-major-damage?ref=blog.subquery.network). + +Since SubQuery relies on performant and scalable RPCs to maximise our indexing speed, we already work extremely closely with RPC providers. On our quest to index over [115+ chains and counting](https://subquery.network/networks?ref=blog.subquery.network), we’ve discovered that the RPC ecosystem is very fractured: some ecosystems have excellent support, and some don’t, and that makes delivering an excellent indexing experience across all chains difficult. + +Across many smaller emergent networks, amateur RPC services operate to provide RPCs to various developers building on the network. These RPCs are usually run (at a loss) by the core network foundation team, and perhaps a collection of validators (for staking advertising purposes). Unfortunately for cost reasons, these RPCs are usually heavily pruned and rate limited, and have no upsell options for unrestricted access. As a result, dApp developers will often run a private RPC endpoint for their own use. This is expensive, frustrating, poses high barriers to entry, and results in no redundancy for dApp developers. + +For more established networks, one or more commercial providers may come and offer a freemium service, where there is a free plan/public endpoint, and a paid upsell to higher scale access. This serves dApp developers well, but the law of economies of scale dictate that networks tend towards a small number of hyperscale RPC providers who centralise the network and cause major outages that affect thousands of dApps when they go offline. They also extract huge economic value from a network and send that directly to big private cloud companies and VCs. + +We have built an alternative to these two dangerous equilibriums, and help decentralise everything.The SubQuery Network provides an open market for both data indexers and RPC providers and their consumers that: + +- Maintains low barriers of entry: Any node operator can join as a provider for any service on any network. +- Incentivises performance and cost: Node operators are automatically rewarded with requests based on these metrics, driving these values across the network. +- Encourages constant expansion to new chains: Node operators are free to onboard new chains and projects for first mover advantage, constantly expanding the network. + +### Enhancing RPCs - SubQuery’s Data Node + +The performance limitations of data indexers and many other applications have long been limited by the RPC endpoint. Developers have long focussed on building nodes to ensure efficient validation to ensure the safety of the network. As a result of this sacrifice, RPCs are extremely costly and they’re not at all optimised for querying. + +This is compounded by the rise of L2 chains where, with higher throughput, the query performance and cost are major outstanding issues to address. With limited querying capabilities, many don’t support complex querying languages or operations, making it inefficient to retrieve specific data. + +We have delivered the SubQuery Data Node, an enhanced and heavily-forked RPC node that is perfectly optimised for querying, especially on endpoints like `eth_getLog`, and the ability to filter transactions in a single API call. + +The Data Node is open source, allowing people to contribute, extend, or fork the implementation in any way. It supports leading layer-2s and other EVM networks initially, and they are optimised to run on the SubQuery Network in a decentralised way. + +Working together, the SubQuery Indexer and SubQuery Data Node provides the most performant indexing performance possible and in a completely decentralised way thanks to the SubQuery Network. + +Our node runners are able to run these data nodes on the network, bringing powerful and cost-effective RPC access to all, cementing SubQuery’s position as the fastest decentralised data indexer in web3. + +### Democratising RPCs - SubQuery’s Sharded Data Node + +In the final stage of our RPC journey, SubQuery will work to democratise RPCs (and solve [EIP-4444](https://eips.ethereum.org/EIPS/eip-4444?ref=blog.subquery.network)) in the process by delivering the Sharded Data Node, which will make RPCs cheaper to run and operate by node providers. + +In the last few months we’ve spoken with many RPC providers in the ecosystem. In many networks (in particular Cosmos), small scale RPC services operate to provide RPCs to various developers building on the network. Unfortunately for cost reasons, these RPCs are usually heavily pruned and rate limited and have no upsell options for unrestricted access. + +One of the key reasons for this is the sheer size of the node - an Ethereum archive requires about ~12 TB on Geth, an Osmosis archive is at least the same. This is an incredible cost that limits these nodes to large centralised infrastructure providers. + +SubQuery recognises that in order to decentralised RPCs correctly, you need to be able to make running these nodes easier and more accessible to everyday users. Currently the storage is made smaller by “pruning” data, which is intentionally discarding older information while cryptographically confirming that the recent data that is valid. This works fine for writing transactions, but means that indexers and other services are unable to query old data. + +SubQuery will extend its Data Node to support sharding, that is making each Data Node smaller by splitting up block ranges between node operators. Since SubQuery’s Data Node only runs within the boundaries of a specific block range, it does not need to constantly sync new data, allowing it to optimise further for query performance rather than validation and verification. + +The SubQuery Sharded node won’t just shard historical data, but also shard the historical state within the node. By itself, this won’t change much, but these sharded nodes will be optimised to run on the network, and the network will be designed to combine all these shards to expose a single unified endpoint that appears to cover the entire historical state of the chain. Developers will benefit from the entire historical state of the given network, and node operators will benefit from significantly lower running costs, creating a more cost efficient network. + +This is a revolutionary step forward for the RPC industry, and a potential solution to one of the great challenges facing older and larger blockchains with their state bloat size. This solution has the potential to help scale Ethereum, solve [EIP-4444](https://eips.ethereum.org/EIPS/eip-4444?ref=blog.subquery.network), and greatly support proliferation of Layer-2’s and rollups, while further democratising and decentralising the SubQuery Network. + +### Summary + +The future of SubQuery is not simply indexing web3 data, but pioneering a complete web3 infrastructure revolution. web3 middleware services like indexers and RPC providers are pivotal in blockchain dApp development, but there is a hidden truth behind the mask of “decentralisation” most of these middleware services wear. The reality is a significant reliance on centralised middleware components, which poses a substantial threat to the envisioned unstoppability of a web3 future. + +Our mission has expanded, and so has the opportunity space we’re going to be working in. We need to decentralise these services, without compromise. We’ve already delivered breakthroughs in decentralised data indexing, but our next steps will focus on enhancing the performance of RPCs with the SubQuery Data Node, and then to bring RPCs to the masses, with SubQuery’s Sharded Data Nodes. These steps together, will help unlock the next level of performance increases in web3. + +No other team today is better equipped at working to provide a holistic approach to solving this problem. In summary, our vision goes beyond data indexing; it's about revolutionising how data and infrastructure services are organised and accessed. + +Pioneering fast, flexible, and scalable decentralised infrastructure, we will help power web3's transition to an open, efficient and user-centric future. Join us in this journey. With SubQuery, it's not just about building for today, but architecting a decentralised, inclusive future. + +_Let's shape the future of web3, together._ \ No newline at end of file diff --git a/docs/th/subquery_network/welcome.md b/docs/th/subquery_network/welcome.md new file mode 100644 index 00000000000..53c14ae9c38 --- /dev/null +++ b/docs/th/subquery_network/welcome.md @@ -0,0 +1,283 @@ +--- +footer: false +lastUpdated: false +contributors: false +editLink: false +photoSwipe: false +--- + + +
+
+
+ SubQuery Network + + The SubQuery Network is the most scalable, reliable, and unified data infrastructure network. 1,000s of decentralised Indexers and RPC providers simplify the data layer for a myriad of applications and use cases. + +
+
+
+ +
+
+ + + One network, all your web3 data needs + +
+ +
+ + {{ item.title }} + {{ item.subtitle }} + + {{ content }} + + + + + + +
+ +
+ Anyone can participate + + There’s a role for everyone in the network, from highly technical + developers to those with some experience and blockchain beginners. Find + out how you can participate and be rewarded. + +
+
+ + {{ anyone.name }} + + {{ anyone.description }} + + + + +
+
+ + +
+ Get Started with the Network Today + Our decentralised network is live and vibrant +
+ + + {{ item.title }} + + {{ item.desc }} + + + +
+
+ + +
+
+ + diff --git a/docs/tr/subquery_network/2024.md b/docs/tr/subquery_network/2024.md new file mode 100644 index 00000000000..412a1f34fc1 --- /dev/null +++ b/docs/tr/subquery_network/2024.md @@ -0,0 +1,62 @@ +# 2024 in Review: SubQuery’s Top 5 Milestones + +As we look back on 2024, we’re proud to call it a major “year of firsts” for us here at SubQuery. This year was filled with groundbreaking achievements, major launches, and remarkable community growth. The year has flown by but it also feels so long ago that we had our TGE, CEX Listing and SubQuery Network mainnet launch - all on the same day! + +Let’s celebrate some of the key milestones that made 2024 unforgettable. + +## 1. Mainnet Launch + +After an extremely successful Public Sale on 30 January 2024, selling out of SubQuery’s native token (SQT) in less than 2 hours, we worked very hard to launch the SubQuery Network mainnet on 23 February 2024. Powered by SQT and launched on Base, immediately users could consume and/or index data from over 150 networks ([now over 270 networks](https://subquery.network/networks)). + +Almost 1 year on and we have: + +- 46 globally distributed and highly skilled Node Operators servicing the network +- More than 330 million SQT staked and delegated in the Network +- Serving more than 50 million RPC requests every day +- An overall average APY of 22.28% and much higher for Node Operators (94.66%) + +## 2. SQT Token Generation Event + +Combined with the Mainnet launch, we ambitiously chose to do our TGE and day one CEX listing with Bybit on the same day (23 February 2024) as well. The SubQuery Token (SQT) is designed as a utility token that powers the SubQuery Network, providing an incentive for participation, as well as serving as a medium of exchange for transactions within the SubQuery Network. Consumers of data commit SQT in exchange for RPC queries or indexed data from our globally distributed Node Operators. + +Today, you can acquire SQT through any of these centralised exchange: + +- [Bybit](https://www.bybit.com/en/trade/spot/SQT/USDT) +- [Gate.io](https://www.gate.io/trade/SQT_USDT) +- [Crypto.com](https://crypto.com/exchange/trade/SQT_USD) +- [MEXC](https://www.mexc.com/exchange/SQT_USDT) + +SQT is on a number of DEX Pools however most liquidity is on Uniswap. + +- [Uniswap Pool on Ethereum](https://app.uniswap.org/explore/tokens/ethereum/0x09395a2A58DB45db0da254c7EAa5AC469D8bDc85) +- [Unsiwap Pool on Base](https://app.uniswap.org/explore/tokens/base/0x858c50c3af1913b0e849afdb74617388a1a5340d) + +## 3. Expansion into Decentralised RPCs + +This vision was announced at the end of 2023 but really came to fruition in 2024. We expanded our network capabilities by introducing support for Remote Procedure Call (RPC) services. This was the first step of expanding away from just a data indexer to a major decentralised infrastructure network, allowing us to support a more accessible, interoperable, and developer-friendly web3 ecosystem. + +Now serving RPC requests on 20+ networks, [get your decentralised RPCs from the SubQuery Network today](https://subquery.network/rpc/list/). + +### 4\. Launching Artificial Intelligence Tools + +SubQuery took its first steps into the AI space by launching decentralised AI inference model hosting on the SubQuery Network plus a new developer SDK called the AI App Framework. This massively expands the tools and services that we can offer to web3 builders across, all under one roof. + +The AI App Framework allows you to build, deploy, and run production AI apps on the SubQuery Network in a trusted and decentralised environment. AI apps are self-contained and easily scalable AI agents that you can use to power your intelligent applications. They are sandboxed to a trusted runner and can be easily distributed and scaled horizontally across the SubQuery Network. + +[Start building AI Apps today!](https://academy.subquery.network/ai/welcome.html) + +## 5. SubQuery Rebranding + +As we expanded into the Artificial Intelligence space, we felt a new look was warranted to match our new pursuit. So we rebranded to a complete new look with sleek chromatic details and a flower/root narrative. + +The flower and root theme symbolises SubQuery’s commitment to fostering innovation and growth within the blockchain community. The roots represent the deep, stable, and reliable infrastructure that SubQuery provides, while the flowers symbolise the diverse and vibrant dApps that developers can create with the help of this infrastructure. + +[Check out the new look](https://subquery.network/). + +## Looking Ahead to 2025 + +While 2024 was full of exciting milestones, we know this is just the beginning. With a stronger community, enhanced technology, and bold new goals, we’re ready to scale even greater heights in 2025. With our most recent [2024 roadmap](https://blog.subquery.network/subquery-releases-network-roadmap-for-2024/?lng=en) almost fully accomplished, stay tuned for a new version packed with ambitious plans. + +Thank you to everyone—developers, partners, and community members—who helped make this year possible. + +Here’s to many more firsts ahead! \ No newline at end of file diff --git a/docs/tr/subquery_network/about.md b/docs/tr/subquery_network/about.md new file mode 100644 index 00000000000..1699165773b --- /dev/null +++ b/docs/tr/subquery_network/about.md @@ -0,0 +1,47 @@ +# About Us + +Our mission is to innovate Web3 infrastructure so builders can decentralise the next generation of applications - without compromise. + +Pioneering fast, flexible, and scalable decentralised infrastructure, we power Web3's transition to an open, efficient and user-centric future.Join us on our journey to build the future of web3 infrastructure. + +[Join our Discord Community](https://discord.com/invite/subquery) + +## Core team + +SubQuery has a deep bench of highly skilled talent of engineers, customer service, and operations personnel.Headquartered in Singapore, we have key representation in New Zealand, Lisbon, and Sydney. + +### Ian He - CTO and Co-Founder + +Ian forged his interest in blockchain during his tenure as the Technical Team Lead for Centrality where he led the development of core components of CENNZnet. Ian also led a team that won 2nd place in the world's first Substrate/Polkadot Hackathon in 2019. Prior to this, Ian obtained significant experience working on large-scale infrastructure working for Alipay and Yihaodian.com. + +### Scott Twiname - Principal Dev of SDK + +Scott has a large wealth of experience in blockchain development. He started out learning about blockchain in his own time and eventually got the opportunity to apply his knowledge as a senior developer at Sylo. He has worked on all facets of blockchain development from smart contracts, dapps, decentralised technologies and wallet integration for various networks including Bitcoin, Ethereum, Tezos and CENNZnet. + +### Marta Adamczyk - Head of Business Development + +Marta is a huge tech advocate, Web3 enthusiast and IT-meetup addict. She helps SubQuery customers develop and scale their projects by delivering technical consultancy, developer-oriented content and technical education. Former product evangelist, frontend developer, digital marketer, educator and sales manager with corporate and start-up experience. + +### Brittany Seales - Head of Marketing + +Brittany has a background in chemistry but since then she became the closest point of contact with SubQuery customers and helped ensure that every SubQuery customer gets an excellent on-boarding experience. Naturally Brittany is heavily integrated with the community and content marketing and has since taken over this area. Sadly, no amount of interaction with successful blockchain projects has give her the ability to pick a winning NFT! + +### James Bayly - Advisor + +Well-versed across the business, from product engineering to being the face of SubQuery, James is also a serial entrepreneur leading several tech companies. When he’s not in Berlin sipping cocktails, you’ll find him hiking up the Routeburn Track in New Zealand. + +## Our Manifesto + +In the new era of Web3, true power isn't bought – it's built with innovation and vision. +We are SubQuery, not just a company, but a revolution. Our mission: to lead the charge in decentralising the future. +We're pioneering an infrastructure that's fast, flexible, scalable – ready to power tomorrow's Web3 world. Crafting an open, efficient, and user-centric digital landscape. +For the visionaries, the forward-thinkers, the builders of tomorrow – SubQuery is your platform. +Join us in this journey. With SubQuery, it's not just about building for today, but architecting a decentralised, inclusive future. Let's shape the future of Web3, together. + +## About SubQuery + +SubQuery Network is innovating in web3 infrastructure with tools that empower builders to decentralise without compromise. SubQuery’s infrastructure network offers everything from data indexers, RPCs and AI agents - all fully decentralised and production ready. + +Our fast, flexible, and open data indexer supercharges thousands of dApps on nearly 300 networks. Our Sharded Data Node will provide breakthroughs in the RPC industry and our AI App framework makes building AI apps easier than ever before. We pioneer the web3 revolution for visionaries and forward-thinkers. We’re not just a company — we’re a movement driving an inclusive and decentralised web3 era, together. + +[Linktree](https://linktr.ee/subquerynetwork) | [Website](https://subquery.network) | [Discord](https://discord.com/invite/subquery) | [Telegram](https://t.me/subquerynetworkcommunity) | [Twitter](https://twitter.com/subquerynetwork) | [Blog](https://blog.subquery.network/?lng=en) | [Medium](https://medium.com/@subquery) | [LinkedIn](https://www.linkedin.com/company/subquery) | [YouTube](https://www.youtube.com/c/SubQueryNetwork) \ No newline at end of file diff --git a/docs/tr/subquery_network/community.md b/docs/tr/subquery_network/community.md new file mode 100644 index 00000000000..59c4aaeb078 --- /dev/null +++ b/docs/tr/subquery_network/community.md @@ -0,0 +1,178 @@ +# SubQuery Network Community + +The key focus of the [SubQuery Foundation](./governance/foundation.md) and community is to ensure that there is enough support that anyone, from an expert blockchain team to a new hobbyist developer, can build their own Project. Together we can pave the way to a more decentralised future! + +## Connecting with others + +Discord is our main community for talking about SubQuery and learning more. You can join with [this link here](https://discord.com/invite/subquery). People most interested in the SubQuery Network will want to join `#network-general`, and Indexers or Delegators should join `#network-indexer-chat` or `#network-delegator-chat` respectively. + +When the conversation is deeper and requires more thought, we move the conversation to [our Forum](https://forum.subquery.network/). Here you will find longer topics, a history of all announcements to Network, and deeper conversation about the direction of the network. Feel free to join and start posting at [forum.subquery.network](https://forum.subquery.network/)! + +### Join the Node Operator community + +If you're a Node Operator on the Network, we strongly suggest that you keep up with the latest news, announcements, and tips by joining the following Discord channels: + +- `#network-announcements` +- `#network-general` +- `#network-services-release` +- `#network-indexer-announcements` +- `#network-indexer-general` + +## Contributing to Codebases + +SubQuery is open source and open to the community, if you want to contribute (e.g. add a feature, fix a bug, suggest an improvement, or even just fix a typo in our documentation), please review our [contributing guide](../miscellaneous/contributing.md). + +The following codebases are where you can find code for all the contracts, applications, and backend SubQuery projects. We're looking forward to seeing your contributions! + +### `network-app` + +dApp for indexers, consumers and delegators interact with SubQuery Network. + + + +### `network-airdrop-app` + +dApp for users to interact with the SubQuery airdrop contract. + + + +### `network-contracts` + +Contracts for SubQuery Network. + + + +You can find smart contract addresses for all network contracts here in [GitHub](https://github.com/subquery/network-contracts/blob/develop/publish/mainnet.json) + +### `network-app-backend` + +SubQuery project for the backend of the SubQuery App. + + + +### `network-airdrop-app-backend` + +SubQuery project for the backend of the SubQuery Airdrop App. + + + +### `network-swap-app-backend` + +SubQuery project for the backend of the SubQuery Swap App. + + + +### `network-indexer-services` + +Services that Indexers run to connect and serve data to the SubQuery Network. + + + +### `network-clients` + +Client SDKs for SubQuery Network. + + + +### `subquery-component-library` + +React UI component library for SubQuery dApps. + + + +## Community Tools + +There are a number of community built tools that you can use to help your SubQuery Network experience. Feel free to contribute your own. + +:::warning +Please note that none of these tools have been endorsed by the SubQuery team and descriptions have been written by third parties. This section is open for contribution by all. + +Please research and use at your own risk +::: + +### SQTScan + +[SQTScan](https://sqtscan.com/?ref=blog.subquery.network) is a ***community-owned application*** designed specifically to help expert users such as Node Operators and Delegators to gain a deeper understanding of historical rewards on the SubQuery Network and optimise their participation. + +SQT Scan helps expert users (Node Operators and Delegators) with: + +1. **Education:** Understand how their rewards are calculated and how they should make decisions +2. **Compare Opportunities:** Decide which projects to deploy based on historical rewards +3. **Compare Others:** Compare their APY with other Node Operators, overall and by project, to see how they're performing relatively +4. **APY Maximisation:** Identify ways to increase their APY + +If you would like to add your support, suggest improvements or new features, or even contribute code, it is welcomed! + +Links + +- [SQTSCan](https://sqtscan.com) +- [Github](https://github.com/HuberTRoy/subquery-sqtscan) + +### Indexer Monitoring Tools (by web3cdn.network) + +Five products: +1. **Toolkit:** A toolkit contains everything you need to index, monitor and properly access from any device +2. **Telegram Uptime Bot:** Eagle Eye is a bot which will provide you live updates in Telegram on the uptime of your indexer +3. **UpdateHunter** +4. **Snapshots** +5. **Snapshots Toolkit** + +Toolkit Features: + +- Extended monitoring of all indexer parameters, sync time, balances, issues. Metrics also support Alerting rules +- Flags problems that have arisen through monitoring and help you to not miss rewards. +- Makes your indexer and infrastructure secure +- Ease of updating without the risk of changing important parameters +- Secured access to dangerous zone with your own VPN, Access from mobile devices to monitoring, and internal services in any time. +- Very easy installation and user error protection + +Eagle Eye Telegram Bot Notifications: + +- Provide reports on your indexer's uptime - help you to know about an errors in advance and not lose funds. +- If your indexer is offline +- If your project is somehow unavailable +- If you do not have enough funds +- If your certificate is about to expire +- And more + +UpdateHunter: + + - A tool that notifies you when a project is updated or a new project is created, providing complete documentation to enable fast and secure upgrades. + - It scans the blockchain and alerts an indexer via a Telegram channel about updates, automati­cally generating instructions and SQL queries. + - The bot integrates with GitHub, posting documentation updates to a public repository. + + Snapshots: + + - Service generates daily snapshots for all active projects + - This service is ideal if your indexer: + - Is newly deployed and you want to avoid ~1 month of downtime for project synchronization + - Has experienced data loss (corrupted disk, hardware failures, or software issues) + + Snapshots Toolkit: + + - Open Source toolkit for an own snapshot generator. With this repository indexer can generate its own snapshots. + +Links + +- [Toolkit Github](https://toolkit.subquery.dev/) +- [Eagle Eye Telegram Bot](https://eagleeye.subquery.dev/) +- [UpdateHunter](https://eagleeye.subquery.dev/updates) +- [Snapshots](https://snapshots.subquery.dev/) +- [Snapshots Toolkit](https://snapshots.subquery.dev/toolkit) + +### Kepler Network Dashboard (by DappLooker) + +To monitor the progress and performance of the Kepler Network, DappLooker has created a dashboard that displays the following key metrics: + +- Active Indexers / Delegators: The number of Indexers and Delegators who are actively participating in the Kepler Network. +- Weekly Indexer Stake / Delegation: The amount of kSQT that Indexers and Delegators have staked on the Kepler Network in the past week. +- Weekly Rewards: The amount of kSQT that Indexers have earned as rewards for serving data requests on the Kepler Network in the past week. +- Stake Distribution: The distribution of kSQT stakes between Indexers and Delegators on the Kepler Network. + +To make the data more accessible and user-friendly, DappLooker has also made the SubQuery Kepler data publicly available for everyone. This means that anyone can create custom dashboards tailored to their needs using the indexed data from the Kepler Network. + +Links + +- [Dashboard](https://dapplooker.com/dashboard/subquery-kepler-network-dashboard-577) +- [Indexed Dataset](https://analytics.dapplooker.com/browse/2/schema/subquery_kepler) +- [Announcement Article](https://blog.dapplooker.com/dapplooker-integrates-subquery-kepler-network-to-provide-analytics-and-dashboard-solution-to-web3-fb0c5aeea899) diff --git a/docs/tr/subquery_network/faq.md b/docs/tr/subquery_network/faq.md new file mode 100644 index 00000000000..a298d22efe5 --- /dev/null +++ b/docs/tr/subquery_network/faq.md @@ -0,0 +1,78 @@ +# Frequently Asked Questions + +FAQs for specific network participants: + +- [Node Operators](./node_operators/setup/faq.md) +- [Consumers](./consumers/faq.md) + +## Proof-of-indexing + +[Proof Of Index](./introduction/proof-of-index.md) + +## How do you ensure indexed data accuracy? + +Ensured by [Proof Of Index](./introduction/proof-of-index.md) + +## Are there a list of RPC providers that can provide support for \_\_\_ chain? + +SubQuery Network is decentralised, so we can't say what individual node operators would decide to serve you, nor can we say what infrastructure the node operators use and where it is hosted + +## What is the integration and deployment timeline for RPCs? + +SubQuery team can enable the RPC in a few days depending on how long an archive node on your network would take to sync. + +## Where is your/provider's infra hosted? + +Depends on the provider, SubQuery don't dictate this. But SubQuery gateway encourages competition to provide high performance, low latency, and geographically decentralised services. Most providers are running on their own bare metal for cost considerations + +## Is there a testnet environment? + +Yes, be sure to check https://dev.thechaindata.com/ + +## Is there a meaning behind SubQuery's name? + +The name "SubQuery" refers to its function in the blockchain ecosystem. A subquery is essentially a query within another query, allowing users to access data more efficiently. It is a powerful tool for indexing and querying blockchain data. + +## What was the first network that SubQuery first supported? + +SubQuery initially supported the Polkadot network, focusing on indexing and querying data for the Polkadot and its parachains. + +## How many networks do SubQuery support now? + +As of now, SubQuery supports multiple networks, including Polkadot, Kusama, Ethereum, and many others, expanding its reach to a wide array of blockchain ecosystems. + +## How does SubQuery improve blockchain data access? + +SubQuery enhances blockchain data access by providing an indexing layer that aggregates and organizes data from blockchain networks. This allows developers and applications to quickly retrieve and interact with data in a structured and efficient manner. + +## How does SubQuery differ from traditional block explorers? + +Traditional block explorers allow users to explore blockchain data in a static, non-queryable format. SubQuery, on the other hand, provides dynamic and customizable data querying, giving developers the ability to filter, process, and retrieve data in real-time for their applications. + +## What programming languages does SubQuery support? + +SubQuery primarily supports JavaScript and TypeScript for building queries and processing data. Developers can use these languages to define the structure and logic for data retrieval from supported networks. + +## Is SubQuery open-source? + +Yes, SubQuery is open-source. It encourages developers to contribute to its growth and use its tools to build decentralized applications (dApps) more efficiently. The source code is available on GitHub. + +## What are the main use cases for SubQuery? + +SubQuery is used for various purposes, such as: + +- Building decentralized applications (dApps) that need to access blockchain data. +- Indexing and querying blockchain data for analysis and reporting. +- Creating custom data solutions for blockchain ecosystems and decentralized finance (DeFi) platforms. + +## Can I deploy SubQuery on my own infrastructure? + +Yes, SubQuery can be deployed on your own infrastructure, whether on-premise or in the cloud. It offers flexibility to users who want complete control over their indexing and querying solutions. + +## How does SubQuery handle data updates and changes? + +SubQuery continuously updates its data by monitoring blockchain events in real-time. This ensures that the indexed data is always up to date, and any changes to the blockchain are reflected immediately in the data queries. + +## How can I get started with SubQuery? + +To get started with SubQuery, you can visit their official documentation, which provides step-by-step guides on setting up a project, writing queries, and deploying them on supported networks. The community also offers support through forums and Discord. diff --git a/docs/tr/subquery_network/infra-changes.md b/docs/tr/subquery_network/infra-changes.md new file mode 100644 index 00000000000..b30b5fa306d --- /dev/null +++ b/docs/tr/subquery_network/infra-changes.md @@ -0,0 +1,109 @@ +# Redefining Web3: SubQuery Network’s Bold Infrastructure Evolution + +Back in December 2023, we announced the evolution of SubQuery, in which we aim to transition from simply indexing web3 data to pioneering a complete web3 infrastructure revolution. + +Over the last year, as we’ve been building out our data indexing service and network, we realised our network is in a prime position to address broader centralisation issues throughout the web3 infrastructure landscape. + +Our mission has expanded, and so has the opportunity space we’re going to be working in. + +Read on to learn about the challenges we’re taking on and the next steps we’re taking to play a bigger role in decentralising the future. + +### The Web3 Infrastructure Landscape + +Web3 middleware services like indexers, RPCs, oracles and storage services are pivotal in blockchain dApp development. In fact, the utilisation of these middleware services is what sets apart successful, large-scale, production dApps - they accelerate performance and can scale to thousands of users, while providing a superior developer experience to bring in more users, TVL, and value. Indexers and RPCs shoulder the heavy lifting, standing as mission-critical services that underpin the functionality and efficiency of web3 applications. + +![](https://lh7-us.googleusercontent.com/2lbQyLR4fxrgV2dTqljyFV6bECXrfq3anA2k_qM6gJuWdSN01dHrVjIFU6OZeFXXJv57dwaXNQ6_lKdGtLK9YDWr0EdS7yDDv0BwZfFXT_j6aw-iu7bDxIS5ZkgliPD2mY_l5kbJXGKEqI6OWuZIEwk) + +**The current segregated web3 infrastructure landscape** + +Data indexers (like SubQuery) speed up data retrieval, enhancing performance and response times for users. They also simplify data by transforming raw blockchain information into more digestible formats, facilitating efficient development and a smooth user experience. + +Meanwhile, RPCs are pivotal for communication between blockchain nodes and external entities, facilitating data retrieval, smart contract interactions, and transaction submissions. Under the hood of your favourite dApp, tens of requests are passing through RPC providers to query and submit transactions to the network. + +While these middleware services are integral to a successful dApp, there is a significant issue that needs to be addressed. + +### Web3’s Dirty Little Secret + +There is a hidden truth behind the mask of “decentralisation” most of these middleware services wear. The reality is that many leading dApps have a significant reliance on centralised middleware components. This centralisation poses a substantial threat to the envisioned unstoppability of a web3 future, at any given moment, a single entity can undermine supposedly decentralised applications. + +Nowhere is this more apparent with RPC providers, and to a lesser extent, data indexers. These crucial services distinguish the scalable, reliable, and polished dApps from rudimentary applications that go without. But due to historical challenges in the process of decentralisation, for a long time, this has been a compromise most apps have accepted. + +The call for decentralised alternatives to these pivotal middleware services is essential for the foundation of the next generation of dApps to build upon. We need to decentralise these services, without compromise. + +### SubQuery Network Evolution Revealed + +At the start we set out to create a viable decentralised solution to the data indexing problem. + +Web3 developers face great difficulties aggregating and organising data to power dApps, and SubQuery has helped thousands of developers building the world's best and biggest networks, dApps, and analytics tools by providing fast and performant data indexing. + +In 2022 we launched Kepler Network, a pre-mainnet release that enabled us to bootstrap the network sustainably by bringing onboard proficient indexers and projects. The success of Kepler lead to the realisation that the ecosystem we’ve built could bring benefits for more than just decentralised data indexing, but for middleware infrastructure as a whole. The key components of the network we have built and deployed - reward and pricing rails, service verification tools, and dispute resolution processes - are valuable for others verticals. + +Knowing that the SubQuery Network could give our existing community of top node runners a solution to trustlessly receive rewards for running data indexing infrastructure, why couldn’t it work for those other services, for other parts of the dApp tech stack? + +We realised the full potential of the SubQuery Network mainnet should not be limited to just data indexing; its fundamental contracts, tools, and reward flows enable it to be so much more. By harnessing the power of the existing participants and mechanisms, the SubQuery Network is ready to extend to various infrastructure verticals. It dawned on us that there is a massive opportunity ahead of us when we think holistically about the entire developer experience. + +> With the launch of mainnet, the SubQuery Network will emerge as a solution to _decentralise everything_, revolutionising the entire developer experience in web3. + +![](https://lh7-us.googleusercontent.com/fXK85pf2n1zTFAsbxyhYKk4I_negGP3mNvXP_vE-_k-ppDlNQeCUPc-iKG7b2HjaeBaisWhkdDqPL8SoQb0QHW6eHI4-5Bra1GK7hrfIhzx9SW1SWgVJ9Nces5Vfza3fwYNug_nduW_8HJ-XB8eZwig) + +**The vision for SubQuery Network to encompass key web3 infrastructure components in a completely decentralised manner** + +### Starting with RPCs + +Our next step that we have completed is to decentralise the biggest infrastructure component for dApps - _Remote Procedure Call_ or RPC services. + +RPC services are still the main interface to the blockchain, under the hood of your favourite dApp, dozens of requests are passing through RPC providers to query and submit transactions to the network. They are the most critical part of the ecosystem, when one has an outage, [the effects reverberate across the industry](https://decrypt.co/47846/ethereum-backbone-infura-suffers-major-damage?ref=blog.subquery.network). + +Since SubQuery relies on performant and scalable RPCs to maximise our indexing speed, we already work extremely closely with RPC providers. On our quest to index over [115+ chains and counting](https://subquery.network/networks?ref=blog.subquery.network), we’ve discovered that the RPC ecosystem is very fractured: some ecosystems have excellent support, and some don’t, and that makes delivering an excellent indexing experience across all chains difficult. + +Across many smaller emergent networks, amateur RPC services operate to provide RPCs to various developers building on the network. These RPCs are usually run (at a loss) by the core network foundation team, and perhaps a collection of validators (for staking advertising purposes). Unfortunately for cost reasons, these RPCs are usually heavily pruned and rate limited, and have no upsell options for unrestricted access. As a result, dApp developers will often run a private RPC endpoint for their own use. This is expensive, frustrating, poses high barriers to entry, and results in no redundancy for dApp developers. + +For more established networks, one or more commercial providers may come and offer a freemium service, where there is a free plan/public endpoint, and a paid upsell to higher scale access. This serves dApp developers well, but the law of economies of scale dictate that networks tend towards a small number of hyperscale RPC providers who centralise the network and cause major outages that affect thousands of dApps when they go offline. They also extract huge economic value from a network and send that directly to big private cloud companies and VCs. + +We have built an alternative to these two dangerous equilibriums, and help decentralise everything.The SubQuery Network provides an open market for both data indexers and RPC providers and their consumers that: + +- Maintains low barriers of entry: Any node operator can join as a provider for any service on any network. +- Incentivises performance and cost: Node operators are automatically rewarded with requests based on these metrics, driving these values across the network. +- Encourages constant expansion to new chains: Node operators are free to onboard new chains and projects for first mover advantage, constantly expanding the network. + +### Enhancing RPCs - SubQuery’s Data Node + +The performance limitations of data indexers and many other applications have long been limited by the RPC endpoint. Developers have long focussed on building nodes to ensure efficient validation to ensure the safety of the network. As a result of this sacrifice, RPCs are extremely costly and they’re not at all optimised for querying. + +This is compounded by the rise of L2 chains where, with higher throughput, the query performance and cost are major outstanding issues to address. With limited querying capabilities, many don’t support complex querying languages or operations, making it inefficient to retrieve specific data. + +We have delivered the SubQuery Data Node, an enhanced and heavily-forked RPC node that is perfectly optimised for querying, especially on endpoints like `eth_getLog`, and the ability to filter transactions in a single API call. + +The Data Node is open source, allowing people to contribute, extend, or fork the implementation in any way. It supports leading layer-2s and other EVM networks initially, and they are optimised to run on the SubQuery Network in a decentralised way. + +Working together, the SubQuery Indexer and SubQuery Data Node provides the most performant indexing performance possible and in a completely decentralised way thanks to the SubQuery Network. + +Our node runners are able to run these data nodes on the network, bringing powerful and cost-effective RPC access to all, cementing SubQuery’s position as the fastest decentralised data indexer in web3. + +### Democratising RPCs - SubQuery’s Sharded Data Node + +In the final stage of our RPC journey, SubQuery will work to democratise RPCs (and solve [EIP-4444](https://eips.ethereum.org/EIPS/eip-4444?ref=blog.subquery.network)) in the process by delivering the Sharded Data Node, which will make RPCs cheaper to run and operate by node providers. + +In the last few months we’ve spoken with many RPC providers in the ecosystem. In many networks (in particular Cosmos), small scale RPC services operate to provide RPCs to various developers building on the network. Unfortunately for cost reasons, these RPCs are usually heavily pruned and rate limited and have no upsell options for unrestricted access. + +One of the key reasons for this is the sheer size of the node - an Ethereum archive requires about ~12 TB on Geth, an Osmosis archive is at least the same. This is an incredible cost that limits these nodes to large centralised infrastructure providers. + +SubQuery recognises that in order to decentralised RPCs correctly, you need to be able to make running these nodes easier and more accessible to everyday users. Currently the storage is made smaller by “pruning” data, which is intentionally discarding older information while cryptographically confirming that the recent data that is valid. This works fine for writing transactions, but means that indexers and other services are unable to query old data. + +SubQuery will extend its Data Node to support sharding, that is making each Data Node smaller by splitting up block ranges between node operators. Since SubQuery’s Data Node only runs within the boundaries of a specific block range, it does not need to constantly sync new data, allowing it to optimise further for query performance rather than validation and verification. + +The SubQuery Sharded node won’t just shard historical data, but also shard the historical state within the node. By itself, this won’t change much, but these sharded nodes will be optimised to run on the network, and the network will be designed to combine all these shards to expose a single unified endpoint that appears to cover the entire historical state of the chain. Developers will benefit from the entire historical state of the given network, and node operators will benefit from significantly lower running costs, creating a more cost efficient network. + +This is a revolutionary step forward for the RPC industry, and a potential solution to one of the great challenges facing older and larger blockchains with their state bloat size. This solution has the potential to help scale Ethereum, solve [EIP-4444](https://eips.ethereum.org/EIPS/eip-4444?ref=blog.subquery.network), and greatly support proliferation of Layer-2’s and rollups, while further democratising and decentralising the SubQuery Network. + +### Summary + +The future of SubQuery is not simply indexing web3 data, but pioneering a complete web3 infrastructure revolution. web3 middleware services like indexers and RPC providers are pivotal in blockchain dApp development, but there is a hidden truth behind the mask of “decentralisation” most of these middleware services wear. The reality is a significant reliance on centralised middleware components, which poses a substantial threat to the envisioned unstoppability of a web3 future. + +Our mission has expanded, and so has the opportunity space we’re going to be working in. We need to decentralise these services, without compromise. We’ve already delivered breakthroughs in decentralised data indexing, but our next steps will focus on enhancing the performance of RPCs with the SubQuery Data Node, and then to bring RPCs to the masses, with SubQuery’s Sharded Data Nodes. These steps together, will help unlock the next level of performance increases in web3. + +No other team today is better equipped at working to provide a holistic approach to solving this problem. In summary, our vision goes beyond data indexing; it's about revolutionising how data and infrastructure services are organised and accessed. + +Pioneering fast, flexible, and scalable decentralised infrastructure, we will help power web3's transition to an open, efficient and user-centric future. Join us in this journey. With SubQuery, it's not just about building for today, but architecting a decentralised, inclusive future. + +_Let's shape the future of web3, together._ \ No newline at end of file diff --git a/docs/tr/subquery_network/welcome.md b/docs/tr/subquery_network/welcome.md new file mode 100644 index 00000000000..53c14ae9c38 --- /dev/null +++ b/docs/tr/subquery_network/welcome.md @@ -0,0 +1,283 @@ +--- +footer: false +lastUpdated: false +contributors: false +editLink: false +photoSwipe: false +--- + + +
+
+
+ SubQuery Network + + The SubQuery Network is the most scalable, reliable, and unified data infrastructure network. 1,000s of decentralised Indexers and RPC providers simplify the data layer for a myriad of applications and use cases. + +
+
+
+ +
+
+ + + One network, all your web3 data needs + +
+ +
+ + {{ item.title }} + {{ item.subtitle }} + + {{ content }} + + + + + + +
+ +
+ Anyone can participate + + There’s a role for everyone in the network, from highly technical + developers to those with some experience and blockchain beginners. Find + out how you can participate and be rewarded. + +
+
+ + {{ anyone.name }} + + {{ anyone.description }} + + + + +
+
+ + +
+ Get Started with the Network Today + Our decentralised network is live and vibrant +
+ + + {{ item.title }} + + {{ item.desc }} + + + +
+
+ + +
+
+ + diff --git a/docs/uk/subquery_network/2024.md b/docs/uk/subquery_network/2024.md new file mode 100644 index 00000000000..29790ca0542 --- /dev/null +++ b/docs/uk/subquery_network/2024.md @@ -0,0 +1,62 @@ +# 2024 in Review: SubQuery’s Top 5 Milestones + +As we look back on 2024, we’re proud to call it a major “year of firsts” for us here at SubQuery. This year was filled with groundbreaking achievements, major launches, and remarkable community growth. The year has flown by but it also feels so long ago that we had our TGE, CEX Listing and SubQuery Network mainnet launch - all on the same day! + +Let’s celebrate some of the key milestones that made 2024 unforgettable. + +## 1. Mainnet Launch + +After an extremely successful Public Sale on 30 January 2024, selling out of SubQuery’s native token (SQT) in less than 2 hours, we worked very hard to launch the SubQuery Network mainnet on 23 February 2024. Powered by SQT and launched on Base, immediately users could consume and/or index data from over 150 networks ([now over 270 networks](https://subquery.network/networks)). + +Almost 1 year on and we have: + +- 46 globally distributed and highly skilled Node Operators servicing the network +- More than 330 million SQT staked and delegated in the Network +- Serving more than 50 million RPC requests every day +- An overall average APY of 22.28% and much higher for Node Operators (94.66%) + +## 2. SQT Token Generation Event + +Combined with the Mainnet launch, we ambitiously chose to do our TGE and day one CEX listing with Bybit on the same day (23 February 2024) as well. Токен SubQuery Token (SQT) розроблений як корисний токен, який забезпечує роботу мережі SubQuery Network, стимулює участь у ній, а також служить засобом обміну для транзакцій у мережі SubQuery Network. Consumers of data commit SQT in exchange for RPC queries or indexed data from our globally distributed Node Operators. + +Today, you can acquire SQT through any of these centralised exchange: + +- [Bybit](https://www.bybit.com/en/trade/spot/SQT/USDT) +- [Gate.io](https://www.gate.io/trade/SQT_USDT) +- [Crypto.com](https://crypto.com/exchange/trade/SQT_USD) +- [MEXC](https://www.mexc.com/exchange/SQT_USDT) + +SQT is on a number of DEX Pools however most liquidity is on Uniswap. + +- [Uniswap Pool on Ethereum](https://app.uniswap.org/explore/tokens/ethereum/0x09395a2A58DB45db0da254c7EAa5AC469D8bDc85) +- [Unsiwap Pool on Base](https://app.uniswap.org/explore/tokens/base/0x858c50c3af1913b0e849afdb74617388a1a5340d) + +## 3. Expansion into Decentralised RPCs + +This vision was announced at the end of 2023 but really came to fruition in 2024. We expanded our network capabilities by introducing support for Remote Procedure Call (RPC) services. This was the first step of expanding away from just a data indexer to a major decentralised infrastructure network, allowing us to support a more accessible, interoperable, and developer-friendly web3 ecosystem. + +Now serving RPC requests on 20+ networks, [get your decentralised RPCs from the SubQuery Network today](https://subquery.network/rpc/list/). + +### 4\. Launching Artificial Intelligence Tools + +SubQuery took its first steps into the AI space by launching decentralised AI inference model hosting on the SubQuery Network plus a new developer SDK called the AI App Framework. This massively expands the tools and services that we can offer to web3 builders across, all under one roof. + +The AI App Framework allows you to build, deploy, and run production AI apps on the SubQuery Network in a trusted and decentralised environment. AI apps are self-contained and easily scalable AI agents that you can use to power your intelligent applications. They are sandboxed to a trusted runner and can be easily distributed and scaled horizontally across the SubQuery Network. + +[Start building AI Apps today!](https://academy.subquery.network/ai/welcome.html) + +## 5. SubQuery Rebranding + +As we expanded into the Artificial Intelligence space, we felt a new look was warranted to match our new pursuit. So we rebranded to a complete new look with sleek chromatic details and a flower/root narrative. + +The flower and root theme symbolises SubQuery’s commitment to fostering innovation and growth within the blockchain community. The roots represent the deep, stable, and reliable infrastructure that SubQuery provides, while the flowers symbolise the diverse and vibrant dApps that developers can create with the help of this infrastructure. + +[Check out the new look](https://subquery.network/). + +## Looking Ahead to 2025 + +While 2024 was full of exciting milestones, we know this is just the beginning. With a stronger community, enhanced technology, and bold new goals, we’re ready to scale even greater heights in 2025. With our most recent [2024 roadmap](https://blog.subquery.network/subquery-releases-network-roadmap-for-2024/?lng=en) almost fully accomplished, stay tuned for a new version packed with ambitious plans. + +Thank you to everyone—developers, partners, and community members—who helped make this year possible. + +Here’s to many more firsts ahead! \ No newline at end of file diff --git a/docs/uk/subquery_network/about.md b/docs/uk/subquery_network/about.md new file mode 100644 index 00000000000..1699165773b --- /dev/null +++ b/docs/uk/subquery_network/about.md @@ -0,0 +1,47 @@ +# About Us + +Our mission is to innovate Web3 infrastructure so builders can decentralise the next generation of applications - without compromise. + +Pioneering fast, flexible, and scalable decentralised infrastructure, we power Web3's transition to an open, efficient and user-centric future.Join us on our journey to build the future of web3 infrastructure. + +[Join our Discord Community](https://discord.com/invite/subquery) + +## Core team + +SubQuery has a deep bench of highly skilled talent of engineers, customer service, and operations personnel.Headquartered in Singapore, we have key representation in New Zealand, Lisbon, and Sydney. + +### Ian He - CTO and Co-Founder + +Ian forged his interest in blockchain during his tenure as the Technical Team Lead for Centrality where he led the development of core components of CENNZnet. Ian also led a team that won 2nd place in the world's first Substrate/Polkadot Hackathon in 2019. Prior to this, Ian obtained significant experience working on large-scale infrastructure working for Alipay and Yihaodian.com. + +### Scott Twiname - Principal Dev of SDK + +Scott has a large wealth of experience in blockchain development. He started out learning about blockchain in his own time and eventually got the opportunity to apply his knowledge as a senior developer at Sylo. He has worked on all facets of blockchain development from smart contracts, dapps, decentralised technologies and wallet integration for various networks including Bitcoin, Ethereum, Tezos and CENNZnet. + +### Marta Adamczyk - Head of Business Development + +Marta is a huge tech advocate, Web3 enthusiast and IT-meetup addict. She helps SubQuery customers develop and scale their projects by delivering technical consultancy, developer-oriented content and technical education. Former product evangelist, frontend developer, digital marketer, educator and sales manager with corporate and start-up experience. + +### Brittany Seales - Head of Marketing + +Brittany has a background in chemistry but since then she became the closest point of contact with SubQuery customers and helped ensure that every SubQuery customer gets an excellent on-boarding experience. Naturally Brittany is heavily integrated with the community and content marketing and has since taken over this area. Sadly, no amount of interaction with successful blockchain projects has give her the ability to pick a winning NFT! + +### James Bayly - Advisor + +Well-versed across the business, from product engineering to being the face of SubQuery, James is also a serial entrepreneur leading several tech companies. When he’s not in Berlin sipping cocktails, you’ll find him hiking up the Routeburn Track in New Zealand. + +## Our Manifesto + +In the new era of Web3, true power isn't bought – it's built with innovation and vision. +We are SubQuery, not just a company, but a revolution. Our mission: to lead the charge in decentralising the future. +We're pioneering an infrastructure that's fast, flexible, scalable – ready to power tomorrow's Web3 world. Crafting an open, efficient, and user-centric digital landscape. +For the visionaries, the forward-thinkers, the builders of tomorrow – SubQuery is your platform. +Join us in this journey. With SubQuery, it's not just about building for today, but architecting a decentralised, inclusive future. Let's shape the future of Web3, together. + +## About SubQuery + +SubQuery Network is innovating in web3 infrastructure with tools that empower builders to decentralise without compromise. SubQuery’s infrastructure network offers everything from data indexers, RPCs and AI agents - all fully decentralised and production ready. + +Our fast, flexible, and open data indexer supercharges thousands of dApps on nearly 300 networks. Our Sharded Data Node will provide breakthroughs in the RPC industry and our AI App framework makes building AI apps easier than ever before. We pioneer the web3 revolution for visionaries and forward-thinkers. We’re not just a company — we’re a movement driving an inclusive and decentralised web3 era, together. + +[Linktree](https://linktr.ee/subquerynetwork) | [Website](https://subquery.network) | [Discord](https://discord.com/invite/subquery) | [Telegram](https://t.me/subquerynetworkcommunity) | [Twitter](https://twitter.com/subquerynetwork) | [Blog](https://blog.subquery.network/?lng=en) | [Medium](https://medium.com/@subquery) | [LinkedIn](https://www.linkedin.com/company/subquery) | [YouTube](https://www.youtube.com/c/SubQueryNetwork) \ No newline at end of file diff --git a/docs/uk/subquery_network/community.md b/docs/uk/subquery_network/community.md new file mode 100644 index 00000000000..59c4aaeb078 --- /dev/null +++ b/docs/uk/subquery_network/community.md @@ -0,0 +1,178 @@ +# SubQuery Network Community + +The key focus of the [SubQuery Foundation](./governance/foundation.md) and community is to ensure that there is enough support that anyone, from an expert blockchain team to a new hobbyist developer, can build their own Project. Together we can pave the way to a more decentralised future! + +## Connecting with others + +Discord is our main community for talking about SubQuery and learning more. You can join with [this link here](https://discord.com/invite/subquery). People most interested in the SubQuery Network will want to join `#network-general`, and Indexers or Delegators should join `#network-indexer-chat` or `#network-delegator-chat` respectively. + +When the conversation is deeper and requires more thought, we move the conversation to [our Forum](https://forum.subquery.network/). Here you will find longer topics, a history of all announcements to Network, and deeper conversation about the direction of the network. Feel free to join and start posting at [forum.subquery.network](https://forum.subquery.network/)! + +### Join the Node Operator community + +If you're a Node Operator on the Network, we strongly suggest that you keep up with the latest news, announcements, and tips by joining the following Discord channels: + +- `#network-announcements` +- `#network-general` +- `#network-services-release` +- `#network-indexer-announcements` +- `#network-indexer-general` + +## Contributing to Codebases + +SubQuery is open source and open to the community, if you want to contribute (e.g. add a feature, fix a bug, suggest an improvement, or even just fix a typo in our documentation), please review our [contributing guide](../miscellaneous/contributing.md). + +The following codebases are where you can find code for all the contracts, applications, and backend SubQuery projects. We're looking forward to seeing your contributions! + +### `network-app` + +dApp for indexers, consumers and delegators interact with SubQuery Network. + + + +### `network-airdrop-app` + +dApp for users to interact with the SubQuery airdrop contract. + + + +### `network-contracts` + +Contracts for SubQuery Network. + + + +You can find smart contract addresses for all network contracts here in [GitHub](https://github.com/subquery/network-contracts/blob/develop/publish/mainnet.json) + +### `network-app-backend` + +SubQuery project for the backend of the SubQuery App. + + + +### `network-airdrop-app-backend` + +SubQuery project for the backend of the SubQuery Airdrop App. + + + +### `network-swap-app-backend` + +SubQuery project for the backend of the SubQuery Swap App. + + + +### `network-indexer-services` + +Services that Indexers run to connect and serve data to the SubQuery Network. + + + +### `network-clients` + +Client SDKs for SubQuery Network. + + + +### `subquery-component-library` + +React UI component library for SubQuery dApps. + + + +## Community Tools + +There are a number of community built tools that you can use to help your SubQuery Network experience. Feel free to contribute your own. + +:::warning +Please note that none of these tools have been endorsed by the SubQuery team and descriptions have been written by third parties. This section is open for contribution by all. + +Please research and use at your own risk +::: + +### SQTScan + +[SQTScan](https://sqtscan.com/?ref=blog.subquery.network) is a ***community-owned application*** designed specifically to help expert users such as Node Operators and Delegators to gain a deeper understanding of historical rewards on the SubQuery Network and optimise their participation. + +SQT Scan helps expert users (Node Operators and Delegators) with: + +1. **Education:** Understand how their rewards are calculated and how they should make decisions +2. **Compare Opportunities:** Decide which projects to deploy based on historical rewards +3. **Compare Others:** Compare their APY with other Node Operators, overall and by project, to see how they're performing relatively +4. **APY Maximisation:** Identify ways to increase their APY + +If you would like to add your support, suggest improvements or new features, or even contribute code, it is welcomed! + +Links + +- [SQTSCan](https://sqtscan.com) +- [Github](https://github.com/HuberTRoy/subquery-sqtscan) + +### Indexer Monitoring Tools (by web3cdn.network) + +Five products: +1. **Toolkit:** A toolkit contains everything you need to index, monitor and properly access from any device +2. **Telegram Uptime Bot:** Eagle Eye is a bot which will provide you live updates in Telegram on the uptime of your indexer +3. **UpdateHunter** +4. **Snapshots** +5. **Snapshots Toolkit** + +Toolkit Features: + +- Extended monitoring of all indexer parameters, sync time, balances, issues. Metrics also support Alerting rules +- Flags problems that have arisen through monitoring and help you to not miss rewards. +- Makes your indexer and infrastructure secure +- Ease of updating without the risk of changing important parameters +- Secured access to dangerous zone with your own VPN, Access from mobile devices to monitoring, and internal services in any time. +- Very easy installation and user error protection + +Eagle Eye Telegram Bot Notifications: + +- Provide reports on your indexer's uptime - help you to know about an errors in advance and not lose funds. +- If your indexer is offline +- If your project is somehow unavailable +- If you do not have enough funds +- If your certificate is about to expire +- And more + +UpdateHunter: + + - A tool that notifies you when a project is updated or a new project is created, providing complete documentation to enable fast and secure upgrades. + - It scans the blockchain and alerts an indexer via a Telegram channel about updates, automati­cally generating instructions and SQL queries. + - The bot integrates with GitHub, posting documentation updates to a public repository. + + Snapshots: + + - Service generates daily snapshots for all active projects + - This service is ideal if your indexer: + - Is newly deployed and you want to avoid ~1 month of downtime for project synchronization + - Has experienced data loss (corrupted disk, hardware failures, or software issues) + + Snapshots Toolkit: + + - Open Source toolkit for an own snapshot generator. With this repository indexer can generate its own snapshots. + +Links + +- [Toolkit Github](https://toolkit.subquery.dev/) +- [Eagle Eye Telegram Bot](https://eagleeye.subquery.dev/) +- [UpdateHunter](https://eagleeye.subquery.dev/updates) +- [Snapshots](https://snapshots.subquery.dev/) +- [Snapshots Toolkit](https://snapshots.subquery.dev/toolkit) + +### Kepler Network Dashboard (by DappLooker) + +To monitor the progress and performance of the Kepler Network, DappLooker has created a dashboard that displays the following key metrics: + +- Active Indexers / Delegators: The number of Indexers and Delegators who are actively participating in the Kepler Network. +- Weekly Indexer Stake / Delegation: The amount of kSQT that Indexers and Delegators have staked on the Kepler Network in the past week. +- Weekly Rewards: The amount of kSQT that Indexers have earned as rewards for serving data requests on the Kepler Network in the past week. +- Stake Distribution: The distribution of kSQT stakes between Indexers and Delegators on the Kepler Network. + +To make the data more accessible and user-friendly, DappLooker has also made the SubQuery Kepler data publicly available for everyone. This means that anyone can create custom dashboards tailored to their needs using the indexed data from the Kepler Network. + +Links + +- [Dashboard](https://dapplooker.com/dashboard/subquery-kepler-network-dashboard-577) +- [Indexed Dataset](https://analytics.dapplooker.com/browse/2/schema/subquery_kepler) +- [Announcement Article](https://blog.dapplooker.com/dapplooker-integrates-subquery-kepler-network-to-provide-analytics-and-dashboard-solution-to-web3-fb0c5aeea899) diff --git a/docs/uk/subquery_network/faq.md b/docs/uk/subquery_network/faq.md new file mode 100644 index 00000000000..a298d22efe5 --- /dev/null +++ b/docs/uk/subquery_network/faq.md @@ -0,0 +1,78 @@ +# Frequently Asked Questions + +FAQs for specific network participants: + +- [Node Operators](./node_operators/setup/faq.md) +- [Consumers](./consumers/faq.md) + +## Proof-of-indexing + +[Proof Of Index](./introduction/proof-of-index.md) + +## How do you ensure indexed data accuracy? + +Ensured by [Proof Of Index](./introduction/proof-of-index.md) + +## Are there a list of RPC providers that can provide support for \_\_\_ chain? + +SubQuery Network is decentralised, so we can't say what individual node operators would decide to serve you, nor can we say what infrastructure the node operators use and where it is hosted + +## What is the integration and deployment timeline for RPCs? + +SubQuery team can enable the RPC in a few days depending on how long an archive node on your network would take to sync. + +## Where is your/provider's infra hosted? + +Depends on the provider, SubQuery don't dictate this. But SubQuery gateway encourages competition to provide high performance, low latency, and geographically decentralised services. Most providers are running on their own bare metal for cost considerations + +## Is there a testnet environment? + +Yes, be sure to check https://dev.thechaindata.com/ + +## Is there a meaning behind SubQuery's name? + +The name "SubQuery" refers to its function in the blockchain ecosystem. A subquery is essentially a query within another query, allowing users to access data more efficiently. It is a powerful tool for indexing and querying blockchain data. + +## What was the first network that SubQuery first supported? + +SubQuery initially supported the Polkadot network, focusing on indexing and querying data for the Polkadot and its parachains. + +## How many networks do SubQuery support now? + +As of now, SubQuery supports multiple networks, including Polkadot, Kusama, Ethereum, and many others, expanding its reach to a wide array of blockchain ecosystems. + +## How does SubQuery improve blockchain data access? + +SubQuery enhances blockchain data access by providing an indexing layer that aggregates and organizes data from blockchain networks. This allows developers and applications to quickly retrieve and interact with data in a structured and efficient manner. + +## How does SubQuery differ from traditional block explorers? + +Traditional block explorers allow users to explore blockchain data in a static, non-queryable format. SubQuery, on the other hand, provides dynamic and customizable data querying, giving developers the ability to filter, process, and retrieve data in real-time for their applications. + +## What programming languages does SubQuery support? + +SubQuery primarily supports JavaScript and TypeScript for building queries and processing data. Developers can use these languages to define the structure and logic for data retrieval from supported networks. + +## Is SubQuery open-source? + +Yes, SubQuery is open-source. It encourages developers to contribute to its growth and use its tools to build decentralized applications (dApps) more efficiently. The source code is available on GitHub. + +## What are the main use cases for SubQuery? + +SubQuery is used for various purposes, such as: + +- Building decentralized applications (dApps) that need to access blockchain data. +- Indexing and querying blockchain data for analysis and reporting. +- Creating custom data solutions for blockchain ecosystems and decentralized finance (DeFi) platforms. + +## Can I deploy SubQuery on my own infrastructure? + +Yes, SubQuery can be deployed on your own infrastructure, whether on-premise or in the cloud. It offers flexibility to users who want complete control over their indexing and querying solutions. + +## How does SubQuery handle data updates and changes? + +SubQuery continuously updates its data by monitoring blockchain events in real-time. This ensures that the indexed data is always up to date, and any changes to the blockchain are reflected immediately in the data queries. + +## How can I get started with SubQuery? + +To get started with SubQuery, you can visit their official documentation, which provides step-by-step guides on setting up a project, writing queries, and deploying them on supported networks. The community also offers support through forums and Discord. diff --git a/docs/uk/subquery_network/infra-changes.md b/docs/uk/subquery_network/infra-changes.md new file mode 100644 index 00000000000..b30b5fa306d --- /dev/null +++ b/docs/uk/subquery_network/infra-changes.md @@ -0,0 +1,109 @@ +# Redefining Web3: SubQuery Network’s Bold Infrastructure Evolution + +Back in December 2023, we announced the evolution of SubQuery, in which we aim to transition from simply indexing web3 data to pioneering a complete web3 infrastructure revolution. + +Over the last year, as we’ve been building out our data indexing service and network, we realised our network is in a prime position to address broader centralisation issues throughout the web3 infrastructure landscape. + +Our mission has expanded, and so has the opportunity space we’re going to be working in. + +Read on to learn about the challenges we’re taking on and the next steps we’re taking to play a bigger role in decentralising the future. + +### The Web3 Infrastructure Landscape + +Web3 middleware services like indexers, RPCs, oracles and storage services are pivotal in blockchain dApp development. In fact, the utilisation of these middleware services is what sets apart successful, large-scale, production dApps - they accelerate performance and can scale to thousands of users, while providing a superior developer experience to bring in more users, TVL, and value. Indexers and RPCs shoulder the heavy lifting, standing as mission-critical services that underpin the functionality and efficiency of web3 applications. + +![](https://lh7-us.googleusercontent.com/2lbQyLR4fxrgV2dTqljyFV6bECXrfq3anA2k_qM6gJuWdSN01dHrVjIFU6OZeFXXJv57dwaXNQ6_lKdGtLK9YDWr0EdS7yDDv0BwZfFXT_j6aw-iu7bDxIS5ZkgliPD2mY_l5kbJXGKEqI6OWuZIEwk) + +**The current segregated web3 infrastructure landscape** + +Data indexers (like SubQuery) speed up data retrieval, enhancing performance and response times for users. They also simplify data by transforming raw blockchain information into more digestible formats, facilitating efficient development and a smooth user experience. + +Meanwhile, RPCs are pivotal for communication between blockchain nodes and external entities, facilitating data retrieval, smart contract interactions, and transaction submissions. Under the hood of your favourite dApp, tens of requests are passing through RPC providers to query and submit transactions to the network. + +While these middleware services are integral to a successful dApp, there is a significant issue that needs to be addressed. + +### Web3’s Dirty Little Secret + +There is a hidden truth behind the mask of “decentralisation” most of these middleware services wear. The reality is that many leading dApps have a significant reliance on centralised middleware components. This centralisation poses a substantial threat to the envisioned unstoppability of a web3 future, at any given moment, a single entity can undermine supposedly decentralised applications. + +Nowhere is this more apparent with RPC providers, and to a lesser extent, data indexers. These crucial services distinguish the scalable, reliable, and polished dApps from rudimentary applications that go without. But due to historical challenges in the process of decentralisation, for a long time, this has been a compromise most apps have accepted. + +The call for decentralised alternatives to these pivotal middleware services is essential for the foundation of the next generation of dApps to build upon. We need to decentralise these services, without compromise. + +### SubQuery Network Evolution Revealed + +At the start we set out to create a viable decentralised solution to the data indexing problem. + +Web3 developers face great difficulties aggregating and organising data to power dApps, and SubQuery has helped thousands of developers building the world's best and biggest networks, dApps, and analytics tools by providing fast and performant data indexing. + +In 2022 we launched Kepler Network, a pre-mainnet release that enabled us to bootstrap the network sustainably by bringing onboard proficient indexers and projects. The success of Kepler lead to the realisation that the ecosystem we’ve built could bring benefits for more than just decentralised data indexing, but for middleware infrastructure as a whole. The key components of the network we have built and deployed - reward and pricing rails, service verification tools, and dispute resolution processes - are valuable for others verticals. + +Knowing that the SubQuery Network could give our existing community of top node runners a solution to trustlessly receive rewards for running data indexing infrastructure, why couldn’t it work for those other services, for other parts of the dApp tech stack? + +We realised the full potential of the SubQuery Network mainnet should not be limited to just data indexing; its fundamental contracts, tools, and reward flows enable it to be so much more. By harnessing the power of the existing participants and mechanisms, the SubQuery Network is ready to extend to various infrastructure verticals. It dawned on us that there is a massive opportunity ahead of us when we think holistically about the entire developer experience. + +> With the launch of mainnet, the SubQuery Network will emerge as a solution to _decentralise everything_, revolutionising the entire developer experience in web3. + +![](https://lh7-us.googleusercontent.com/fXK85pf2n1zTFAsbxyhYKk4I_negGP3mNvXP_vE-_k-ppDlNQeCUPc-iKG7b2HjaeBaisWhkdDqPL8SoQb0QHW6eHI4-5Bra1GK7hrfIhzx9SW1SWgVJ9Nces5Vfza3fwYNug_nduW_8HJ-XB8eZwig) + +**The vision for SubQuery Network to encompass key web3 infrastructure components in a completely decentralised manner** + +### Starting with RPCs + +Our next step that we have completed is to decentralise the biggest infrastructure component for dApps - _Remote Procedure Call_ or RPC services. + +RPC services are still the main interface to the blockchain, under the hood of your favourite dApp, dozens of requests are passing through RPC providers to query and submit transactions to the network. They are the most critical part of the ecosystem, when one has an outage, [the effects reverberate across the industry](https://decrypt.co/47846/ethereum-backbone-infura-suffers-major-damage?ref=blog.subquery.network). + +Since SubQuery relies on performant and scalable RPCs to maximise our indexing speed, we already work extremely closely with RPC providers. On our quest to index over [115+ chains and counting](https://subquery.network/networks?ref=blog.subquery.network), we’ve discovered that the RPC ecosystem is very fractured: some ecosystems have excellent support, and some don’t, and that makes delivering an excellent indexing experience across all chains difficult. + +Across many smaller emergent networks, amateur RPC services operate to provide RPCs to various developers building on the network. These RPCs are usually run (at a loss) by the core network foundation team, and perhaps a collection of validators (for staking advertising purposes). Unfortunately for cost reasons, these RPCs are usually heavily pruned and rate limited, and have no upsell options for unrestricted access. As a result, dApp developers will often run a private RPC endpoint for their own use. This is expensive, frustrating, poses high barriers to entry, and results in no redundancy for dApp developers. + +For more established networks, one or more commercial providers may come and offer a freemium service, where there is a free plan/public endpoint, and a paid upsell to higher scale access. This serves dApp developers well, but the law of economies of scale dictate that networks tend towards a small number of hyperscale RPC providers who centralise the network and cause major outages that affect thousands of dApps when they go offline. They also extract huge economic value from a network and send that directly to big private cloud companies and VCs. + +We have built an alternative to these two dangerous equilibriums, and help decentralise everything.The SubQuery Network provides an open market for both data indexers and RPC providers and their consumers that: + +- Maintains low barriers of entry: Any node operator can join as a provider for any service on any network. +- Incentivises performance and cost: Node operators are automatically rewarded with requests based on these metrics, driving these values across the network. +- Encourages constant expansion to new chains: Node operators are free to onboard new chains and projects for first mover advantage, constantly expanding the network. + +### Enhancing RPCs - SubQuery’s Data Node + +The performance limitations of data indexers and many other applications have long been limited by the RPC endpoint. Developers have long focussed on building nodes to ensure efficient validation to ensure the safety of the network. As a result of this sacrifice, RPCs are extremely costly and they’re not at all optimised for querying. + +This is compounded by the rise of L2 chains where, with higher throughput, the query performance and cost are major outstanding issues to address. With limited querying capabilities, many don’t support complex querying languages or operations, making it inefficient to retrieve specific data. + +We have delivered the SubQuery Data Node, an enhanced and heavily-forked RPC node that is perfectly optimised for querying, especially on endpoints like `eth_getLog`, and the ability to filter transactions in a single API call. + +The Data Node is open source, allowing people to contribute, extend, or fork the implementation in any way. It supports leading layer-2s and other EVM networks initially, and they are optimised to run on the SubQuery Network in a decentralised way. + +Working together, the SubQuery Indexer and SubQuery Data Node provides the most performant indexing performance possible and in a completely decentralised way thanks to the SubQuery Network. + +Our node runners are able to run these data nodes on the network, bringing powerful and cost-effective RPC access to all, cementing SubQuery’s position as the fastest decentralised data indexer in web3. + +### Democratising RPCs - SubQuery’s Sharded Data Node + +In the final stage of our RPC journey, SubQuery will work to democratise RPCs (and solve [EIP-4444](https://eips.ethereum.org/EIPS/eip-4444?ref=blog.subquery.network)) in the process by delivering the Sharded Data Node, which will make RPCs cheaper to run and operate by node providers. + +In the last few months we’ve spoken with many RPC providers in the ecosystem. In many networks (in particular Cosmos), small scale RPC services operate to provide RPCs to various developers building on the network. Unfortunately for cost reasons, these RPCs are usually heavily pruned and rate limited and have no upsell options for unrestricted access. + +One of the key reasons for this is the sheer size of the node - an Ethereum archive requires about ~12 TB on Geth, an Osmosis archive is at least the same. This is an incredible cost that limits these nodes to large centralised infrastructure providers. + +SubQuery recognises that in order to decentralised RPCs correctly, you need to be able to make running these nodes easier and more accessible to everyday users. Currently the storage is made smaller by “pruning” data, which is intentionally discarding older information while cryptographically confirming that the recent data that is valid. This works fine for writing transactions, but means that indexers and other services are unable to query old data. + +SubQuery will extend its Data Node to support sharding, that is making each Data Node smaller by splitting up block ranges between node operators. Since SubQuery’s Data Node only runs within the boundaries of a specific block range, it does not need to constantly sync new data, allowing it to optimise further for query performance rather than validation and verification. + +The SubQuery Sharded node won’t just shard historical data, but also shard the historical state within the node. By itself, this won’t change much, but these sharded nodes will be optimised to run on the network, and the network will be designed to combine all these shards to expose a single unified endpoint that appears to cover the entire historical state of the chain. Developers will benefit from the entire historical state of the given network, and node operators will benefit from significantly lower running costs, creating a more cost efficient network. + +This is a revolutionary step forward for the RPC industry, and a potential solution to one of the great challenges facing older and larger blockchains with their state bloat size. This solution has the potential to help scale Ethereum, solve [EIP-4444](https://eips.ethereum.org/EIPS/eip-4444?ref=blog.subquery.network), and greatly support proliferation of Layer-2’s and rollups, while further democratising and decentralising the SubQuery Network. + +### Summary + +The future of SubQuery is not simply indexing web3 data, but pioneering a complete web3 infrastructure revolution. web3 middleware services like indexers and RPC providers are pivotal in blockchain dApp development, but there is a hidden truth behind the mask of “decentralisation” most of these middleware services wear. The reality is a significant reliance on centralised middleware components, which poses a substantial threat to the envisioned unstoppability of a web3 future. + +Our mission has expanded, and so has the opportunity space we’re going to be working in. We need to decentralise these services, without compromise. We’ve already delivered breakthroughs in decentralised data indexing, but our next steps will focus on enhancing the performance of RPCs with the SubQuery Data Node, and then to bring RPCs to the masses, with SubQuery’s Sharded Data Nodes. These steps together, will help unlock the next level of performance increases in web3. + +No other team today is better equipped at working to provide a holistic approach to solving this problem. In summary, our vision goes beyond data indexing; it's about revolutionising how data and infrastructure services are organised and accessed. + +Pioneering fast, flexible, and scalable decentralised infrastructure, we will help power web3's transition to an open, efficient and user-centric future. Join us in this journey. With SubQuery, it's not just about building for today, but architecting a decentralised, inclusive future. + +_Let's shape the future of web3, together._ \ No newline at end of file diff --git a/docs/uk/subquery_network/welcome.md b/docs/uk/subquery_network/welcome.md new file mode 100644 index 00000000000..53c14ae9c38 --- /dev/null +++ b/docs/uk/subquery_network/welcome.md @@ -0,0 +1,283 @@ +--- +footer: false +lastUpdated: false +contributors: false +editLink: false +photoSwipe: false +--- + + +
+
+
+ SubQuery Network + + The SubQuery Network is the most scalable, reliable, and unified data infrastructure network. 1,000s of decentralised Indexers and RPC providers simplify the data layer for a myriad of applications and use cases. + +
+
+
+ +
+
+ + + One network, all your web3 data needs + +
+ +
+ + {{ item.title }} + {{ item.subtitle }} + + {{ content }} + + + + + + +
+ +
+ Anyone can participate + + There’s a role for everyone in the network, from highly technical + developers to those with some experience and blockchain beginners. Find + out how you can participate and be rewarded. + +
+
+ + {{ anyone.name }} + + {{ anyone.description }} + + + + +
+
+ + +
+ Get Started with the Network Today + Our decentralised network is live and vibrant +
+ + + {{ item.title }} + + {{ item.desc }} + + + +
+
+ + +
+
+ + diff --git a/docs/vi/subquery_network/2024.md b/docs/vi/subquery_network/2024.md new file mode 100644 index 00000000000..3b99879288c --- /dev/null +++ b/docs/vi/subquery_network/2024.md @@ -0,0 +1,62 @@ +# 2024 in Review: SubQuery’s Top 5 Milestones + +As we look back on 2024, we’re proud to call it a major “year of firsts” for us here at SubQuery. This year was filled with groundbreaking achievements, major launches, and remarkable community growth. The year has flown by but it also feels so long ago that we had our TGE, CEX Listing and SubQuery Network mainnet launch - all on the same day! + +Let’s celebrate some of the key milestones that made 2024 unforgettable. + +## 1. Mainnet Launch + +After an extremely successful Public Sale on 30 January 2024, selling out of SubQuery’s native token (SQT) in less than 2 hours, we worked very hard to launch the SubQuery Network mainnet on 23 February 2024. Powered by SQT and launched on Base, immediately users could consume and/or index data from over 150 networks ([now over 270 networks](https://subquery.network/networks)). + +Almost 1 year on and we have: + +- 46 globally distributed and highly skilled Node Operators servicing the network +- More than 330 million SQT staked and delegated in the Network +- Serving more than 50 million RPC requests every day +- An overall average APY of 22.28% and much higher for Node Operators (94.66%) + +## 2. SQT Token Generation Event + +Combined with the Mainnet launch, we ambitiously chose to do our TGE and day one CEX listing with Bybit on the same day (23 February 2024) as well. Mã thông báo SubQuery (SQT) được thiết kế như một mã thông báo tiện ích cung cấp năng lượng cho Mạng SubQuery, cung cấp động lực cho sự tham gia, cũng như phục vụ như một phương tiện trao đổi cho các giao dịch trong Mạng SubQuery. Consumers of data commit SQT in exchange for RPC queries or indexed data from our globally distributed Node Operators. + +Today, you can acquire SQT through any of these centralised exchange: + +- [Bybit](https://www.bybit.com/en/trade/spot/SQT/USDT) +- [Gate.io](https://www.gate.io/trade/SQT_USDT) +- [Crypto.com](https://crypto.com/exchange/trade/SQT_USD) +- [MEXC](https://www.mexc.com/exchange/SQT_USDT) + +SQT is on a number of DEX Pools however most liquidity is on Uniswap. + +- [Uniswap Pool on Ethereum](https://app.uniswap.org/explore/tokens/ethereum/0x09395a2A58DB45db0da254c7EAa5AC469D8bDc85) +- [Unsiwap Pool on Base](https://app.uniswap.org/explore/tokens/base/0x858c50c3af1913b0e849afdb74617388a1a5340d) + +## 3. Expansion into Decentralised RPCs + +This vision was announced at the end of 2023 but really came to fruition in 2024. We expanded our network capabilities by introducing support for Remote Procedure Call (RPC) services. This was the first step of expanding away from just a data indexer to a major decentralised infrastructure network, allowing us to support a more accessible, interoperable, and developer-friendly web3 ecosystem. + +Now serving RPC requests on 20+ networks, [get your decentralised RPCs from the SubQuery Network today](https://subquery.network/rpc/list/). + +### 4\. Launching Artificial Intelligence Tools + +SubQuery took its first steps into the AI space by launching decentralised AI inference model hosting on the SubQuery Network plus a new developer SDK called the AI App Framework. This massively expands the tools and services that we can offer to web3 builders across, all under one roof. + +The AI App Framework allows you to build, deploy, and run production AI apps on the SubQuery Network in a trusted and decentralised environment. AI apps are self-contained and easily scalable AI agents that you can use to power your intelligent applications. They are sandboxed to a trusted runner and can be easily distributed and scaled horizontally across the SubQuery Network. + +[Start building AI Apps today!](https://academy.subquery.network/ai/welcome.html) + +## 5. SubQuery Rebranding + +As we expanded into the Artificial Intelligence space, we felt a new look was warranted to match our new pursuit. So we rebranded to a complete new look with sleek chromatic details and a flower/root narrative. + +The flower and root theme symbolises SubQuery’s commitment to fostering innovation and growth within the blockchain community. The roots represent the deep, stable, and reliable infrastructure that SubQuery provides, while the flowers symbolise the diverse and vibrant dApps that developers can create with the help of this infrastructure. + +[Check out the new look](https://subquery.network/). + +## Looking Ahead to 2025 + +While 2024 was full of exciting milestones, we know this is just the beginning. With a stronger community, enhanced technology, and bold new goals, we’re ready to scale even greater heights in 2025. With our most recent [2024 roadmap](https://blog.subquery.network/subquery-releases-network-roadmap-for-2024/?lng=en) almost fully accomplished, stay tuned for a new version packed with ambitious plans. + +Thank you to everyone—developers, partners, and community members—who helped make this year possible. + +Here’s to many more firsts ahead! \ No newline at end of file diff --git a/docs/vi/subquery_network/about.md b/docs/vi/subquery_network/about.md new file mode 100644 index 00000000000..1699165773b --- /dev/null +++ b/docs/vi/subquery_network/about.md @@ -0,0 +1,47 @@ +# About Us + +Our mission is to innovate Web3 infrastructure so builders can decentralise the next generation of applications - without compromise. + +Pioneering fast, flexible, and scalable decentralised infrastructure, we power Web3's transition to an open, efficient and user-centric future.Join us on our journey to build the future of web3 infrastructure. + +[Join our Discord Community](https://discord.com/invite/subquery) + +## Core team + +SubQuery has a deep bench of highly skilled talent of engineers, customer service, and operations personnel.Headquartered in Singapore, we have key representation in New Zealand, Lisbon, and Sydney. + +### Ian He - CTO and Co-Founder + +Ian forged his interest in blockchain during his tenure as the Technical Team Lead for Centrality where he led the development of core components of CENNZnet. Ian also led a team that won 2nd place in the world's first Substrate/Polkadot Hackathon in 2019. Prior to this, Ian obtained significant experience working on large-scale infrastructure working for Alipay and Yihaodian.com. + +### Scott Twiname - Principal Dev of SDK + +Scott has a large wealth of experience in blockchain development. He started out learning about blockchain in his own time and eventually got the opportunity to apply his knowledge as a senior developer at Sylo. He has worked on all facets of blockchain development from smart contracts, dapps, decentralised technologies and wallet integration for various networks including Bitcoin, Ethereum, Tezos and CENNZnet. + +### Marta Adamczyk - Head of Business Development + +Marta is a huge tech advocate, Web3 enthusiast and IT-meetup addict. She helps SubQuery customers develop and scale their projects by delivering technical consultancy, developer-oriented content and technical education. Former product evangelist, frontend developer, digital marketer, educator and sales manager with corporate and start-up experience. + +### Brittany Seales - Head of Marketing + +Brittany has a background in chemistry but since then she became the closest point of contact with SubQuery customers and helped ensure that every SubQuery customer gets an excellent on-boarding experience. Naturally Brittany is heavily integrated with the community and content marketing and has since taken over this area. Sadly, no amount of interaction with successful blockchain projects has give her the ability to pick a winning NFT! + +### James Bayly - Advisor + +Well-versed across the business, from product engineering to being the face of SubQuery, James is also a serial entrepreneur leading several tech companies. When he’s not in Berlin sipping cocktails, you’ll find him hiking up the Routeburn Track in New Zealand. + +## Our Manifesto + +In the new era of Web3, true power isn't bought – it's built with innovation and vision. +We are SubQuery, not just a company, but a revolution. Our mission: to lead the charge in decentralising the future. +We're pioneering an infrastructure that's fast, flexible, scalable – ready to power tomorrow's Web3 world. Crafting an open, efficient, and user-centric digital landscape. +For the visionaries, the forward-thinkers, the builders of tomorrow – SubQuery is your platform. +Join us in this journey. With SubQuery, it's not just about building for today, but architecting a decentralised, inclusive future. Let's shape the future of Web3, together. + +## About SubQuery + +SubQuery Network is innovating in web3 infrastructure with tools that empower builders to decentralise without compromise. SubQuery’s infrastructure network offers everything from data indexers, RPCs and AI agents - all fully decentralised and production ready. + +Our fast, flexible, and open data indexer supercharges thousands of dApps on nearly 300 networks. Our Sharded Data Node will provide breakthroughs in the RPC industry and our AI App framework makes building AI apps easier than ever before. We pioneer the web3 revolution for visionaries and forward-thinkers. We’re not just a company — we’re a movement driving an inclusive and decentralised web3 era, together. + +[Linktree](https://linktr.ee/subquerynetwork) | [Website](https://subquery.network) | [Discord](https://discord.com/invite/subquery) | [Telegram](https://t.me/subquerynetworkcommunity) | [Twitter](https://twitter.com/subquerynetwork) | [Blog](https://blog.subquery.network/?lng=en) | [Medium](https://medium.com/@subquery) | [LinkedIn](https://www.linkedin.com/company/subquery) | [YouTube](https://www.youtube.com/c/SubQueryNetwork) \ No newline at end of file diff --git a/docs/vi/subquery_network/community.md b/docs/vi/subquery_network/community.md new file mode 100644 index 00000000000..59c4aaeb078 --- /dev/null +++ b/docs/vi/subquery_network/community.md @@ -0,0 +1,178 @@ +# SubQuery Network Community + +The key focus of the [SubQuery Foundation](./governance/foundation.md) and community is to ensure that there is enough support that anyone, from an expert blockchain team to a new hobbyist developer, can build their own Project. Together we can pave the way to a more decentralised future! + +## Connecting with others + +Discord is our main community for talking about SubQuery and learning more. You can join with [this link here](https://discord.com/invite/subquery). People most interested in the SubQuery Network will want to join `#network-general`, and Indexers or Delegators should join `#network-indexer-chat` or `#network-delegator-chat` respectively. + +When the conversation is deeper and requires more thought, we move the conversation to [our Forum](https://forum.subquery.network/). Here you will find longer topics, a history of all announcements to Network, and deeper conversation about the direction of the network. Feel free to join and start posting at [forum.subquery.network](https://forum.subquery.network/)! + +### Join the Node Operator community + +If you're a Node Operator on the Network, we strongly suggest that you keep up with the latest news, announcements, and tips by joining the following Discord channels: + +- `#network-announcements` +- `#network-general` +- `#network-services-release` +- `#network-indexer-announcements` +- `#network-indexer-general` + +## Contributing to Codebases + +SubQuery is open source and open to the community, if you want to contribute (e.g. add a feature, fix a bug, suggest an improvement, or even just fix a typo in our documentation), please review our [contributing guide](../miscellaneous/contributing.md). + +The following codebases are where you can find code for all the contracts, applications, and backend SubQuery projects. We're looking forward to seeing your contributions! + +### `network-app` + +dApp for indexers, consumers and delegators interact with SubQuery Network. + + + +### `network-airdrop-app` + +dApp for users to interact with the SubQuery airdrop contract. + + + +### `network-contracts` + +Contracts for SubQuery Network. + + + +You can find smart contract addresses for all network contracts here in [GitHub](https://github.com/subquery/network-contracts/blob/develop/publish/mainnet.json) + +### `network-app-backend` + +SubQuery project for the backend of the SubQuery App. + + + +### `network-airdrop-app-backend` + +SubQuery project for the backend of the SubQuery Airdrop App. + + + +### `network-swap-app-backend` + +SubQuery project for the backend of the SubQuery Swap App. + + + +### `network-indexer-services` + +Services that Indexers run to connect and serve data to the SubQuery Network. + + + +### `network-clients` + +Client SDKs for SubQuery Network. + + + +### `subquery-component-library` + +React UI component library for SubQuery dApps. + + + +## Community Tools + +There are a number of community built tools that you can use to help your SubQuery Network experience. Feel free to contribute your own. + +:::warning +Please note that none of these tools have been endorsed by the SubQuery team and descriptions have been written by third parties. This section is open for contribution by all. + +Please research and use at your own risk +::: + +### SQTScan + +[SQTScan](https://sqtscan.com/?ref=blog.subquery.network) is a ***community-owned application*** designed specifically to help expert users such as Node Operators and Delegators to gain a deeper understanding of historical rewards on the SubQuery Network and optimise their participation. + +SQT Scan helps expert users (Node Operators and Delegators) with: + +1. **Education:** Understand how their rewards are calculated and how they should make decisions +2. **Compare Opportunities:** Decide which projects to deploy based on historical rewards +3. **Compare Others:** Compare their APY with other Node Operators, overall and by project, to see how they're performing relatively +4. **APY Maximisation:** Identify ways to increase their APY + +If you would like to add your support, suggest improvements or new features, or even contribute code, it is welcomed! + +Links + +- [SQTSCan](https://sqtscan.com) +- [Github](https://github.com/HuberTRoy/subquery-sqtscan) + +### Indexer Monitoring Tools (by web3cdn.network) + +Five products: +1. **Toolkit:** A toolkit contains everything you need to index, monitor and properly access from any device +2. **Telegram Uptime Bot:** Eagle Eye is a bot which will provide you live updates in Telegram on the uptime of your indexer +3. **UpdateHunter** +4. **Snapshots** +5. **Snapshots Toolkit** + +Toolkit Features: + +- Extended monitoring of all indexer parameters, sync time, balances, issues. Metrics also support Alerting rules +- Flags problems that have arisen through monitoring and help you to not miss rewards. +- Makes your indexer and infrastructure secure +- Ease of updating without the risk of changing important parameters +- Secured access to dangerous zone with your own VPN, Access from mobile devices to monitoring, and internal services in any time. +- Very easy installation and user error protection + +Eagle Eye Telegram Bot Notifications: + +- Provide reports on your indexer's uptime - help you to know about an errors in advance and not lose funds. +- If your indexer is offline +- If your project is somehow unavailable +- If you do not have enough funds +- If your certificate is about to expire +- And more + +UpdateHunter: + + - A tool that notifies you when a project is updated or a new project is created, providing complete documentation to enable fast and secure upgrades. + - It scans the blockchain and alerts an indexer via a Telegram channel about updates, automati­cally generating instructions and SQL queries. + - The bot integrates with GitHub, posting documentation updates to a public repository. + + Snapshots: + + - Service generates daily snapshots for all active projects + - This service is ideal if your indexer: + - Is newly deployed and you want to avoid ~1 month of downtime for project synchronization + - Has experienced data loss (corrupted disk, hardware failures, or software issues) + + Snapshots Toolkit: + + - Open Source toolkit for an own snapshot generator. With this repository indexer can generate its own snapshots. + +Links + +- [Toolkit Github](https://toolkit.subquery.dev/) +- [Eagle Eye Telegram Bot](https://eagleeye.subquery.dev/) +- [UpdateHunter](https://eagleeye.subquery.dev/updates) +- [Snapshots](https://snapshots.subquery.dev/) +- [Snapshots Toolkit](https://snapshots.subquery.dev/toolkit) + +### Kepler Network Dashboard (by DappLooker) + +To monitor the progress and performance of the Kepler Network, DappLooker has created a dashboard that displays the following key metrics: + +- Active Indexers / Delegators: The number of Indexers and Delegators who are actively participating in the Kepler Network. +- Weekly Indexer Stake / Delegation: The amount of kSQT that Indexers and Delegators have staked on the Kepler Network in the past week. +- Weekly Rewards: The amount of kSQT that Indexers have earned as rewards for serving data requests on the Kepler Network in the past week. +- Stake Distribution: The distribution of kSQT stakes between Indexers and Delegators on the Kepler Network. + +To make the data more accessible and user-friendly, DappLooker has also made the SubQuery Kepler data publicly available for everyone. This means that anyone can create custom dashboards tailored to their needs using the indexed data from the Kepler Network. + +Links + +- [Dashboard](https://dapplooker.com/dashboard/subquery-kepler-network-dashboard-577) +- [Indexed Dataset](https://analytics.dapplooker.com/browse/2/schema/subquery_kepler) +- [Announcement Article](https://blog.dapplooker.com/dapplooker-integrates-subquery-kepler-network-to-provide-analytics-and-dashboard-solution-to-web3-fb0c5aeea899) diff --git a/docs/vi/subquery_network/faq.md b/docs/vi/subquery_network/faq.md new file mode 100644 index 00000000000..a298d22efe5 --- /dev/null +++ b/docs/vi/subquery_network/faq.md @@ -0,0 +1,78 @@ +# Frequently Asked Questions + +FAQs for specific network participants: + +- [Node Operators](./node_operators/setup/faq.md) +- [Consumers](./consumers/faq.md) + +## Proof-of-indexing + +[Proof Of Index](./introduction/proof-of-index.md) + +## How do you ensure indexed data accuracy? + +Ensured by [Proof Of Index](./introduction/proof-of-index.md) + +## Are there a list of RPC providers that can provide support for \_\_\_ chain? + +SubQuery Network is decentralised, so we can't say what individual node operators would decide to serve you, nor can we say what infrastructure the node operators use and where it is hosted + +## What is the integration and deployment timeline for RPCs? + +SubQuery team can enable the RPC in a few days depending on how long an archive node on your network would take to sync. + +## Where is your/provider's infra hosted? + +Depends on the provider, SubQuery don't dictate this. But SubQuery gateway encourages competition to provide high performance, low latency, and geographically decentralised services. Most providers are running on their own bare metal for cost considerations + +## Is there a testnet environment? + +Yes, be sure to check https://dev.thechaindata.com/ + +## Is there a meaning behind SubQuery's name? + +The name "SubQuery" refers to its function in the blockchain ecosystem. A subquery is essentially a query within another query, allowing users to access data more efficiently. It is a powerful tool for indexing and querying blockchain data. + +## What was the first network that SubQuery first supported? + +SubQuery initially supported the Polkadot network, focusing on indexing and querying data for the Polkadot and its parachains. + +## How many networks do SubQuery support now? + +As of now, SubQuery supports multiple networks, including Polkadot, Kusama, Ethereum, and many others, expanding its reach to a wide array of blockchain ecosystems. + +## How does SubQuery improve blockchain data access? + +SubQuery enhances blockchain data access by providing an indexing layer that aggregates and organizes data from blockchain networks. This allows developers and applications to quickly retrieve and interact with data in a structured and efficient manner. + +## How does SubQuery differ from traditional block explorers? + +Traditional block explorers allow users to explore blockchain data in a static, non-queryable format. SubQuery, on the other hand, provides dynamic and customizable data querying, giving developers the ability to filter, process, and retrieve data in real-time for their applications. + +## What programming languages does SubQuery support? + +SubQuery primarily supports JavaScript and TypeScript for building queries and processing data. Developers can use these languages to define the structure and logic for data retrieval from supported networks. + +## Is SubQuery open-source? + +Yes, SubQuery is open-source. It encourages developers to contribute to its growth and use its tools to build decentralized applications (dApps) more efficiently. The source code is available on GitHub. + +## What are the main use cases for SubQuery? + +SubQuery is used for various purposes, such as: + +- Building decentralized applications (dApps) that need to access blockchain data. +- Indexing and querying blockchain data for analysis and reporting. +- Creating custom data solutions for blockchain ecosystems and decentralized finance (DeFi) platforms. + +## Can I deploy SubQuery on my own infrastructure? + +Yes, SubQuery can be deployed on your own infrastructure, whether on-premise or in the cloud. It offers flexibility to users who want complete control over their indexing and querying solutions. + +## How does SubQuery handle data updates and changes? + +SubQuery continuously updates its data by monitoring blockchain events in real-time. This ensures that the indexed data is always up to date, and any changes to the blockchain are reflected immediately in the data queries. + +## How can I get started with SubQuery? + +To get started with SubQuery, you can visit their official documentation, which provides step-by-step guides on setting up a project, writing queries, and deploying them on supported networks. The community also offers support through forums and Discord. diff --git a/docs/vi/subquery_network/infra-changes.md b/docs/vi/subquery_network/infra-changes.md new file mode 100644 index 00000000000..b30b5fa306d --- /dev/null +++ b/docs/vi/subquery_network/infra-changes.md @@ -0,0 +1,109 @@ +# Redefining Web3: SubQuery Network’s Bold Infrastructure Evolution + +Back in December 2023, we announced the evolution of SubQuery, in which we aim to transition from simply indexing web3 data to pioneering a complete web3 infrastructure revolution. + +Over the last year, as we’ve been building out our data indexing service and network, we realised our network is in a prime position to address broader centralisation issues throughout the web3 infrastructure landscape. + +Our mission has expanded, and so has the opportunity space we’re going to be working in. + +Read on to learn about the challenges we’re taking on and the next steps we’re taking to play a bigger role in decentralising the future. + +### The Web3 Infrastructure Landscape + +Web3 middleware services like indexers, RPCs, oracles and storage services are pivotal in blockchain dApp development. In fact, the utilisation of these middleware services is what sets apart successful, large-scale, production dApps - they accelerate performance and can scale to thousands of users, while providing a superior developer experience to bring in more users, TVL, and value. Indexers and RPCs shoulder the heavy lifting, standing as mission-critical services that underpin the functionality and efficiency of web3 applications. + +![](https://lh7-us.googleusercontent.com/2lbQyLR4fxrgV2dTqljyFV6bECXrfq3anA2k_qM6gJuWdSN01dHrVjIFU6OZeFXXJv57dwaXNQ6_lKdGtLK9YDWr0EdS7yDDv0BwZfFXT_j6aw-iu7bDxIS5ZkgliPD2mY_l5kbJXGKEqI6OWuZIEwk) + +**The current segregated web3 infrastructure landscape** + +Data indexers (like SubQuery) speed up data retrieval, enhancing performance and response times for users. They also simplify data by transforming raw blockchain information into more digestible formats, facilitating efficient development and a smooth user experience. + +Meanwhile, RPCs are pivotal for communication between blockchain nodes and external entities, facilitating data retrieval, smart contract interactions, and transaction submissions. Under the hood of your favourite dApp, tens of requests are passing through RPC providers to query and submit transactions to the network. + +While these middleware services are integral to a successful dApp, there is a significant issue that needs to be addressed. + +### Web3’s Dirty Little Secret + +There is a hidden truth behind the mask of “decentralisation” most of these middleware services wear. The reality is that many leading dApps have a significant reliance on centralised middleware components. This centralisation poses a substantial threat to the envisioned unstoppability of a web3 future, at any given moment, a single entity can undermine supposedly decentralised applications. + +Nowhere is this more apparent with RPC providers, and to a lesser extent, data indexers. These crucial services distinguish the scalable, reliable, and polished dApps from rudimentary applications that go without. But due to historical challenges in the process of decentralisation, for a long time, this has been a compromise most apps have accepted. + +The call for decentralised alternatives to these pivotal middleware services is essential for the foundation of the next generation of dApps to build upon. We need to decentralise these services, without compromise. + +### SubQuery Network Evolution Revealed + +At the start we set out to create a viable decentralised solution to the data indexing problem. + +Web3 developers face great difficulties aggregating and organising data to power dApps, and SubQuery has helped thousands of developers building the world's best and biggest networks, dApps, and analytics tools by providing fast and performant data indexing. + +In 2022 we launched Kepler Network, a pre-mainnet release that enabled us to bootstrap the network sustainably by bringing onboard proficient indexers and projects. The success of Kepler lead to the realisation that the ecosystem we’ve built could bring benefits for more than just decentralised data indexing, but for middleware infrastructure as a whole. The key components of the network we have built and deployed - reward and pricing rails, service verification tools, and dispute resolution processes - are valuable for others verticals. + +Knowing that the SubQuery Network could give our existing community of top node runners a solution to trustlessly receive rewards for running data indexing infrastructure, why couldn’t it work for those other services, for other parts of the dApp tech stack? + +We realised the full potential of the SubQuery Network mainnet should not be limited to just data indexing; its fundamental contracts, tools, and reward flows enable it to be so much more. By harnessing the power of the existing participants and mechanisms, the SubQuery Network is ready to extend to various infrastructure verticals. It dawned on us that there is a massive opportunity ahead of us when we think holistically about the entire developer experience. + +> With the launch of mainnet, the SubQuery Network will emerge as a solution to _decentralise everything_, revolutionising the entire developer experience in web3. + +![](https://lh7-us.googleusercontent.com/fXK85pf2n1zTFAsbxyhYKk4I_negGP3mNvXP_vE-_k-ppDlNQeCUPc-iKG7b2HjaeBaisWhkdDqPL8SoQb0QHW6eHI4-5Bra1GK7hrfIhzx9SW1SWgVJ9Nces5Vfza3fwYNug_nduW_8HJ-XB8eZwig) + +**The vision for SubQuery Network to encompass key web3 infrastructure components in a completely decentralised manner** + +### Starting with RPCs + +Our next step that we have completed is to decentralise the biggest infrastructure component for dApps - _Remote Procedure Call_ or RPC services. + +RPC services are still the main interface to the blockchain, under the hood of your favourite dApp, dozens of requests are passing through RPC providers to query and submit transactions to the network. They are the most critical part of the ecosystem, when one has an outage, [the effects reverberate across the industry](https://decrypt.co/47846/ethereum-backbone-infura-suffers-major-damage?ref=blog.subquery.network). + +Since SubQuery relies on performant and scalable RPCs to maximise our indexing speed, we already work extremely closely with RPC providers. On our quest to index over [115+ chains and counting](https://subquery.network/networks?ref=blog.subquery.network), we’ve discovered that the RPC ecosystem is very fractured: some ecosystems have excellent support, and some don’t, and that makes delivering an excellent indexing experience across all chains difficult. + +Across many smaller emergent networks, amateur RPC services operate to provide RPCs to various developers building on the network. These RPCs are usually run (at a loss) by the core network foundation team, and perhaps a collection of validators (for staking advertising purposes). Unfortunately for cost reasons, these RPCs are usually heavily pruned and rate limited, and have no upsell options for unrestricted access. As a result, dApp developers will often run a private RPC endpoint for their own use. This is expensive, frustrating, poses high barriers to entry, and results in no redundancy for dApp developers. + +For more established networks, one or more commercial providers may come and offer a freemium service, where there is a free plan/public endpoint, and a paid upsell to higher scale access. This serves dApp developers well, but the law of economies of scale dictate that networks tend towards a small number of hyperscale RPC providers who centralise the network and cause major outages that affect thousands of dApps when they go offline. They also extract huge economic value from a network and send that directly to big private cloud companies and VCs. + +We have built an alternative to these two dangerous equilibriums, and help decentralise everything.The SubQuery Network provides an open market for both data indexers and RPC providers and their consumers that: + +- Maintains low barriers of entry: Any node operator can join as a provider for any service on any network. +- Incentivises performance and cost: Node operators are automatically rewarded with requests based on these metrics, driving these values across the network. +- Encourages constant expansion to new chains: Node operators are free to onboard new chains and projects for first mover advantage, constantly expanding the network. + +### Enhancing RPCs - SubQuery’s Data Node + +The performance limitations of data indexers and many other applications have long been limited by the RPC endpoint. Developers have long focussed on building nodes to ensure efficient validation to ensure the safety of the network. As a result of this sacrifice, RPCs are extremely costly and they’re not at all optimised for querying. + +This is compounded by the rise of L2 chains where, with higher throughput, the query performance and cost are major outstanding issues to address. With limited querying capabilities, many don’t support complex querying languages or operations, making it inefficient to retrieve specific data. + +We have delivered the SubQuery Data Node, an enhanced and heavily-forked RPC node that is perfectly optimised for querying, especially on endpoints like `eth_getLog`, and the ability to filter transactions in a single API call. + +The Data Node is open source, allowing people to contribute, extend, or fork the implementation in any way. It supports leading layer-2s and other EVM networks initially, and they are optimised to run on the SubQuery Network in a decentralised way. + +Working together, the SubQuery Indexer and SubQuery Data Node provides the most performant indexing performance possible and in a completely decentralised way thanks to the SubQuery Network. + +Our node runners are able to run these data nodes on the network, bringing powerful and cost-effective RPC access to all, cementing SubQuery’s position as the fastest decentralised data indexer in web3. + +### Democratising RPCs - SubQuery’s Sharded Data Node + +In the final stage of our RPC journey, SubQuery will work to democratise RPCs (and solve [EIP-4444](https://eips.ethereum.org/EIPS/eip-4444?ref=blog.subquery.network)) in the process by delivering the Sharded Data Node, which will make RPCs cheaper to run and operate by node providers. + +In the last few months we’ve spoken with many RPC providers in the ecosystem. In many networks (in particular Cosmos), small scale RPC services operate to provide RPCs to various developers building on the network. Unfortunately for cost reasons, these RPCs are usually heavily pruned and rate limited and have no upsell options for unrestricted access. + +One of the key reasons for this is the sheer size of the node - an Ethereum archive requires about ~12 TB on Geth, an Osmosis archive is at least the same. This is an incredible cost that limits these nodes to large centralised infrastructure providers. + +SubQuery recognises that in order to decentralised RPCs correctly, you need to be able to make running these nodes easier and more accessible to everyday users. Currently the storage is made smaller by “pruning” data, which is intentionally discarding older information while cryptographically confirming that the recent data that is valid. This works fine for writing transactions, but means that indexers and other services are unable to query old data. + +SubQuery will extend its Data Node to support sharding, that is making each Data Node smaller by splitting up block ranges between node operators. Since SubQuery’s Data Node only runs within the boundaries of a specific block range, it does not need to constantly sync new data, allowing it to optimise further for query performance rather than validation and verification. + +The SubQuery Sharded node won’t just shard historical data, but also shard the historical state within the node. By itself, this won’t change much, but these sharded nodes will be optimised to run on the network, and the network will be designed to combine all these shards to expose a single unified endpoint that appears to cover the entire historical state of the chain. Developers will benefit from the entire historical state of the given network, and node operators will benefit from significantly lower running costs, creating a more cost efficient network. + +This is a revolutionary step forward for the RPC industry, and a potential solution to one of the great challenges facing older and larger blockchains with their state bloat size. This solution has the potential to help scale Ethereum, solve [EIP-4444](https://eips.ethereum.org/EIPS/eip-4444?ref=blog.subquery.network), and greatly support proliferation of Layer-2’s and rollups, while further democratising and decentralising the SubQuery Network. + +### Summary + +The future of SubQuery is not simply indexing web3 data, but pioneering a complete web3 infrastructure revolution. web3 middleware services like indexers and RPC providers are pivotal in blockchain dApp development, but there is a hidden truth behind the mask of “decentralisation” most of these middleware services wear. The reality is a significant reliance on centralised middleware components, which poses a substantial threat to the envisioned unstoppability of a web3 future. + +Our mission has expanded, and so has the opportunity space we’re going to be working in. We need to decentralise these services, without compromise. We’ve already delivered breakthroughs in decentralised data indexing, but our next steps will focus on enhancing the performance of RPCs with the SubQuery Data Node, and then to bring RPCs to the masses, with SubQuery’s Sharded Data Nodes. These steps together, will help unlock the next level of performance increases in web3. + +No other team today is better equipped at working to provide a holistic approach to solving this problem. In summary, our vision goes beyond data indexing; it's about revolutionising how data and infrastructure services are organised and accessed. + +Pioneering fast, flexible, and scalable decentralised infrastructure, we will help power web3's transition to an open, efficient and user-centric future. Join us in this journey. With SubQuery, it's not just about building for today, but architecting a decentralised, inclusive future. + +_Let's shape the future of web3, together._ \ No newline at end of file diff --git a/docs/vi/subquery_network/welcome.md b/docs/vi/subquery_network/welcome.md new file mode 100644 index 00000000000..53c14ae9c38 --- /dev/null +++ b/docs/vi/subquery_network/welcome.md @@ -0,0 +1,283 @@ +--- +footer: false +lastUpdated: false +contributors: false +editLink: false +photoSwipe: false +--- + + +
+
+
+ SubQuery Network + + The SubQuery Network is the most scalable, reliable, and unified data infrastructure network. 1,000s of decentralised Indexers and RPC providers simplify the data layer for a myriad of applications and use cases. + +
+
+
+ +
+
+ + + One network, all your web3 data needs + +
+ +
+ + {{ item.title }} + {{ item.subtitle }} + + {{ content }} + + + + + + +
+ +
+ Anyone can participate + + There’s a role for everyone in the network, from highly technical + developers to those with some experience and blockchain beginners. Find + out how you can participate and be rewarded. + +
+
+ + {{ anyone.name }} + + {{ anyone.description }} + + + + +
+
+ + +
+ Get Started with the Network Today + Our decentralised network is live and vibrant +
+ + + {{ item.title }} + + {{ item.desc }} + + + +
+
+ + +
+
+ + diff --git a/docs/zh/subquery_network/2024.md b/docs/zh/subquery_network/2024.md new file mode 100644 index 00000000000..9ea2cd7f617 --- /dev/null +++ b/docs/zh/subquery_network/2024.md @@ -0,0 +1,62 @@ +# 2024 in Review: SubQuery’s Top 5 Milestones + +As we look back on 2024, we’re proud to call it a major “year of firsts” for us here at SubQuery. This year was filled with groundbreaking achievements, major launches, and remarkable community growth. The year has flown by but it also feels so long ago that we had our TGE, CEX Listing and SubQuery Network mainnet launch - all on the same day! + +Let’s celebrate some of the key milestones that made 2024 unforgettable. + +## 1. Mainnet Launch + +After an extremely successful Public Sale on 30 January 2024, selling out of SubQuery’s native token (SQT) in less than 2 hours, we worked very hard to launch the SubQuery Network mainnet on 23 February 2024. Powered by SQT and launched on Base, immediately users could consume and/or index data from over 150 networks ([now over 270 networks](https://subquery.network/networks)). + +Almost 1 year on and we have: + +- 46 globally distributed and highly skilled Node Operators servicing the network +- More than 330 million SQT staked and delegated in the Network +- Serving more than 50 million RPC requests every day +- An overall average APY of 22.28% and much higher for Node Operators (94.66%) + +## 2. SQT Token Generation Event + +Combined with the Mainnet launch, we ambitiously chose to do our TGE and day one CEX listing with Bybit on the same day (23 February 2024) as well. 我们的目标是将SQT作为SubQuery网络的通证经济，提供参与激励，并作为SubQuery网络内交易的交换媒介。 Consumers of data commit SQT in exchange for RPC queries or indexed data from our globally distributed Node Operators. + +Today, you can acquire SQT through any of these centralised exchange: + +- [Bybit](https://www.bybit.com/en/trade/spot/SQT/USDT) +- [Gate.io](https://www.gate.io/trade/SQT_USDT) +- [Crypto.com](https://crypto.com/exchange/trade/SQT_USD) +- [MEXC](https://www.mexc.com/exchange/SQT_USDT) + +SQT is on a number of DEX Pools however most liquidity is on Uniswap. + +- [Uniswap Pool on Ethereum](https://app.uniswap.org/explore/tokens/ethereum/0x09395a2A58DB45db0da254c7EAa5AC469D8bDc85) +- [Unsiwap Pool on Base](https://app.uniswap.org/explore/tokens/base/0x858c50c3af1913b0e849afdb74617388a1a5340d) + +## 3. Expansion into Decentralised RPCs + +This vision was announced at the end of 2023 but really came to fruition in 2024. We expanded our network capabilities by introducing support for Remote Procedure Call (RPC) services. This was the first step of expanding away from just a data indexer to a major decentralised infrastructure network, allowing us to support a more accessible, interoperable, and developer-friendly web3 ecosystem. + +Now serving RPC requests on 20+ networks, [get your decentralised RPCs from the SubQuery Network today](https://subquery.network/rpc/list/). + +### 4\. Launching Artificial Intelligence Tools + +SubQuery took its first steps into the AI space by launching decentralised AI inference model hosting on the SubQuery Network plus a new developer SDK called the AI App Framework. This massively expands the tools and services that we can offer to web3 builders across, all under one roof. + +The AI App Framework allows you to build, deploy, and run production AI apps on the SubQuery Network in a trusted and decentralised environment. AI apps are self-contained and easily scalable AI agents that you can use to power your intelligent applications. They are sandboxed to a trusted runner and can be easily distributed and scaled horizontally across the SubQuery Network. + +[Start building AI Apps today!](https://academy.subquery.network/ai/welcome.html) + +## 5. SubQuery Rebranding + +As we expanded into the Artificial Intelligence space, we felt a new look was warranted to match our new pursuit. So we rebranded to a complete new look with sleek chromatic details and a flower/root narrative. + +The flower and root theme symbolises SubQuery’s commitment to fostering innovation and growth within the blockchain community. The roots represent the deep, stable, and reliable infrastructure that SubQuery provides, while the flowers symbolise the diverse and vibrant dApps that developers can create with the help of this infrastructure. + +[Check out the new look](https://subquery.network/). + +## Looking Ahead to 2025 + +While 2024 was full of exciting milestones, we know this is just the beginning. With a stronger community, enhanced technology, and bold new goals, we’re ready to scale even greater heights in 2025. With our most recent [2024 roadmap](https://blog.subquery.network/subquery-releases-network-roadmap-for-2024/?lng=en) almost fully accomplished, stay tuned for a new version packed with ambitious plans. + +Thank you to everyone—developers, partners, and community members—who helped make this year possible. + +Here’s to many more firsts ahead! \ No newline at end of file diff --git a/docs/zh/subquery_network/about.md b/docs/zh/subquery_network/about.md new file mode 100644 index 00000000000..1699165773b --- /dev/null +++ b/docs/zh/subquery_network/about.md @@ -0,0 +1,47 @@ +# About Us + +Our mission is to innovate Web3 infrastructure so builders can decentralise the next generation of applications - without compromise. + +Pioneering fast, flexible, and scalable decentralised infrastructure, we power Web3's transition to an open, efficient and user-centric future.Join us on our journey to build the future of web3 infrastructure. + +[Join our Discord Community](https://discord.com/invite/subquery) + +## Core team + +SubQuery has a deep bench of highly skilled talent of engineers, customer service, and operations personnel.Headquartered in Singapore, we have key representation in New Zealand, Lisbon, and Sydney. + +### Ian He - CTO and Co-Founder + +Ian forged his interest in blockchain during his tenure as the Technical Team Lead for Centrality where he led the development of core components of CENNZnet. Ian also led a team that won 2nd place in the world's first Substrate/Polkadot Hackathon in 2019. Prior to this, Ian obtained significant experience working on large-scale infrastructure working for Alipay and Yihaodian.com. + +### Scott Twiname - Principal Dev of SDK + +Scott has a large wealth of experience in blockchain development. He started out learning about blockchain in his own time and eventually got the opportunity to apply his knowledge as a senior developer at Sylo. He has worked on all facets of blockchain development from smart contracts, dapps, decentralised technologies and wallet integration for various networks including Bitcoin, Ethereum, Tezos and CENNZnet. + +### Marta Adamczyk - Head of Business Development + +Marta is a huge tech advocate, Web3 enthusiast and IT-meetup addict. She helps SubQuery customers develop and scale their projects by delivering technical consultancy, developer-oriented content and technical education. Former product evangelist, frontend developer, digital marketer, educator and sales manager with corporate and start-up experience. + +### Brittany Seales - Head of Marketing + +Brittany has a background in chemistry but since then she became the closest point of contact with SubQuery customers and helped ensure that every SubQuery customer gets an excellent on-boarding experience. Naturally Brittany is heavily integrated with the community and content marketing and has since taken over this area. Sadly, no amount of interaction with successful blockchain projects has give her the ability to pick a winning NFT! + +### James Bayly - Advisor + +Well-versed across the business, from product engineering to being the face of SubQuery, James is also a serial entrepreneur leading several tech companies. When he’s not in Berlin sipping cocktails, you’ll find him hiking up the Routeburn Track in New Zealand. + +## Our Manifesto + +In the new era of Web3, true power isn't bought – it's built with innovation and vision. +We are SubQuery, not just a company, but a revolution. Our mission: to lead the charge in decentralising the future. +We're pioneering an infrastructure that's fast, flexible, scalable – ready to power tomorrow's Web3 world. Crafting an open, efficient, and user-centric digital landscape. +For the visionaries, the forward-thinkers, the builders of tomorrow – SubQuery is your platform. +Join us in this journey. With SubQuery, it's not just about building for today, but architecting a decentralised, inclusive future. Let's shape the future of Web3, together. + +## About SubQuery + +SubQuery Network is innovating in web3 infrastructure with tools that empower builders to decentralise without compromise. SubQuery’s infrastructure network offers everything from data indexers, RPCs and AI agents - all fully decentralised and production ready. + +Our fast, flexible, and open data indexer supercharges thousands of dApps on nearly 300 networks. Our Sharded Data Node will provide breakthroughs in the RPC industry and our AI App framework makes building AI apps easier than ever before. We pioneer the web3 revolution for visionaries and forward-thinkers. We’re not just a company — we’re a movement driving an inclusive and decentralised web3 era, together. + +[Linktree](https://linktr.ee/subquerynetwork) | [Website](https://subquery.network) | [Discord](https://discord.com/invite/subquery) | [Telegram](https://t.me/subquerynetworkcommunity) | [Twitter](https://twitter.com/subquerynetwork) | [Blog](https://blog.subquery.network/?lng=en) | [Medium](https://medium.com/@subquery) | [LinkedIn](https://www.linkedin.com/company/subquery) | [YouTube](https://www.youtube.com/c/SubQueryNetwork) \ No newline at end of file diff --git a/docs/zh/subquery_network/community.md b/docs/zh/subquery_network/community.md new file mode 100644 index 00000000000..59c4aaeb078 --- /dev/null +++ b/docs/zh/subquery_network/community.md @@ -0,0 +1,178 @@ +# SubQuery Network Community + +The key focus of the [SubQuery Foundation](./governance/foundation.md) and community is to ensure that there is enough support that anyone, from an expert blockchain team to a new hobbyist developer, can build their own Project. Together we can pave the way to a more decentralised future! + +## Connecting with others + +Discord is our main community for talking about SubQuery and learning more. You can join with [this link here](https://discord.com/invite/subquery). People most interested in the SubQuery Network will want to join `#network-general`, and Indexers or Delegators should join `#network-indexer-chat` or `#network-delegator-chat` respectively. + +When the conversation is deeper and requires more thought, we move the conversation to [our Forum](https://forum.subquery.network/). Here you will find longer topics, a history of all announcements to Network, and deeper conversation about the direction of the network. Feel free to join and start posting at [forum.subquery.network](https://forum.subquery.network/)! + +### Join the Node Operator community + +If you're a Node Operator on the Network, we strongly suggest that you keep up with the latest news, announcements, and tips by joining the following Discord channels: + +- `#network-announcements` +- `#network-general` +- `#network-services-release` +- `#network-indexer-announcements` +- `#network-indexer-general` + +## Contributing to Codebases + +SubQuery is open source and open to the community, if you want to contribute (e.g. add a feature, fix a bug, suggest an improvement, or even just fix a typo in our documentation), please review our [contributing guide](../miscellaneous/contributing.md). + +The following codebases are where you can find code for all the contracts, applications, and backend SubQuery projects. We're looking forward to seeing your contributions! + +### `network-app` + +dApp for indexers, consumers and delegators interact with SubQuery Network. + + + +### `network-airdrop-app` + +dApp for users to interact with the SubQuery airdrop contract. + + + +### `network-contracts` + +Contracts for SubQuery Network. + + + +You can find smart contract addresses for all network contracts here in [GitHub](https://github.com/subquery/network-contracts/blob/develop/publish/mainnet.json) + +### `network-app-backend` + +SubQuery project for the backend of the SubQuery App. + + + +### `network-airdrop-app-backend` + +SubQuery project for the backend of the SubQuery Airdrop App. + + + +### `network-swap-app-backend` + +SubQuery project for the backend of the SubQuery Swap App. + + + +### `network-indexer-services` + +Services that Indexers run to connect and serve data to the SubQuery Network. + + + +### `network-clients` + +Client SDKs for SubQuery Network. + + + +### `subquery-component-library` + +React UI component library for SubQuery dApps. + + + +## Community Tools + +There are a number of community built tools that you can use to help your SubQuery Network experience. Feel free to contribute your own. + +:::warning +Please note that none of these tools have been endorsed by the SubQuery team and descriptions have been written by third parties. This section is open for contribution by all. + +Please research and use at your own risk +::: + +### SQTScan + +[SQTScan](https://sqtscan.com/?ref=blog.subquery.network) is a ***community-owned application*** designed specifically to help expert users such as Node Operators and Delegators to gain a deeper understanding of historical rewards on the SubQuery Network and optimise their participation. + +SQT Scan helps expert users (Node Operators and Delegators) with: + +1. **Education:** Understand how their rewards are calculated and how they should make decisions +2. **Compare Opportunities:** Decide which projects to deploy based on historical rewards +3. **Compare Others:** Compare their APY with other Node Operators, overall and by project, to see how they're performing relatively +4. **APY Maximisation:** Identify ways to increase their APY + +If you would like to add your support, suggest improvements or new features, or even contribute code, it is welcomed! + +Links + +- [SQTSCan](https://sqtscan.com) +- [Github](https://github.com/HuberTRoy/subquery-sqtscan) + +### Indexer Monitoring Tools (by web3cdn.network) + +Five products: +1. **Toolkit:** A toolkit contains everything you need to index, monitor and properly access from any device +2. **Telegram Uptime Bot:** Eagle Eye is a bot which will provide you live updates in Telegram on the uptime of your indexer +3. **UpdateHunter** +4. **Snapshots** +5. **Snapshots Toolkit** + +Toolkit Features: + +- Extended monitoring of all indexer parameters, sync time, balances, issues. Metrics also support Alerting rules +- Flags problems that have arisen through monitoring and help you to not miss rewards. +- Makes your indexer and infrastructure secure +- Ease of updating without the risk of changing important parameters +- Secured access to dangerous zone with your own VPN, Access from mobile devices to monitoring, and internal services in any time. +- Very easy installation and user error protection + +Eagle Eye Telegram Bot Notifications: + +- Provide reports on your indexer's uptime - help you to know about an errors in advance and not lose funds. +- If your indexer is offline +- If your project is somehow unavailable +- If you do not have enough funds +- If your certificate is about to expire +- And more + +UpdateHunter: + + - A tool that notifies you when a project is updated or a new project is created, providing complete documentation to enable fast and secure upgrades. + - It scans the blockchain and alerts an indexer via a Telegram channel about updates, automati­cally generating instructions and SQL queries. + - The bot integrates with GitHub, posting documentation updates to a public repository. + + Snapshots: + + - Service generates daily snapshots for all active projects + - This service is ideal if your indexer: + - Is newly deployed and you want to avoid ~1 month of downtime for project synchronization + - Has experienced data loss (corrupted disk, hardware failures, or software issues) + + Snapshots Toolkit: + + - Open Source toolkit for an own snapshot generator. With this repository indexer can generate its own snapshots. + +Links + +- [Toolkit Github](https://toolkit.subquery.dev/) +- [Eagle Eye Telegram Bot](https://eagleeye.subquery.dev/) +- [UpdateHunter](https://eagleeye.subquery.dev/updates) +- [Snapshots](https://snapshots.subquery.dev/) +- [Snapshots Toolkit](https://snapshots.subquery.dev/toolkit) + +### Kepler Network Dashboard (by DappLooker) + +To monitor the progress and performance of the Kepler Network, DappLooker has created a dashboard that displays the following key metrics: + +- Active Indexers / Delegators: The number of Indexers and Delegators who are actively participating in the Kepler Network. +- Weekly Indexer Stake / Delegation: The amount of kSQT that Indexers and Delegators have staked on the Kepler Network in the past week. +- Weekly Rewards: The amount of kSQT that Indexers have earned as rewards for serving data requests on the Kepler Network in the past week. +- Stake Distribution: The distribution of kSQT stakes between Indexers and Delegators on the Kepler Network. + +To make the data more accessible and user-friendly, DappLooker has also made the SubQuery Kepler data publicly available for everyone. This means that anyone can create custom dashboards tailored to their needs using the indexed data from the Kepler Network. + +Links + +- [Dashboard](https://dapplooker.com/dashboard/subquery-kepler-network-dashboard-577) +- [Indexed Dataset](https://analytics.dapplooker.com/browse/2/schema/subquery_kepler) +- [Announcement Article](https://blog.dapplooker.com/dapplooker-integrates-subquery-kepler-network-to-provide-analytics-and-dashboard-solution-to-web3-fb0c5aeea899) diff --git a/docs/zh/subquery_network/faq.md b/docs/zh/subquery_network/faq.md new file mode 100644 index 00000000000..a298d22efe5 --- /dev/null +++ b/docs/zh/subquery_network/faq.md @@ -0,0 +1,78 @@ +# Frequently Asked Questions + +FAQs for specific network participants: + +- [Node Operators](./node_operators/setup/faq.md) +- [Consumers](./consumers/faq.md) + +## Proof-of-indexing + +[Proof Of Index](./introduction/proof-of-index.md) + +## How do you ensure indexed data accuracy? + +Ensured by [Proof Of Index](./introduction/proof-of-index.md) + +## Are there a list of RPC providers that can provide support for \_\_\_ chain? + +SubQuery Network is decentralised, so we can't say what individual node operators would decide to serve you, nor can we say what infrastructure the node operators use and where it is hosted + +## What is the integration and deployment timeline for RPCs? + +SubQuery team can enable the RPC in a few days depending on how long an archive node on your network would take to sync. + +## Where is your/provider's infra hosted? + +Depends on the provider, SubQuery don't dictate this. But SubQuery gateway encourages competition to provide high performance, low latency, and geographically decentralised services. Most providers are running on their own bare metal for cost considerations + +## Is there a testnet environment? + +Yes, be sure to check https://dev.thechaindata.com/ + +## Is there a meaning behind SubQuery's name? + +The name "SubQuery" refers to its function in the blockchain ecosystem. A subquery is essentially a query within another query, allowing users to access data more efficiently. It is a powerful tool for indexing and querying blockchain data. + +## What was the first network that SubQuery first supported? + +SubQuery initially supported the Polkadot network, focusing on indexing and querying data for the Polkadot and its parachains. + +## How many networks do SubQuery support now? + +As of now, SubQuery supports multiple networks, including Polkadot, Kusama, Ethereum, and many others, expanding its reach to a wide array of blockchain ecosystems. + +## How does SubQuery improve blockchain data access? + +SubQuery enhances blockchain data access by providing an indexing layer that aggregates and organizes data from blockchain networks. This allows developers and applications to quickly retrieve and interact with data in a structured and efficient manner. + +## How does SubQuery differ from traditional block explorers? + +Traditional block explorers allow users to explore blockchain data in a static, non-queryable format. SubQuery, on the other hand, provides dynamic and customizable data querying, giving developers the ability to filter, process, and retrieve data in real-time for their applications. + +## What programming languages does SubQuery support? + +SubQuery primarily supports JavaScript and TypeScript for building queries and processing data. Developers can use these languages to define the structure and logic for data retrieval from supported networks. + +## Is SubQuery open-source? + +Yes, SubQuery is open-source. It encourages developers to contribute to its growth and use its tools to build decentralized applications (dApps) more efficiently. The source code is available on GitHub. + +## What are the main use cases for SubQuery? + +SubQuery is used for various purposes, such as: + +- Building decentralized applications (dApps) that need to access blockchain data. +- Indexing and querying blockchain data for analysis and reporting. +- Creating custom data solutions for blockchain ecosystems and decentralized finance (DeFi) platforms. + +## Can I deploy SubQuery on my own infrastructure? + +Yes, SubQuery can be deployed on your own infrastructure, whether on-premise or in the cloud. It offers flexibility to users who want complete control over their indexing and querying solutions. + +## How does SubQuery handle data updates and changes? + +SubQuery continuously updates its data by monitoring blockchain events in real-time. This ensures that the indexed data is always up to date, and any changes to the blockchain are reflected immediately in the data queries. + +## How can I get started with SubQuery? + +To get started with SubQuery, you can visit their official documentation, which provides step-by-step guides on setting up a project, writing queries, and deploying them on supported networks. The community also offers support through forums and Discord. diff --git a/docs/zh/subquery_network/infra-changes.md b/docs/zh/subquery_network/infra-changes.md new file mode 100644 index 00000000000..b30b5fa306d --- /dev/null +++ b/docs/zh/subquery_network/infra-changes.md @@ -0,0 +1,109 @@ +# Redefining Web3: SubQuery Network’s Bold Infrastructure Evolution + +Back in December 2023, we announced the evolution of SubQuery, in which we aim to transition from simply indexing web3 data to pioneering a complete web3 infrastructure revolution. + +Over the last year, as we’ve been building out our data indexing service and network, we realised our network is in a prime position to address broader centralisation issues throughout the web3 infrastructure landscape. + +Our mission has expanded, and so has the opportunity space we’re going to be working in. + +Read on to learn about the challenges we’re taking on and the next steps we’re taking to play a bigger role in decentralising the future. + +### The Web3 Infrastructure Landscape + +Web3 middleware services like indexers, RPCs, oracles and storage services are pivotal in blockchain dApp development. In fact, the utilisation of these middleware services is what sets apart successful, large-scale, production dApps - they accelerate performance and can scale to thousands of users, while providing a superior developer experience to bring in more users, TVL, and value. Indexers and RPCs shoulder the heavy lifting, standing as mission-critical services that underpin the functionality and efficiency of web3 applications. + +![](https://lh7-us.googleusercontent.com/2lbQyLR4fxrgV2dTqljyFV6bECXrfq3anA2k_qM6gJuWdSN01dHrVjIFU6OZeFXXJv57dwaXNQ6_lKdGtLK9YDWr0EdS7yDDv0BwZfFXT_j6aw-iu7bDxIS5ZkgliPD2mY_l5kbJXGKEqI6OWuZIEwk) + +**The current segregated web3 infrastructure landscape** + +Data indexers (like SubQuery) speed up data retrieval, enhancing performance and response times for users. They also simplify data by transforming raw blockchain information into more digestible formats, facilitating efficient development and a smooth user experience. + +Meanwhile, RPCs are pivotal for communication between blockchain nodes and external entities, facilitating data retrieval, smart contract interactions, and transaction submissions. Under the hood of your favourite dApp, tens of requests are passing through RPC providers to query and submit transactions to the network. + +While these middleware services are integral to a successful dApp, there is a significant issue that needs to be addressed. + +### Web3’s Dirty Little Secret + +There is a hidden truth behind the mask of “decentralisation” most of these middleware services wear. The reality is that many leading dApps have a significant reliance on centralised middleware components. This centralisation poses a substantial threat to the envisioned unstoppability of a web3 future, at any given moment, a single entity can undermine supposedly decentralised applications. + +Nowhere is this more apparent with RPC providers, and to a lesser extent, data indexers. These crucial services distinguish the scalable, reliable, and polished dApps from rudimentary applications that go without. But due to historical challenges in the process of decentralisation, for a long time, this has been a compromise most apps have accepted. + +The call for decentralised alternatives to these pivotal middleware services is essential for the foundation of the next generation of dApps to build upon. We need to decentralise these services, without compromise. + +### SubQuery Network Evolution Revealed + +At the start we set out to create a viable decentralised solution to the data indexing problem. + +Web3 developers face great difficulties aggregating and organising data to power dApps, and SubQuery has helped thousands of developers building the world's best and biggest networks, dApps, and analytics tools by providing fast and performant data indexing. + +In 2022 we launched Kepler Network, a pre-mainnet release that enabled us to bootstrap the network sustainably by bringing onboard proficient indexers and projects. The success of Kepler lead to the realisation that the ecosystem we’ve built could bring benefits for more than just decentralised data indexing, but for middleware infrastructure as a whole. The key components of the network we have built and deployed - reward and pricing rails, service verification tools, and dispute resolution processes - are valuable for others verticals. + +Knowing that the SubQuery Network could give our existing community of top node runners a solution to trustlessly receive rewards for running data indexing infrastructure, why couldn’t it work for those other services, for other parts of the dApp tech stack? + +We realised the full potential of the SubQuery Network mainnet should not be limited to just data indexing; its fundamental contracts, tools, and reward flows enable it to be so much more. By harnessing the power of the existing participants and mechanisms, the SubQuery Network is ready to extend to various infrastructure verticals. It dawned on us that there is a massive opportunity ahead of us when we think holistically about the entire developer experience. + +> With the launch of mainnet, the SubQuery Network will emerge as a solution to _decentralise everything_, revolutionising the entire developer experience in web3. + +![](https://lh7-us.googleusercontent.com/fXK85pf2n1zTFAsbxyhYKk4I_negGP3mNvXP_vE-_k-ppDlNQeCUPc-iKG7b2HjaeBaisWhkdDqPL8SoQb0QHW6eHI4-5Bra1GK7hrfIhzx9SW1SWgVJ9Nces5Vfza3fwYNug_nduW_8HJ-XB8eZwig) + +**The vision for SubQuery Network to encompass key web3 infrastructure components in a completely decentralised manner** + +### Starting with RPCs + +Our next step that we have completed is to decentralise the biggest infrastructure component for dApps - _Remote Procedure Call_ or RPC services. + +RPC services are still the main interface to the blockchain, under the hood of your favourite dApp, dozens of requests are passing through RPC providers to query and submit transactions to the network. They are the most critical part of the ecosystem, when one has an outage, [the effects reverberate across the industry](https://decrypt.co/47846/ethereum-backbone-infura-suffers-major-damage?ref=blog.subquery.network). + +Since SubQuery relies on performant and scalable RPCs to maximise our indexing speed, we already work extremely closely with RPC providers. On our quest to index over [115+ chains and counting](https://subquery.network/networks?ref=blog.subquery.network), we’ve discovered that the RPC ecosystem is very fractured: some ecosystems have excellent support, and some don’t, and that makes delivering an excellent indexing experience across all chains difficult. + +Across many smaller emergent networks, amateur RPC services operate to provide RPCs to various developers building on the network. These RPCs are usually run (at a loss) by the core network foundation team, and perhaps a collection of validators (for staking advertising purposes). Unfortunately for cost reasons, these RPCs are usually heavily pruned and rate limited, and have no upsell options for unrestricted access. As a result, dApp developers will often run a private RPC endpoint for their own use. This is expensive, frustrating, poses high barriers to entry, and results in no redundancy for dApp developers. + +For more established networks, one or more commercial providers may come and offer a freemium service, where there is a free plan/public endpoint, and a paid upsell to higher scale access. This serves dApp developers well, but the law of economies of scale dictate that networks tend towards a small number of hyperscale RPC providers who centralise the network and cause major outages that affect thousands of dApps when they go offline. They also extract huge economic value from a network and send that directly to big private cloud companies and VCs. + +We have built an alternative to these two dangerous equilibriums, and help decentralise everything.The SubQuery Network provides an open market for both data indexers and RPC providers and their consumers that: + +- Maintains low barriers of entry: Any node operator can join as a provider for any service on any network. +- Incentivises performance and cost: Node operators are automatically rewarded with requests based on these metrics, driving these values across the network. +- Encourages constant expansion to new chains: Node operators are free to onboard new chains and projects for first mover advantage, constantly expanding the network. + +### Enhancing RPCs - SubQuery’s Data Node + +The performance limitations of data indexers and many other applications have long been limited by the RPC endpoint. Developers have long focussed on building nodes to ensure efficient validation to ensure the safety of the network. As a result of this sacrifice, RPCs are extremely costly and they’re not at all optimised for querying. + +This is compounded by the rise of L2 chains where, with higher throughput, the query performance and cost are major outstanding issues to address. With limited querying capabilities, many don’t support complex querying languages or operations, making it inefficient to retrieve specific data. + +We have delivered the SubQuery Data Node, an enhanced and heavily-forked RPC node that is perfectly optimised for querying, especially on endpoints like `eth_getLog`, and the ability to filter transactions in a single API call. + +The Data Node is open source, allowing people to contribute, extend, or fork the implementation in any way. It supports leading layer-2s and other EVM networks initially, and they are optimised to run on the SubQuery Network in a decentralised way. + +Working together, the SubQuery Indexer and SubQuery Data Node provides the most performant indexing performance possible and in a completely decentralised way thanks to the SubQuery Network. + +Our node runners are able to run these data nodes on the network, bringing powerful and cost-effective RPC access to all, cementing SubQuery’s position as the fastest decentralised data indexer in web3. + +### Democratising RPCs - SubQuery’s Sharded Data Node + +In the final stage of our RPC journey, SubQuery will work to democratise RPCs (and solve [EIP-4444](https://eips.ethereum.org/EIPS/eip-4444?ref=blog.subquery.network)) in the process by delivering the Sharded Data Node, which will make RPCs cheaper to run and operate by node providers. + +In the last few months we’ve spoken with many RPC providers in the ecosystem. In many networks (in particular Cosmos), small scale RPC services operate to provide RPCs to various developers building on the network. Unfortunately for cost reasons, these RPCs are usually heavily pruned and rate limited and have no upsell options for unrestricted access. + +One of the key reasons for this is the sheer size of the node - an Ethereum archive requires about ~12 TB on Geth, an Osmosis archive is at least the same. This is an incredible cost that limits these nodes to large centralised infrastructure providers. + +SubQuery recognises that in order to decentralised RPCs correctly, you need to be able to make running these nodes easier and more accessible to everyday users. Currently the storage is made smaller by “pruning” data, which is intentionally discarding older information while cryptographically confirming that the recent data that is valid. This works fine for writing transactions, but means that indexers and other services are unable to query old data. + +SubQuery will extend its Data Node to support sharding, that is making each Data Node smaller by splitting up block ranges between node operators. Since SubQuery’s Data Node only runs within the boundaries of a specific block range, it does not need to constantly sync new data, allowing it to optimise further for query performance rather than validation and verification. + +The SubQuery Sharded node won’t just shard historical data, but also shard the historical state within the node. By itself, this won’t change much, but these sharded nodes will be optimised to run on the network, and the network will be designed to combine all these shards to expose a single unified endpoint that appears to cover the entire historical state of the chain. Developers will benefit from the entire historical state of the given network, and node operators will benefit from significantly lower running costs, creating a more cost efficient network. + +This is a revolutionary step forward for the RPC industry, and a potential solution to one of the great challenges facing older and larger blockchains with their state bloat size. This solution has the potential to help scale Ethereum, solve [EIP-4444](https://eips.ethereum.org/EIPS/eip-4444?ref=blog.subquery.network), and greatly support proliferation of Layer-2’s and rollups, while further democratising and decentralising the SubQuery Network. + +### Summary + +The future of SubQuery is not simply indexing web3 data, but pioneering a complete web3 infrastructure revolution. web3 middleware services like indexers and RPC providers are pivotal in blockchain dApp development, but there is a hidden truth behind the mask of “decentralisation” most of these middleware services wear. The reality is a significant reliance on centralised middleware components, which poses a substantial threat to the envisioned unstoppability of a web3 future. + +Our mission has expanded, and so has the opportunity space we’re going to be working in. We need to decentralise these services, without compromise. We’ve already delivered breakthroughs in decentralised data indexing, but our next steps will focus on enhancing the performance of RPCs with the SubQuery Data Node, and then to bring RPCs to the masses, with SubQuery’s Sharded Data Nodes. These steps together, will help unlock the next level of performance increases in web3. + +No other team today is better equipped at working to provide a holistic approach to solving this problem. In summary, our vision goes beyond data indexing; it's about revolutionising how data and infrastructure services are organised and accessed. + +Pioneering fast, flexible, and scalable decentralised infrastructure, we will help power web3's transition to an open, efficient and user-centric future. Join us in this journey. With SubQuery, it's not just about building for today, but architecting a decentralised, inclusive future. + +_Let's shape the future of web3, together._ \ No newline at end of file diff --git a/docs/zh/subquery_network/welcome.md b/docs/zh/subquery_network/welcome.md new file mode 100644 index 00000000000..53c14ae9c38 --- /dev/null +++ b/docs/zh/subquery_network/welcome.md @@ -0,0 +1,283 @@ +--- +footer: false +lastUpdated: false +contributors: false +editLink: false +photoSwipe: false +--- + + +
+
+
+ SubQuery Network + + The SubQuery Network is the most scalable, reliable, and unified data infrastructure network. 1,000s of decentralised Indexers and RPC providers simplify the data layer for a myriad of applications and use cases. + +
+
+
+ +
+
+ + + One network, all your web3 data needs + +
+ +
+ + {{ item.title }} + {{ item.subtitle }} + + {{ content }} + + + + + + +
+ +
+ Anyone can participate + + There’s a role for everyone in the network, from highly technical + developers to those with some experience and blockchain beginners. Find + out how you can participate and be rewarded. + +
+
+ + {{ anyone.name }} + + {{ anyone.description }} + + + + +
+
+ + +
+ Get Started with the Network Today + Our decentralised network is live and vibrant +
+ + + {{ item.title }} + + {{ item.desc }} + + + +
+
+ + +
+
+ +