From f1a98b96a9d7c00873ad3ccc36e95d9ebaa955dd Mon Sep 17 00:00:00 2001 From: Damian Parrino Date: Wed, 30 Aug 2023 14:24:30 -0300 Subject: [PATCH] Update indexer4explorer.md --- docs/4.tools/indexer4explorer.md | 52 +++++++++++++++++++++++++++++++- 1 file changed, 51 insertions(+), 1 deletion(-) diff --git a/docs/4.tools/indexer4explorer.md b/docs/4.tools/indexer4explorer.md index b3ab4ebbd97..aa56ba21da3 100644 --- a/docs/4.tools/indexer4explorer.md +++ b/docs/4.tools/indexer4explorer.md @@ -1,7 +1,7 @@ --- id: indexer-for-explorer title: NEAR Indexer for Explorer -sidebar_label: Query the Blockchain History +sidebar_label: Indexer for Explorer --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; @@ -33,6 +33,7 @@ For a reliable source of real-time and past information, please run your own [in --- ## Example Queries + ### Transactions Calling a Method Query for all transactions that called `contribute` in the `v1.faucet.nonofficial.testnet` testnet account. @@ -72,3 +73,52 @@ from receipts r, action_receipt_actions ara where r.predecessor_account_id ='v1.faucet.nonofficial.testnet' and ara.receipt_id = r.receipt_id and ara.action_kind = 'TRANSFER' ``` + +--- + +## NEAR Explorer sunsetting + +Pagoda made a decision to sunset NEAR Explorer as a product. This means that `explorer.near.org` (and `explorer.testnet.near.org`) will become a landing page with a list of available alternatives, and the existing [explorer.near.org](https://explorer.near.org) will be hosted under a new domain name and will be transitioned to the community through DevHub. [Read more here](https://near.social/devgovgigs.near/widget/gigs-board.pages.Post?id=635). + + +### What exactly is being shut down? + +You will lose access to databases with these URLs, or other Replicas you might have been given access to: +* `testnet.db.explorer.indexer.near.dev/testnet_explorer` +* `mainnet.db.explorer.indexer.near.dev/mainnet_explorer` + + +There is no plan to shut down any other data products, such as [NEAR Lake](https://docs.near.org/concepts/advanced/near-lake-framework) or [EnhancedAPI](https://www.pagoda.co/enhanced-api) at the moment. + +### What is the timeline? + +Postgres users will lose access to data on the 30th of November, Thursday (12:00 pm Pacific Time Zone). Please migrate to one of the options listed below instead. + +### What does this mean for me? + +If you are using the public Postgres Explorer Database, you will need to migrate to other solutions, depending on your use-case. You should start planning for it right now and reach out to [this Telegram group](https://nearbuilders.com/tg-data) to get help. + +### What are the alternatives? + +There are two major use-cases that you might be using Explorer DB for: analytics and real-time queries from web user interfaces. + +#### Analytics Use-Case + +This is if you use Explorer DB to build internal or external dashboards. Pagoda is working with Google Web3 team to enable BigQuery public dataset that has a compatible schema with Explorer DB. This will be enabled early September 2023. Please follow the announcements on [near.org](https://near.org) and in [Telegram chat](https://nearbuilders.com/tg-data). + +#### Web or API usage + +This is if you make queries to Explorer DB in response to API requests that your users make on your application. There are various options that you can explore: +1. If you are working with token balances, including $NEAR, fungible or non-fungible tokens, consider using [Enhanced API](https://www.pagoda.co/enhanced-api) hosted by Pagoda, or run it yourself using https://github.com/near/near-enhanced-api-server and https://github.com/near/near-microindexers +2. Use NEAR QueryAPI – serverless indexers and GraphQL endpoints: https://near.org/s/p?a=nearpavel.near&b=97029570 +3. Use NEAR Lake Indexer. Create an indexer using [Rust](https://github.com/near/near-lake-framework-rs), [JavaScript](https://github.com/near/near-lake-framework-js). There are other languages supported by community, try this search: https://github.com/search?q=near-lake-framework&type=repositories +4. Consider other indexer solutions built by the community + +### Can I still continue using Explorer Database? + +No, you won’t be able to continue using Public Explorer Database after the sunset. However you can start your own instance of https://github.com/near/near-indexer-for-explorer and reindex the history from scratch or use a latest backup. We will share a backup of Explorer DB in September if you want to run your own instance. + + +To run your own infra, you will need: +* **Indexer services:** We use two e2-medium instances on GCP for redundancy, with 2 vCPUs and 4GB of RAM. +* **A database:** We use Postgres version 11, with 8+ vCPUs, 52GB+ RAM and ~8TB of SSD storage. In addition, we recommend running an extra read-replica on a similar or more powerful machine.