├── .github └── workflows │ ├── deploy-prod.yml │ └── deploy-staging.yml ├── .gitignore ├── .vscode └── settings.json ├── CODE_OF_CONDUCT.md ├── README.md ├── archived ├── bg │ ├── README.md │ ├── academy │ │ ├── academy.md │ │ ├── herocourse │ │ │ ├── module1.md │ │ │ ├── module2.md │ │ │ ├── module3.md │ │ │ ├── module4.md │ │ │ ├── module5.md │ │ │ ├── module6.md │ │ │ └── welcome.md │ │ ├── subquery101 │ │ │ └── subquery101.md │ │ └── tutorials_examples │ │ │ ├── batch-size.md │ │ │ ├── block-height.md │ │ │ ├── debug-projects.md │ │ │ ├── delete-projects.md │ │ │ ├── dictionary.md │ │ │ ├── introduction.md │ │ │ ├── run-indexer.md │ │ │ └── terminology.md │ ├── build │ │ ├── dynamicdatasources.md │ │ ├── graphql.md │ │ ├── install.md │ │ ├── introduction.md │ │ ├── manifest.md │ │ ├── mapping.md │ │ └── substrate-evm.md │ ├── faqs │ │ └── faqs.md │ ├── miscellaneous │ │ ├── ambassadors.md │ │ ├── branding.md │ │ ├── contributing.md │ │ └── social_media.md │ ├── quickstart │ │ ├── helloworld-hosted.md │ │ ├── helloworld-localhost.md │ │ ├── quickstart-avalanche.md │ │ ├── quickstart-cosmos.md │ │ ├── quickstart-polkadot.md │ │ ├── quickstart-terra.md │ │ ├── quickstart.md │ │ ├── understanding-helloworld.md │ │ └── whats-next.md │ ├── run_publish │ │ ├── aggregate.md │ │ ├── connect.md │ │ ├── graphql.md │ │ ├── historical.md │ │ ├── ipfs.md │ │ ├── publish.md │ │ ├── query.md │ │ ├── references.md │ │ ├── run.md │ │ ├── sandbox.md │ │ ├── subscription.md │ │ └── upgrade.md │ └── subquery_network │ │ ├── consumers.md │ │ ├── delegators.md │ │ ├── design-philosophy.md │ │ ├── foundation.md │ │ ├── frontier-testnet.md │ │ ├── indexers.md │ │ ├── intro.md │ │ ├── introduction.md │ │ ├── payment-methods.md │ │ ├── terminology.md │ │ └── token.md ├── de │ ├── README.md │ ├── academy │ │ ├── academy.md │ │ ├── herocourse │ │ │ ├── README.md │ │ │ ├── module1.md │ │ │ ├── module2.md │ │ │ ├── module3.md │ │ │ ├── module4.md │ │ │ ├── module5.md │ │ │ ├── module6.md │ │ │ └── welcome.md │ │ ├── subquery101 │ │ │ └── subquery101.md │ │ └── tutorials_examples │ │ │ ├── batch-size.md │ │ │ ├── block-height.md │ │ │ ├── debug-projects.md │ │ │ ├── delete-projects.md │ │ │ ├── dictionary.md │ │ │ ├── howto.md │ │ │ ├── introduction.md │ │ │ ├── run-indexer.md │ │ │ └── terminology.md │ ├── build │ │ ├── dynamicdatasources.md │ │ ├── graphql.md │ │ ├── install.md │ │ ├── introduction.md │ │ ├── manifest.md │ │ ├── mapping.md │ │ └── substrate-evm.md │ ├── faqs │ │ └── faqs.md │ ├── miscellaneous │ │ ├── ambassadors.md │ │ ├── branding.md │ │ ├── contributing.md │ │ └── social_media.md │ ├── quickstart │ │ ├── helloworld-hosted.md │ │ ├── helloworld-localhost.md │ │ ├── quickstart-avalanche.md │ │ ├── quickstart-cosmos.md │ │ ├── quickstart-polkadot.md │ │ ├── quickstart-terra.md │ │ ├── quickstart.md │ │ ├── understanding-helloworld.md │ │ └── whats-next.md │ ├── run_publish │ │ ├── aggregate.md │ │ ├── connect.md │ │ ├── graphql.md │ │ ├── historical.md │ │ ├── ipfs.md │ │ ├── publish.md │ │ ├── query.md │ │ ├── references.md │ │ ├── run.md │ │ ├── sandbox.md │ │ ├── subscription.md │ │ └── upgrade.md │ └── subquery_network │ │ ├── consumers.md │ │ ├── delegators.md │ │ ├── design-philosophy.md │ │ ├── foundation.md │ │ ├── frontier-testnet.md │ │ ├── indexers.md │ │ ├── introduction.md │ │ ├── payment-methods.md │ │ ├── terminology.md │ │ └── token.md ├── es │ ├── README.md │ ├── academy │ │ ├── academy.md │ │ ├── herocourse │ │ │ ├── module1.md │ │ │ ├── module2.md │ │ │ ├── module3.md │ │ │ ├── module4.md │ │ │ ├── module5.md │ │ │ ├── module6.md │ │ │ └── welcome.md │ │ ├── subquery101 │ │ │ └── subquery101.md │ │ └── tutorials_examples │ │ │ ├── batch-size.md │ │ │ ├── block-height.md │ │ │ ├── debug-projects.md │ │ │ ├── delete-projects.md │ │ │ ├── dictionary.md │ │ │ ├── howto.md │ │ │ ├── introduction.md │ │ │ ├── run-indexer.md │ │ │ └── terminology.md │ ├── build │ │ ├── dynamicdatasources.md │ │ ├── graphql.md │ │ ├── install.md │ │ ├── introduction.md │ │ ├── manifest.md │ │ ├── mapping.md │ │ └── substrate-evm.md │ ├── faqs │ │ └── faqs.md │ ├── miscellaneous │ │ ├── ambassadors.md │ │ ├── branding.md │ │ ├── contributing.md │ │ └── social_media.md │ ├── quickstart │ │ ├── helloworld-hosted.md │ │ ├── helloworld-localhost.md │ │ ├── quickstart-avalanche.md │ │ ├── quickstart-cosmos.md │ │ ├── quickstart-polkadot.md │ │ ├── quickstart-terra.md │ │ ├── quickstart.md │ │ ├── understanding-helloworld.md │ │ └── whats-next.md │ ├── run_publish │ │ ├── aggregate.md │ │ ├── connect.md │ │ ├── graphql.md │ │ ├── historical.md │ │ ├── ipfs.md │ │ ├── publish.md │ │ ├── query.md │ │ ├── references.md │ │ ├── run.md │ │ ├── sandbox.md │ │ ├── subscription.md │ │ └── upgrade.md │ └── subquery_network │ │ ├── consumers.md │ │ ├── delegators.md │ │ ├── design-philosophy.md │ │ ├── foundation.md │ │ ├── frontier-testnet.md │ │ ├── indexers.md │ │ ├── intro.md │ │ ├── introduction.md │ │ ├── payment-methods.md │ │ ├── terminology.md │ │ └── token.md ├── fr │ ├── README.md │ ├── academy │ │ ├── academy.md │ │ ├── herocourse │ │ │ ├── module1.md │ │ │ ├── module2.md │ │ │ ├── module3.md │ │ │ ├── module4.md │ │ │ ├── module5.md │ │ │ ├── module6.md │ │ │ └── welcome.md │ │ ├── subquery101 │ │ │ └── subquery101.md │ │ └── tutorials_examples │ │ │ ├── batch-size.md │ │ │ ├── block-height.md │ │ │ ├── debug-projects.md │ │ │ ├── delete-projects.md │ │ │ ├── dictionary.md │ │ │ ├── introduction.md │ │ │ ├── run-indexer.md │ │ │ └── terminology.md │ ├── build │ │ ├── dynamicdatasources.md │ │ ├── graphql.md │ │ ├── install.md │ │ ├── introduction.md │ │ ├── manifest.md │ │ ├── mapping.md │ │ └── substrate-evm.md │ ├── faqs │ │ └── faqs.md │ ├── miscellaneous │ │ ├── ambassadors.md │ │ ├── branding.md │ │ ├── contributing.md │ │ └── social_media.md │ ├── quickstart │ │ ├── helloworld-hosted.md │ │ ├── helloworld-localhost.md │ │ ├── quickstart-avalanche.md │ │ ├── quickstart-cosmos.md │ │ ├── quickstart-polkadot.md │ │ ├── quickstart-terra.md │ │ ├── quickstart.md │ │ ├── understanding-helloworld.md │ │ └── whats-next.md │ ├── run_publish │ │ ├── aggregate.md │ │ ├── connect.md │ │ ├── graphql.md │ │ ├── historical.md │ │ ├── ipfs.md │ │ ├── publish.md │ │ ├── query.md │ │ ├── references.md │ │ ├── run.md │ │ ├── sandbox.md │ │ ├── subscription.md │ │ └── upgrade.md │ └── subquery_network │ │ ├── consumers.md │ │ ├── delegators.md │ │ ├── design-philosophy.md │ │ ├── foundation.md │ │ ├── frontier-testnet.md │ │ ├── indexers.md │ │ ├── intro.md │ │ ├── introduction.md │ │ ├── payment-methods.md │ │ ├── terminology.md │ │ └── token.md ├── id │ ├── README.md │ ├── academy │ │ ├── academy.md │ │ ├── herocourse │ │ │ ├── module1.md │ │ │ ├── module2.md │ │ │ ├── module3.md │ │ │ ├── module4.md │ │ │ ├── module5.md │ │ │ ├── module6.md │ │ │ └── welcome.md │ │ ├── subquery101 │ │ │ └── subquery101.md │ │ └── tutorials_examples │ │ │ ├── batch-size.md │ │ │ ├── block-height.md │ │ │ ├── debug-projects.md │ │ │ ├── delete-projects.md │ │ │ ├── dictionary.md │ │ │ ├── howto.md │ │ │ ├── introduction.md │ │ │ ├── run-indexer.md │ │ │ └── terminology.md │ ├── build │ │ ├── dynamicdatasources.md │ │ ├── graphql.md │ │ ├── install.md │ │ ├── introduction.md │ │ ├── manifest.md │ │ ├── mapping.md │ │ └── substrate-evm.md │ ├── faqs │ │ └── faqs.md │ ├── miscellaneous │ │ ├── ambassadors.md │ │ ├── branding.md │ │ ├── contributing.md │ │ └── social_media.md │ ├── quickstart │ │ ├── helloworld-hosted.md │ │ ├── helloworld-localhost.md │ │ ├── quickstart-avalanche.md │ │ ├── quickstart-cosmos.md │ │ ├── quickstart-polkadot.md │ │ ├── quickstart-terra.md │ │ ├── quickstart.md │ │ ├── understanding-helloworld.md │ │ └── whats-next.md │ ├── run_publish │ │ ├── aggregate.md │ │ ├── connect.md │ │ ├── graphql.md │ │ ├── historical.md │ │ ├── ipfs.md │ │ ├── publish.md │ │ ├── query.md │ │ ├── references.md │ │ ├── run.md │ │ ├── sandbox.md │ │ ├── subscription.md │ │ └── upgrade.md │ └── subquery_network │ │ ├── consumers.md │ │ ├── delegators.md │ │ ├── design-philosophy.md │ │ ├── foundation.md │ │ ├── frontier-testnet.md │ │ ├── indexers.md │ │ ├── intro.md │ │ ├── introduction.md │ │ ├── payment-methods.md │ │ ├── terminology.md │ │ └── token.md ├── it │ ├── README.md │ ├── academy │ │ ├── academy.md │ │ ├── herocourse │ │ │ ├── module1.md │ │ │ ├── module2.md │ │ │ ├── module3.md │ │ │ ├── module4.md │ │ │ ├── module5.md │ │ │ ├── module6.md │ │ │ └── welcome.md │ │ ├── subquery101 │ │ │ └── subquery101.md │ │ └── tutorials_examples │ │ │ ├── batch-size.md │ │ │ ├── block-height.md │ │ │ ├── debug-projects.md │ │ │ ├── delete-projects.md │ │ │ ├── dictionary.md │ │ │ ├── howto.md │ │ │ ├── introduction.md │ │ │ ├── run-indexer.md │ │ │ └── terminology.md │ ├── build │ │ ├── dynamicdatasources.md │ │ ├── graphql.md │ │ ├── install.md │ │ ├── introduction.md │ │ ├── manifest.md │ │ ├── mapping.md │ │ └── substrate-evm.md │ ├── faqs │ │ └── faqs.md │ ├── miscellaneous │ │ ├── ambassadors.md │ │ ├── branding.md │ │ ├── contributing.md │ │ └── social_media.md │ ├── quickstart │ │ ├── helloworld-hosted.md │ │ ├── helloworld-localhost.md │ │ ├── quickstart-avalanche.md │ │ ├── quickstart-cosmos.md │ │ ├── quickstart-polkadot.md │ │ ├── quickstart-terra.md │ │ ├── quickstart.md │ │ ├── understanding-helloworld.md │ │ └── whats-next.md │ ├── run_publish │ │ ├── aggregate.md │ │ ├── connect.md │ │ ├── graphql.md │ │ ├── historical.md │ │ ├── ipfs.md │ │ ├── publish.md │ │ ├── query.md │ │ ├── references.md │ │ ├── run.md │ │ ├── sandbox.md │ │ ├── subscription.md │ │ └── upgrade.md │ └── subquery_network │ │ ├── consumers.md │ │ ├── delegators.md │ │ ├── design-philosophy.md │ │ ├── foundation.md │ │ ├── frontier-testnet.md │ │ ├── indexers.md │ │ ├── intro.md │ │ ├── introduction.md │ │ ├── payment-methods.md │ │ ├── terminology.md │ │ └── token.md ├── ja │ ├── README.md │ ├── academy │ │ ├── academy.md │ │ ├── herocourse │ │ │ ├── module1.md │ │ │ ├── module2.md │ │ │ ├── module3.md │ │ │ ├── module4.md │ │ │ ├── module5.md │ │ │ ├── module6.md │ │ │ └── welcome.md │ │ ├── subquery101 │ │ │ └── subquery101.md │ │ └── tutorials_examples │ │ │ ├── batch-size.md │ │ │ ├── block-height.md │ │ │ ├── debug-projects.md │ │ │ ├── delete-projects.md │ │ │ ├── dictionary.md │ │ │ ├── howto.md │ │ │ ├── introduction.md │ │ │ ├── run-indexer.md │ │ │ └── terminology.md │ ├── build │ │ ├── dynamicdatasources.md │ │ ├── graphql.md │ │ ├── install.md │ │ ├── introduction.md │ │ ├── manifest.md │ │ ├── mapping.md │ │ └── substrate-evm.md │ ├── faqs │ │ └── faqs.md │ ├── miscellaneous │ │ ├── ambassadors.md │ │ ├── branding.md │ │ ├── contributing.md │ │ └── social_media.md │ ├── quickstart │ │ ├── helloworld-hosted.md │ │ ├── helloworld-localhost.md │ │ ├── quickstart-avalanche.md │ │ ├── quickstart-cosmos.md │ │ ├── quickstart-polkadot.md │ │ ├── quickstart-terra.md │ │ ├── quickstart.md │ │ ├── understanding-helloworld.md │ │ └── whats-next.md │ ├── run_publish │ │ ├── aggregate.md │ │ ├── connect.md │ │ ├── graphql.md │ │ ├── historical.md │ │ ├── ipfs.md │ │ ├── publish.md │ │ ├── query.md │ │ ├── references.md │ │ ├── run.md │ │ ├── sandbox.md │ │ ├── subscription.md │ │ └── upgrade.md │ └── subquery_network │ │ ├── consumers.md │ │ ├── delegators.md │ │ ├── design-philosophy.md │ │ ├── foundation.md │ │ ├── frontier-testnet.md │ │ ├── indexers.md │ │ ├── intro.md │ │ ├── introduction.md │ │ ├── payment-methods.md │ │ ├── terminology.md │ │ └── token.md ├── ko │ ├── README.md │ ├── academy │ │ ├── academy.md │ │ ├── herocourse │ │ │ ├── module1.md │ │ │ ├── module2.md │ │ │ ├── module3.md │ │ │ ├── module4.md │ │ │ ├── module5.md │ │ │ ├── module6.md │ │ │ └── welcome.md │ │ ├── subquery101 │ │ │ └── subquery101.md │ │ └── tutorials_examples │ │ │ ├── batch-size.md │ │ │ ├── block-height.md │ │ │ ├── debug-projects.md │ │ │ ├── delete-projects.md │ │ │ ├── dictionary.md │ │ │ ├── howto.md │ │ │ ├── introduction.md │ │ │ ├── run-indexer.md │ │ │ └── terminology.md │ ├── build │ │ ├── dynamicdatasources.md │ │ ├── graphql.md │ │ ├── install.md │ │ ├── introduction.md │ │ ├── manifest.md │ │ ├── mapping.md │ │ └── substrate-evm.md │ ├── faqs │ │ └── faqs.md │ ├── miscellaneous │ │ ├── ambassadors.md │ │ ├── branding.md │ │ ├── contributing.md │ │ └── social_media.md │ ├── quickstart │ │ ├── helloworld-hosted.md │ │ ├── helloworld-localhost.md │ │ ├── quickstart-avalanche.md │ │ ├── quickstart-cosmos.md │ │ ├── quickstart-polkadot.md │ │ ├── quickstart-terra.md │ │ ├── quickstart.md │ │ ├── understanding-helloworld.md │ │ └── whats-next.md │ ├── run_publish │ │ ├── aggregate.md │ │ ├── connect.md │ │ ├── graphql.md │ │ ├── historical.md │ │ ├── ipfs.md │ │ ├── publish.md │ │ ├── query.md │ │ ├── references.md │ │ ├── run.md │ │ ├── sandbox.md │ │ ├── subscription.md │ │ └── upgrade.md │ └── subquery_network │ │ ├── consumers.md │ │ ├── delegators.md │ │ ├── design-philosophy.md │ │ ├── foundation.md │ │ ├── frontier-testnet.md │ │ ├── indexers.md │ │ ├── intro.md │ │ ├── introduction.md │ │ ├── payment-methods.md │ │ ├── terminology.md │ │ └── token.md ├── ru │ ├── README.md │ ├── academy │ │ ├── academy.md │ │ ├── herocourse │ │ │ ├── module1.md │ │ │ ├── module2.md │ │ │ ├── module3.md │ │ │ ├── module4.md │ │ │ ├── module5.md │ │ │ ├── module6.md │ │ │ └── welcome.md │ │ ├── subquery101 │ │ │ └── subquery101.md │ │ └── tutorials_examples │ │ │ ├── batch-size.md │ │ │ ├── block-height.md │ │ │ ├── debug-projects.md │ │ │ ├── delete-projects.md │ │ │ ├── dictionary.md │ │ │ ├── howto.md │ │ │ ├── introduction.md │ │ │ ├── run-indexer.md │ │ │ └── terminology.md │ ├── build │ │ ├── dynamicdatasources.md │ │ ├── graphql.md │ │ ├── install.md │ │ ├── introduction.md │ │ ├── manifest.md │ │ ├── mapping.md │ │ └── substrate-evm.md │ ├── faqs │ │ └── faqs.md │ ├── miscellaneous │ │ ├── ambassadors.md │ │ ├── branding.md │ │ ├── contributing.md │ │ └── social_media.md │ ├── quickstart │ │ ├── helloworld-hosted.md │ │ ├── helloworld-localhost.md │ │ ├── quickstart-avalanche.md │ │ ├── quickstart-cosmos.md │ │ ├── quickstart-polkadot.md │ │ ├── quickstart-terra.md │ │ ├── quickstart.md │ │ ├── understanding-helloworld.md │ │ └── whats-next.md │ ├── run_publish │ │ ├── aggregate.md │ │ ├── connect.md │ │ ├── graphql.md │ │ ├── historical.md │ │ ├── ipfs.md │ │ ├── publish.md │ │ ├── query.md │ │ ├── references.md │ │ ├── run.md │ │ ├── sandbox.md │ │ ├── subscription.md │ │ └── upgrade.md │ └── subquery_network │ │ ├── consumers.md │ │ ├── delegators.md │ │ ├── design-philosophy.md │ │ ├── foundation.md │ │ ├── frontier-testnet.md │ │ ├── indexers.md │ │ ├── intro.md │ │ ├── introduction.md │ │ ├── payment-methods.md │ │ ├── terminology.md │ │ └── token.md ├── th │ ├── README.md │ ├── academy │ │ ├── academy.md │ │ ├── herocourse │ │ │ ├── module1.md │ │ │ ├── module2.md │ │ │ ├── module3.md │ │ │ ├── module4.md │ │ │ ├── module5.md │ │ │ ├── module6.md │ │ │ └── welcome.md │ │ ├── subquery101 │ │ │ └── subquery101.md │ │ └── tutorials_examples │ │ │ ├── batch-size.md │ │ │ ├── block-height.md │ │ │ ├── debug-projects.md │ │ │ ├── delete-projects.md │ │ │ ├── dictionary.md │ │ │ ├── introduction.md │ │ │ ├── run-indexer.md │ │ │ └── terminology.md │ ├── build │ │ ├── dynamicdatasources.md │ │ ├── graphql.md │ │ ├── install.md │ │ ├── introduction.md │ │ ├── manifest.md │ │ ├── mapping.md │ │ └── substrate-evm.md │ ├── faqs │ │ └── faqs.md │ ├── miscellaneous │ │ ├── ambassadors.md │ │ ├── branding.md │ │ ├── contributing.md │ │ └── social_media.md │ ├── quickstart │ │ ├── helloworld-hosted.md │ │ ├── helloworld-localhost.md │ │ ├── quickstart-avalanche.md │ │ ├── quickstart-cosmos.md │ │ ├── quickstart-polkadot.md │ │ ├── quickstart-terra.md │ │ ├── quickstart.md │ │ ├── understanding-helloworld.md │ │ └── whats-next.md │ ├── run_publish │ │ ├── aggregate.md │ │ ├── connect.md │ │ ├── graphql.md │ │ ├── historical.md │ │ ├── ipfs.md │ │ ├── publish.md │ │ ├── query.md │ │ ├── references.md │ │ ├── run.md │ │ ├── sandbox.md │ │ ├── subscription.md │ │ └── upgrade.md │ └── subquery_network │ │ ├── consumers.md │ │ ├── delegators.md │ │ ├── design-philosophy.md │ │ ├── foundation.md │ │ ├── frontier-testnet.md │ │ ├── indexers.md │ │ ├── intro.md │ │ ├── introduction.md │ │ ├── payment-methods.md │ │ ├── terminology.md │ │ └── token.md ├── tr │ ├── README.md │ ├── academy │ │ ├── academy.md │ │ ├── herocourse │ │ │ ├── module1.md │ │ │ ├── module2.md │ │ │ ├── module3.md │ │ │ ├── module4.md │ │ │ ├── module5.md │ │ │ ├── module6.md │ │ │ └── welcome.md │ │ ├── subquery101 │ │ │ └── subquery101.md │ │ └── tutorials_examples │ │ │ ├── batch-size.md │ │ │ ├── block-height.md │ │ │ ├── debug-projects.md │ │ │ ├── delete-projects.md │ │ │ ├── dictionary.md │ │ │ ├── introduction.md │ │ │ ├── run-indexer.md │ │ │ └── terminology.md │ ├── build │ │ ├── dynamicdatasources.md │ │ ├── graphql.md │ │ ├── install.md │ │ ├── introduction.md │ │ ├── manifest.md │ │ ├── mapping.md │ │ └── substrate-evm.md │ ├── faqs │ │ └── faqs.md │ ├── miscellaneous │ │ ├── ambassadors.md │ │ ├── branding.md │ │ ├── contributing.md │ │ └── social_media.md │ ├── quickstart │ │ ├── helloworld-hosted.md │ │ ├── helloworld-localhost.md │ │ ├── quickstart-avalanche.md │ │ ├── quickstart-cosmos.md │ │ ├── quickstart-polkadot.md │ │ ├── quickstart-terra.md │ │ ├── quickstart.md │ │ ├── understanding-helloworld.md │ │ └── whats-next.md │ ├── run_publish │ │ ├── aggregate.md │ │ ├── connect.md │ │ ├── graphql.md │ │ ├── historical.md │ │ ├── ipfs.md │ │ ├── publish.md │ │ ├── query.md │ │ ├── references.md │ │ ├── run.md │ │ ├── sandbox.md │ │ ├── subscription.md │ │ └── upgrade.md │ └── subquery_network │ │ ├── consumers.md │ │ ├── delegators.md │ │ ├── design-philosophy.md │ │ ├── foundation.md │ │ ├── frontier-testnet.md │ │ ├── indexers.md │ │ ├── intro.md │ │ ├── introduction.md │ │ ├── payment-methods.md │ │ ├── terminology.md │ │ └── token.md ├── uk │ ├── README.md │ ├── academy │ │ ├── academy.md │ │ ├── herocourse │ │ │ ├── module1.md │ │ │ ├── module2.md │ │ │ ├── module3.md │ │ │ ├── module4.md │ │ │ ├── module5.md │ │ │ ├── module6.md │ │ │ └── welcome.md │ │ ├── subquery101 │ │ │ └── subquery101.md │ │ └── tutorials_examples │ │ │ ├── batch-size.md │ │ │ ├── block-height.md │ │ │ ├── debug-projects.md │ │ │ ├── delete-projects.md │ │ │ ├── dictionary.md │ │ │ ├── howto.md │ │ │ ├── introduction.md │ │ │ ├── run-indexer.md │ │ │ └── terminology.md │ ├── build │ │ ├── dynamicdatasources.md │ │ ├── graphql.md │ │ ├── install.md │ │ ├── introduction.md │ │ ├── manifest.md │ │ ├── mapping.md │ │ └── substrate-evm.md │ ├── faqs │ │ └── faqs.md │ ├── miscellaneous │ │ ├── ambassadors.md │ │ ├── branding.md │ │ ├── contributing.md │ │ └── social_media.md │ ├── quickstart │ │ ├── helloworld-hosted.md │ │ ├── helloworld-localhost.md │ │ ├── quickstart-avalanche.md │ │ ├── quickstart-cosmos.md │ │ ├── quickstart-polkadot.md │ │ ├── quickstart-terra.md │ │ ├── quickstart.md │ │ ├── understanding-helloworld.md │ │ └── whats-next.md │ ├── run_publish │ │ ├── aggregate.md │ │ ├── connect.md │ │ ├── graphql.md │ │ ├── historical.md │ │ ├── ipfs.md │ │ ├── publish.md │ │ ├── query.md │ │ ├── references.md │ │ ├── run.md │ │ ├── sandbox.md │ │ ├── subscription.md │ │ └── upgrade.md │ └── subquery_network │ │ ├── consumers.md │ │ ├── delegators.md │ │ ├── design-philosophy.md │ │ ├── foundation.md │ │ ├── frontier-testnet.md │ │ ├── indexers.md │ │ ├── intro.md │ │ ├── introduction.md │ │ ├── payment-methods.md │ │ ├── terminology.md │ │ └── token.md ├── vi │ ├── README.md │ ├── academy │ │ ├── academy.md │ │ ├── herocourse │ │ │ ├── README.md │ │ │ ├── module1.md │ │ │ ├── module2.md │ │ │ ├── module3.md │ │ │ ├── module4.md │ │ │ ├── module5.md │ │ │ ├── module6.md │ │ │ └── welcome.md │ │ ├── subquery101 │ │ │ └── subquery101.md │ │ └── tutorials_examples │ │ │ ├── batch-size.md │ │ │ ├── block-height.md │ │ │ ├── debug-projects.md │ │ │ ├── delete-projects.md │ │ │ ├── dictionary.md │ │ │ ├── howto.md │ │ │ ├── introduction.md │ │ │ ├── run-indexer.md │ │ │ └── terminology.md │ ├── build │ │ ├── dynamicdatasources.md │ │ ├── graphql.md │ │ ├── install.md │ │ ├── introduction.md │ │ ├── manifest.md │ │ ├── mapping.md │ │ └── substrate-evm.md │ ├── faqs │ │ └── faqs.md │ ├── miscellaneous │ │ ├── ambassadors.md │ │ ├── branding.md │ │ ├── contributing.md │ │ └── social_media.md │ ├── quickstart │ │ ├── helloworld-hosted.md │ │ ├── helloworld-localhost.md │ │ ├── quickstart-avalanche.md │ │ ├── quickstart-cosmos.md │ │ ├── quickstart-polkadot.md │ │ ├── quickstart-terra.md │ │ ├── quickstart.md │ │ ├── understanding-helloworld.md │ │ └── whats-next.md │ ├── run_publish │ │ ├── aggregate.md │ │ ├── connect.md │ │ ├── graphql.md │ │ ├── historical.md │ │ ├── ipfs.md │ │ ├── publish.md │ │ ├── query.md │ │ ├── references.md │ │ ├── run.md │ │ ├── sandbox.md │ │ ├── subscription.md │ │ └── upgrade.md │ └── subquery_network │ │ ├── consumers.md │ │ ├── delegators.md │ │ ├── design-philosophy.md │ │ ├── foundation.md │ │ ├── frontier-testnet.md │ │ ├── indexers.md │ │ ├── intro.md │ │ ├── introduction.md │ │ ├── payment-methods.md │ │ ├── terminology.md │ │ └── token.md └── zh │ ├── README.md │ ├── academy │ ├── academy.md │ ├── herocourse │ │ ├── README.md │ │ ├── module1.md │ │ ├── module2.md │ │ ├── module3.md │ │ ├── module4.md │ │ ├── module5.md │ │ ├── module6.md │ │ └── welcome.md │ ├── subquery101 │ │ └── subquery101.md │ └── tutorials_examples │ │ ├── batch-size.md │ │ ├── block-height.md │ │ ├── debug-projects.md │ │ ├── delete-projects.md │ │ ├── dictionary.md │ │ ├── howto.md │ │ ├── introduction.md │ │ ├── run-indexer.md │ │ └── terminology.md │ ├── build │ ├── dynamicdatasources.md │ ├── graphql.md │ ├── install.md │ ├── introduction.md │ ├── manifest.md │ ├── mapping.md │ └── substrate-evm.md │ ├── faqs │ └── faqs.md │ ├── miscellaneous │ ├── ambassadors.md │ ├── branding.md │ ├── contributing.md │ └── social_media.md │ ├── quickstart │ ├── helloworld-hosted.md │ ├── helloworld-localhost.md │ ├── quickstart-avalanche.md │ ├── quickstart-cosmos.md │ ├── quickstart-polkadot.md │ ├── quickstart-terra.md │ ├── quickstart.md │ ├── understanding-helloworld.md │ └── whats-next.md │ ├── run_publish │ ├── aggregate.md │ ├── connect.md │ ├── graphql.md │ ├── historical.md │ ├── ipfs.md │ ├── publish.md │ ├── query.md │ ├── references.md │ ├── run.md │ ├── sandbox.md │ ├── subscription.md │ └── upgrade.md │ └── subquery_network │ ├── consumers.md │ ├── delegators.md │ ├── design-philosophy.md │ ├── foundation.md │ ├── frontier-testnet.md │ ├── indexers.md │ ├── intro.md │ ├── introduction.md │ ├── payment-methods.md │ ├── terminology.md │ └── token.md ├── contributing.md ├── crowdin.yaml ├── docs ├── .vuepress │ ├── components │ │ ├── Banner.vue │ │ ├── BaseCard.vue │ │ ├── Button.vue │ │ ├── Faqs.vue │ │ ├── Footer.vue │ │ ├── NeedHelp.vue │ │ ├── QuickStart.vue │ │ └── Typography.vue │ ├── config.ts │ ├── public │ │ └── assets │ │ │ ├── favicons │ │ │ ├── apple-touch-icon.png │ │ │ ├── favicon-16x16.png │ │ │ ├── favicon-32x32.png │ │ │ └── favicon.ico │ │ │ ├── fonts │ │ │ └── Inter-Regular.ttf │ │ │ ├── icons │ │ │ ├── icon-128x128.png │ │ │ ├── icon-144x144.png │ │ │ ├── icon-152x152.png │ │ │ ├── icon-192x192.png │ │ │ ├── icon-384x384.png │ │ │ ├── icon-48x48.png │ │ │ ├── icon-512x512.png │ │ │ ├── icon-72x72.png │ │ │ └── icon-96x96.png │ │ │ ├── img │ │ │ ├── academy │ │ │ │ ├── academy.png │ │ │ │ ├── debugging_projects.png │ │ │ │ ├── delete_production.png │ │ │ │ ├── delete_staging.png │ │ │ │ ├── dictionary_blocks.png │ │ │ │ ├── events_table.png │ │ │ │ ├── extrinsics_table.png │ │ │ │ ├── node_inspect.png │ │ │ │ └── specversion_table.png │ │ │ ├── add_network.png │ │ │ ├── ambassador_banner.png │ │ │ ├── architects.png │ │ │ ├── arrow.svg │ │ │ ├── build │ │ │ │ ├── directory_stucture.png │ │ │ │ ├── genesis-hash.jpg │ │ │ │ ├── graph.png │ │ │ │ ├── graph_comparison.jpg │ │ │ │ ├── logging_debug.png │ │ │ │ ├── multi_chain.jpg │ │ │ │ ├── multi_chain_publish.png │ │ │ │ ├── project-scaffold-evm.png │ │ │ │ ├── schema_docstring.png │ │ │ │ ├── subquery_logging.png │ │ │ │ ├── tf-fail-summary.png │ │ │ │ ├── tf-fail-test.png │ │ │ │ └── tf-pass-test.png │ │ │ ├── choose_account.png │ │ │ ├── depth_learning.svg │ │ │ ├── discord_icon.svg │ │ │ ├── faqIcon.svg │ │ │ ├── glossary │ │ │ │ └── terminology.png │ │ │ ├── graphGuideIcon.svg │ │ │ ├── home │ │ │ │ ├── indexer-sdk.png │ │ │ │ └── subquery-network.png │ │ │ ├── journeyIcon1.svg │ │ │ ├── journeyIcon2.svg │ │ │ ├── journeyIcon3.svg │ │ │ ├── journeyIcon4.svg │ │ │ ├── journeyIcon5.svg │ │ │ ├── journeyIcon6.svg │ │ │ ├── lastIntroduce_1.svg │ │ │ ├── lastIntroduce_2.svg │ │ │ ├── logo.png │ │ │ ├── logo_algorand.svg │ │ │ ├── logo_algorand_blue.svg │ │ │ ├── logo_arbitrum.svg │ │ │ ├── logo_arbitrum_blue.svg │ │ │ ├── logo_avalanche.svg │ │ │ ├── logo_avalanche_blue.svg │ │ │ ├── logo_bsc.svg │ │ │ ├── logo_bsc_blue.svg │ │ │ ├── logo_cosmos.svg │ │ │ ├── logo_cosmos_cronos.svg │ │ │ ├── logo_cosmos_cronos_blue.svg │ │ │ ├── logo_cosmos_juno.svg │ │ │ ├── logo_cosmos_juno_blue.svg │ │ │ ├── logo_cosmos_thorchain.svg │ │ │ ├── logo_cosmos_thorchain_blue.svg │ │ │ ├── logo_ethereum.svg │ │ │ ├── logo_ethereum_blue.svg │ │ │ ├── logo_near.svg │ │ │ ├── logo_near_blue.svg │ │ │ ├── logo_optimism.svg │ │ │ ├── logo_optimism_blue.svg │ │ │ ├── logo_polkadot.svg │ │ │ ├── logo_polkadot_astar.svg │ │ │ ├── logo_polkadot_astar_blue.svg │ │ │ ├── logo_polkadot_humanode.svg │ │ │ ├── logo_polkadot_humanode_blue.svg │ │ │ ├── logo_polkadot_polkadot.svg │ │ │ ├── logo_polkadot_polkadot_blue.svg │ │ │ ├── logo_polygon.svg │ │ │ ├── logo_polygon_blue.svg │ │ │ ├── logo_terra.svg │ │ │ ├── logo_terra_blue.svg │ │ │ ├── nag-circle.svg │ │ │ ├── network │ │ │ │ ├── architect_manage_project.png │ │ │ │ ├── architect_manage_project_deploy.png │ │ │ │ ├── architect_publish.png │ │ │ │ ├── architect_publish_ipfs.png │ │ │ │ ├── bridge.jpg │ │ │ │ ├── bridge_polygon_token_1.png │ │ │ │ ├── bridge_polygon_token_2.png │ │ │ │ ├── claim_connect_wallet.png │ │ │ │ ├── claim_page.png │ │ │ │ ├── claim_page_tokens.png │ │ │ │ ├── claim_redeem.png │ │ │ │ ├── claim_unknown_error.png │ │ │ │ ├── claim_wrong_network.png │ │ │ │ ├── cobb_douglas.png │ │ │ │ ├── consumer_billing_account.png │ │ │ │ ├── consumer_billing_account_action.png │ │ │ │ ├── consumer_boosting_1.png │ │ │ │ ├── consumer_boosting_2.png │ │ │ │ ├── consumer_boosting_3.png │ │ │ │ ├── consumer_boosting_manage.png │ │ │ │ ├── consumer_flex_plan.png │ │ │ │ ├── consumer_get_endpoint_1.png │ │ │ │ ├── consumer_get_endpoint_2.png │ │ │ │ ├── consumer_get_endpoint_3.png │ │ │ │ ├── consumer_get_endpoint_4.png │ │ │ │ ├── delegate_action.png │ │ │ │ ├── delegate_cannot.png │ │ │ │ ├── delegate_indexers.png │ │ │ │ ├── delegate_status.png │ │ │ │ ├── delegate_undelegate.png │ │ │ │ ├── ether_on_base.png │ │ │ │ ├── flex-plan-create.png │ │ │ │ ├── flex-plan-update.png │ │ │ │ ├── flex-plan.png │ │ │ │ ├── grafana_query_count.png │ │ │ │ ├── grafana_query_stats.png │ │ │ │ ├── indexer-excellency.png │ │ │ │ ├── indexer_controller_account.png │ │ │ │ ├── indexer_controller_account_added.png │ │ │ │ ├── indexer_controller_add.png │ │ │ │ ├── indexer_docker_compose_v2.png │ │ │ │ ├── indexer_docker_services.png │ │ │ │ ├── indexer_endpoint_invalid.png │ │ │ │ ├── indexer_endpoint_valid.png │ │ │ │ ├── indexer_eof_error_client_connection_troubleshooting.png │ │ │ │ ├── indexer_icr.png │ │ │ │ ├── indexer_icr_change.png │ │ │ │ ├── indexer_metadata_update.png │ │ │ │ ├── indexer_project_add.png │ │ │ │ ├── indexer_project_announce.png │ │ │ │ ├── indexer_project_deployment_id_error.png │ │ │ │ ├── indexer_project_indexing.png │ │ │ │ ├── indexer_project_ready.png │ │ │ │ ├── indexer_project_remove.png │ │ │ │ ├── indexer_project_restart.png │ │ │ │ ├── indexer_project_start_indexing.png │ │ │ │ ├── indexer_project_stop.png │ │ │ │ ├── indexer_project_stop_indexing.png │ │ │ │ ├── indexer_registration.png │ │ │ │ ├── indexer_service_logs.png │ │ │ │ ├── indexer_setup_connect_node.png │ │ │ │ ├── indexer_setup_distributed.png │ │ │ │ ├── indexer_setup_distributed_2.png │ │ │ │ ├── indexer_stake_add.png │ │ │ │ ├── indexer_stake_manage.png │ │ │ │ ├── indexer_stake_manage_add.png │ │ │ │ ├── indexer_stake_manage_over_allocated.png │ │ │ │ ├── indexer_sync_coordinator.png │ │ │ │ ├── indexer_topology.png │ │ │ │ ├── join-network.png │ │ │ │ ├── kSQT_add_wallet.png │ │ │ │ ├── plans.png │ │ │ │ ├── plans_empty.png │ │ │ │ ├── plans_price.png │ │ │ │ ├── plans_template_select.png │ │ │ │ ├── profile_rewards.png │ │ │ │ ├── profile_withdrawls.png │ │ │ │ ├── reward_pools.png │ │ │ │ ├── rpc_connect_node.png │ │ │ │ ├── rpc_project_add.png │ │ │ │ ├── service_agreement.png │ │ │ │ ├── sqt.png │ │ │ │ ├── swap.png │ │ │ │ ├── technical_stack.png │ │ │ │ ├── token_allocation.png │ │ │ │ ├── token_economy.png │ │ │ │ └── vesting_schedule.png │ │ │ ├── networkIcon.svg │ │ │ ├── new-evm-chain-support.png │ │ │ ├── plus-circle.svg │ │ │ ├── run_publish │ │ │ │ ├── bigquery │ │ │ │ │ └── consoleBigquery.png │ │ │ │ ├── graphql_aggregation.png │ │ │ │ ├── historic_indexing.png │ │ │ │ ├── integration_ecosystem.png │ │ │ │ ├── metabase │ │ │ │ │ ├── metabase-database-connection.png │ │ │ │ │ ├── metabaseLiquidityByPoolsQuery.png │ │ │ │ │ ├── metabaseLiquidityByPoolsQuerySQL.png │ │ │ │ │ ├── metabaseLiquidityByPoolsResult.png │ │ │ │ │ ├── metabaseSwapCountByHourQuery.png │ │ │ │ │ ├── metabaseSwapCountByHourResultLineGraph.png │ │ │ │ │ └── metabaseSwapCountByHourResultPieChart.png │ │ │ │ ├── monitoring.png │ │ │ │ ├── project_auth_request.png │ │ │ │ ├── project_auth_revoke.png │ │ │ │ ├── project_created.png │ │ │ │ ├── projects_account_switcher.png │ │ │ │ ├── projects_create.png │ │ │ │ ├── projects_dashboard.png │ │ │ │ ├── projects_deploy_sync.png │ │ │ │ ├── projects_explorer.png │ │ │ │ ├── projects_first_deployment.png │ │ │ │ ├── projects_staging_slot.png │ │ │ │ └── query.png │ │ │ ├── select_account.png │ │ │ ├── startSection_img.svg │ │ │ ├── startSection_robot_img.svg │ │ │ ├── switch_networks.png │ │ │ ├── tutorialsIcon.svg │ │ │ ├── wantMoreDepthBg.png │ │ │ ├── welcomeBanner.png │ │ │ ├── welcome_img.svg │ │ │ ├── welcome_img_robot.svg │ │ │ ├── welcome_to_subquery_projects.png │ │ │ └── wordCycle.svg │ │ │ ├── manifest.json │ │ │ ├── pdf │ │ │ ├── Account_Balances.pdf │ │ │ ├── Account_Transfer_with_Reverse_Lookups.pdf │ │ │ ├── Account_Transfers.pdf │ │ │ ├── Council_Proposal.pdf │ │ │ ├── Deploying_Subquery_Project.pdf │ │ │ ├── Hello_World_Lab.pdf │ │ │ ├── SubQuery_201_Lab_List_All_Transaction.pdf │ │ │ └── Sum_Rewards.pdf │ │ │ └── style │ │ │ └── homepage.css │ ├── sidebar.ts │ └── styles │ │ ├── index.scss │ │ └── palette.scss ├── README.md ├── indexer │ ├── academy │ │ ├── academy.md │ │ ├── herocourse │ │ │ ├── module1.md │ │ │ ├── module2.md │ │ │ ├── module3.md │ │ │ ├── module4.md │ │ │ ├── module5.md │ │ │ ├── module6.md │ │ │ └── welcome.md │ │ ├── moonbeam_course │ │ │ ├── lesson1.md │ │ │ ├── lesson2.md │ │ │ ├── lesson3.md │ │ │ ├── lesson4.md │ │ │ ├── lesson5.md │ │ │ ├── lesson6.md │ │ │ └── welcome.md │ │ ├── subquery101 │ │ │ └── subquery101.md │ │ └── tutorials_examples │ │ │ ├── batch-size.md │ │ │ ├── block-height.md │ │ │ ├── debug-projects.md │ │ │ ├── delete-projects.md │ │ │ ├── dictionary.md │ │ │ ├── introduction.md │ │ │ ├── run-indexer.md │ │ │ └── terminology.md │ ├── build │ │ ├── cosmos-evm.md │ │ ├── dynamicdatasources.md │ │ ├── graph-migration.md │ │ ├── graphql.md │ │ ├── install.md │ │ ├── introduction.md │ │ ├── manifest │ │ │ ├── algorand.md │ │ │ ├── arbitrum.md │ │ │ ├── avalanche.md │ │ │ ├── bsc.md │ │ │ ├── concordium.md │ │ │ ├── cosmos.md │ │ │ ├── ethereum.md │ │ │ ├── flare.md │ │ │ ├── gnosis.md │ │ │ ├── near.md │ │ │ ├── optimism.md │ │ │ ├── polkadot.md │ │ │ ├── polygon.md │ │ │ └── stellar.md │ │ ├── mapping │ │ │ ├── algorand.md │ │ │ ├── arbitrum.md │ │ │ ├── avalanche.md │ │ │ ├── bsc.md │ │ │ ├── cache.md │ │ │ ├── concordium.md │ │ │ ├── cosmos.md │ │ │ ├── ethereum.md │ │ │ ├── flare.md │ │ │ ├── gnosis.md │ │ │ ├── near.md │ │ │ ├── optimism.md │ │ │ ├── polkadot.md │ │ │ ├── polygon.md │ │ │ ├── stellar.md │ │ │ └── store.md │ │ ├── multi-chain.md │ │ ├── optimisation.md │ │ ├── project-upgrades.md │ │ ├── substrate-evm.md │ │ ├── substrate-wasm.md │ │ └── testing.md │ ├── miscellaneous │ │ ├── avalanche-eth-migration.md │ │ ├── faqs.md │ │ └── ipfs.md │ ├── quickstart │ │ ├── quickstart.md │ │ ├── quickstart_chains │ │ │ ├── algorand.md │ │ │ ├── arbitrum.md │ │ │ ├── astar-zkevm.md │ │ │ ├── avalanche-crabada.md │ │ │ ├── avalanche.md │ │ │ ├── base-goerli.md │ │ │ ├── base.md │ │ │ ├── bevm.md │ │ │ ├── boba-bnb.md │ │ │ ├── boba-eth.md │ │ │ ├── botanix.md │ │ │ ├── bsc-pancakeswap-v3.md │ │ │ ├── bsc.md │ │ │ ├── celo.md │ │ │ ├── concordium.md │ │ │ ├── cosmos-agoric.md │ │ │ ├── cosmos-akash.md │ │ │ ├── cosmos-archway.md │ │ │ ├── cosmos-cronos.md │ │ │ ├── cosmos-dymension.md │ │ │ ├── cosmos-juno.md │ │ │ ├── cosmos-neutron.md │ │ │ ├── cosmos-osmosis.md │ │ │ ├── cosmos-other.md │ │ │ ├── cosmos-sei.md │ │ │ ├── cosmos-thorchain.md │ │ │ ├── ethereum-bayc.md │ │ │ ├── ethereum-chainlink.md │ │ │ ├── ethereum-ens.md │ │ │ ├── ethereum-gravatar.md │ │ │ ├── ethereum-opensea.md │ │ │ ├── ethereum-uniswap.md │ │ │ ├── ethsriptions.md │ │ │ ├── evm.md │ │ │ ├── fantom.md │ │ │ ├── flare.md │ │ │ ├── gnosis.md │ │ │ ├── harmony.md │ │ │ ├── heco.md │ │ │ ├── immutable-testnet.md │ │ │ ├── iotex.md │ │ │ ├── klaytn.md │ │ │ ├── mantle.md │ │ │ ├── meter.md │ │ │ ├── metis.md │ │ │ ├── near-aurora.md │ │ │ ├── near-ref-finance.md │ │ │ ├── near.md │ │ │ ├── optimism.md │ │ │ ├── polkadot-astar.md │ │ │ ├── polkadot-humanode.md │ │ │ ├── polkadot-kilt.md │ │ │ ├── polkadot-moonbeam.md │ │ │ ├── polkadot-other.md │ │ │ ├── polkadot.md │ │ │ ├── polygon-lens.md │ │ │ ├── polygon-zkevm.md │ │ │ ├── polygon.md │ │ │ ├── scroll-sepolia.md │ │ │ ├── scroll.md │ │ │ ├── skale.md │ │ │ ├── stellar-soroban.md │ │ │ ├── stellar.md │ │ │ ├── xdc-apothem.md │ │ │ ├── xlayer-testnet.md │ │ │ └── zksync-era.md │ │ ├── quickstart_multichain │ │ │ ├── galxe-nft.md │ │ │ ├── ibc-transfers.md │ │ │ ├── kava-multi-chain.md │ │ │ ├── polygon-plasma-bridge.md │ │ │ ├── safe.md │ │ │ ├── snapshot.md │ │ │ └── snippets │ │ │ │ ├── multi-chain-cosmos-manifest-intro.md │ │ │ │ ├── multi-chain-cosmos-quickstart-reference.md │ │ │ │ ├── multi-chain-creation.md │ │ │ │ ├── multi-chain-evm-manifest-intro.md │ │ │ │ ├── multi-chain-network-origin-note.md │ │ │ │ └── multi-chain-quickstart-reference.md │ │ ├── snippets │ │ │ ├── arbitrum-manifest-note.md │ │ │ ├── arbitrum-mapping-note.md │ │ │ ├── avalanche-manifest-note.md │ │ │ ├── avalanche-mapping-note.md │ │ │ ├── bsc-manifest-note.md │ │ │ ├── bsc-mapping-note.md │ │ │ ├── build.md │ │ │ ├── codegen.md │ │ │ ├── cosmos-codegen.md │ │ │ ├── cosmos-handlers.md │ │ │ ├── cosmos-manifest-intro.md │ │ │ ├── cosmos-manifest-note.md │ │ │ ├── cosmos-mapping-intro.md │ │ │ ├── cosmos-mapping-note.md │ │ │ ├── cosmos-quickstart-reference.md │ │ │ ├── ethereum-manifest-note.md │ │ │ ├── ethereum-mapping-note.md │ │ │ ├── evm-abi.md │ │ │ ├── evm-codegen.md │ │ │ ├── evm-handlers.md │ │ │ ├── evm-manifest-intro.md │ │ │ ├── evm-mapping-intro.md │ │ │ ├── evm-quickstart-reference-abi-scaffold.md │ │ │ ├── evm-quickstart-reference.md │ │ │ ├── final-code.md │ │ │ ├── flare-manifest-note.md │ │ │ ├── flare-mapping-note.md │ │ │ ├── gnosis-manifest-note.md │ │ │ ├── gnosis-mapping-note.md │ │ │ ├── gravatar-note.md │ │ │ ├── manifest-intro.md │ │ │ ├── mapping-intro.md │ │ │ ├── near-codegen.md │ │ │ ├── near-handlers.md │ │ │ ├── near-manifest-intro.md │ │ │ ├── near-manifest-note.md │ │ │ ├── near-mapping-intro.md │ │ │ ├── near-mapping-note.md │ │ │ ├── near-quickstart-reference.md │ │ │ ├── note-on-entity-relationships.md │ │ │ ├── polkadot-handlers.md │ │ │ ├── polkadot-manifest-intro.md │ │ │ ├── polkadot-manifest-note.md │ │ │ ├── polkadot-mapping-note.md │ │ │ ├── polygon-manifest-note.md │ │ │ ├── polygon-mapping-note.md │ │ │ ├── query-intro.md │ │ │ ├── quickstart-reference.md │ │ │ ├── run-locally.md │ │ │ ├── schema-intro.md │ │ │ ├── schema-note.md │ │ │ ├── stellar-codegen.md │ │ │ ├── stellar-handlers.md │ │ │ ├── stellar-manifest-intro.md │ │ │ ├── stellar-manifest-note.md │ │ │ ├── stellar-mapping-note.md │ │ │ ├── types-regeneration-warning.md │ │ │ └── whats-next.md │ │ └── whats-next.md │ ├── run_publish │ │ ├── cli.md │ │ ├── historical.md │ │ ├── monitor.md │ │ ├── optimisation.md │ │ ├── publish.md │ │ ├── query │ │ │ ├── aggregate.md │ │ │ ├── graphql.md │ │ │ ├── other_tools │ │ │ │ ├── bigquery.md │ │ │ │ └── metabase.md │ │ │ ├── query.md │ │ │ └── subscription.md │ │ ├── references.md │ │ └── run.md │ └── welcome.md ├── miscellaneous │ ├── ambassadors.md │ ├── branding.md │ ├── contributing.md │ ├── social_media.md │ └── vulnerability-reporting.md └── subquery_network │ ├── architects │ ├── introduction.md │ └── publish.md │ ├── community.md │ ├── consumers │ ├── boosting.md │ ├── faq.md │ ├── introduction.md │ ├── plan.md │ └── playground.md │ ├── data_node │ ├── introduction.md │ ├── rpc.md │ └── run.md │ ├── delegators │ ├── delegating.md │ ├── introduction.md │ └── rewards.md │ ├── foundation.md │ ├── glossary.md │ ├── introduction │ ├── design-philosophy.md │ ├── era.md │ ├── introduction.md │ ├── kepler.md │ ├── payment-methods.md │ └── reward-distribution.md │ ├── node_operators │ ├── indexers │ │ ├── index-project.md │ │ └── introduction.md │ ├── introduction.md │ ├── plans.md │ ├── rewards.md │ ├── rpc_providers │ │ ├── connect-node.md │ │ └── introduction.md │ ├── setup │ │ ├── becoming-a-node-operator.md │ │ ├── faq.md │ │ ├── install-linux.md │ │ ├── install-local-docker.md │ │ ├── security-guide.md │ │ ├── separated-db.md │ │ └── troubleshooting.md │ └── stake.md │ ├── parameters.md │ ├── token │ ├── bridge.md │ ├── claim.md │ ├── swap.md │ ├── token.md │ └── tokenomics.md │ └── welcome.md ├── package.json └── pnpm-lock.yaml /.github/workflows/deploy-staging.yml: -------------------------------------------------------------------------------- 1 | name: Deploy to Staging - doc.thechaindata.com 2 | on: 3 | push: 4 | branches: 5 | - master 6 | paths: 7 | - "docs/**" 8 | workflow_dispatch: 9 | 10 | jobs: 11 | build: 12 | runs-on: ubuntu-latest 13 | steps: 14 | - name: Checkout 15 | uses: actions/checkout@v4 16 | 17 | - name: Install pnpm 18 | uses: pnpm/action-setup@v2 19 | with: 20 | run_install: true 21 | 22 | - name: Setup Node.js 23 | uses: actions/setup-node@v4 24 | with: 25 | node-version: 20 26 | cache: pnpm 27 | 28 | - name: Build docs 29 | run: pnpm docs:build 30 | 31 | - uses: aws-actions/configure-aws-credentials@v1 32 | with: 33 | aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }} 34 | aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }} 35 | aws-region: ap-northeast-1 36 | - run: aws s3 sync ./docs/.vuepress/dist s3://doc.thechaindata.com/ --delete 37 | -------------------------------------------------------------------------------- /.vscode/settings.json: -------------------------------------------------------------------------------- 1 | { 2 | "compile-hero.disable-compile-files-on-did-save-code": false 3 | } 4 | -------------------------------------------------------------------------------- /archived/bg/academy/academy.md: -------------------------------------------------------------------------------- 1 | # Заповядайте в Академията 2 | -------------------------------------------------------------------------------- /archived/bg/academy/tutorials_examples/delete-projects.md: -------------------------------------------------------------------------------- 1 | # Как да изтрия проект в SubQuery? 2 | 3 | ## Въведение 4 | 5 | Важно е да поддържате вашите проекти и актуалността им в проекта SubQuery. За всички проекти, вече качени в проекта SubQuery за тестване, се препоръчва премахнето им след това, за спестяване на ресурси и намаляване на разходи. 6 | 7 | Стартирането на възел в индексатор е допълнителна опция, освен използването на Docker или разполагане на проект в[SubQuery Managed Service](https://managedservice.subquery.network/). Това отнема повече време и усилия, но подобрява разбирането ви за начина на работа на SubQuery. 8 | 9 | ## Премахване на проект от staging слот 10 | 11 | За да премахнете проект от staging слота, щракнете върху 3-те точки в секцията на междинния слот в детайлите за внедряване на страницата на контролния панел за вашия проект и изберете Изтриване. 12 | 13 | ![Премахване на проект от междинния слот](/assets/img/delete_staging.png) 14 | 15 | ## Премахване на проект от работното пространство 16 | 17 | За да премахнете проект от работното пространство, ще трябва да изтриете целия проект. Отидете в горния десен ъгъл и кликнете върху 3-те точки, които представляват настройките за целия проект. Изберите "Премахване на проект". 18 | 19 | ![Премахване на проект от работното пространство](/assets/img/delete_production.png) 20 | -------------------------------------------------------------------------------- /archived/bg/academy/tutorials_examples/terminology.md: -------------------------------------------------------------------------------- 1 | # Терминология 2 | 3 | - SubQuery Project (_където се случват магиите_): Определение ([`@subql/cli`](https://www.npmjs.com/package/@subql/cli)) за това как SubQuery Node трябва да преминава и агрегира мрежата от проекти и как данните трябва да бъдат трансформирани и съхранени, за да бъдат включени полезни GraphQL заявки 4 | - SubQuery Node (_където се изпълнява работата_): Пакет ([`@subql/node`](https://www.npmjs.com/package/@subql/node)) което ще приеме дефиницията на проекта SubQuery и ще стартира нода, която от своя страна постоянно индексира свързаната мрежа към базата данни 5 | - Услуга за запитвания SubQuery (_откъдето получаваме данните_): Пакет ([`@subql/query`](https://www.npmjs.com/package/@subql/query)), взаимодействащ с GraphQL API на активната вече нода SubQuery за запитване и преглед на индексираните данни 6 | - GraphQL (_как правим запитвания за данните_): Език за запитвания за APIs който е специално подходящ за гъвкави данни, базирани върху графици - виж[graphql.org](https://graphql.org/learn/) 7 | -------------------------------------------------------------------------------- /archived/bg/miscellaneous/branding.md: -------------------------------------------------------------------------------- 1 | # Брандирани материали 2 | 3 | **Всички елементи от бранда/ марката SubQuery са фирмена собственост, като се отнасяме много отговорно към нашата визията бранда. ** 4 | 5 | Ако решите да използвате различни търговски марки, лого, дизайни или други характеристики на марката, моля, следвайте внимателно указанията описани тук или се свържете с нас чрез социалните медии за допълнително разяснение. 6 | 7 | Ако се съмнявате, попитайте! 8 | 9 | ## Експортируем файл Figma 10 | 11 | Нашият файл Figma съдържа пълна колекция от всички активи на марката (лого, шрифтове, цветове, изображения и т.н.) с възможност за експорт. 12 | 13 | [Figma - Ресурси за бранда SubQuery](https://www.figma.com/file/AaCXaOcElrlbxq8fz39sJU/SubQuery-Brand-Resources?node-id=3%3A2) 14 | 15 | ## Пакет от брандинг активи 16 | 17 | По-малък ZIP пакет с активи на марката: [public_branding.zip](https://static.subquery.network/public_branding.zip). 18 | -------------------------------------------------------------------------------- /archived/bg/run_publish/connect.md: -------------------------------------------------------------------------------- 1 | # Connect to your new project 2 | 3 | Once your deployment has succesfully completed and our nodes have indexed your data from the chain, you'll be able to connect to your project via the displayed Query endpoint. 4 | 5 | ![Проектът се внедрява и се синхронизира](/assets/img/projects_deploy_sync.png) 6 | 7 | Като алтернатива можете да щракнете върху трите точки до заглавието на вашия проект и да го видите в SubQuery Explorer. There you can use the in browser playground to get started. 8 | 9 | ![Projects in SubQuery Explorer](/assets/img/projects_explorer.png) 10 | 11 | ::: tip Note Learn more about the [GraphQL Query language.](./graphql.md) ::: 12 | -------------------------------------------------------------------------------- /archived/bg/run_publish/graphql.md: -------------------------------------------------------------------------------- 1 | # Научете повече за GraphQL 2 | 3 | Можете да разгледате [официалното ръководство за GraphQL тук](https://graphql.org/learn/), за да научите повече за GraphQL, как работи и как да го използвате: 4 | 5 | - Има библиотеки, които да ви помогнат да внедрите GraphQL на [много различни езици](https://graphql.org/code/). 6 | - За задълбочено обучение с практически уроци вижте [Как да GraphQL](https://www.howtographql.com/). 7 | - Вижте безплатния онлайн курс [Изследване на GraphQL: език за заявки за API](https://www.edx.org/course/exploring-graphql-a-query-language-for-apis). 8 | -------------------------------------------------------------------------------- /archived/bg/run_publish/sandbox.md: -------------------------------------------------------------------------------- 1 | # The Sandbox 2 | 3 | В нашия преполагаем сценарий на използване нодата SubQuery обикновено се изпълнява от доверен хост и кодът на проекта за SubQuery, изпратен от Потребителя към нодата, не е напълно надежден. 4 | 5 | Някои злонамерени кодове може да атакуват хоста или дори да го компрометират като нанесът ущърб на данните на други проекти на същия хост. Затова използваме [VM2](https://www.npmjs.com/package/vm2) sandbox защитен механизъм за намаляване на риска. Този: 6 | 7 | - Безопасно изпълнява ненадежден код в изолирана среда и злонамереният код не получава достъп до мрежата и файловата система на хоста, освен ако е чрез публичен интерфейс, който сме внедрили в sandbox. 8 | 9 | - Безопасно генерира методи и обменя даннис обратни повиквания между изолирани среди. 10 | 11 | - Устойчив срещу разлини популярни методи за атака. 12 | 13 | ## Ограничения 14 | 15 | - За да ограничите достъпа до определени вградени модули, само`assert`, `buffer`, `crypto`,`util` и `path` са включени в белия списък. 16 | 17 | - Ние подкрепяме [модули от трети страни](../create/mapping/polkadot.md#third-party-libraries) написани в **CommonJS** и **hybrid** библиотеки като `@polkadot/*` използващи ESM по подразбиране. 18 | 19 | - Всеки модули използващи `HTTP` и `WebSocket` са забранени. 20 | -------------------------------------------------------------------------------- /archived/bg/subquery_network/frontier-testnet.md: -------------------------------------------------------------------------------- 1 | # Frontier Testnet 2 | -------------------------------------------------------------------------------- /archived/de/academy/academy.md: -------------------------------------------------------------------------------- 1 | # Herzlich Willkommen in der Akademie 2 | -------------------------------------------------------------------------------- /archived/de/academy/tutorials_examples/terminology.md: -------------------------------------------------------------------------------- 1 | # Terminologie 2 | 3 | - SubQuery-Projekt (_wo die Magie passiert_): Eine Definition ([`@subql/cli`](https://www.npmjs.com/package/@subql/cli)), wie eine SubQuery-Node ein Projektnetzwerk durchlaufen und aggregieren soll und wie die Daten transformiert und gespeichert werden sollen, um nützliche GraphQL-Abfragen zu ermöglichen 4 | - SubQuery-Node (_wo die Arbeit erledigt wird_): Ein Paket ([`@subql/node`](https://www.npmjs.com/package/@subql/node)), das eine SubQuery-Projektdefinition akzeptiert und eine ausführte Node, die ein verbundenes Netzwerk ständig mit einer Datenbank indiziert 5 | - SubQuery-Abfragedienst (_woher wir die Daten beziehen_): Ein Paket ([`@subql/query`](https://www.npmjs.com/package/@subql/query)), das mit der GraphQL-API eines bereitgestellten SubQuery-Node zum Abfragen und Anzeigen der indizierten Daten 6 | - GraphQL (_wie wir die Daten abfragen_): Eine Abfragesprache für APIs, die speziell für flexible graphbasierte Daten geeignet ist – siehe [graphql.org](https://graphql.org/learn/) 7 | -------------------------------------------------------------------------------- /archived/de/miscellaneous/branding.md: -------------------------------------------------------------------------------- 1 | # Markenmaterialien 2 | 3 | **Alle Markenfunktionen von SubQuery sind proprietär und wir nehmen unsere Marke sehr ernst.** 4 | 5 | Wenn Sie sich für die Verwendung von Marken, Logos, Designs oder anderen Markenmerkmalen entscheiden, befolgen Sie bitte sorgfältig die Richtlinien hier oder kontaktieren Sie uns über soziale Medien zur Klärung. 6 | 7 | Im Zweifel bitte nachfragen! 8 | 9 | ## Exportierbare Figma-Datei 10 | 11 | Unsere Figma-Datei enthält eine vollständige Sammlung aller Markenelemente (Logos, Schriftarten, Farben, Bilder usw.) zum Exportieren. 12 | 13 | [Figma - SubQuery Markenressourcen](https://www.figma.com/file/AaCXaOcElrlbxq8fz39sJU/SubQuery-Brand-Resources?node-id=3%3A2) 14 | 15 | ## Marken-Assets-Paket 16 | 17 | Ein kleineres ZIP-Paket mit Marken-Assets: [public_branding.zip](https://static.subquery.network/public_branding.zip). 18 | -------------------------------------------------------------------------------- /archived/de/run_publish/connect.md: -------------------------------------------------------------------------------- 1 | # Verbinden Sie sich mit Ihrem neuen Projekt 2 | 3 | Sobald Ihre Bereitstellung erfolgreich abgeschlossen wurde und unsere Knoten Ihre Daten aus der Chain indiziert haben, können Sie über den angezeigten Abfrageendpunkt eine Verbindung zu Ihrem Projekt herstellen. 4 | 5 | ![Projekt wird bereitgestellt und synchronisiert](/assets/img/projects_deploy_sync.png) 6 | 7 | Alternativ können Sie auf die drei Punkte neben dem Titel Ihres Projekts klicken und es im SubQuery Explorer anzeigen. Dort können Sie den Spielplatz im Browser verwenden, um loszulegen. 8 | 9 | ![Projekte im SubQuery Explorer](/assets/img/projects_explorer.png) 10 | 11 | ::: tip Hinweis Erfahren Sie mehr über die [GraphQL-Abfragesprache.](./graphql.md) ::: 12 | -------------------------------------------------------------------------------- /archived/de/run_publish/graphql.md: -------------------------------------------------------------------------------- 1 | # Erfahren Sie mehr über GraphQL 2 | 3 | Sie können der [offiziellen GraphQL-Anleitung hier](https://graphql.org/learn/) folgen, um mehr über GraphQL, seine Funktionsweise und seine Verwendung zu erfahren: 4 | 5 | - Es gibt Bibliotheken, die Ihnen helfen, GraphQL in [vielen verschiedenen Sprachen](https://graphql.org/code/) zu implementieren. 6 | - Eine ausführliche Lernerfahrung mit praktischen Tutorials finden Sie unter [How to GraphQL](https://www.howtographql.com/). 7 | - Sehen Sie sich den kostenlosen Online-Kurs [Exploring GraphQL: A Query Language for APIs](https://www.edx.org/course/exploring-graphql-a-query-language-for-apis) an. 8 | -------------------------------------------------------------------------------- /archived/de/subquery_network/frontier-testnet.md: -------------------------------------------------------------------------------- 1 | # Frontier Testnet 2 | -------------------------------------------------------------------------------- /archived/es/academy/academy.md: -------------------------------------------------------------------------------- 1 | # Bienvenido a la Academia 2 | -------------------------------------------------------------------------------- /archived/es/academy/tutorials_examples/batch-size.md: -------------------------------------------------------------------------------- 1 | # ¿Cómo cambiar el tamaño del lote de la búsqueda en cadena de bloques? 2 | 3 | ## Guía en vídeo 4 | 5 |
6 |
7 | 8 |
9 | 10 | ## Introducción 11 | 12 | El tamaño del lote por defecto es 100, pero esto se puede cambiar usando el comando extra `--batch-size=xx`. 13 | 14 | Necesitas esto a la línea de comandos como una bandera extra o si estás usando Docker, modificar el docker-compose.yml con: 15 | 16 | ```shell 17 | subquery-node: 18 | image: onfinality/subql-node:latest 19 | depends_on: 20 | - "postgres" 21 | restart: always 22 | environment: DB_USER: postgres 23 | DB_PASS: postgres 24 | DB_DATABASE: postgres 25 | DB_HOST: postgres 26 | DB_PORT: 5432 27 | volumes: 28 | - ./:/app 29 | command: 30 | - -f=/app 31 | - --local 32 | - --batch-size=50 33 | 34 | ``` 35 | 36 | Este ejemplo establece el tamaño del lote a 50. 37 | 38 | ## ¿Por qué cambiar el tamaño del lote? 39 | 40 | Usar un tamaño por lotes más pequeño puede reducir el uso de memoria y no dejar a los usuarios colgando para grandes consultas. En otras palabras, su aplicación puede ser más receptiva. 41 | -------------------------------------------------------------------------------- /archived/es/academy/tutorials_examples/terminology.md: -------------------------------------------------------------------------------- 1 | # Terminología 2 | 3 | - SubQuery Project (_donde sucede la magia_): Una definición ([`@subql/cli`](https://www.npmjs.com/package/@subql/cli)) de cómo un SubQuery Node debe recorrer y agregar una red de proyectos y cómo los datos deben transformarse y almacenarse para permitir consultas útiles en GraphQL 4 | - SubQuery Node (_donde se realiza el trabajo_): Un paquete ([`@subql/node`](https://www.npmjs.com/package/@subql/node)) que aceptará la definicion del proyecto SubQuery, y ejecutar un nodo que indexa constantemente una red conectada a una base de datos 5 | - Servicio de consulta SubQuery (_donde obtenemos los datos de_): Un paquete ([`@subql/query`](https://www.npmjs.com/package/@subql/query)) que interactúa con la API GraphQL de un nodo de subconsulta desplegado para consultar y ver los datos indexados 6 | - GraphQL (_cómo consultamos los datos_): Un ángulo de consulta para API que es especialmente adecuado para datos flexibles basados en gráficos - ver [graphql.org](https://graphql.org/learn/) 7 | -------------------------------------------------------------------------------- /archived/es/miscellaneous/branding.md: -------------------------------------------------------------------------------- 1 | # Material de Marca 2 | 3 | **Todas las características de la marca de SubQuery son propietarias y nos tomamos nuestra marca extremadamente en serio.** 4 | 5 | Si opta por utilizar cualquier marca registrada, logotipos, diseños u otras características de marca, por favor siga cuidadosamente las directrices aquí o comuníquese con nosotros a través de los medios de comunicación sociales para aclaración. 6 | 7 | En caso de duda, por favor, pregunte! 8 | 9 | ## Archivo de Figma exportable 10 | 11 | Nuestro archivo Figma tiene una colección completa de todos los activos de la marca (logotipos, fuentes, colores, imágenes etc) para su exportación. 12 | 13 | [Figma - Recursos de la marca SubQuery](https://www.figma.com/file/AaCXaOcElrlbxq8fz39sJU/SubQuery-Brand-Resources?node-id=3%3A2) 14 | 15 | ## Paquete de Recursos de Marca 16 | 17 | A smaller ZIP package of brand assets: [public_branding.zip](https://static.subquery.network/public_branding.zip). 18 | -------------------------------------------------------------------------------- /archived/es/run_publish/connect.md: -------------------------------------------------------------------------------- 1 | # Connect to your new project 2 | 3 | Once your deployment has succesfully completed and our nodes have indexed your data from the chain, you'll be able to connect to your project via the displayed Query endpoint. 4 | 5 | ![Proyecto en despliegue y sincronización](/assets/img/projects_deploy_sync.png) 6 | 7 | Alternativamente, puedes hacer clic en los tres puntos al lado del título de tu proyecto, y verlo en SubQuery Explorer. There you can use the in browser playground to get started. 8 | 9 | ![Projects in SubQuery Explorer](/assets/img/projects_explorer.png) 10 | 11 | ::: tip Note Learn more about the [GraphQL Query language.](./graphql.md) ::: 12 | -------------------------------------------------------------------------------- /archived/es/run_publish/graphql.md: -------------------------------------------------------------------------------- 1 | # Más acerca de GraphQL 2 | 3 | Puedes seguir la guía [oficial de GraphQL aquí](https://graphql.org/learn/) para aprender más sobre GraphQL, cómo funciona y cómo usarla: 4 | 5 | - There are libraries to help you implement GraphQL in [many different languages](https://graphql.org/code/). 6 | - Para obtener una experiencia de aprendizaje en profundidad con tutoriales prácticos, consulte [How to GraphQL](https://www.howtographql.com/). 7 | - Echa un vistazo al curso en línea gratuito, [Explorando GraphQL: Un idioma de consulta para APIs](https://www.edx.org/course/exploring-graphql-a-query-language-for-apis). 8 | -------------------------------------------------------------------------------- /archived/es/run_publish/sandbox.md: -------------------------------------------------------------------------------- 1 | # The Sandbox 2 | 3 | En nuestro escenario de uso visionado, el nodo SubQuery es generalmente ejecutado por un host de confianza, y el código del proyecto SubQuery enviado por el usuario al nodo no es del todo fiable. 4 | 5 | Es probable que algún código malicioso ataque al anfitrión o incluso lo comprometa, y causar daños a los datos de otros proyectos en el mismo anfitrión. Por lo tanto, utilizamos el mecanismo protegido de sandbox [VM2](https://www.npmjs.com/package/vm2) para reducir los riesgos. Esto: 6 | 7 | - Ejecuta código no confiable de forma segura en un contexto aislado y código malicioso no accederá a la red y al sistema de archivos del host a menos que a través de la interfaz expuesta inyectemos en el sandbox. 8 | 9 | - Llama de forma segura a métodos e intercambia datos y callbacks entre sandboxes. 10 | 11 | - Es inmune a muchos métodos conocidos de ataque. 12 | 13 | ## Restricción 14 | 15 | - Para limitar el acceso a ciertos módulos integrados, solo `assert`, `buffer`, `crypto`,`util` y `path` están en la lista blanca. 16 | 17 | - Soportamos [módulos de terceros](../create/mapping/polkadot.md#third-party-libraries) escritos en **CommonJS** y **bibliotecas híbridas** como `@polkadot/*` que usan ESM por defecto. 18 | 19 | - Cualquier módulo que utilice `HTTP` y `WebSocket` está prohibido. 20 | -------------------------------------------------------------------------------- /archived/es/subquery_network/frontier-testnet.md: -------------------------------------------------------------------------------- 1 | # Testnet Frontier 2 | -------------------------------------------------------------------------------- /archived/fr/academy/academy.md: -------------------------------------------------------------------------------- 1 | # Bienvenue à l'Académie 2 | -------------------------------------------------------------------------------- /archived/fr/academy/tutorials_examples/terminology.md: -------------------------------------------------------------------------------- 1 | # Terminologie 2 | 3 | - SubQuery Project (_où la magie se produit_) : Une définition ([`@subql/cli`](https://www.npmjs.com/package/@subql/cli)) de la façon dont un noeud de sous-requête doit traverser et agréger un réseau de projets et comment les données devraient être transformées et stockées pour permettre des requêtes GraphQL utiles 4 | - SubQuery Node (_où le travail est fait_) : Un paquet ([`@subql/node`](https://www.npmjs.com/package/@subql/node)) qui acceptera un projet definiton de SubQuery, et exécuter un nœud qui indexe constamment un réseau connecté à une base de données 5 | - SubQuery Query Service (_où nous obtenons les données de_) : Un paquet ([`@subql/query`](https://www.npmjs.com/package/@subql/query)) qui interagit avec l'API GraphQL d'un noeud de SubQuery déployé pour interroger et voir les données indexées 6 | - GraphQL (_comment nous interrogeons les données_) : Un langage de requête pour les APIs qui est spécifiquement adapté pour des données flexibles basées sur des graphiques - voir [graphql.org](https://graphql.org/learn/) 7 | -------------------------------------------------------------------------------- /archived/fr/miscellaneous/branding.md: -------------------------------------------------------------------------------- 1 | # Matériel d'image de marque 2 | 3 | **Toutes les caractéristiques de la marque SubQuery sont exclusives et nous prenons notre marque très au sérieux.** 4 | 5 | Si vous décidez d'utiliser des marques, des logos, des dessins ou d'autres caractéristiques de la marque, veuillez suivre attentivement les directives énoncées ici ou nous contacter via les médias sociaux pour obtenir des précisions. 6 | 7 | En cas de doute, n'hésitez pas à demander ! 8 | 9 | ## Fichier Figma exportable 10 | 11 | Notre fichier Figma contient une collection complète de tous les actifs de la marque (logos, polices, couleurs, images, etc.) à exporter. 12 | 13 | [Figma - Ressources de la marque SubQuery](https://www.figma.com/file/AaCXaOcElrlbxq8fz39sJU/SubQuery-Brand-Resources?node-id=3%3A2) 14 | 15 | ## Paquet d'actifs de marque 16 | 17 | A smaller ZIP package of brand assets: [public_branding.zip](https://static.subquery.network/public_branding.zip). 18 | -------------------------------------------------------------------------------- /archived/fr/run_publish/connect.md: -------------------------------------------------------------------------------- 1 | # Connect to your new project 2 | 3 | Once your deployment has succesfully completed and our nodes have indexed your data from the chain, you'll be able to connect to your project via the displayed Query endpoint. 4 | 5 | ![Projet en cours de déploiement et de synchronisation](/assets/img/projects_deploy_sync.png) 6 | 7 | Vous pouvez également cliquer sur les trois points situés à côté du titre de votre projet, et le visualiser dans l'explorateur de SubQuery. There you can use the in browser playground to get started. 8 | 9 | ![Projects in SubQuery Explorer](/assets/img/projects_explorer.png) 10 | 11 | ::: tip Note Learn more about the [GraphQL Query language.](./graphql.md) ::: 12 | -------------------------------------------------------------------------------- /archived/fr/run_publish/graphql.md: -------------------------------------------------------------------------------- 1 | # En savoir plus sur GraphQL 2 | 3 | Vous pouvez suivre le [guide officiel GraphQL ici](https://graphql.org/learn/) pour en savoir plus sur GraphQL, son fonctionnement et son utilisation : 4 | 5 | - There are libraries to help you implement GraphQL in [many different languages](https://graphql.org/code/). 6 | - Pour un apprentissage approfondi avec des tutoriels pratiques, voir [Comment faire du GraphQL](https://www.howtographql.com/). 7 | - Consultez le cours en ligne gratuit, [Explorer GraphQL : Un langage de requête pour les API](https://www.edx.org/course/exploring-graphql-a-query-language-for-apis). 8 | -------------------------------------------------------------------------------- /archived/fr/subquery_network/frontier-testnet.md: -------------------------------------------------------------------------------- 1 | # Frontier Testnet 2 | -------------------------------------------------------------------------------- /archived/id/academy/academy.md: -------------------------------------------------------------------------------- 1 | # Selamat datang di Akademi 2 | -------------------------------------------------------------------------------- /archived/id/academy/tutorials_examples/batch-size.md: -------------------------------------------------------------------------------- 1 | # Bagaimana cara mengubah ukuran blockchain fetching batch? 2 | 3 | ## Panduan video 4 | 5 |
6 |
7 | 8 |
9 | 10 | ## Pengenalan 11 | 12 | Ukuran batch default adalah 100, tapi ini bisa diubah menggunakan perintah ekstra `--batch-size=xx`. 13 | 14 | Anda perlu memasukkannya ke garis perintah sebagai extra flag atau jika menggunakan Docker, modifikasi file docker-compose.yml dengan: 15 | 16 | ```shell 17 | subquery-node: 18 | image: onfinality/subql-node:latest 19 | depends_on: 20 | - "postgres" 21 | restart: always 22 | environment: 23 | DB_USER: postgres 24 | DB_PASS: postgres 25 | DB_DATABASE: postgres 26 | DB_HOST: postgres 27 | DB_PORT: 5432 28 | volumes: 29 | - ./:/app 30 | command: 31 | - -f=/app 32 | - --local 33 | - --batch-size=50 34 | 35 | ``` 36 | 37 | Contoh ini mengatur ukuran batch (batch size) ke 50. 38 | 39 | ## Kenapa mengubah ukuran batch? 40 | 41 | Menggunakan ukuran batch yang lebih kecil dapat mengurangi penggunaan memori dan tidak membuat pengguna menggantung untuk kueri besar. Dengan kata lain, aplikasi Anda bisa lebih responsif. 42 | -------------------------------------------------------------------------------- /archived/id/academy/tutorials_examples/terminology.md: -------------------------------------------------------------------------------- 1 | # Terminologi 2 | 3 | - SubQuery Project (_tempat sihirnya terjadi_): Sebuah definisi ([`@subql/cli`](https://www.npmjs.com/package/@subql/cli)) tentang bagaimana SubQuery Node perlu melintasi dan menyatukan jaringan proyek dan bagaimana datanya ditransformasi dan disimpan untuk menghasilkan query GraphQL yang berguna 4 | - SubQuery Node (_tempat kerjanya dilakukan_): Sebuah paket ([`@subql/node`](https://www.npmjs.com/package/@subql/node)) yang akan menerima definisi proyek SubQuery, dan menjalankan node yang secara konstan mengindeks jaringan yang terhubung ke basis data 5 | - SubQuery Query Service (_tempat kami mendapatkan datanya_): Sebuah paket ([`@subql/query`](https://www.npmjs.com/package/@subql/query)) yang berinteraksi dengan GraphQL API dari node SubQuery yang dikeluarkan untuk melakukan query dan melihat data yang sudah diindeks 6 | - GraphQL (_bagaimana kami melakukan query data_): Bahasa Query untuk API yang secara khusus diperuntukkan data berbasis grafik yang fleksibel - lihat [graphql.org](https://graphql.org/learn/) 7 | -------------------------------------------------------------------------------- /archived/id/miscellaneous/branding.md: -------------------------------------------------------------------------------- 1 | # Materi Merek 2 | 3 | **Semua fitur merek SubQuery adalah hak milik dan kami memperlakukan merek kami dengan sangat serius.** 4 | 5 | Jika Anda memilih untuk menggunakan merek dagang, logo, desain, atau fitur merek lainnya, harap ikuti panduan di sini dengan cermat atau hubungi kami melalui media sosial untuk klarifikasi. 6 | 7 | Jika ragu, silakan bertanya! 8 | 9 | ## File Figma yang Dapat Diekspor 10 | 11 | File Figma kami memiliki koleksi lengkap semua aset merek (logo, font, warna, gambar, dll.) untuk diekspor. 12 | 13 | [Figma - Sumber Daya Merek SubQuery](https://www.figma.com/file/AaCXaOcElrlbxq8fz39sJU/SubQuery-Brand-Resources?node-id=3%3A2) 14 | 15 | ## Paket Aset Merek 16 | 17 | Paket ZIP aset merek yang lebih kecil: [public_branding.zip](https://static.subquery.network/public_branding.zip). 18 | -------------------------------------------------------------------------------- /archived/id/run_publish/connect.md: -------------------------------------------------------------------------------- 1 | # Hubungkan ke Proyek Baru Anda 2 | 3 | Setelah penyebaran Anda berhasil diselesaikan dan node kami telah mengindeks data Anda dari rantai, Anda akan dapat terhubung ke proyek Anda melalui titik akhir Query yang ditampilkan. 4 | 5 | ![Proyek sedang diterapkan dan disinkronkan](/assets/img/projects_deploy_sync.png) 6 | 7 | Atau, Anda dapat mengklik tiga titik di samping judul proyek Anda, dan melihatnya di SubQuery Explorer. Di sana Anda dapat menggunakan taman bermain di browser untuk memulai. 8 | 9 | ![Proyek di SubQuery Explorer](/assets/img/projects_explorer.png) 10 | 11 | :::: tip Catatan Pelajari lebih lanjut tentang [GraphQL Query language.](./graphql.md) ::: 12 | -------------------------------------------------------------------------------- /archived/id/run_publish/graphql.md: -------------------------------------------------------------------------------- 1 | # Pelajari lebih lanjut tentang GraphQL 2 | 3 | Anda dapat mengikuti [panduan resmi GraphQL di sini](https://graphql.org/learn/) untuk mempelajari lebih lanjut tentang GraphQL, cara kerjanya, dan cara menggunakannya: 4 | 5 | - Ada pustaka untuk membantu Anda mengimplementasikan GraphQL dalam [banyak bahasa yang berbeda](https://graphql.org/code/). 6 | - Untuk pengalaman belajar yang mendalam dengan tutorial praktis, lihat [Cara GraphQL](https://www.howtographql.com/). 7 | - Lihatlah kursus online gratis, [Menjelajahi GraphQL: Bahasa Kueri untuk API](https://www.edx.org/course/exploring-graphql-a-query-language-for-apis). 8 | -------------------------------------------------------------------------------- /archived/id/subquery_network/frontier-testnet.md: -------------------------------------------------------------------------------- 1 | # Frontier Testnet 2 | -------------------------------------------------------------------------------- /archived/it/academy/academy.md: -------------------------------------------------------------------------------- 1 | # Benvenuti in Accademia 2 | -------------------------------------------------------------------------------- /archived/it/academy/tutorials_examples/batch-size.md: -------------------------------------------------------------------------------- 1 | # How to change the blockchain fetching batch size? 2 | 3 | ## Video guida 4 | 5 |
6 |
7 | 8 |
9 | 10 | ## Introduction 11 | 12 | The default batch size is 100, but this can be changed by using the extra command `--batch-size=xx`. 13 | 14 | You need to this to the command line as an extra flag or if you are using Docker, modify the docker-compose.yml with: 15 | 16 | ```shell 17 | subquery-node: 18 | image: onfinality/subql-node:latest 19 | depends_on: 20 | - "postgres" 21 | restart: always 22 | environment: 23 | DB_USER: postgres 24 | DB_PASS: postgres 25 | DB_DATABASE: postgres 26 | DB_HOST: postgres 27 | DB_PORT: 5432 28 | volumes: 29 | - ./:/app 30 | command: 31 | - -f=/app 32 | - --local 33 | - --batch-size=50 34 | 35 | ``` 36 | 37 | This example sets the batch size to 50. 38 | 39 | ## Why change the batch size? 40 | 41 | Using a smaller batch size can reduce memory usage and not leave users hanging for large queries. In otherwords, your application can be more responsive. 42 | -------------------------------------------------------------------------------- /archived/it/academy/tutorials_examples/terminology.md: -------------------------------------------------------------------------------- 1 | # Terminology 2 | 3 | - SubQuery Project (_where the magic happens_): A definition ([`@subql/cli`](https://www.npmjs.com/package/@subql/cli)) of how a SubQuery Node should traverse and aggregate a projects network and how the data should the transformed and stored to enable useful GraphQL queries 4 | - SubQuery Node (_where the work is done_): A package ([`@subql/node`](https://www.npmjs.com/package/@subql/node)) that will accept a SubQuery project definiton, and run a node that constantly indexes a connected network to a database 5 | - SubQuery Query Service (_where we get the data from_): A package ([`@subql/query`](https://www.npmjs.com/package/@subql/query)) that interacts with the GraphQL API of a deployed SubQuery node to query and view the indexed data 6 | - GraphQL (_how we query the data_): A query langage for APIs that is specifically suited for flexible graph based data - see [graphql.org](https://graphql.org/learn/) 7 | -------------------------------------------------------------------------------- /archived/it/miscellaneous/branding.md: -------------------------------------------------------------------------------- 1 | # Materiali per il branding 2 | 3 | **Tutte le caratteristiche del marchio di SubQuery sono proprietarie e noi prendiamo il nostro marchio molto seriamente.** 4 | 5 | Se si sceglie di utilizzare qualsiasi marchio, logo, design o altre caratteristiche del marchio, si prega di seguire attentamente le linee guida qui o di contattarci tramite i social media per chiarimenti. 6 | 7 | Se avete dei dubbi, chiedete pure! 8 | 9 | ## File Figma esportabile 10 | 11 | Il nostro file Figma ha una collezione completa di tutte le risorse del marchio (loghi, font, colori, immagini ecc.) per l'esportazione. 12 | 13 | [Figma - Risorse del marchio SubQuery](https://www.figma.com/file/AaCXaOcElrlbxq8fz39sJU/SubQuery-Brand-Resources?node-id=3%3A2) 14 | 15 | ## Pacchetto di risorse del marchio 16 | 17 | A smaller ZIP package of brand assets: [public_branding.zip](https://static.subquery.network/public_branding.zip). 18 | -------------------------------------------------------------------------------- /archived/it/run_publish/connect.md: -------------------------------------------------------------------------------- 1 | # Connect to your new project 2 | 3 | Once your deployment has succesfully completed and our nodes have indexed your data from the chain, you'll be able to connect to your project via the displayed Query endpoint. 4 | 5 | ![Progetto distribuito e sincronizzato](/assets/img/projects_deploy_sync.png) 6 | 7 | In alternativa, puoi cliccare sui tre puntini accanto al titolo del tuo progetto e visualizzarlo su SubQuery Explorer. There you can use the in browser playground to get started. 8 | 9 | ![Projects in SubQuery Explorer](/assets/img/projects_explorer.png) 10 | 11 | ::: tip Note Learn more about the [GraphQL Query language.](./graphql.md) ::: 12 | -------------------------------------------------------------------------------- /archived/it/run_publish/graphql.md: -------------------------------------------------------------------------------- 1 | # Per saperne di più su GraphQL 2 | 3 | Puoi seguire la [guida ufficiale di GraphQL qui](https://graphql.org/learn/) per saperne di più su GraphQL, come funziona e come usarlo: 4 | 5 | - There are libraries to help you implement GraphQL in [many different languages](https://graphql.org/code/). 6 | - Per un'esperienza di apprendimento approfondita con tutorial pratici, vedere [How to GraphQL](https://www.howtographql.com/). 7 | - Guarda il corso online gratuito, [Esplorare GraphQL: Un linguaggio di interrogazione per API](https://www.edx.org/course/exploring-graphql-a-query-language-for-apis). 8 | -------------------------------------------------------------------------------- /archived/it/run_publish/sandbox.md: -------------------------------------------------------------------------------- 1 | # The Sandbox 2 | 3 | Nel nostro scenario d'uso previsto, il nodo SubQuery è solitamente eseguito da un host fidato, e il codice del progetto SubQuery inviato dall'utente al nodo non è completamente affidabile. 4 | 5 | Alcuni codici maligni possono attaccare l'host o addirittura comprometterlo, e causare danni ai dati di altri progetti nello stesso host. Perciò, usiamo il meccanismo protetto della [VM2](https://www.npmjs.com/package/vm2) sandbox per ridurre i rischi. Questo: 6 | 7 | - Esegue il codice untrusted in modo sicuro in un contesto isolato e il codice maligno non accederà alla rete e al file system dell'host se non attraverso l'interfaccia esposta che abbiamo iniettato nella sandbox. 8 | 9 | - Chiama in modo sicuro i metodi e scambia dati e callback tra le sandbox. 10 | 11 | - È immune a molti metodi di attacco conosciuti. 12 | 13 | ## Restrizione 14 | 15 | - Per limitare l'accesso a certi moduli integrati, solo`assert`, `buffer`, `crypto`,`util` и `path` sono inseriti nella lista bianca. 16 | 17 | - Noi sosteniamo [Moduli di terze parti](../create/mapping/polkadot.md#third-party-libraries) scritto in **CommonJS** e **ibrido** biblioteche come `@polkadot/*` che usano ESM come predefinito. 18 | 19 | - Tutti i moduli che usano `HTTP` e `WebSocket` sono proibiti. 20 | -------------------------------------------------------------------------------- /archived/it/subquery_network/frontier-testnet.md: -------------------------------------------------------------------------------- 1 | # Frontier Testnet 2 | -------------------------------------------------------------------------------- /archived/ja/academy/academy.md: -------------------------------------------------------------------------------- 1 | # アカデミーへようこそ 2 | -------------------------------------------------------------------------------- /archived/ja/academy/tutorials_examples/batch-size.md: -------------------------------------------------------------------------------- 1 | # ブロックチェーンの取得したバッチサイズを変更するには？ 2 | 3 | ## ビデオのガイド 4 | 5 |
6 |
7 | 8 |
9 | 10 | ## はじめに 11 | 12 | 既定のバッチサイズは 100 ですが、追加コマンド `--batch-size=xx` で変更可能です。 13 | 14 | このフラグをコマンドラインに追加するか、Docker を使用している場合は、docker-compose.yml を以下に変更します。 15 | 16 | ```shell 17 | subquery-node: 18 | image: onfinality/subql-node:latest 19 | depends_on: 20 | - "postgres" 21 | restart: always 22 | environment: 23 | DB_USER: postgres 24 | DB_PASS: postgres 25 | DB_DATABASE: postgres 26 | DB_HOST: postgres 27 | DB_PORT: 5432 28 | volumes: 29 | - ./:/app 30 | command: 31 | - -f=/app 32 | - --local 33 | - --batch-size=50 34 | 35 | ``` 36 | 37 | この例では、バッチサイズを 50 に設定しています。 38 | 39 | ## なぜバッチサイズを変更するのですか？ 40 | 41 | よりバッチサイズを小さくすることで、メモリ使用量を削減し、大規模なクエリでもユーザーを待たせることがありません。 つまり、アプリケーションの応答性を高めることが出来ます。 42 | -------------------------------------------------------------------------------- /archived/ja/academy/tutorials_examples/debug-projects.md: -------------------------------------------------------------------------------- 1 | # SubQuery プロジェクトをデバッグするには？ 2 | 3 | ## ビデオのガイド 4 | 5 |
6 |
7 | 8 |
9 | 10 | ## はじめに 11 | 12 | コードのステップ実行、ブレークポイントの設定、変数の検査など、SubQuery プロジェクトのデバッグを行うには、Chrome の開発者ツールと組み合わせて、Node.js インスペクタを使用する必要があります。 13 | 14 | ## ノード監察 15 | 16 | ターミナル画面で次のコマンドを実行します。 17 | 18 | ```shell 19 | node --inspect-brk -f 20 | ``` 21 | 22 | 例： 23 | 24 | ```shell 25 | node --inspect-brk /usr/local/bin/subql-node -f ~/Code/subQuery/projects/subql-helloworld/ 26 | Debugger listening on ws://127.0.0.1:9229/56156753-c07d-4bbe-af2d-2c7ff4bcc5ad 27 | For help, see: https://nodejs.org/en/docs/inspector 28 | Debugger attached. 29 | ``` 30 | 31 | ## Chrome の開発ツール 32 | 33 | Chrome 開発ツールを開き、Sources タブに移動します。 緑色のアイコンをクリックすると、新しいウィンドウが開きます。 34 | 35 | ![ノード監察](/assets/img/node_inspect.png) 36 | 37 | ファイルシステムに移動し、プロジェクトフォルダをワークスペースに追加します。 次に dist > mappings フォルダを開き、デバッグしたいコードを選択します。 次に、標準的なデバッグツールと同様にコードをステップ実行します。 38 | 39 | ![プロジェクトのデバッグ](/assets/img/debugging_projects.png) 40 | -------------------------------------------------------------------------------- /archived/ja/academy/tutorials_examples/delete-projects.md: -------------------------------------------------------------------------------- 1 | # SubQuery プロジェクトを削除する方法は？ 2 | 3 | ## はじめに 4 | 5 | SubQuery Project の関連性を保ち、最新の状態に保つことが重要です。 テスト用に SubQuery Project にアップロードされたプロジェクトは、リソースの節約とコスト削減のために、後で削除することをお勧めします。 6 | 7 | Docker を使用するか、[SubQuery Managed Service](https://managedservice.subquery.network/) でプロジェクトをホストしてもらう以外に、インデクサノードを実行することもできます。 より多くの時間と労力を必要としますが、SubQuery がどのように機能するのか、その理解を深めることができます。 8 | 9 | ## ステージングスロットからプロジェクトを削除する 10 | 11 | ステージングスロットからプロジェクトを削除するには、プロジェクトのダッシュボードの詳細にあるステージングスロットセクションの 3 つの点をクリックし、削除を選択します。 12 | 13 | ![ステージングスロットからプロジェクトを削除する](/assets/img/delete_staging.png) 14 | 15 | ## ステージングスロットからプロジェクトを削除する 16 | 17 | 本番スロットからプロジェクトを削除するには、プロジェクト全体を削除する必要があります。 右上にある 3 つの点をクリックすると、プロジェクト全体の設定が表示されます。 「プロジェクトを削除」を選択します。 18 | 19 | ![本番スロットからプロジェクトを削除する](/assets/img/delete_production.png) 20 | -------------------------------------------------------------------------------- /archived/ja/academy/tutorials_examples/terminology.md: -------------------------------------------------------------------------------- 1 | # 用語集 2 | 3 | - SubQuery Project (_魔法が起きる場所_): SubQuery Node がどのようにプロジェクトネットワークを横断し、集約するか、また、有用な GraphQL クエリを可能にするためにデータをどのように変換し保存するかの定義([`@subql/cli`](https://www.npmjs.com/package/@subql/cli)) 4 | - SubQuery Node (_作業場所_): SubQuery プロジェクトの定義を受け取り、接続されたネットワークとデータベースを常時インデックスするノードを実行するパッケージ ([`@subql/node`](https://www.npmjs.com/package/@subql/node)) 5 | - SubQuery Service (_データ取得元_): 展開された SubQuery ノードの GraphQL API と対話し、インデックス化されたデータを照会・表示するパッケージ ([`@subql/query`](https://www.npmjs.com/package/@subql/query)) 6 | - GraphQL (_データへの問合せ_): 柔軟なグラフベースのデータに特化した API 用クエリ言語 - [graphql.org](https://graphql.org/learn/) を参照。 7 | -------------------------------------------------------------------------------- /archived/ja/miscellaneous/branding.md: -------------------------------------------------------------------------------- 1 | # ブランディング素材 2 | 3 | **SubQuery のブランド素材はすべて独自のものであり、私たちはブランドを極めて重要視しています。** 4 | 5 | 商標、ロゴ、デザイン、その他のブランドの特徴を使用する場合は、このガイドラインに注意深く従うか、ソーシャルメディアを通じて私たちに連絡して明確にしてください。 6 | 7 | 疑問がある場合は、お問い合わせください！ 8 | 9 | ## エクスポート可能な Figma ファイル 10 | 11 | 私たちの Figma ファイルには、エクスポート用のすべてのブランド資産（ロゴ、フォント、カラー、画像など）が完全に集められています。 12 | 13 | [Figma - SubQuery ブランドリソース](https://www.figma.com/file/AaCXaOcElrlbxq8fz39sJU/SubQuery-Brand-Resources?node-id=3%3A2) 14 | 15 | ## ブランド素材パッケージ 16 | 17 | A smaller ZIP package of brand assets: [public_branding.zip](https://static.subquery.network/public_branding.zip). 18 | -------------------------------------------------------------------------------- /archived/ja/miscellaneous/social_media.md: -------------------------------------------------------------------------------- 1 | # ソーシャル メディアリンク 2 | 3 | SubQuery は、多くのソーシャルメディアチャンネルを通じてフォロワーを維持し、コミュニケーションのアクティブなプロジェクトです。 4 | 5 | 私たちの目標は、常に忠実なコミュニティの声に耳を傾け、それに応えることです。 6 | 7 | ## 公式 SubQuery コミュニティ 8 | 9 | - [Linktree](https://linktr.ee/subquerynetwork) 10 | - [Discord](https://discord.com/invite/subquery)(専用のテクニカルサポートチャンネルを持つプライマリーコミュニティ) 11 | - [Medium](https://subquery.medium.com) (プライマリー・アナウンスチャネル) 12 | - [Twitter](https://twitter.com/subquerynetwork) 13 | - [Telegram](https://t.me/subquerynetwork) (アナウンスチャネルのみ) 14 | - [GitHub](https://github.com/subquery/) 15 | - [Matrix/Riot](https://matrix.to/#/#subquery:matrix.org) 16 | - [LinkedIn](https://www.linkedin.com/company/subquery) 17 | 18 | ## 非公式 SubQuery コミュニティ 19 | 20 | これらのコミュニティは SubQuery チームの管理下にはありませんが、アンバサダーがサポートしてくれる場合があります。 SubQuery はその中で起こることに**責任を負わない**ので、詐欺にはご注意ください。 21 | 22 | - [Telegram (中国語)](https://t.me/subquerychina) 23 | - [Telegram (ロシア語)](https://t.me/SubQuery_russia) 24 | - [Telegram (スペイン語)](https://t.me/SubQueryES) 25 | - [Telegram (タイ語)](https://t.me/subquerynetworkthai) 26 | - [Telegram (トルコ語)](https://t.me/subquery_TR) 27 | - [Telegram (ベトナム語)](https://t.me/subqueryvietnam) 28 | - [Telegram (ベトナム語アナウンス)](https://t.me/subqueryannvn) 29 | -------------------------------------------------------------------------------- /archived/ja/run_publish/connect.md: -------------------------------------------------------------------------------- 1 | # Connect to your new project 2 | 3 | Once your deployment has succesfully completed and our nodes have indexed your data from the chain, you'll be able to connect to your project via the displayed Query endpoint. 4 | 5 | ![プロジェクトを展開および同期する](/assets/img/projects_deploy_sync.png) 6 | 7 | または、プロジェクトのタイトルの横にある 3 つの点をクリックして、SubQuery Explorer で表示することもできます。 There you can use the in browser playground to get started. 8 | 9 | ![Projects in SubQuery Explorer](/assets/img/projects_explorer.png) 10 | 11 | ::: tip Note Learn more about the [GraphQL Query language.](./graphql.md) ::: 12 | -------------------------------------------------------------------------------- /archived/ja/run_publish/graphql.md: -------------------------------------------------------------------------------- 1 | # GraphQL について詳しく知る 2 | 3 | [公式 GraphQL ガイド](https://graphql.org/learn/) に従って、GraphQL の動作方法、使い方を学ぶことができます。 4 | 5 | - There are libraries to help you implement GraphQL in [many different languages](https://graphql.org/code/). 6 | - 実用的なチュートリアルを使用した詳細な学習体験については、 [GraphQL](https://www.howtographql.com/) を参照してください。 7 | - 無料オンラインコースをチェックしてください。 [GraphQL: API 用のクエリ言語](https://www.edx.org/course/exploring-graphql-a-query-language-for-apis)。 8 | -------------------------------------------------------------------------------- /archived/ja/run_publish/query.md: -------------------------------------------------------------------------------- 1 | # SubQuery Explorer でプロジェクトのクエリを実行する 2 | 3 | [SubQuery Explorer](https://explorer.subquery.network) is an online Managed Service that provides access to published SubQuery projects made by contributors in our community and managed by the SubQuery team. You can publish your own SubQuery projects to our explorer by following our guide to [Publish your SubQuery Project](../run_publish/publish.md). 4 | 5 | ![SubQuery Explorer](https://static.subquery.network/media/explorer/explorer-header.png) 6 | 7 | SubQuery Explorer は簡単に開始できます。 私たちはこれらの SubQuery ノードをオンラインでホスティングしており、誰もが無料でそれぞれクエリを実行することができます。 これらのマネージドノードは、SubQuery チームによってパフォーマンスレベルで監視および実行され、これにより本番アプリケーションの使用と依存が可能になります。 8 | 9 | ![SubQuery Project](https://static.subquery.network/media/explorer/explorer-project.png) 10 | 11 | SubQuery Explorer は、サンプルクエリを使用して利用可能なデータを検出するためのプレイグラウンドを提供していることにも注意してください。コードを実装することなくブラウザで直接クエリをテストすることができます。 さらに、開発者が世界中の Polkadot データを照会し、分析するための旅をよりよくサポートするために、ドキュメントにいくつかの小さな改良を加えました。 12 | 13 | On the top right of the playground, you'll find a _Docs_ button that will open a documentation draw. このドキュメントは自動的に生成され、クエリできるエンティティやメソッドを見つけるのに役立ちます。 14 | 15 | ::: tip Note Learn more about the [GraphQL Query language.](./graphql.md) ::: 16 | -------------------------------------------------------------------------------- /archived/ja/run_publish/sandbox.md: -------------------------------------------------------------------------------- 1 | # サンドボックス 2 | 3 | 想定された使用シナリオでは、SubQuery ノードは通常、信頼されたホストによって実行されます。 そして、ユーザーがノードに送信した SubQuery プロジェクトのコードは完全に信頼できるものではありません。 4 | 5 | 悪意のあるコードの中には、ホストを攻撃したり、ホストを危険にさらして、同じホストにある他のプロジェクトのデータに損害を与える可能性のあるものもあります。 したがって、 [VM2](https://www.npmjs.com/package/vm2) サンドボックスで保護されたメカニズムを使用してリスクを削減します。 下記に示します: 6 | 7 | - 信頼されていないコードを隔離されたコンテキストで安全に実行し、サンドボックスに注入したインタフェースを介さない限り、悪意のあるコードはホストのネットワークとファイルシステムにアクセスしません。 8 | 9 | - メソッドを安全に呼び出し、サンドボックス間で交換するデータやコールバックを行います。 10 | 11 | - 既知の多くの攻撃方法に対して免疫があります。 12 | 13 | ## 制限事項 14 | 15 | - 特定の組み込みモジュールへのアクセスを制限するため、`assert`, `buffer`, `crypto`, `util`, `path` のみをホワイトリストに登録しています。 16 | 17 | - **CommonJS** で書かれた[サードパーティモジュール](../create/mapping/polkadot.md#third-party-libraries) や、`@polkadot/*`のように ESM をデフォルトで使用する**hybrid** ライブラリに対応しています。 18 | 19 | - `HTTP` と `WebSocket` を使用するモジュールは禁止されています。 20 | -------------------------------------------------------------------------------- /archived/ja/subquery_network/frontier-testnet.md: -------------------------------------------------------------------------------- 1 | # Frontier Testnet 2 | -------------------------------------------------------------------------------- /archived/ko/academy/academy.md: -------------------------------------------------------------------------------- 1 | # Welcome to Academy 2 | -------------------------------------------------------------------------------- /archived/ko/academy/tutorials_examples/batch-size.md: -------------------------------------------------------------------------------- 1 | # 블록체인의 설치 뱃지 크기를 변경하려면 어떻게 해야 합니까? 2 | 3 | ## 비디오 가이드 4 | 5 |
6 |
7 | 8 |
9 | 10 | ## 소개 11 | 12 | 기본 뱃지 사이즈는 100 이지만, 이는 추가 명령어 `--batch-size=xx`를 사용하여 변경할 수 있습니다. 13 | 14 | 이는 추가 플래그로 명령줄에 대해 수행해야 합니다. 도커를 사용하는 경우에는 docker-compose.yml을 다음과 같이 변경합니다: 15 | 16 | ```shell 17 | subquery-node: 18 | image: onfinality/subql-node:latest 19 | depends_on: 20 | - "postgres" 21 | restart: always 22 | environment: 23 | DB_USER: postgres 24 | DB_PASS: postgres 25 | DB_DATABASE: postgres 26 | DB_HOST: postgres 27 | DB_PORT: 5432 28 | volumes: 29 | - ./:/app 30 | command: 31 | - -f=/app 32 | - --local 33 | - --batch-size=50 34 | 35 | ``` 36 | 37 | 본 예에서는 배치 사이즈를 50으로 설정합니다. 38 | 39 | ## 왜 뱃지 크기를 변경하나요? 40 | 41 | 배치 크기를 작게 하면 메모리 사용량이 줄어들어 사용자가 큰 query를 받지 않게 됩니다. 즉, 애플리케이션의 응답성이 향상됩니다. 42 | -------------------------------------------------------------------------------- /archived/ko/academy/tutorials_examples/debug-projects.md: -------------------------------------------------------------------------------- 1 | # SubQuery 프로젝트 디버깅 방법 2 | 3 | ## 비디오 가이드 4 | 5 |
6 |
7 | 8 |
9 | 10 | ## 소개 11 | 12 | 단계별 코드 실행, 중단점 설정, 변수 검사와 같은 SubQuery 프로젝트를 디버그하려면, Chrome 개발자 도구와 함께 Node.js 검사기를 사용해야 합니다. 13 | 14 | ## 노드 검사기 15 | 16 | 터미널 화면에서 다음 명령어를 실행합니다. 17 | 18 | ```shell 19 | node --inspect-brk -f 20 | ``` 21 | 22 | 예시 23 | 24 | ```shell 25 | node --inspect-brk /usr/local/bin/subql-node -f ~/Code/subQuery/projects/subql-helloworld/ 26 | ws://127.0.0.1:9229/56156753-c07d-4bbe-af2d-2c7ff4bcc5ad에서 수신하는 디버거 27 | 도움이 필요하면 https://nodejs.org/en/docs/inspector를 참조하세요. 28 | ``` 29 | 30 | ## Chrome 개발도구 31 | 32 | Chrome DevTools를 열고 소스 탭으로 이동합니다. 녹색 아이콘을 클릭하면 새 창이 열립니다. 33 | 34 | ![노드 점검](/assets/img/node_inspect.png) 35 | 36 | 파일 시스템으로 이동하여 프로젝트 폴더를 작업 공간에 추가하십시오. 그런 다음 dist > mappings 폴더를 열고 디버그할 코드를 선택합니다. 이후 표준 디버깅 도구와 마찬가지로 코드를 단계별로 실행합니다. 37 | 38 | ![디버깅 프로젝트](/assets/img/debugging_projects.png) 39 | -------------------------------------------------------------------------------- /archived/ko/academy/tutorials_examples/delete-projects.md: -------------------------------------------------------------------------------- 1 | # 서브쿼리 프로젝트 삭제하기 2 | 3 | ## 소개 4 | 5 | 서브쿼리 프로젝트 내에서 프로젝트를 최신의 상태로 유지하는 것이 중요합니다. 서브쿼리 프로젝트에 업로드한 시험용 프로젝트는 자원 유지 및 비용 절감을 위해 시험 이후에는 삭제하는 것을 권장합니다. 6 | 7 | Docker를 사용하거나 [서브쿼리 프로젝트](https://managedservice.subquery.network/) 상에서 프로젝트를 호스팅하는 것 외에 인덱서 노드를 실행하는 것은 또 다른 옵션입니다. 이는 보다 많은 시간과 노력을 필요로 하지만, 서브쿼리의 작동에 대해 이해하는데 큰 도움이 될 것입니다. 8 | 9 | ## 스테이징 슬롯의 프로젝트 삭제하기 10 | 11 | 스테이징 슬롯의 프로젝트를 삭제하려면 프로젝트 대시보드 페이지의 세부 정보 내 스테이징 슬롯 섹션에 있는 점 3개를 클릭하고 삭제를 선택합니다. 12 | 13 | ![스테이징 슬롯의 프로젝트 삭제하기](/assets/img/delete_staging.png) 14 | 15 | ## 가동 슬롯의 프로젝트 삭제하기 16 | 17 | 가동 슬롯의 프로젝트를 삭제하려면 해당 프로젝트 전체를 삭제해야 합니다. 먼저 오른쪽 상단부에 위치한 점 3개를 클릭합니다. 이후 "프로젝트 삭제"를 선택합니다. 18 | 19 | ![가동 슬롯의 프로젝트 삭제하기](/assets/img/delete_production.png) 20 | -------------------------------------------------------------------------------- /archived/ko/academy/tutorials_examples/terminology.md: -------------------------------------------------------------------------------- 1 | # 용어 2 | 3 | - SubQuery 프로젝트(_마법이 일어나는 곳_): SubQuery 노드가 프로젝트 네트워크를 순회하고 집계하는 방법과 데이터가 변환되는 방법에 대한 정의([`@subql/cli`](https://www.npmjs.com/package/@subql/cli)) 유용한 GraphQL 쿼리를 활성화하기 위해 저장 4 | - SubQuery 노드(_작업이 완료된 곳_): SubQuery 프로젝트 정의를 수락하고 연결된 네트워크를 지속적으로 인덱싱하는 노드를 실행하는 패키지([`@subql/node`](https://www.npmjs.com/package/@subql/node)) 데이터베이스에 5 | - SubQuery 쿼리 서비스(_데이터를 가져오는 위치_): 배포된 SubQuery 노드의 GraphQL API와 상호 작용하여 쿼리하고 확인하는 패키지([`@subql/query`](https://www.npmjs.com/package/@subql/query)) 인덱싱된 데이터 6 | - GraphQL (_how we query the data_): 유연한 그래프 기반 데이터에 특히 적합한 API 쿼리 언어 - [graphql.org](https://graphql.org/learn/)를 참조 7 | -------------------------------------------------------------------------------- /archived/ko/miscellaneous/branding.md: -------------------------------------------------------------------------------- 1 | # 브랜딩 자료 2 | 3 | **SubQuery의 브랜드 관련된 모든 것들은 상표 등록이 되어 있으며 우리는 우리 브랜드를 매우 중요하게 생각합니다.** 4 | 5 | 만약 상표, 로고, 디자인 또는 기타 브랜드 기능을 사용하고자 한다면, 지침을 주의 깊게 따르거나 소셜 미디어를 통해 당사에 연락하시길 바랍니다. 6 | 7 | 의문점이 있다면, 물어보십시오! 8 | 9 | ## 내보내기 가능한 Figma 파일 10 | 11 | 당사의 Figma 파일에는 내보낼 수 있는 브랜드의 모든 자산(로고, 글꼴, 색상, 이미지 등)을 모아놨습니다. 12 | 13 | [Figma - SubQuery 브랜드 자료들](https://www.figma.com/file/AaCXaOcElrlbxq8fz39sJU/SubQuery-Brand-Resources?node-id=3%3A2) 14 | 15 | ## 브랜드 자산 패키지 16 | 17 | A smaller ZIP package of brand assets: [public_branding.zip](https://static.subquery.network/public_branding.zip). 18 | -------------------------------------------------------------------------------- /archived/ko/miscellaneous/social_media.md: -------------------------------------------------------------------------------- 1 | # 소셜 미디어 링크 2 | 3 | SubQuery는 다양한 소셜 미디어 채널을 통해 팔로워들과 소통하고 유지하는 활발한 프로젝트입니다. 4 | 5 | 항상 커뮤니티에 귀를 기울이고 참여하는 것을 목표로 하며, 커뮤니티에 참여하여 아이디어 또는 질문을 보내주세요! 6 | 7 | ## 공식 SubQuery 커뮤니티 8 | 9 | - [Linktree](https://linktr.ee/subquerynetwork) 10 | - [Discord](https://discord.com/invite/subquery) (집중 기술 지원 채널이 있는 기본 커뮤니티) 11 | - [Medium](https://subquery.medium.com) (기본 공지 채널) 12 | - [Twitter](https://twitter.com/subquerynetwork) 13 | - [Telegram](https://t.me/subquerynetwork) (공식 발표 채널만) 14 | - [GitHub](https://github.com/subquery/) 15 | - [Matrix/Riot](https://matrix.to/#/#subquery:matrix.org) 16 | - [LinkedIn](https://www.linkedin.com/company/subquery) 17 | 18 | ## 비공식 SubQuery 커뮤니티 19 | 20 | 이러한 커뮤니티는 SubQuery 팀에서 관여하지 않지만, 우리의 앰버서더들이 지원할 수 있습니다. SubQuery는 그 안에서 일어나는 일에 대해 책임이 **없으므로** 스캠에 주의하십시오. 21 | 22 | - [Telegram (중국)](https://t.me/subquerychina) 23 | - [Telegram (러시아)](https://t.me/SubQuery_russia) 24 | - [Telegram (스페인)](https://t.me/SubQueryES) 25 | - [Telegram (태국)](https://t.me/subquerynetworkthai) 26 | - [Telegram (터키)](https://t.me/subquery_TR) 27 | - [Telegram (베트남)](https://t.me/subqueryvietnam) 28 | - [Telegram (베트남 공지)](https://t.me/subqueryannvn) 29 | -------------------------------------------------------------------------------- /archived/ko/run_publish/connect.md: -------------------------------------------------------------------------------- 1 | # Connect to your new project 2 | 3 | Once your deployment has succesfully completed and our nodes have indexed your data from the chain, you'll be able to connect to your project via the displayed Query endpoint. 4 | 5 | ![배포 및 동기화된 프로젝트](/assets/img/projects_deploy_sync.png) 6 | 7 | 프로젝트 제목 옆에 있는 3개의 점을 클릭하여 SubQuery 탐색기로 표시할 수도 있습니다. There you can use the in browser playground to get started. 8 | 9 | ![Projects in SubQuery Explorer](/assets/img/projects_explorer.png) 10 | 11 | ::: tip Note Learn more about the [GraphQL Query language.](./graphql.md) ::: 12 | -------------------------------------------------------------------------------- /archived/ko/run_publish/graphql.md: -------------------------------------------------------------------------------- 1 | # GraphQL에 대해 더 알아보기 2 | 3 | [official GraphQL guide here](https://graphql.org/learn/)에 따라 GraphQL의 상세, 동작 방법 및 사용 방법을 확인할 수 있습니다. 4 | 5 | - There are libraries to help you implement GraphQL in [many different languages](https://graphql.org/code/). 6 | - 실제 튜토리얼을 사용한 자세한 학습 경험은 [How to GraphQL](https://www.howtographql.com/)을 참조해 주세요. 7 | - 무료 온라인 코스 [Exploring GraphQL: A Query Language for APIs](https://www.edx.org/course/exploring-graphql-a-query-language-for-apis)을 확인하시기 바랍니다. 8 | -------------------------------------------------------------------------------- /archived/ko/run_publish/query.md: -------------------------------------------------------------------------------- 1 | # SubQuery Explorer에서 여러분의 프로젝트를 Query하세요 2 | 3 | [SubQuery Explorer](https://explorer.subquery.network) is an online Managed Service that provides access to published SubQuery projects made by contributors in our community and managed by the SubQuery team. You can publish your own SubQuery projects to our explorer by following our guide to [Publish your SubQuery Project](../run_publish/publish.md). 4 | 5 | ![SubQuery Explorer](https://static.subquery.network/media/explorer/explorer-header.png) 6 | 7 | SubQuery Explorer를 사용하면 쉽게 시작할 수 있습니다. 저희는 이러한 SubQuery 프로젝트를 온라인으로 호스팅하고 있으며, 누구나 무료로 Query할 수 있습니다. 이러한 관리대상 노드는 SubQuery 팀에 의해 감시 및 실행되며, 실제 가동 어플리케이션이 이러한 노드를 사용 및 의존할 수 있도록 합니다. 8 | 9 | ![SubQuery 프로젝트](https://static.subquery.network/media/explorer/explorer-project.png) 10 | 11 | 또한 SubQuery Explorer는 샘플 Query에서 사용 가능한 데이터를 검색하기 위한 플레이그라운드를 제공합니다. 코드를 구현하지 않아도 브라우저에서 직접 Query를 테스트할 수 있습니다. 또한 개발자들이 전 세계의 Polkadot 데이터를 더 잘 조회하고 분석하는 과정에서 더 나은 지원을 제공하기 위해 문서를 약간 개선했습니다. 12 | 13 | On the top right of the playground, you'll find a _Docs_ button that will open a documentation draw. 이 문서는 자동으로 생성되어 조회할 수 있는 Entity와 Method를 찾는데 도움이 됩니다. 14 | 15 | ::: tip Note Learn more about the [GraphQL Query language.](./graphql.md) ::: 16 | -------------------------------------------------------------------------------- /archived/ko/run_publish/sandbox.md: -------------------------------------------------------------------------------- 1 | # 샌드박스 2 | 3 | 되는 사용 시나리오에서 SubQuery 노드는 일반적으로 신뢰할 수 있는 호스트에 의해 실행되며, 사용자가 노드에 제출한 SubQuery 프로젝트의 코드는 완전히 신뢰할 수 있는 것은 아닙니다. 4 | 5 | 일부 악의적인 코드는 호스트를 공격하거나 침해할 수 있으며 같은 호스트 내 다른 프로젝트의 데이터에 손상을 줄 수 있습니다. 따라서, 위험을 줄이기 위해 [VM2](https://www.npmjs.com/package/vm2) 샌드박스 보안 메커니즘을 사용합니다. 이는: 6 | 7 | - 신뢰할 수 없는 코드를 격리된 콘텍스트에서 안전하게 실행하고 악의적인 코드는 공개된 인터페이스를 통해 샌드박스에 주입하지 않는 한 호스트의 네트워크와 파일 시스템에 접근하지 않습니다. 8 | 9 | - 샌드박스 간에 메소드를 안전하게 호출하여 데이터와 콜백을 교환합니다. 10 | 11 | - 많은 기존의 공격방법에 면역이 있습니다. 12 | 13 | ## 제한 사항 14 | 15 | - 특정 임베디드 모듈에 대한 액세스를 제한하기 위해 `assert`, `buffer`, `crypto`,`util` 와 `path` 만이 화이트 리스트에 표시됩니다. 16 | 17 | - 저희는 ESM 를 디폴트로서 사용하는**CommonJS** 과 **hybrid**등의 라이브러리, `@polkadot/*` 와 같은 기술된 [3rd party modules](../create/mapping/polkadot.md#third-party-libraries) 을 지원 합니다. 18 | 19 | - `HTTP` 을 사용하는 임의의 모듈 및 `WebSocket` 은 금지되어 있습니다. 20 | -------------------------------------------------------------------------------- /archived/ko/subquery_network/frontier-testnet.md: -------------------------------------------------------------------------------- 1 | # Frontier Testnet 2 | -------------------------------------------------------------------------------- /archived/ru/academy/academy.md: -------------------------------------------------------------------------------- 1 | # Добро пожаловать в Академию 2 | -------------------------------------------------------------------------------- /archived/ru/academy/tutorials_examples/delete-projects.md: -------------------------------------------------------------------------------- 1 | # Как удалить проект SubQuery? 2 | 3 | ## Вступление 4 | 5 | Очень важно поддерживать проекты и актуальность ваших проектов в SubQuery Project. Для любых проектов, загруженных в SubQuery Project для тестирования, рекомендуется впоследствии удалить их, чтобы сэкономить ресурсы и сократить расходы. 6 | 7 | Запуск узла индексатора это еще один вариант помимо использования Docker или размещения проекта в [ SubQuery Projects ](https://managedservice.subquery.network/). Это требует больше времени и усилий, но улучшит ваше понимание того, каким образом работает SubQuery. 8 | 9 | ## Удаление проекта из стейджинг слота 10 | 11 | Чтобы удалить проект из стейджинг слота, нажмите на 3 точки в разделе промежуточного слота в сведениях о развертывании на странице подробных сведений о проекте и выберите «Удалить». 12 | 13 | ![Удаление проекта из промежуточного слота](/assets/img/delete_staging.png) 14 | 15 | ## Удаление проекта из производственного слота 16 | 17 | Чтобы удалить проект из производственного слота, вам придется удалить весь проект. Перейдите в верхний правый угол и нажмите на 3 точки, которые являются настройками для проекта. Затем выберите «Удалить проект». 18 | 19 | ![Удаление проекта из производственного слота](/assets/img/delete_production.png) 20 | -------------------------------------------------------------------------------- /archived/ru/academy/tutorials_examples/terminology.md: -------------------------------------------------------------------------------- 1 | # Терминология 2 | 3 | - SubQuery Project (_ где происходит волшебство _): определение ([`@ subql / cli`](https://www.npmjs.com/package/@subql/cli)) того, как SubQuery Node должен проходить и агрегировать сеть проектов и как данные должны преобразовываться и храниться для включения полезных запросов GraphQL 4 | - SubQuery Node (_ где выполняется работа _): пакет ([`@ subql / node`](https://www.npmjs.com/package/@subql/node)), который примет определение SubQuery project и запустит ноду, которая постоянно индексирует подключенную сеть к базе данных 5 | - Служба запросов SubQuery (_ откуда мы получаем данные _): пакет ([`@ subql / query`](https://www.npmjs.com/package/@subql/query)), который взаимодействует с GraphQL API запущенной ноды SubQuery для запроса и просмотра индексированных данных 6 | - GraphQL (_ как мы запрашиваем данные _): язык запросов для API, который специально подходит для гибких данных на основе графиков - смотрите [ graphql.org ](https://graphql.org/learn/) 7 | -------------------------------------------------------------------------------- /archived/ru/miscellaneous/branding.md: -------------------------------------------------------------------------------- 1 | # Брендинговые материалы 2 | 3 | **Все элементы бренда SubQuery являются собственностью, и мы очень серьезно относимся к нашему бренду.** 4 | 5 | Если вы решили использовать любые торговые марки, логотипы, дизайны или другие функции бренда, внимательно следуйте руководящим принципам здесь или обращайтесь к нам через социальные сети для уточнения. 6 | 7 | Если у вас есть сомнения, спросите! 8 | 9 | ## Экспортируемый Figma File 10 | 11 | Наш Figma File имеет полную коллекцию всех активов бренда (логотипы, шрифты, цвета, изображения и т.д.) 12 | 13 | [Figma - ресурсы бренда SubQuery](https://www.figma.com/file/AaCXaOcElrlbxq8fz39sJU/SubQuery-Brand-Resources?node-id=3%3A2) 14 | 15 | ## Пакет брендовых активов 16 | 17 | Уменьшенный ZIP-пакет активов бренда: [public_branding.zip](https://static.subquery.network/public_branding.zip). 18 | -------------------------------------------------------------------------------- /archived/ru/run_publish/connect.md: -------------------------------------------------------------------------------- 1 | # Подключитесь к вашему новому проекту 2 | 3 | После успешного завершения развертывания, когда наши узлы проиндексируют ваши данные из цепочки, вы сможете подключиться к своему проекту через отображаемую конечную точку Query. 4 | 5 | ![Проект будет развернут и синхронизирован](/assets/img/projects_deploy_sync.png) 6 | 7 | Кроме того, вы можете щелкнуть три точки рядом с названием вашего проекта и просмотреть его в SubQuery Explorer. Там вы можете использовать игровую площадку в браузере, чтобы начать работу. 8 | 9 | ![Проекты в SubQuery Explorer](/assets/img/projects_explorer.png) 10 | 11 | ::: Информация Примечание Узнайте больше о языке запросов [GraphQL.](./graphql.md) ::: 12 | -------------------------------------------------------------------------------- /archived/ru/run_publish/graphql.md: -------------------------------------------------------------------------------- 1 | # Узнать больше о GraphQL 2 | 3 | Вы можете следовать [ официальному руководству по GraphQL здесь ](https://graphql.org/learn/), чтобы узнать больше о GraphQL, как он работает и как его использовать: 4 | 5 | - Существуют библиотеки, которые помогут вам реализовать GraphQL на [многих различных языках](https://graphql.org/code/). 6 | - Для более тщательного изучения с практическими руководствами см. [ How to GraphQL ](https://www.howtographql.com/). 7 | - Ознакомьтесь с бесплатным онлайн-курсом [ Изучение GraphQL: язык запросов для API ](https://www.edx.org/course/exploring-graphql-a-query-language-for-apis). 8 | -------------------------------------------------------------------------------- /archived/ru/run_publish/sandbox.md: -------------------------------------------------------------------------------- 1 | # The Sandbox 2 | 3 | В нашем предполагаемом сценарии использования нода SubQuery обычно запускается доверенным хостом, и код проекта SubQuery, отправленный пользователем ноде, не является полностью надежным. 4 | 5 | Некоторый вредоносный код может атаковать хост или даже скомпрометировать его, а также нанести ущерб данным других проектов на том же хосте. Поэтому мы используем защищенный механизм Sandbox [VM2](https://www.npmjs.com/package/vm2) для снижения рисков. Это позволяет: 6 | 7 | - Безопасно запускать ненадежный код в изолированной среде, и вредоносный код не получит доступа к сети и файловой системе хоста, кроме как через открытый интерфейс, который мы внедрили в изолированную среду. 8 | 9 | - Безопасно вызывать методы и обмениваться данными и обратными вызовами между изолированными средами. 10 | 11 | - Обладать иммунитетом ко многим известным методам атаки. 12 | 13 | ## Ограничения 14 | 15 | - Ограниченный доступ к определенным встроенным модулям, только`assert`, `buffer`, `crypto`,`util` и `path` занесены в белый список. 16 | 17 | - Мы поддерживаем [сторонние модули](../create/mapping/polkadot.md#third-party-libraries) написанные на **CommonJS** и **hybrid** библиотеки, такие как `@polkadot/*`, которые используют ESM по умолчанию. 18 | 19 | - Любые модули, использующие `HTTP` и `WebSocket`, запрещены. 20 | -------------------------------------------------------------------------------- /archived/ru/subquery_network/frontier-testnet.md: -------------------------------------------------------------------------------- 1 | # Тестнет Frontier 2 | -------------------------------------------------------------------------------- /archived/th/academy/academy.md: -------------------------------------------------------------------------------- 1 | # ยินดีต้อนรับเข้าสู่โรงเรียน 2 | -------------------------------------------------------------------------------- /archived/th/academy/tutorials_examples/batch-size.md: -------------------------------------------------------------------------------- 1 | # จะเปลี่ยน batch size การ fetch บล็อกเชนได้อย่างไร? 2 | 3 | ## คู่มือวิดีโอ 4 | 5 |
6 |
7 | 8 |
9 | 10 | ## บทนำ 11 | 12 | batch size เริ่มต้นคือ 100 แต่สามารถเปลี่ยนแปลงได้โดยใช้คำสั่งเพิ่มเติม `--batch-size=xx` 13 | 14 | คุณต้องใช้สิ่งนี้กับ command line ซึ่งเป็น flag เพิ่มเติม หรือหากคุณใช้ Docker ให้แก้ไขไฟล์ docker-compose.yml ด้วย: 15 | 16 | ```shell 17 | subquery-node: 18 | image: onfinality/subql-node:latest 19 | depends_on: 20 | - "postgres" 21 | restart: always 22 | environment: 23 | DB_USER: postgres 24 | DB_PASS: postgres 25 | DB_DATABASE: postgres 26 | DB_HOST: postgres 27 | DB_PORT: 5432 28 | volumes: 29 | - ./:/app 30 | command: 31 | - -f=/app 32 | - --local 33 | - --batch-size=50 34 | 35 | ``` 36 | 37 | ตัวอย่างนี้กำหนด batch size เป็น 50 38 | 39 | ## ทำไมต้องเปลี่ยน batch size? 40 | 41 | การใช้ batch size ที่เล็กลงสามารถลดการใช้หน่วยความจำได้ และไม่ปล่อยให้ผู้ใช้ต้องค้างกับการสืบค้นข้อมูลจำนวนมาก กล่าวอีกนัยหนึ่งคือ แอปพลิเคชันของคุณสามารถตอบสนองได้มากขึ้น 42 | -------------------------------------------------------------------------------- /archived/th/academy/tutorials_examples/delete-projects.md: -------------------------------------------------------------------------------- 1 | # การลบโปรเจกต์บน SubQuery ทำได้อย่างไร? 2 | 3 | ## บทนำ 4 | 5 | เป็นเรื่องสำคัญที่คุณจะทำให้โปรเจกต์ต่างๆของคุณใน SubQuery Project ยังคงมีข้อมูลที่เกี่ยวข้องและอัปเดตล่าสุดอยู่เสมอ สำหรับโปรเจกต์ต่างๆ ที่คุณที่อัพโหลดไปยัง SubQuery Project เพื่อการทดสอบนั้น เราแนะนำให้ลบมันทิ้งภายหลัง เพื่อรักษาทรัพยากร และ ประหยัดต้นทุน 6 | 7 | การรัน indexer node เป็นอีกทางเลือกหนึ่ง นอกเหนือจากการใช้ Docker หรือการที่มีโปรเจคที่โฮสต์ให้คุณที่ [SubQuery Managed Service](https://managedservice.subquery.network/) แม้จะต้องต้องใช้เวลาและความพยายามมากกว่า แต่การรันโหนดนี้จะช่วยให้คุณเข้าใจการทำงานของ SubQuery ในเบื้องลึกมากขึ้น 8 | 9 | ## การลบโปรเจคออกจากสล็อต staging 10 | 11 | การลบโปรเจคจากสล็อต staging นั้น ให้กดไปที่จุดสามจุดในส่วนของสล็อต staging ซึ่งอยู่ภายในรายละเอียดของการปรับใช้แดชบอร์ดของโปรเจคคุณ จากนั้นให้เลือก delete 12 | 13 | ![การลบโปรเจคออกจากสล็อต staging](/assets/img/delete_staging.png) 14 | 15 | ## การลบโปรเจคจากสล็อต production 16 | 17 | ในการลบโปรเจคจากสล็อต production นั้น คุณจำเป็นจะต้องลบโปรเจคทั้งหมด โดยไปที่มุมขวาบนและคลิกบนจุดสามจุด ซึ่งเป็นส่วนของการตั้งค่าของทั้งโปรเจค จากนั้นเลือก "Delete Project" 18 | 19 | ![การลบโปรเจคจากสล็อต production](/assets/img/delete_production.png) 20 | -------------------------------------------------------------------------------- /archived/th/academy/tutorials_examples/terminology.md: -------------------------------------------------------------------------------- 1 | # การจำกัดความ 2 | 3 | - โปรเจค SubQuery (_ที่ที่เวทมนตร์เกิดขึ้น_): คำจำกัดความ ([`@subql/cli`](https://www.npmjs.com/package/@subql/cli)) ของวิธีที่ SubQuery Node ควรสำรวจและรวมเครือข่ายของโปรเจกต์ และวิธีที่ข้อมูลควรแปลง และเก็บไว้เพื่อเปิดใช้งานการสืบค้น GraphQL ที่เป็นประโยชน์ 4 | - SubQuery Node (_ที่ซึ่งงานจะถูกทำให้เสร็จสิ้น_): แพ็คเกจ ([`@subql/node`](https://www.npmjs.com/package/@subql/node)) ที่เป็นไปตามคำจำกัดความของโปรเจกต์ SubQuery และมีการรันโหนดซึ่งมีการจัดทำดัชนีของเครือข่ายที่เชื่อมต่อกับฐานข้อมูลอย่างต่อเนื่อง 5 | - SubQuery Query Service (_ที่ซึ่งเราไปเอาข้อมูลมา_): แพ็คเกจ ([`@subql/query`](https://www.npmjs.com/package/@subql/query)) ที่สื่อสารกับ GraphQL API ของโหนด SubQuery ที่ใช้เพื่อสืบค้นและดูข้อมูลในดัชนี 6 | - GraphQL (_วิธีที่เราสืบค้นข้อมูล_): ภาษาที่ใช้สืบค้นสำหรับ API ซึ่งเหมาะสมและเจาะจงกับข้อมูลตามกราฟที่มีความยืดหยุ่น - ดูที่ [graphql.org](https://graphql.org/learn/) 7 | -------------------------------------------------------------------------------- /archived/th/miscellaneous/branding.md: -------------------------------------------------------------------------------- 1 | # สิ่งต่าง ๆ สำหรับการทำแบรนด์ของ SubQuery 2 | 3 | **โลโก้หรือเครื่องหมายต่างๆ ของ SubQuery ทั้งหมดเป็นกรรมสิทธิ์ของเรา และเราให้ความสำคัญกับแบรนด์ของเราเป็นอย่างมาก** 4 | 5 | หากคุณเลือกใช้เครื่องหมายการค้า, โลโก้, งานดีไซน์, หรือคุณลักษณะอื่นๆ ของแบรนด์ โปรดปฏิบัติตามหลักเกณฑ์นี้อย่างละเอียด หรือติดต่อเราผ่านโซเชียลมีเดียเพื่อสอบถามเพิ่มเติม 6 | 7 | หากมีข้อสงสัย โปรดอย่าลังเลที่จะติดต่อเราเพื่อสอบถาม! 8 | 9 | ## ไฟล์ Figma ที่สามารถ Export ได้ 10 | 11 | ไฟล์ Figma ของเรามีคอลเลกชั่นเต็มรูปแบบของทรัพยากรของแบรนด์ทั้งหมด (โลโก้, ฟอนต์, สี, ภาพ, ฯลฯ) สำหรับการ Export 12 | 13 | [Figma - SubQuery Brand Resources (แหล่งรวมสิ่งต่าง ๆ เกี่ยวกับแบรนด์ของ SubQuery)](https://www.figma.com/file/AaCXaOcElrlbxq8fz39sJU/SubQuery-Brand-Resources?node-id=3%3A2) 14 | 15 | ## แพ็คเกจทรัพยากรแบรนด์ 16 | 17 | A smaller ZIP package of brand assets: [public_branding.zip](https://static.subquery.network/public_branding.zip). 18 | -------------------------------------------------------------------------------- /archived/th/run_publish/connect.md: -------------------------------------------------------------------------------- 1 | # Connect to your new project 2 | 3 | Once your deployment has succesfully completed and our nodes have indexed your data from the chain, you'll be able to connect to your project via the displayed Query endpoint. 4 | 5 | ![โปรเจกต์ที่กำลัง deploy และ sync](/assets/img/projects_deploy_sync.png) 6 | 7 | หรือคุณสามารถคลิกที่จุดสามจุดถัดจากชื่อโปรเจกต์ของคุณ และดูบน SubQuery Explorer There you can use the in browser playground to get started. 8 | 9 | ![Projects in SubQuery Explorer](/assets/img/projects_explorer.png) 10 | 11 | ::: tip Note Learn more about the [GraphQL Query language.](./graphql.md) ::: 12 | -------------------------------------------------------------------------------- /archived/th/run_publish/graphql.md: -------------------------------------------------------------------------------- 1 | # เรียนรู้เพิ่มเติมเกี่ยวกับ GraphQL 2 | 3 | คุณสามารถทำตาม [คู่มือ GraphQL อย่างเป็นทางการที่นี่](https://graphql.org/learn/) เพื่อเรียนรู้เพิ่มเติมเกี่ยวกับ GraphQL วิธีการทำงาน และวิธีใช้งาน: 4 | 5 | - There are libraries to help you implement GraphQL in [many different languages](https://graphql.org/code/). 6 | - สำหรับประสบการณ์การเรียนรู้เชิงลึกพร้อมบทช่วยสอนเชิงปฏิบัติ โปรดดูที่ [วิธีสร้าง GraphQL](https://www.howtographql.com/) 7 | - ดูหลักสูตรออนไลน์ฟรี [การสำรวจ GraphQL: ภาษาการสืบค้นสำหรับ API](https://www.edx.org/course/exploring-graphql-a-query-language-for-apis) 8 | -------------------------------------------------------------------------------- /archived/th/run_publish/sandbox.md: -------------------------------------------------------------------------------- 1 | # The Sandbox 2 | 3 | ในสถานการณ์การใช้งานที่เราได้คิดไว้คือ โหนดของ SubQuery จะถูกรันโดยโฮสต์ที่เชื่อถือได้ ในขณะที่โค้ดของโปรเจกต์ SubQuery ที่ผู้ใช้ส่งไปยังโหนดนั้น ไม่น่าเชื่อถือไปทั้งหมด 4 | 5 | โค้ดที่เป็นอันตรายบางตัวมีแนวโน้มที่จะโจมตีโฮสต์หรืออาจทำอันตรายโฮสต์ แล้วทำให้ข้อมูลของโปรเจกต์อื่นๆ ในโฮสต์เดียวกันเสียหาย ดังนั้นเราจึงใช้กลไกการรักษาความปลอดภัยอย่าง sandbox [VM2](https://www.npmjs.com/package/vm2) เพื่อลดความเสี่ยงนี้ โดย: 6 | 7 | - รันโค้ดที่ไม่น่าเชื่อถือในบริบทที่แยกออกมาเพื่อความปลอดภัย และโค้ดที่เป็นอันตรายนั้นจะเข้าถึงเครือข่ายและระบบไฟล์ของโฮสต์ไม่ได้ เว้นแต่เราจะใส่อินเทอร์เฟซที่เปิดเผยลงใน sandbox 8 | 9 | - เรียกใช้ method และแลกเปลี่ยนข้อมูลและการเรียกกลับระหว่าง sandboxes ต่าง ๆ อย่างปลอดภัย 10 | 11 | - มีความปลอดภัยต่อวิธีการโจมตีที่เป็น known methods มากมาย 12 | 13 | ## ข้อจำกัด 14 | 15 | - มีเพียง `assert`, `buffer`, `crypto`,`util` และ `path` เท่านั้นที่อยู่ในรายการที่อนุญาตพิเศษ เพื่อจำกัดการเข้าถึงโมดูลแบบบิวท์อินบางโมดูล 16 | 17 | - เราสนับสนุน [โมดูลจากแหล่งอื่น](../create/mapping/polkadot.md#third-party-libraries) ที่เขียนในไลบรารี **CommonJS** และ **ไฮบริด** เช่น `@polkadot/*` ที่ใช้ ESM เป็นค่าเริ่มต้น 18 | 19 | - โมดูลใดๆ ที่ใช้ `HTTP` และ `WebSocket` จะถูกห้ามใช้ 20 | -------------------------------------------------------------------------------- /archived/th/subquery_network/frontier-testnet.md: -------------------------------------------------------------------------------- 1 | # Frontier Testnet 2 | -------------------------------------------------------------------------------- /archived/tr/academy/academy.md: -------------------------------------------------------------------------------- 1 | # Akademi'ye Hoş Geldiniz 2 | -------------------------------------------------------------------------------- /archived/tr/academy/tutorials_examples/batch-size.md: -------------------------------------------------------------------------------- 1 | # Blockchain getirme toplu iş boyutu nasıl değiştirilir? 2 | 3 | ## Video kılavuzu 4 | 5 |
6 |
7 | 8 |
9 | 10 | ## Giriş 11 | 12 | Varsayılan toplu iş boyutu 100'dür, ancak bu, `--batch-size=xx` komutu kullanılarak değiştirilebilir. 13 | 14 | Bunu komut satırına ek bir bayrak olarak yapmanız veya Docker kullanıyorsanız, docker-compose.yml dosyasını aşağıdakilerle değiştirin: 15 | 16 | ```shell 17 | subquery-node: 18 | image: onfinality/subql-node:latest 19 | depends_on: 20 | - "postgres" 21 | restart: always 22 | environment: 23 | DB_USER: postgres 24 | DB_PASS: postgres 25 | DB_DATABASE: postgres 26 | DB_HOST: postgres 27 | DB_PORT: 5432 28 | volumes: 29 | - ./:/app 30 | command: 31 | - -f=/app 32 | - --local 33 | - --batch-size=50 34 | 35 | ``` 36 | 37 | Bu örnek, toplu iş boyutunu 50 olarak ayarlar. 38 | 39 | ## Toplu iş boyutu neden değiştirilir? 40 | 41 | Daha küçük bir toplu iş boyutu kullanmak bellek kullanımını azaltabilir ve kullanıcıları büyük sorgular için asılı bırakmaz. Diğer sözcüklerde, uygulamanız daha duyarlı olabilir. 42 | -------------------------------------------------------------------------------- /archived/tr/academy/tutorials_examples/delete-projects.md: -------------------------------------------------------------------------------- 1 | # Bir SubQuery projesi nasıl silinir? 2 | 3 | ## Tanıtım 4 | 5 | SubQuery Project'teki projelerinizi alakalı ve güncel tutmanız önemlidir. Test amacıyla SubQuery Project'e yüklenen projeler için, kaynakları korumak ve maliyetten tasarruf etmek için daha sonra silinmeleri önerilir. 6 | 7 | Bir dizin oluşturucu düğümü çalıştırmak, Docker kullanmanın veya[SubQuery Projeleri'nde](https://managedservice.subquery.network/) sizin için bir proje barındırmanın dışında başka bir seçenektir. Daha fazla zaman ve çaba gerektirir, ancak SubQuery'nin kapaklar altında nasıl çalıştığına dair anlayışınızı geliştirecektir. 8 | 9 | ## Bir projeyi hazırlama yuvasından silme 10 | 11 | Bir projeyi hazırlama yuvasından silmek için, proje ayrıntısı kontrol paneli sayfanızdaki dağıtım ayrıntılarında bulunan hazırlama yuvası bölümündeki 3 noktaya tıklayın ve sil'i seçin. 12 | 13 | ![Bir projeyi hazırlama yuvasından silme](/assets/img/delete_staging.png) 14 | 15 | ## Bir projeyi üretim yuvasından silme 16 | 17 | Bir projeyi üretim yuvasından silmek için bunun yerine tüm projeyi silmeniz gerekir. Sağ üst köşeye gidin ve tüm proje için ayarlar olan 3 noktaya tıklayın. Ardından "Projeyi Sil" i seçin. 18 | 19 | ![Bir projeyi üretim yuvasından silme](/assets/img/delete_production.png) 20 | -------------------------------------------------------------------------------- /archived/tr/academy/tutorials_examples/terminology.md: -------------------------------------------------------------------------------- 1 | # Terminoloji 2 | 3 | - SubQuery Project (_ where the magic happens_): Bir SubQuery Düğümünün bir proje ağından nasıl geçmesi ve toplaması gerektiği ve verilerin yararlı GraphQL sorgularını etkinleştirmek için nasıl dönüştürülmesi ve depolandığı hakkında bir tanım ([`@subql/cli`](https://www.npmjs.com/package/@subql/cli)) 4 | - SubQuery Node (_ where the work is doner_): Bir SubQuery projesi definiton'ını kabul edecek ve bağlı bir ağı veritabanına sürekli olarak dizine alan bir düğümü çalıştıracak bir paket ([`@subql/node`](https://www.npmjs.com/package/@subql/node)) 5 | - SubQuery Query Service (_where we get the data from_): Dizine alınan verileri sorgulamak ve görüntülemek için dağıtılan bir SubQuery node GraphQL API'si ile etkileşime giren bir paket ([`@subql/query`](https://www.npmjs.com/package/@subql/query)) 6 | - GraphQL (_how we query the data_): Esnek grafik tabanlı veriler için özel olarak uygun API'ler için bir query langage - bkz[graphql.org](https://graphql.org/learn/) 7 | -------------------------------------------------------------------------------- /archived/tr/miscellaneous/branding.md: -------------------------------------------------------------------------------- 1 | # Markalaşma Materyalleri 2 | 3 | **SubQuery'nin tüm marka özellikleri tescillidir ve markamızı son derece ciddiye alıyoruz.** 4 | 5 | Herhangi bir ticari marka, logo, tasarım veya diğer marka özelliklerini kullanmayı tercih ederseniz, lütfen buradaki yönergeleri dikkatle izleyin veya açıklama için sosyal medya üzerinden bize ulaşın. 6 | 7 | Şüpheniz varsa, lütfen bize sorun! 8 | 9 | ## Dışa Aktarılabilir Figma Dosyası 10 | 11 | Figma dosyamız, ihracat için tüm marka varlıklarının (logolar, yazı tipleri, renkler, görüntüler vb.) tam bir koleksiyonuna sahiptir. 12 | 13 | [Figma - SubQuery Marka Kaynakları](https://www.figma.com/file/AaCXaOcElrlbxq8fz39sJU/SubQuery-Brand-Resources?node-id=3%3A2) 14 | 15 | ## Marka Varlıkları Paketi 16 | 17 | A smaller ZIP package of brand assets: [public_branding.zip](https://static.subquery.network/public_branding.zip). 18 | -------------------------------------------------------------------------------- /archived/tr/run_publish/connect.md: -------------------------------------------------------------------------------- 1 | # Connect to your new project 2 | 3 | Once your deployment has succesfully completed and our nodes have indexed your data from the chain, you'll be able to connect to your project via the displayed Query endpoint. 4 | 5 | ![Projenize yeni sürümü dağıtın](/assets/img/projects_deploy_sync.png) 6 | 7 | Alternatif olarak, projenizin başlığının yanında bulunan üç noktaya tıklayabilir ve onu SubQuery Explorer'da görüntüleyebilirsiniz. There you can use the in browser playground to get started. 8 | 9 | ![Projects in SubQuery Explorer](/assets/img/projects_explorer.png) 10 | 11 | ::: tip Note Learn more about the [GraphQL Query language.](./graphql.md) ::: 12 | -------------------------------------------------------------------------------- /archived/tr/run_publish/graphql.md: -------------------------------------------------------------------------------- 1 | # GraphQL hakkında daha fazla bilgi edinin 2 | 3 | GraphQL, nasıl çalıştığı ve nasıl kullanılacağı hakkında daha fazla bilgi edinmek için [resmi GraphQL rehberini buradan](https://graphql.org/learn/) takip edebilirsiniz: 4 | 5 | - There are libraries to help you implement GraphQL in [many different languages](https://graphql.org/code/). 6 | - Pratik öğreticilerle derinlemesine bir öğrenme deneyimi için [GraphQL Nasıl Kullanılır](https://www.howtographql.com/) bölümüne göz atın. 7 | - [GraphQL'yi Keşfetmek: API'ler için Bir Sorgu Dili](https://www.edx.org/course/exploring-graphql-a-query-language-for-apis) isimli ücretsiz çevrimiçi kursa göz atın. 8 | -------------------------------------------------------------------------------- /archived/tr/subquery_network/frontier-testnet.md: -------------------------------------------------------------------------------- 1 | # Frontier Testnet 2 | -------------------------------------------------------------------------------- /archived/uk/academy/academy.md: -------------------------------------------------------------------------------- 1 | # Ласкаво просимо до академії 2 | -------------------------------------------------------------------------------- /archived/uk/academy/tutorials_examples/delete-projects.md: -------------------------------------------------------------------------------- 1 | # Як видалити проект SubQuery? 2 | 3 | ## Вступ 4 | 5 | Важливо зберігати ваші проекти в проекті SubQuery в актуальному стані. Для всіх проектів, що завантажуються в SubQuery Project для тестування, рекомендується видалити їх пізніше, щоб зберегти ресурси та заощадити витрати. 6 | 7 | Запуск вузла індексера є іншою опцією за межами Docker або виконання проекту, розміщеного для вас за адресою SubQuery Projects. Це потребує більше часу та зусиль, але покращить ваше розуміння того, як працює SubQuery "під капотом". 8 | 9 | ## Видалення проекту зі staging слоту 10 | 11 | Щоб видалити проект зі staging слотів, натисніть на 3 крапки у секції staging слоті в межах розгортання на сторінці деталей проекту і оберіть видалити. 12 | 13 | ![Видалення проекту зі staging слоту](/assets/img/delete_staging.png) 14 | 15 | ## Видалення проекту з production слоту 16 | 17 | Щоб видалити проект із виробничого слота, вам доведеться видалити весь проект. Перейдіть до правого кута зверху та натисніть на 3 крапки, що є налаштуваннями для всього проекту. Потім оберіть "Видалити проект". 18 | 19 | ![Видалення проекту з production слоту](/assets/img/delete_production.png) 20 | -------------------------------------------------------------------------------- /archived/uk/academy/tutorials_examples/terminology.md: -------------------------------------------------------------------------------- 1 | # Термінологія 2 | 3 | - SubQuery Project (_де відбувається магія_): визначення ([`@subql/cli`](https://www.npmjs.com/package/@subql/cli)) про те, як SubQuery Node повинен трасувати і об'єднувати проекти і як дані повинні бути перетворені і збережені, щоб увімкнути корисні графічні запити GraphQL 4 | - SubQuery Node (_де виконується робота_): Пакет ([`@subql/node`](https://www.npmjs.com/package/@subql/node)), який прийматиме визначення проекту SubQuery та запускатиме вузол, який постійно індексує підключену мережу до бази даних 5 | - SubQuery Query Service (_Звідки ми отримуємо дані_): пакет ([`@subql/query`](https://www.npmjs.com/package/@subql/query)), який взаємодіє з API GraphQL розгорнутого вузла SubQuery для запиту та перегляду індексованих даних 6 | - GraphQL (_як ми запитуємо дані_): мова запитів для API, яка спеціально підходить для гнучких даних на основі графіків - набір [graphql.org](https://graphql.org/learn/) 7 | -------------------------------------------------------------------------------- /archived/uk/miscellaneous/branding.md: -------------------------------------------------------------------------------- 1 | # Брендінг Матеріали 2 | 3 | **Всі функції бренду SubQuery є власними, і ми сприймаємо наш бренд надзвичайно серйозно.** 4 | 5 | Якщо ви вирішили використовувати будь-які торгові марки, логотипи, конструкції чи інші функції бренду, будь ласка, уважно дотримуйтесь вказівок тут або звертайтесь до нас через соціальні медіа для уточнення. 6 | 7 | Якщо сумніви, запитайте будь ласка! 8 | 9 | ## Експортний файл Figma 10 | 11 | Наш файл Figma має повну колекцію всіх активів марки (логотипи, шрифти, кольори, зображення тощо) для експорту. 12 | 13 | [Figma - Ресурси торгової марки SubQuery](https://www.figma.com/file/AaCXaOcElrlbxq8fz39sJU/SubQuery-Brand-Resources?node-id=3%3A2) 14 | 15 | ## Пакет активів марки 16 | 17 | Менший пакет ZIP активів бренду: [public_branding.zip](https://static.subquery.network/public_branding.zip). 18 | -------------------------------------------------------------------------------- /archived/uk/run_publish/connect.md: -------------------------------------------------------------------------------- 1 | # Увімкнутися до свого нового проєкту 2 | 3 | Як тільки ваше розгортання буде успішно завершено і наші вузли проіндексують ваші дані з ланцюжка, ви зможете увімкнутися до свого проєкту через відбиваний кінцеву точку запиту. 4 | 5 | ![Проєкт розгортається і синхронізується](/assets/img/projects_deploy_sync.png) 6 | 7 | Крім того, ви можете натиснути на три точки поруч із заголовком проєкту та переглянути його на SubQuery Explorer. Там ви можете використовувати ігровий майданчик в браузері, щоб почати роботу. 8 | 9 | ![Проєкти в провіднику вкладених SubQuery](/assets/img/projects_explorer.png) 10 | 11 | ::: інформаційна записка Дізнайтеся більше про [GraphQL Query language.](./graphql.md)::: 12 | -------------------------------------------------------------------------------- /archived/uk/run_publish/graphql.md: -------------------------------------------------------------------------------- 1 | # Дізнайтеся більше про GraphQL 2 | 3 | Ви можете слідувати [офіційному посібнику GraphQL тут ](https://graphql.org/learn/), щоб дізнатися більше про GraphQL, як він працює та як ним користуватися: 4 | 5 | - Існують бібліотеки, які допоможуть вам реалізувати GraphQL на [багатьох різних мовах](https://graphql.org/code/). 6 | - Для поглибленого досвіду навчання з практичними навчальними посібниками див. [ Як графічний ](https://www.howtographql.com/). 7 | - Ознайомтеся з безкоштовним онлайн-курсом, [ Вивчення GraphQL: Мова запитів для API ](https://www.edx.org/course/exploring-graphql-a-query-language-for-apis). 8 | -------------------------------------------------------------------------------- /archived/uk/run_publish/sandbox.md: -------------------------------------------------------------------------------- 1 | # Пісочниця 2 | 3 | У нашому передбачуваному сценарії використання SubQuery node зазвичай працює надійним хостом, а код проекту SubQuery, поданий користувачем у вузол, не є повністю надійним. 4 | 5 | Якийсь шкідливий код, ймовірно, нападе на хоста або навіть поставить під загрозу його та завдасть шкоди даним інших проектів того ж хоста. Тому ми використовуємо захищений механізм [ VM2 ](https://www.npmjs.com/package/vm2) для зменшення ризиків. Це: 6 | 7 | - Безпечно запускає ненадійний код в ізольованому контексті, і шкідливий код не отримає доступ до мережі та файлової системи хоста, якщо через відкритий інтерфейс ми не ввели в пісочницю. 8 | 9 | - Безпечно викликає методи та обмінюється даними та зворотними дзвінками між пісочницями. 10 | 11 | - Не застрахований від багатьох відомих методів нападу. 12 | 13 | ## Обмеження 14 | 15 | - Щоб обмежити доступ до певних вбудованих модулів, лише `Assert`, `buffer`, `crypto`, `util` та ` path білі. 16 | - Ми підтримуємо [third-party-libraries](../create/mapping/polkadot.md#third-party-libraries) сторонні модулі, написані в **CommonJS** та **hybrid** бібліотек, таких як `@ polkadot / *`, які використовують ESM як за замовчуванням. 17 | - Будь-які модулі, що використовують `HTTP` та `WebSocket`, заборонені. 18 | -------------------------------------------------------------------------------- /archived/uk/subquery_network/foundation.md: -------------------------------------------------------------------------------- 1 | # Фонд "SubQuery Foundation" 2 | 3 | Фонд "SubQuery Foundation" служить для управління та розвитку мережі SubQuery та її екосистеми. Його мета - сприяти розробці та росту мережі SubQuery та надавати підтримку користувачам і розробникам для створення власних проектів для SubQuery. 4 | 5 | Фонд "SubQuery Foundation" - це перший крок до децентралізації власності за мережею SubQuery. 6 | 7 | ## Мета 8 | 9 | Мережа SubQuery буде керуватись фондом "SubQuery Foundation". Фонд "SubQuery Foundation" буде неприбутковою організацією, створеною спеціально для обслуговування, управління, розвитку мережі SubQuery та надання підтримки користувачам і розробникам. 10 | 11 | Попередньо, фонд "SubQuery Foundation" матиме наступні обов'язки: 12 | 13 | - Розробка та оновлення мережі SubQuery. 14 | - Управління та розподіл активів із казни Фонду. 15 | - Управління програмою грантів SubQuery для стимулювання розробки екосистеми та мережі. 16 | - Розробка екосистеми партнерів і спільноти SubQuery. 17 | - Управління освітніми програмами та документаціями. 18 | - Децентралізація контролю над мережею SubQuery. 19 | 20 | Заплановано, що Фонд SubQuery буде підзвітний Раді SubQueri, контра буде контролювати рішення щодо управління та буде складатися з ключових представників основної команди SubQuery та інших ключових партнерів та консультантів. 21 | -------------------------------------------------------------------------------- /archived/uk/subquery_network/frontier-testnet.md: -------------------------------------------------------------------------------- 1 | # Тестнет Frontier 2 | -------------------------------------------------------------------------------- /archived/vi/academy/academy.md: -------------------------------------------------------------------------------- 1 | # Chào mừng bạn đến với Học viện 2 | -------------------------------------------------------------------------------- /archived/vi/academy/tutorials_examples/batch-size.md: -------------------------------------------------------------------------------- 1 | # Làm cách nào để thay đổi kích thước lô tìm nạp chuỗi khối? 2 | 3 | ## Video hướng dẫn 4 | 5 |
6 |
7 | 8 |
9 | 10 | ## Giới thiệu 11 | 12 | Kích thước lô mặc định là 100, nhưng điều này có thể được thay đổi bằng cách sử dụng lệnh bổ sung `--batch-size = xx`. 13 | 14 | Bạn cần làm điều này bằng dòng lệnh như một cờ bổ sung hoặc nếu bạn đang sử dụng Docker, hãy sửa đổi docker-compos.yml thành: 15 | 16 | ```shell 17 | subquery-node: 18 | image: onfinality/subql-node:latest 19 | depends_on: 20 | - "postgres" 21 | restart: always 22 | environment: 23 | DB_USER: postgres 24 | DB_PASS: postgres 25 | DB_DATABASE: postgres 26 | DB_HOST: postgres 27 | DB_PORT: 5432 28 | volumes: 29 | - ./:/app 30 | command: 31 | - -f=/app 32 | - --local 33 | - --batch-size=50 34 | 35 | ``` 36 | 37 | Ví dụ này đặt kích thước lô thành 50. 38 | 39 | ## Tại sao phải thay đổi kích thước lô? 40 | 41 | Việc sử dụng kích thước lô nhỏ hơn có thể làm giảm mức sử dụng bộ nhớ và không khiến người dùng bị treo cho các truy vấn lớn. Nói cách khác, ứng dụng của bạn có thể phản hồi nhanh hơn. 42 | -------------------------------------------------------------------------------- /archived/vi/academy/tutorials_examples/delete-projects.md: -------------------------------------------------------------------------------- 1 | # Làm thế nào để xoá một dự án SubQuery? 2 | 3 | ## Giới thiệu 4 | 5 | Điều quan trọng là giữ cho các dự án của bạn trong Dự án SubQuery phù hợp và được cập nhật. Đối với bất kỳ dự án nào đã tải lên Dự án SubQuery với mục đích thử nghiệm, bạn nên xóa chúng sau đó để tiết kiệm tài nguyên và tiết kiệm chi phí. 6 | 7 | Chạy một nút chỉ mục là một tùy chọn khác ngoài việc sử dụng Docker hoặc có một dự án được lưu trữ tại [SubQuery Managed Service](https://managedservice.subquery.network/). Nó đòi hỏi nhiều thời gian và nỗ lực hơn nhưng sẽ nâng cao hiểu biết của bạn về cách SubQuery hoạt động. 8 | 9 | ## Xóa một dự án khỏi vị trí dàn dựng 10 | 11 | Để xóa dự án khỏi vị trí dàn dựng, hãy nhấp vào 3 dấu chấm trong phần vị trí dàn dựng trong chi tiết triển khai trên trang bảng điều khiển chi tiết dự án của bạn và chọn Delete. 12 | 13 | ![Xóa một dự án khỏi vị trí dàn dựng](/assets/img/delete_staging.png) 14 | 15 | ## Xóa dự án khỏi vị trí sản xuất 16 | 17 | Để xóa dự án khỏi vị trí sản xuất, bạn sẽ phải xóa toàn bộ dự án. Điều hướng đến góc trên cùng bên phải và nhấp vào 3 dấu chấm, đây là cài đặt cho toàn bộ dự án. Sau đó chọn "Delete Project". 18 | 19 | ![Xóa dự án khỏi vị trí sản xuất](/assets/img/delete_production.png) 20 | -------------------------------------------------------------------------------- /archived/vi/academy/tutorials_examples/terminology.md: -------------------------------------------------------------------------------- 1 | # Thuật ngữ 2 | 3 | - Dự án SubQuery (_ nơi điều kỳ diệu xảy ra _): Định nghĩa ([ `@ subql / cli` ](https://www.npmjs.com/package/@subql/cli)) về cách một SubQuery Node sẽ đi qua và tổng hợp một mạng dự án, và dữ liệu sẽ được chuyển đổi và lưu trữ như thế nào để kích hoạt các truy vấn GraphQL hữu ích 4 | - SubQuery Node (_ nơi công việc được thực hiện _): Một Package ([ `@ subql / node` ](https://www.npmjs.com/package/@subql/node)) sẽ chấp nhận một dự án SubQuery xác định và chạy một Node liên tục lập chỉ mục một Network được kết nối với một database 5 | - Dịch vụ truy vấn SubQuery (_nơi để lấy dữ liệu_): Package này ([`@subql/query`](https://www.npmjs.com/package/@subql/query)) tương tác với API GraphQL của một Node SubQuery đã được triển khai để truy vấn và xem dữ liệu được lập Index 6 | - GraphQL (_cách để truy vấn dữ liệu_): Đây là một ngôn ngữ truy vấn dành cho các API, đặc biệt phù hợp với dữ liệu dựa trên biểu đồ linh hoạt - xem [graphql.org](https://graphql.org/learn/) 7 | -------------------------------------------------------------------------------- /archived/vi/miscellaneous/branding.md: -------------------------------------------------------------------------------- 1 | # Vật liệu xây dựng thương hiệu 2 | 3 | **Tất cả các đặc điểm thương hiệu của SubQuery là độc quyền và chúng tôi rất coi trọng thương hiệu của mình.** 4 | 5 | Nếu bạn chọn sử dụng bất kỳ nhãn hiệu, biểu tượng, thiết kế hoặc đặc điểm nhãn hiệu nào khác, vui lòng thực hiện nghiêm túc các hướng dẫn tại đây hoặc liên hệ với chúng tôi qua phương tiện truyền thông xã hội để được giải thích rõ. 6 | 7 | Nếu có thắc mắc, xin hãy đặt câu hỏi! 8 | 9 | ## Tệp Figma có thể xuất 10 | 11 | Tệp Figma của chúng tôi có một bộ sưu tập đầy đủ tất cả các tài sản thương hiệu (biểu trưng, ​​phông chữ, màu sắc, hình ảnh, v. v.) để xuất. 12 | 13 | [Figma - Tài nguyên thương hiệu SubQuery](https://www.figma.com/file/AaCXaOcElrlbxq8fz39sJU/SubQuery-Brand-Resources?node-id=3%3A2) 14 | 15 | ## Gói tài sản thương hiệu 16 | 17 | Gói tài sản thương hiệu ZIP nhỏ hơn: [public_branding.zip](https://static.subquery.network/public_branding.zip). 18 | -------------------------------------------------------------------------------- /archived/vi/run_publish/connect.md: -------------------------------------------------------------------------------- 1 | # Connect to your new project 2 | 3 | Once your deployment has succesfully completed and our nodes have indexed your data from the chain, you'll be able to connect to your project via the displayed Query endpoint. 4 | 5 | ![Các dự án đang được triển khai và đồng bộ](/assets/img/projects_deploy_sync.png) 6 | 7 | Ngoài ra, bạn có thể nhấp vào ba dấu chấm bên cạnh tiêu đề dự án của mình và xem nó trên SubQuery Explorer. There you can use the in browser playground to get started. 8 | 9 | ![Projects in SubQuery Explorer](/assets/img/projects_explorer.png) 10 | 11 | ::: tip Note Learn more about the [GraphQL Query language.](./graphql.md) ::: 12 | -------------------------------------------------------------------------------- /archived/vi/run_publish/graphql.md: -------------------------------------------------------------------------------- 1 | # Tìm hiểu thêm về GraphQL 2 | 3 | Bạn có thể theo dõi [hướng dẫn GraphQL chính thức tại đây](https://graphql.org/learn/) để tìm hiểu thêm về GraphQL, cách thức hoạt động và cách sử dụng: 4 | 5 | - Có nhiều thư viện để giúp bạn thực thi GraphQL bằng [nhiều ngôn ngữ khác nhau](https://graphql.org/code/). 6 | - Để hiểu sâu hơn bằng các hướng dẫn thực hành, hãy xem qua [Cách để GraphQL](https://www.howtographql.com/). 7 | - Xem qua khóa học online miễn phí, [Khám Phá GraphQL: Một Ngôn Ngữ truy vấn cho APIs](https://www.edx.org/course/exploring-graphql-a-query-language-for-apis). 8 | -------------------------------------------------------------------------------- /archived/vi/subquery_network/frontier-testnet.md: -------------------------------------------------------------------------------- 1 | # Frontier Testnet 2 | -------------------------------------------------------------------------------- /archived/zh/academy/academy.md: -------------------------------------------------------------------------------- 1 | # 欢迎来到学院 2 | -------------------------------------------------------------------------------- /archived/zh/academy/tutorials_examples/batch-size.md: -------------------------------------------------------------------------------- 1 | # 如何更改区块链批处理大小? 2 | 3 | ## 视频教程 4 | 5 |
6 |
7 | 8 |
9 | 10 | ## 简介 11 | 12 | 默认的批处理大小是 100，但可以通过命令 `--batch-size=xx` 来改变。 13 | 14 | 你需要在命令行中特殊标记，或者如果你正在使用 Docker，修改 docker-compose.yml 15 | 16 | ```shell 17 | subquery-node: 18 | image: onfinality/subql-node:latest 19 | depends_on: 20 | - "postgres" 21 | resting: always 22 | environment: 23 | DB_USER: postgres 24 | DB_PASS: postgres 25 | DB_DATABASE: postgres 26 | DB_HOST: postgres 27 | DB_PORT: 5432 28 | volumes: 29 | - . :app 30 | command: 31 | - -f=/app 32 | - --local 33 | - --batch-size=50 34 | 35 | ``` 36 | 37 | 此配置将批处理大小设置为 50。 38 | 39 | ## 为什么要改变批处理大小？ 40 | 41 | 使用较小的批量大小可以减少内存使用，而不会让用户挂起大量查询。 换言之，您的应用程序响应速度更快。 42 | -------------------------------------------------------------------------------- /archived/zh/academy/tutorials_examples/debug-projects.md: -------------------------------------------------------------------------------- 1 | # 如何调试一个 SubQuery 项目？ 2 | 3 | ## 视频教程 4 | 5 |
6 |
7 | 8 |
9 | 10 | ## 介绍 11 | 12 | 为了调试 SubQuery 项目，例如通过代码、设置 breakpoints 和检查变量，您必须使用一个 Node.js 监视器与 Chrome 开发者工具结合使用 13 | 14 | ## 节点监视器 15 | 16 | 在终端屏幕上运行以下命令。 17 | 18 | ```shell 19 | node --inspect-brk -f 20 | ``` 21 | 22 | 例如： 23 | 24 | ```shell 25 | node --expect-brk /usr/local/bin/subql-node -f ~/Code/subQuery/projects/subql-Helloworld/ 26 | Debugger 监听ws:127.0.0.1:9229/56156753-c07d-4bbe-af2d-2c7ff4bcc5ad 27 | 关于帮助，请参阅：https://nodejs.org/en/docs/spector 28 | Debugger 已附后。 29 | ``` 30 | 31 | ## Chrome 开发工具 32 | 33 | 打开 Chrome DevTools 并导航到源标签页。 注意，点击绿色图标将打开一个新窗口。 34 | 35 | ![节点查看](/assets/img/node_inspect.png) 36 | 37 | 导航到文件系统并将您的项目文件夹添加到工作区。 然后打开 dist > 映射文件夹并选择你想要调试的代码。 然后跟任何标准调试工具一样来完成代码。 38 | 39 | ![调试项目](/assets/img/debugging_projects.png) 40 | -------------------------------------------------------------------------------- /archived/zh/academy/tutorials_examples/delete-projects.md: -------------------------------------------------------------------------------- 1 | # 如何调试一个 SubQuery 项目？ 2 | 3 | ## 简介 4 | 5 | 在 SubQuery 项目中保持您的项目的相关性和最新性很重要。 对于上传到 SubQuery 项目进行测试的任何项目，我们建议您随后予以删除，以节省资源和节省费用。 6 | 7 | 除了使用 Docker 或者在 [SubQuery Project](https://managedservice.subquery.network/) 上托管项目， 您还可以选择运行 indexer 节点。 这需要花费更多的时间和精力，但是它可以帮助您加深对 SubQuery 工作原理的理解。 8 | 9 | ## 从暂存项中删除项目 10 | 11 | 您可以打开项目细节面板页面，在部署详细信息中点击暂存项部分的 3 个点并选择删除，就可以从暂存项删除一个项目。 12 | 13 | ![从暂存项中删除项目](/assets/img/delete_staging.png) 14 | 15 | ## 从成品项中删除项目 16 | 17 | 如果您需要要从成品项删除一个项目，您必须删除整个项目。 导航到页面右上角，点击 3 个点，就可以打开整个项目的设置， 然后选择 “删除项目”。 然后选择 “删除项目”。 18 | 19 | ![从成品项中删除项目](/assets/img/delete_production.png) 20 | -------------------------------------------------------------------------------- /archived/zh/academy/tutorials_examples/terminology.md: -------------------------------------------------------------------------------- 1 | # 术语 2 | 3 | - SubQuery 项目 (_一个奇迹发生的地方_): 一个关于 SubQuery 节点([`@subql/cli`](https://www.npmjs.com/package/@subql/cli)) 应如何遍历和聚合项目网络以及应如何转换和存储数据以启用有用的 GraphQL 查询的定义 4 | - SubQuery 节点 (_工作完成了_): 一个包([`@subql/node`](https://www.npmjs.com/package/@subql/node)) 将接受一个 SubQuery 项目定义， 然后运行一个不断索引连接网络到数据库的节点 5 | - SubQuery 查询服务(_我们从其中获取数据_): 包([`@subql/quy`](https://www.npmjs.com/package/@subql/query)) 与已部署的 SubQuery 节点的 GraphQL API 交互以查询和查看索引数据 6 | - GraphQL (_我们如何查询数据_)：一个 API 的查询 langage ，它特别适合于基于灵活图形的数据 - 查看 graphql。 7 | -------------------------------------------------------------------------------- /archived/zh/miscellaneous/branding.md: -------------------------------------------------------------------------------- 1 | # 品牌材料 2 | 3 | **SubQuery 的所有品牌特性都是专有的，我们极为认真地对待我们的品牌。** 4 | 5 | 如果您选择使用任何商标、徽标、设计或其他品牌功能，请仔细遵守此处的指导原则，或通过社交媒体联系我们以获得授权。 6 | 7 | 如果有疑问，请咨询！ 8 | 9 | ## 可导出的 Figma 文件 10 | 11 | 我们的 Figma 文件包含了所有品牌资产(logos、字体、颜色、图像等)，以供导出。 12 | 13 | [\[Figma - SubQuery 品牌资源\](https://www.figma.com/file/AaCXaOccrlbxq8fz39sJU/ SubQuery-Brand-Resources?node-id=3%3A2)](https://www.figma.com/file/AaCXaOcElrlbxq8fz39sJU/SubQuery-Brand-Resources?node-id=3%3A2) 14 | 15 | ## 品牌资源包 16 | 17 | 一个较小的 ZIP 品牌资源包： [public_branding.zip](https://static.subquery.network/public_branding.zip)。 18 | -------------------------------------------------------------------------------- /archived/zh/miscellaneous/social_media.md: -------------------------------------------------------------------------------- 1 | # 社交媒体链接 2 | 3 | SubQuery 是一个活跃的项目，通过许多社交媒体与我们的用户保持联系和沟通。 4 | 5 | 我们希望倾听社区的声音，所以请加入社区并向我们发送您的想法或问题！ 6 | 7 | ## SubQuery 官方社区 8 | 9 | - [链接](https://linktr.ee/subquerynetwork) 10 | - [Discord](https://discord.com/invite/subquery) (拥有专业技术支持频道的主社区) 11 | - [ Medium ](https://subquery.medium.com) (主要通知公告) 12 | - [Twitter](https://twitter.com/subquerynetwork) 13 | - [Telegram](https://t.me/subquerynetwork) (公告频道) 14 | - [GitHub](https://github.com/subquery/) 15 | - [Matrix/Riot](https://matrix.to/#/#subquery:matrix.org) 16 | - [LinkedIn](https://www.linkedin.com/company/subquery) 17 | 18 | ## SubQuery 非官方社区 19 | 20 | 这些社区并不是由 SubQuery 团队搭建的，但我们的大使可能在那里提供支持。 请注意防骗，因为 SubQuery **不** 负责它们内部发生的事情。 21 | 22 | - [Telegram (Chinese)](https://t.me/subquerychina) 23 | - [Telegram (Russian)](https://t.me/SubQuery_russia) 24 | - [Telegram (Spanish)](https://t.me/SubQueryES) 25 | - [Telegram (Thai)](https://t.me/subquerynetworkthai) 26 | - [Telegram (Turkish)](https://t.me/subquery_TR) 27 | - [Telegram (Vietname)](https://t.me/subqueryvietnam) 28 | - [Telegram (Vietnamese Announcement)](https://t.me/subqueryannvn) 29 | -------------------------------------------------------------------------------- /archived/zh/quickstart/whats-next.md: -------------------------------------------------------------------------------- 1 | # 3. 下一步 2 | 3 | 现在您已经清楚地了解如何构建一个基本的 SubQuery 项目，您的旅程下一步是什么？ 4 | 5 | - 现在，您可以轻松地发布您的项目。 SubQuery provides a managed service solution where you can deploy your new project. 您可以将其部署到 [SubQuery 项目](https://managedservice.subquery.network) 并使用我们的 [Explorer](https://explorer.subquery.network) 进行查询。 阅读 [的指南向 SubQuery 项目发布您的新项目](../run_publish/publish.md). 6 | 7 | - 深入到开发者文档中， 跳到 [构建 ](../../build/introduction.md) 部分并了解更多关于三个关键文件的信息： **清单文件， GraphQL schema 以及映射文件。** 8 | 9 | - 如果您想要练习更多的实际例子， 然后走到我们的 [课程](../academy/herocourse/welcome.md) 部分，并通过相关练习和实验室工作手册学习重要的概念。 获取访问便捷可用和开源项目的机会，并获得一个 SubQuery 项目的手动体验。 10 | 11 | - 最后，如果您想要探索更多的方式来运行和发布您的项目，请参阅 [运行 & 发布部分](../../run_publish/run.md)。 获取关于运行您的 SubQuery 项目的所有方式的完整信息，以及高级 GraphQL 聚合和订阅功能。 12 | -------------------------------------------------------------------------------- /archived/zh/run_publish/aggregate.md: -------------------------------------------------------------------------------- 1 | # 聚集函数 2 | 3 | ## 分组依据 4 | 5 | SubQuery 支持高级的总函数，以便您在查询期间能够对一组值进行计算。 6 | 7 | 聚合函数通常与组一起使用。在您的查询中使用按函数。 8 | 9 | Groupby 允许您在一个查询中快速获取一个从 SubQuery 集中的不同值。 10 | 11 | ![Graphql Groupby](/assets/img/graphql_aggregation.png) 12 | 13 | ## 高级聚合函数 14 | 15 | 在不安全模式下，SubQuery 提供以下汇总功能： 16 | 17 | - `sum` (适用于像数字一样的字段) - 将所有值一起添加到一起的结果 18 | - `distCount` (适用于所有字段) - 不同值的数量 19 | - `min` (适用于类似数字的字段) - 最小值 20 | - `max` (适用于类似数字的字段) - 最大值 21 | - `average` (适用于类似数字的字段) - 平均值 (计算值) 22 | - `stddev示例` (适用于类似数字的字段) - 示例标准偏差 23 | - `stddevPopulation` (适用于类似数字的字段) - 示例标准偏差 24 | - `varianceSample` (适用于类似数字的字段) - 值的样本变化量 25 | - `variancePopulation` (适用于类似数字的字段) - 值的人口变化量 26 | 27 | SubQuery 对总函数的实现基于 [pg-aggregates](https://github.com/graphile/pg-aggregates)，您可以在那里找到更多的信息. 28 | 29 | 请注意，您必须在查询服务上启用 `--safe` 标志才能使用这些函数。 [阅读更多](./references.md#unsafe-query-service)。 30 | 31 | 另外，请注意， `--safe` 命令将防止您的项目在 SubQuery 网络中运行。 如果您希望此命令与您的项目一起运行在 [SubQuery 管理的服务](https://managedservice.subquery.network) 中，您必须联系客服。 ::: 32 | -------------------------------------------------------------------------------- /archived/zh/run_publish/connect.md: -------------------------------------------------------------------------------- 1 | # 连接您的新项目 2 | 3 | 一旦您的部署成功完成并且我们的节点已经从该链中为您的数据编制了索引， 您可以通过显示的查询端点连接到您的项目。 4 | 5 | ![正在部署和同步的项目](/assets/img/projects_deploy_sync.png) 6 | 7 | 您也可以点击项目标题旁边的三个小点图标，从而在 SubQuery 浏览器上查看项目， 在这里您可以使用我们的区块链浏览器开始—— [阅读更多关于如何在这里使用](../query/query.md) 的信息。 在这里您可以使用浏览器播放场景开始操作。 8 | 9 | ![SubQuery Explorer 中的项目](/assets/img/projects_explorer.png) 10 | 11 | ::: 信息注释 了解更多关于 [GraphQL 查询语言。](./graphql.md) ::: 12 | -------------------------------------------------------------------------------- /archived/zh/run_publish/graphql.md: -------------------------------------------------------------------------------- 1 | # 了解有关 GraphQL 的更多信息 2 | 3 | 您可以在这里关注 [官方 GraphQL 指南](https://graphql.org/learn/) 来了解 GraphQL 的更多消息、工作原理及应用方法： 4 | 5 | - 有一些库可以帮助您在 [多种不同语言的](https://graphql.org/code/) 中实现 GraphQL 。 6 | - 关于实用教程的深入学习体验，请参阅 [如何 GraphQL](https://www.howtographql.com/)。 7 | - 观看免费在线课程， [探索 GraphQL: API 查询语言](https://www.edx.org/course/exploring-graphql-a-query-language-for-apis)。 8 | -------------------------------------------------------------------------------- /archived/zh/run_publish/query.md: -------------------------------------------------------------------------------- 1 | # 如何在 SubQuery Explorer 中查询您的项目 2 | 3 | [SubQuery Explorer](https://explorer.subquery.network) is an online Managed Service that provides access to published SubQuery projects made by contributors in our community and managed by the SubQuery team. 您可以按照我们的指南 [发布您自己的 SubQuery 项目](../run_publish/publish.md) 向我们的浏览器发布您自己的 SubQuery 项目。 4 | 5 | ![SubQuery 浏览器](https://static.subquery.network/media/explorer/explorer-header.png) 6 | 7 | SubQuery 浏览器使启动变得更加容易。 我们正在在线托管这些 SubQuery 项目，允许任何人免费查询。 这些托管节点将由 SubQuery 团队通过生产应用的使用频率和性能级别进行监测和运行。 8 | 9 | ![SubQuery 项目](https://static.subquery.network/media/explorer/explorer-project.png) 10 | 11 | 您还会注意到 SubQuery Explorer 提供了一个 playground，用于发现可用数据的示例查询 - 您可以直接在您的浏览器中测试查询，而无需执行代码。 此外，我们对文档做了一些小的改进，以更好地支持开发人员查询和分析整个 Polkadot 数据。 12 | 13 | On the top right of the playground, you'll find a _Docs_ button that will open a documentation draw. 该文档是自动生成的，可帮助您查找实体和方法。 14 | 15 | ::: 信息注释 了解更多关于 [GraphQL 查询语言。](./graphql.md) ::: 16 | -------------------------------------------------------------------------------- /archived/zh/run_publish/sandbox.md: -------------------------------------------------------------------------------- 1 | # 沙盒 2 | 3 | 在我们所设想的使用情况下，SubQuery 节点通常是由一个受信任的主机来管理的。 而用户向节点所提交的 SubQuery 项目代码并不完全可信。 4 | 5 | 一些恶意代码很有可能攻击主机甚至破坏主机，造成同一主机内其他项目的数据损坏。 因此，我们使用 [VM2](https://www.npmjs.com/package/vm2) 沙盒安全机制来降低风险。 如下： 6 | 7 | - 在受隔离的系统中运行不受信任的代码，这些代码不会访问主机的网络和文件系统，除非通过我们注入沙箱的公共接口。 8 | 9 | - 使用安全的调用方法，并在沙箱之间交换和接受数据。 10 | 11 | - 对许多已知的攻击方法免疫 12 | 13 | ## 限制 14 | 15 | - 为了限制访问某些内置模块，只有 `conflict`, `buffer` `crypto`,`util` 和 `path` ，上述代码是白名单。 16 | 17 | - 我们支持使用**CommonJS**和**CommonJS**库编写的 第三方模块，如`@polkadt/*`，它们默认使用 ESM。 18 | 19 | - 禁止使用`HTTP`和`WebSocket`的任何模块。 20 | -------------------------------------------------------------------------------- /archived/zh/subquery_network/consumers.md: -------------------------------------------------------------------------------- 1 | # 消费者 2 | 3 | ## 消费者是什么？ 4 | 5 | 用戶是 SubQuery 网络的参与者，是支付来自 SubQuery 网络处理和组织的区块链数据的个人或组织。 消费者将向 SubQuery 网络提出特定数据的请求，并支付以我们的代币 SQT 计数的广播金额。 6 | 7 | 消费者通常是 dApp（去中心化应用程序）开发人员、数据分析公司、区块链网络、中间件开发人员，甚至是需要访问区块链数据以向最终用户提供服务的 Web 聚合公司。 8 | 9 | ## 消费者要求 10 | 11 | 成为 SubQuery 的消費者没有任何要求。 但是，消费者需要了解如何获取 SQT、如何宣传他们的数据需求以及如何使用返回的 JSON 数据。 12 | 13 | 消费者可能还需要了解如何创建要索引的子查询项目或将这项工作外包，以便以他们需要的格式获取数据。 14 | 15 | ## 服务成本 16 | 17 | 在区块链上查询数据的成本将基于供需，并将与当前可用的其他类似服务相媲美。 开放透明的网络和生态系统的优势在于鼓励竞争，为消费者提供最好的服务。 18 | 19 | ## 消费者的支付方式？ 20 | 21 | 为了灵活性，消费者有 3 种支付方式来支付区块链数据。 分别是： 22 | 23 | - 按需付费 pay-as-you-go 24 | - 封闭式服务协议 25 | - 开放式服务协议 26 | 27 | 您可以在[付款方式一文](./payment-methods.md)中详细了解不同的付款方式、它们的工作原理以及优缺点。 28 | 29 | ## 常见问答（FAQ） 30 | 31 | ### 作为消费者，我应该选择 1 个索引器还是多个索引器？ 32 | 33 | 除非使用封闭服务协议，否则将有一个或多个索引器索引子查询项目。 消费者在决定从哪个索引器读取数据时有选择。 通常消费者将选择最可靠和最最低的延迟指数。 消费者还可纳入自动故障并从另一索引器读取数据，如果第一次出现故障或不具响应性。 34 | 35 | ### 如果索引器关机会发生什么情况？ 36 | 37 | 除非正在使用封闭服务协议，否则如果有多个索引器将您的 SubQuery 项目索引。 这只是一个转向另一个索引器的问题。 理想的情景将包括一些策略，例如通知潜在问题的警报监测以及智能路由和缓存。 38 | -------------------------------------------------------------------------------- /archived/zh/subquery_network/foundation.md: -------------------------------------------------------------------------------- 1 | # SubQuery 基金会 2 | 3 | SubQuery 基金会负责管理和开发 SubQuery 网络及其生态系统。 其目的是促进和指导 SubQuery 网络的发展和成长，为用户和开发者建立自己的 SubQuery 项目提供支持。 4 | 5 | SubQuery 基金会是实现对 SubQuery 网络所有权分散的第一步。 6 | 7 | ## 目的 8 | 9 | SubQuery 网络将由 SubQuery 基金会管理。 SubQuery 基金会将是一个专门为服务、管理和开发 SubQuery 网络并为用户和开发者参与提供支持而创建的非营利实体。 10 | 11 | 基金会预计将具有以下任务： 12 | 13 | - 开发和更新 SubQuery 网络. 14 | - 管理和分配来自基金会财务处的资产. 15 | - 管理 SubQuery 赠款方案，以刺激生态系统和网络发展. 16 | - 开发合作伙伴和用户社区的 SubQuery 生态系统. 17 | - 推动教育方案和文献工作. 18 | - 分散对 SubQuery 网络的控制. 19 | 20 | 按照计划，SubQuery 基金会将对 SubQuery 委员会负责，后者将监督治理决策，并由来自核心 SubQuery 团队的主要代表以及其他主要合作伙伴和顾问组成。 21 | -------------------------------------------------------------------------------- /archived/zh/subquery_network/frontier-testnet.md: -------------------------------------------------------------------------------- 1 | # Frontier Testnet 2 | -------------------------------------------------------------------------------- /archived/zh/subquery_network/introduction.md: -------------------------------------------------------------------------------- 1 | # 简介 2 | 3 | **SubQuery 网络是 Web3 基础设施的未来** 4 | 5 | 我们正在为 dApp 开发者构建最开放的、运行最可靠的、可扩展的数据服务。 6 | 7 | SubQuery 网络以一种激励和可验证的方式为全球社区提供数据索引的服务。 8 | 9 | 将项目发布到 SubQuery 网络后，任何人都可以对其进行索引和托管，从而可以更快、更可靠地向世界各地的用户提供数据。 10 | 11 | SubQuery 网络通过允许用户将项目基础架构完全去中心化，从而促进了开放式 Web3 数据革命。 12 | 13 | ## 参与者 14 | 15 | 网络中的每个人都有一个角色，从高技术开发人员到非高技术开发人员。 SubQuery 网络中包括四个主要参与者. 16 | 17 | ### 消费者 18 | 19 | 消费者将向 SubQuery 网络检索其 dApp 或其工具的特定数据，并为每个请求通过代币 SQT 的形式支付广播费用。 20 | 21 | ::: 信息注释 了解更多关于 [Consumers](./consumers.md) ::: 22 | 23 | ### 索引者 24 | 25 | 索引器者将在自己的基础设施中运行和维护高质量的 SubQuery 项目，同时运行着索引器和查询服务，并将会根据其提供的服务获得 SQT 代币奖励。 26 | 27 | ::: 信息注释 了解更多关于 [Indexers](./indexers.md) ::: 28 | 29 | ### 委托者 30 | 31 | 委托者将通过委托来参与网络，支持他们最喜欢的索引者来，以根据索引者所做的工作获得奖励。 32 | 33 | ::: 信息注释 了解更多关于 [Delegators](./delegators.md) ::: 34 | 35 | ### 构建者 36 | 37 | 构建者是网络中运行的 SubQuery 项目的构建者。 他们编写并发布 SubQuery 项目，以便网络索引和运行。 38 | 39 | ::: 信息注释 了解更多关于 [如何建立你的第一个 SubQuery 项目](../build/introduction.md) ::: 40 | -------------------------------------------------------------------------------- /crowdin.yaml: -------------------------------------------------------------------------------- 1 | files: 2 | - source: /docs/*.md 3 | translation: /docs/%two_letters_code%/%original_file_name% 4 | - source: /docs/academy/*.md 5 | translation: /docs/%two_letters_code%/academy/%original_file_name% 6 | - source: /docs/create/*.md 7 | translation: /docs/%two_letters_code%/create/%original_file_name% 8 | - source: /docs/faqs/*.md 9 | translation: /docs/%two_letters_code%/faqs/%original_file_name% 10 | - source: /docs/miscellaneous/*.md 11 | translation: /docs/%two_letters_code%/miscellaneous/%original_file_name% 12 | - source: /docs/quickstart/*.md 13 | translation: /docs/%two_letters_code%/quickstart/%original_file_name% 14 | - source: /docs/run_publish/*.md 15 | translation: /docs/%two_letters_code%/run_publish/%original_file_name% 16 | - source: /docs/subquery_network/*.md 17 | translation: /docs/%two_letters_code%/subquery_network/%original_file_name% 18 | - source: /docs/subquery_data_node/*.md 19 | translation: /docs/%two_letters_code%/subquery_data_node/%original_file_name% 20 | -------------------------------------------------------------------------------- /docs/.vuepress/components/BaseCard.vue: -------------------------------------------------------------------------------- 1 | 6 | 8 | 9 | 27 | -------------------------------------------------------------------------------- /docs/.vuepress/components/Button.vue: -------------------------------------------------------------------------------- 1 | 6 | 11 | 40 | -------------------------------------------------------------------------------- /docs/.vuepress/components/Footer.vue: -------------------------------------------------------------------------------- 1 | 4 | 5 | 6 | 15 | -------------------------------------------------------------------------------- /docs/.vuepress/components/NeedHelp.vue: -------------------------------------------------------------------------------- 1 | 16 | 20 | 21 | 46 | -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/favicons/apple-touch-icon.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/favicons/apple-touch-icon.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/favicons/favicon-16x16.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/favicons/favicon-16x16.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/favicons/favicon-32x32.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/favicons/favicon-32x32.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/favicons/favicon.ico: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/favicons/favicon.ico -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/fonts/Inter-Regular.ttf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/fonts/Inter-Regular.ttf -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/icons/icon-128x128.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/icons/icon-128x128.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/icons/icon-144x144.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/icons/icon-144x144.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/icons/icon-152x152.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/icons/icon-152x152.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/icons/icon-192x192.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/icons/icon-192x192.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/icons/icon-384x384.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/icons/icon-384x384.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/icons/icon-48x48.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/icons/icon-48x48.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/icons/icon-512x512.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/icons/icon-512x512.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/icons/icon-72x72.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/icons/icon-72x72.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/icons/icon-96x96.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/icons/icon-96x96.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/academy/academy.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/academy/academy.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/academy/debugging_projects.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/academy/debugging_projects.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/academy/delete_production.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/academy/delete_production.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/academy/delete_staging.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/academy/delete_staging.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/academy/dictionary_blocks.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/academy/dictionary_blocks.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/academy/events_table.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/academy/events_table.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/academy/extrinsics_table.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/academy/extrinsics_table.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/academy/node_inspect.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/academy/node_inspect.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/academy/specversion_table.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/academy/specversion_table.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/add_network.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/add_network.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/ambassador_banner.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/ambassador_banner.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/architects.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/architects.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/arrow.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/build/directory_stucture.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/build/directory_stucture.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/build/genesis-hash.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/build/genesis-hash.jpg -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/build/graph.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/build/graph.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/build/graph_comparison.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/build/graph_comparison.jpg -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/build/logging_debug.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/build/logging_debug.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/build/multi_chain.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/build/multi_chain.jpg -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/build/multi_chain_publish.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/build/multi_chain_publish.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/build/project-scaffold-evm.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/build/project-scaffold-evm.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/build/schema_docstring.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/build/schema_docstring.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/build/subquery_logging.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/build/subquery_logging.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/build/tf-fail-summary.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/build/tf-fail-summary.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/build/tf-fail-test.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/build/tf-fail-test.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/build/tf-pass-test.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/build/tf-pass-test.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/choose_account.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/choose_account.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/faqIcon.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/glossary/terminology.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/glossary/terminology.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/home/indexer-sdk.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/home/indexer-sdk.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/home/subquery-network.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/home/subquery-network.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/logo.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/nag-circle.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/architect_manage_project.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/architect_manage_project.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/architect_manage_project_deploy.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/architect_manage_project_deploy.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/architect_publish.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/architect_publish.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/architect_publish_ipfs.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/architect_publish_ipfs.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/bridge.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/bridge.jpg -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/bridge_polygon_token_1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/bridge_polygon_token_1.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/bridge_polygon_token_2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/bridge_polygon_token_2.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/claim_connect_wallet.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/claim_connect_wallet.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/claim_page.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/claim_page.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/claim_page_tokens.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/claim_page_tokens.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/claim_redeem.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/claim_redeem.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/claim_unknown_error.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/claim_unknown_error.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/claim_wrong_network.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/claim_wrong_network.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/cobb_douglas.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/cobb_douglas.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/consumer_billing_account.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/consumer_billing_account.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/consumer_billing_account_action.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/consumer_billing_account_action.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/consumer_boosting_1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/consumer_boosting_1.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/consumer_boosting_2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/consumer_boosting_2.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/consumer_boosting_3.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/consumer_boosting_3.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/consumer_boosting_manage.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/consumer_boosting_manage.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/consumer_flex_plan.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/consumer_flex_plan.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/consumer_get_endpoint_1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/consumer_get_endpoint_1.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/consumer_get_endpoint_2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/consumer_get_endpoint_2.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/consumer_get_endpoint_3.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/consumer_get_endpoint_3.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/consumer_get_endpoint_4.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/consumer_get_endpoint_4.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/delegate_action.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/delegate_action.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/delegate_cannot.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/delegate_cannot.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/delegate_indexers.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/delegate_indexers.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/delegate_status.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/delegate_status.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/delegate_undelegate.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/delegate_undelegate.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/ether_on_base.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/ether_on_base.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/flex-plan-create.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/flex-plan-create.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/flex-plan-update.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/flex-plan-update.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/flex-plan.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/flex-plan.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/grafana_query_count.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/grafana_query_count.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/grafana_query_stats.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/grafana_query_stats.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/indexer-excellency.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/indexer-excellency.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/indexer_controller_account.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/indexer_controller_account.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/indexer_controller_account_added.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/indexer_controller_account_added.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/indexer_controller_add.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/indexer_controller_add.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/indexer_docker_compose_v2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/indexer_docker_compose_v2.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/indexer_docker_services.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/indexer_docker_services.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/indexer_endpoint_invalid.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/indexer_endpoint_invalid.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/indexer_endpoint_valid.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/indexer_endpoint_valid.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/indexer_eof_error_client_connection_troubleshooting.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/indexer_eof_error_client_connection_troubleshooting.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/indexer_icr.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/indexer_icr.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/indexer_icr_change.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/indexer_icr_change.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/indexer_metadata_update.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/indexer_metadata_update.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/indexer_project_add.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/indexer_project_add.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/indexer_project_announce.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/indexer_project_announce.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/indexer_project_deployment_id_error.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/indexer_project_deployment_id_error.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/indexer_project_indexing.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/indexer_project_indexing.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/indexer_project_ready.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/indexer_project_ready.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/indexer_project_remove.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/indexer_project_remove.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/indexer_project_restart.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/indexer_project_restart.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/indexer_project_start_indexing.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/indexer_project_start_indexing.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/indexer_project_stop.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/indexer_project_stop.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/indexer_project_stop_indexing.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/indexer_project_stop_indexing.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/indexer_registration.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/indexer_registration.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/indexer_service_logs.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/indexer_service_logs.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/indexer_setup_connect_node.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/indexer_setup_connect_node.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/indexer_setup_distributed.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/indexer_setup_distributed.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/indexer_setup_distributed_2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/indexer_setup_distributed_2.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/indexer_stake_add.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/indexer_stake_add.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/indexer_stake_manage.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/indexer_stake_manage.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/indexer_stake_manage_add.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/indexer_stake_manage_add.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/indexer_stake_manage_over_allocated.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/indexer_stake_manage_over_allocated.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/indexer_sync_coordinator.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/indexer_sync_coordinator.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/indexer_topology.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/indexer_topology.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/join-network.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/join-network.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/kSQT_add_wallet.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/kSQT_add_wallet.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/plans.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/plans.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/plans_empty.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/plans_empty.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/plans_price.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/plans_price.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/plans_template_select.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/plans_template_select.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/profile_rewards.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/profile_rewards.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/profile_withdrawls.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/profile_withdrawls.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/reward_pools.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/reward_pools.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/rpc_connect_node.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/rpc_connect_node.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/rpc_project_add.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/rpc_project_add.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/service_agreement.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/service_agreement.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/sqt.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/sqt.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/swap.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/swap.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/technical_stack.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/technical_stack.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/token_allocation.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/token_allocation.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/token_economy.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/token_economy.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/network/vesting_schedule.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/network/vesting_schedule.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/new-evm-chain-support.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/new-evm-chain-support.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/plus-circle.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/run_publish/bigquery/consoleBigquery.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/run_publish/bigquery/consoleBigquery.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/run_publish/graphql_aggregation.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/run_publish/graphql_aggregation.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/run_publish/historic_indexing.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/run_publish/historic_indexing.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/run_publish/integration_ecosystem.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/run_publish/integration_ecosystem.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/run_publish/metabase/metabase-database-connection.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/run_publish/metabase/metabase-database-connection.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/run_publish/metabase/metabaseLiquidityByPoolsQuery.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/run_publish/metabase/metabaseLiquidityByPoolsQuery.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/run_publish/metabase/metabaseLiquidityByPoolsQuerySQL.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/run_publish/metabase/metabaseLiquidityByPoolsQuerySQL.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/run_publish/metabase/metabaseLiquidityByPoolsResult.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/run_publish/metabase/metabaseLiquidityByPoolsResult.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/run_publish/metabase/metabaseSwapCountByHourQuery.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/run_publish/metabase/metabaseSwapCountByHourQuery.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/run_publish/metabase/metabaseSwapCountByHourResultLineGraph.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/run_publish/metabase/metabaseSwapCountByHourResultLineGraph.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/run_publish/metabase/metabaseSwapCountByHourResultPieChart.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/run_publish/metabase/metabaseSwapCountByHourResultPieChart.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/run_publish/monitoring.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/run_publish/monitoring.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/run_publish/project_auth_request.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/run_publish/project_auth_request.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/run_publish/project_auth_revoke.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/run_publish/project_auth_revoke.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/run_publish/project_created.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/run_publish/project_created.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/run_publish/projects_account_switcher.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/run_publish/projects_account_switcher.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/run_publish/projects_create.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/run_publish/projects_create.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/run_publish/projects_dashboard.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/run_publish/projects_dashboard.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/run_publish/projects_deploy_sync.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/run_publish/projects_deploy_sync.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/run_publish/projects_explorer.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/run_publish/projects_explorer.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/run_publish/projects_first_deployment.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/run_publish/projects_first_deployment.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/run_publish/projects_staging_slot.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/run_publish/projects_staging_slot.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/run_publish/query.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/run_publish/query.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/select_account.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/select_account.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/switch_networks.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/switch_networks.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/wantMoreDepthBg.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/wantMoreDepthBg.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/welcomeBanner.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/welcomeBanner.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/img/welcome_to_subquery_projects.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/img/welcome_to_subquery_projects.png -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/pdf/Account_Balances.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/pdf/Account_Balances.pdf -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/pdf/Account_Transfer_with_Reverse_Lookups.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/pdf/Account_Transfer_with_Reverse_Lookups.pdf -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/pdf/Account_Transfers.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/pdf/Account_Transfers.pdf -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/pdf/Council_Proposal.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/pdf/Council_Proposal.pdf -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/pdf/Deploying_Subquery_Project.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/pdf/Deploying_Subquery_Project.pdf -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/pdf/Hello_World_Lab.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/pdf/Hello_World_Lab.pdf -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/pdf/SubQuery_201_Lab_List_All_Transaction.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/pdf/SubQuery_201_Lab_List_All_Transaction.pdf -------------------------------------------------------------------------------- /docs/.vuepress/public/assets/pdf/Sum_Rewards.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Zikc2023/documentation/4c100f7dd6f97ef09814877bbced320d86a82501/docs/.vuepress/public/assets/pdf/Sum_Rewards.pdf -------------------------------------------------------------------------------- /docs/.vuepress/styles/palette.scss: -------------------------------------------------------------------------------- 1 | $theme-color: #4388dd; 2 | $primary-color: $theme-color; 3 | 4 | $bg-color: #060f32; 5 | $bg-color-secondary: #1b2545; 6 | $text-color: #fff; 7 | $border-color: #34414b; 8 | $border-color-dark: #34414b; 9 | 10 | $navbar-height: 80px; 11 | $navbar-horizontal-padding: 24px; 12 | $navbar-vertical-padding: 16px; 13 | 14 | $font-family: '"Inter", Arial, sans-serif'; 15 | $font-family-heading: '"Futura", Arial, sans-serif'; 16 | -------------------------------------------------------------------------------- /docs/indexer/academy/moonbeam_course/lesson1.md: -------------------------------------------------------------------------------- 1 | # Lesson 1: SubQuery and Moonbeam Integration 2 | 3 | This lesson discusses what problems dApp devs are currently facing and how SubQuery helps overcoming them. This lesson also explores SubQuery and Moonbeam integration in detail. 4 | 5 |
6 |
7 | 8 |
9 | 10 | ## Useful resources: 11 | 12 | - [SubQuery Project Explorer](https://explorer.subquery.network/) 13 | - [Website](https://subquery.network/) 14 | - [Discord](https://discord.com/invite/subquery) 15 | - [Quick Start Guide](../../quickstart/quickstart.md) 16 | - [YouTube Channel](https://www.youtube.com/c/SubQueryNetwork) 17 | -------------------------------------------------------------------------------- /docs/indexer/academy/tutorials_examples/batch-size.md: -------------------------------------------------------------------------------- 1 | # How to change the blockchain fetching batch size? 2 | 3 | ## Video guide 4 | 5 |
6 |
7 | 8 |
9 | 10 | ## Introduction 11 | 12 | The default batch size is 100, but this can be changed by using the extra command `--batch-size=xx`. 13 | 14 | You need to this to the command line as an extra flag or if you are using Docker, modify the `docker-compose.yml` with: 15 | 16 | ```shell 17 | subquery-node: 18 | image: onfinality/subql-node:latest 19 | depends_on: 20 | - "postgres" 21 | restart: always 22 | environment: 23 | DB_USER: postgres 24 | DB_PASS: postgres 25 | DB_DATABASE: postgres 26 | DB_HOST: postgres 27 | DB_PORT: 5432 28 | volumes: 29 | - ./:/app 30 | command: 31 | - -f=/app 32 | - --local 33 | - --batch-size=50 34 | 35 | ``` 36 | 37 | This example sets the batch size to 50. 38 | 39 | ## Why change the batch size? 40 | 41 | Using a smaller batch size can reduce memory usage and not leave users hanging for large queries. In otherwords, your application can be more responsive. 42 | -------------------------------------------------------------------------------- /docs/indexer/academy/tutorials_examples/terminology.md: -------------------------------------------------------------------------------- 1 | # Terminology 2 | 3 | - **SubQuery Project** (_where the magic happens_): A definition ([`@subql/cli`](https://www.npmjs.com/package/@subql/cli)) of how a SubQuery Node should traverse and aggregate a projects network and how the data should be transformed and stored to enable useful GraphQL queries. 4 | - **SubQuery Node** (_where the work is done_): A package ([`@subql/node`](https://www.npmjs.com/package/@subql/node)) that will accept a SubQuery project definiton, and run a node that constantly indexes a connected network to a database. 5 | - **SubQuery Query Service** (_where we get the data from_): A package ([`@subql/query`](https://www.npmjs.com/package/@subql/query)) that interacts with the GraphQL API of a deployed SubQuery node to query and view the indexed data. 6 | - **GraphQL** (_how we query the data_): A query langage for APIs that is specifically suited for flexible graph based data - see [graphql.org](https://graphql.org/learn/). 7 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/quickstart_multichain/snippets/multi-chain-cosmos-manifest-intro.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | The Multichain project contains multiple manifest files, with support for the following handlers: 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | The Multichain project contains multiple manifest files, with support for the following handlers: 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | The Multichain project contains multiple manifest files, with support for the following handlers: 26 | 27 | 28 | 29 | 30 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/quickstart_multichain/snippets/multi-chain-cosmos-quickstart-reference.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | If you are new to SubQuery, we recommend starting your learning journey with single-chain examples, such as the [Osmosis](../../quickstart_chains/cosmos-osmosis.md) example. 4 | ::: 5 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/quickstart_multichain/snippets/multi-chain-creation.md: -------------------------------------------------------------------------------- 1 | Then, create a [multi-chain manifest file](../../build/multi-chain#1-create-a-multi-chain-manifest-file). After, following the steps outlined [here](../../build/multi-chain#3-add-a-new-network-to-the-multi-chain-manifest), start adding the new networks. After you successfuly apply the correct entities for each chain, you will end up with a single `subquery-multichain.yaml` file that we'll map to the individual chain manifest files. This multi-chain manifest file will look something like this: 2 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/quickstart_multichain/snippets/multi-chain-evm-manifest-intro.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | The Multichain project contains multiple manifest files, with support for the following handlers: 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | The Multichain project contains multiple manifest files, with support for the following handlers: 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | The Multichain project contains multiple manifest files, with support for the following handlers: 26 | 27 | 28 | 29 | 30 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/quickstart_multichain/snippets/multi-chain-network-origin-note.md: -------------------------------------------------------------------------------- 1 | As evident from the examples above, we employ various handlers for different chains, while keeping the indexed event logs the same. This approach is adopted to facilitate the identification of the originating network for each specific event (refer to this [tip](../../build/multi-chain#handling-network-specific-logic)). This strategy will prove beneficial later, as it allows us to incorporate a `network` field into the entities. This will simplify the execution of filtering, aggregation, and other data manipulation tasks. 2 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/quickstart_multichain/snippets/multi-chain-quickstart-reference.md: -------------------------------------------------------------------------------- 1 | ::: warning Important 2 | **This project operates across multiple chains, making it more complex than other single chain examples.** 3 | 4 | ::: 5 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/arbitrum-manifest-note.md: -------------------------------------------------------------------------------- 1 | Check out our [Manifest File](../../build/manifest/arbitrum.md) documentation to get more information about the Project Manifest (`project.ts`) file. 2 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/arbitrum-mapping-note.md: -------------------------------------------------------------------------------- 1 | Check out our [Mappings](../../build/mapping/arbitrum.md) documentation to get more information about the Project Manifest (`project.ts`) file. 2 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/avalanche-manifest-note.md: -------------------------------------------------------------------------------- 1 | Check out our [Manifest File](../../build/manifest/avalanche.md) documentation to get more information about the Project Manifest (`project.ts`) file. 2 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/avalanche-mapping-note.md: -------------------------------------------------------------------------------- 1 | Check out our [Mappings](../../build/mapping/avalanche.md) documentation to get more information about the Project Manifest (`project.ts`) file. 2 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/bsc-manifest-note.md: -------------------------------------------------------------------------------- 1 | Check out our [Manifest File](../../build/manifest/gnosis.md) documentation to get more information about the Project Manifest (`project.ts`) file. 2 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/bsc-mapping-note.md: -------------------------------------------------------------------------------- 1 | ::: tip Note 2 | For more information on mapping functions, please refer to our [Mappings](../../build/mapping/gnosis.md) documentation. 3 | ::: 4 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/build.md: -------------------------------------------------------------------------------- 1 | ## Build Your Project 2 | 3 | Next, build your work to run your new SubQuery project. Run the build command from the project's root directory as given here: 4 | 5 | ::: code-tabs 6 | @tab:active yarn 7 | 8 | ```shell 9 | yarn build 10 | ``` 11 | 12 | @tab npm 13 | 14 | ```shell 15 | npm run-script build 16 | ``` 17 | 18 | ::: 19 | 20 | ::: warning Important 21 | Whenever you make changes to your mapping functions, you must rebuild your project. 22 | ::: 23 | 24 | Now, you are ready to run your first SubQuery project. Let’s check out the process of running your project in detail. 25 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/codegen.md: -------------------------------------------------------------------------------- 1 | ::: code-tabs 2 | @tab:active yarn 3 | 4 | ```shell 5 | yarn codegen 6 | ``` 7 | 8 | @tab npm 9 | 10 | ```shell 11 | npm run-script codegen 12 | ``` 13 | 14 | ::: 15 | 16 | This action will generate a new directory (or update the existing one) named `src/types`. Inside this directory, you will find automatically generated entity classes corresponding to each type defined in your `schema.graphql`. These classes facilitate type-safe operations for loading, reading, and writing entity fields. You can learn more about this process in [the GraphQL Schema section](../../build/graphql.md). 17 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/cosmos-codegen.md: -------------------------------------------------------------------------------- 1 | SubQuery simplifies and ensures type-safety when working with GraphQL entities, actions, and transactions. 2 | 3 | 4 | 5 | If you've expressed a preference to employ the Cosmos message based on the provided proto files, this command will also generate types for your listed protobufs and save them into `src/types` directory, providing you with more typesafety. For example, you can find Osmosis' protobuf definitions in the [official documentation](https://docs.osmosis.zone/apis/grpc#grpcurl). Read about how this is done in [Cosmos Codegen from CosmWasm Protobufs](../../build/introduction.md#cosmos-codegen-from-cosmwasm-protobufs) and [Cosmos Manifest File Configuration](../../build/manifest/cosmos.md#chain-types). 6 | 7 | Now that you have made essential changes to the GraphQL Schema file, let’s go ahead with the next configuration. 8 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/cosmos-handlers.md: -------------------------------------------------------------------------------- 1 | - [BlockHanders](../../build/manifest/cosmos.md#mapping-handlers-and-filters): On each and every block, run a mapping function 2 | - [TransactionHandlers](../../build/manifest/cosmos.md#mapping-handlers-and-filters): On each and every transaction, run a mapping function 3 | - [MessageHandlers](../../build/manifest/cosmos.md#mapping-handlers-and-filters): On each and every message that matches optional filter criteria, run a mapping function 4 | - [EventHanders](../../build/manifest/cosmos.md#mapping-handlers-and-filters): On each and every event that matches optional filter criteria, run a mapping function 5 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/cosmos-manifest-intro.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | For Cosmos chains, there are four types of mapping handlers (and you can have more than one in each project): 6 | 7 | 8 | 9 | Note that the manifest file has already been set up correctly and doesn’t require significant changes, but you need to change the datasource handlers. This section lists the triggers that the manifest file looks for on the blockchain to start indexing. 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | For Cosmos chains, there are four types of mapping handlers (and you can have more than one in each project): 18 | 19 | 20 | 21 | Note that the manifest file has already been set up correctly and doesn’t require significant changes, but you need to change the datasource handlers. This section lists the triggers that the manifest file looks for on the blockchain to start indexing. 22 | 23 | 24 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/cosmos-manifest-note.md: -------------------------------------------------------------------------------- 1 | Check out our [Manifest File](../../build/manifest/cosmos.md) documentation to get more information about the Project Manifest (`project.ts`) file. 2 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/cosmos-mapping-intro.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | ::: tip Note 6 | Check out our [Mappings](../../build/mapping/cosmos.md) documentation to get more information on mapping functions. 7 | ::: 8 | 9 | Navigate to the default mapping function in the `src/mappings` directory. Setting up mappings for this the Cosmos chains is straightforward. In this instance, the mappings are stored within the `src/mappings` directory, with the sole mapping file being `mappingHandlers.ts`. Now, let's take a closer look at it: 10 | 11 | 12 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/cosmos-mapping-note.md: -------------------------------------------------------------------------------- 1 | Check out our [Mappings](../../build/mapping/cosmos.md) documentation and get information on the mapping functions in detail. 2 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/cosmos-quickstart-reference.md: -------------------------------------------------------------------------------- 1 | ::: info 2 | 3 | This network is based on the Cosmos SDK, which means you can index chain data via the standard Cosmos RPC interface. 4 | 5 | Before we begin, make sure that you have initialised your project using the provided steps in the **[Start Here](../quickstart.md)** section. You must complete the suggested [4 steps](https://github.com/subquery/cosmos-subql-starter#readme) for Cosmos users. 6 | 7 | ::: 8 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/ethereum-manifest-note.md: -------------------------------------------------------------------------------- 1 | ::: tip Note 2 | 3 | Check out our [Manifest File](../../build/manifest/ethereum.md) documentation to get more information about the Project Manifest (`project.ts`) file. 4 | ::: 5 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/ethereum-mapping-note.md: -------------------------------------------------------------------------------- 1 | ::: tip Note 2 | For more information on mapping functions, please refer to our [Mappings](../../build/mapping/ethereum.md) documentation. 3 | ::: 4 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/evm-abi.md: -------------------------------------------------------------------------------- 1 | As you're creating a new Etheruem based project, this command will also generate ABI types and save them into `src/types` using the `npx typechain --target=ethers-v5` command, allowing you to bind these contracts to specific addresses in the mappings and call read-only contract methods against the block being processed. 2 | 3 | It will also generate a class for every contract event to provide easy access to event parameters, as well as the block and transaction the event originated from. Read about how this is done in [EVM Codegen from ABIs](../../build/introduction.md#evm-codegen-from-abis). 4 | 5 | All of these types are written to `src/types/abi-interfaces` and `src/types/contracts` directories. In this example project, you would import these types like so. 6 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/evm-codegen.md: -------------------------------------------------------------------------------- 1 | SubQuery simplifies and ensures type-safety when working with GraphQL entities, smart contracts, events, transactions, and logs. The SubQuery CLI will generate types based on your project's GraphQL schema and any contract ABIs included in the data sources. 2 | 3 | 4 | 5 | It will also generate a class for every contract event, offering convenient access to event parameters, as well as information about the block and transaction from which the event originated. You can find detailed information on how this is achieved in the [EVM Codegen from ABIs](../../build/introduction.md#evm-codegen-from-abis) section. All of these types are stored in the `src/types/abi-interfaces` and `src/types/contracts` directories. 6 | 7 | You can conveniently import all these types: 8 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/evm-handlers.md: -------------------------------------------------------------------------------- 1 | - [BlockHanders](../../build/manifest/ethereum.md#mapping-handlers-and-filters): On each and every block, run a mapping function 2 | - [TransactionHandlers](../../build/manifest/ethereum.md#mapping-handlers-and-filters): On each and every transaction that matches optional filter criteria, run a mapping function 3 | - [LogHanders](../../build/manifest/ethereum.md#mapping-handlers-and-filters): On each and every log that matches optional filter criteria, run a mapping function 4 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/evm-manifest-intro.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | For EVM chains, there are three types of mapping handlers (and you can have more than one in each project): 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | For EVM chains, there are three types of mapping handlers (and you can have more than one in each project): 16 | 17 | 18 | 19 | 20 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/evm-mapping-intro.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | ::: tip Note 6 | Check out our [Manifest File](../../build/manifest/ethereum.md) documentation to get more information about the Project Manifest (`project.ts`) file. 7 | ::: 8 | 9 | Navigate to the default mapping function in the `src/mappings` directory. Setting up mappings for this the Cosmos chains is straightforward. In this instance, the mappings are stored within the `src/mappings` directory, with the sole mapping file being `mappingHandlers.ts`. Now, let's take a closer look at it: 10 | 11 | 12 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/evm-quickstart-reference-abi-scaffold.md: -------------------------------------------------------------------------------- 1 | As a prerequisite, you will need to generate types from the ABI files of each smart contract. Additionally, you can kickstart your project by using the EVM Scaffolding approach (detailed [here](../quickstart.md#evm-project-scaffolding)). You'll find all the relevant events to be scaffolded in the documentation for each type of smart contract. 2 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/evm-quickstart-reference.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/final-code.md: -------------------------------------------------------------------------------- 1 | Not included 2 | 3 | 4 | 5 | ::: tip 6 | The final code of this project can be found here: 7 | 8 | 9 | 10 | 11 | 12 | ::: 13 | 14 | 15 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/flare-manifest-note.md: -------------------------------------------------------------------------------- 1 | Check out our [Manifest File](../../build/manifest/flare.md) documentation to get more information about the Project Manifest (`project.ts`) file. 2 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/flare-mapping-note.md: -------------------------------------------------------------------------------- 1 | ::: tip Note 2 | For more information on mapping functions, please refer to our [Mappings](../../build/mapping/flare.md) documentation. 3 | ::: 4 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/gnosis-manifest-note.md: -------------------------------------------------------------------------------- 1 | Check out our [Manifest File](../../build/manifest/gnosis.md) documentation to get more information about the Project Manifest (`project.ts`) file. 2 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/gnosis-mapping-note.md: -------------------------------------------------------------------------------- 1 | ::: tip Note 2 | For more information on mapping functions, please refer to our [Mappings](../../build/mapping/gnosis.md) documentation. 3 | ::: 4 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/gravatar-note.md: -------------------------------------------------------------------------------- 1 | ::: warning Important 2 | We suggest starting with the [Ethereum Gravatar example](./ethereum-gravatar). The Ethereum PancakeSwap project is a lot more complicated and introduces some more advanced concepts 3 | ::: 4 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/manifest-intro.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | ## Your Project Manifest File 4 | 5 | The Project Manifest file is an entry point to your project. It defines most of the details on how SubQuery will index and transform the chain data. 6 | 7 | 8 | 9 | 10 | 11 | #### Your Project Manifest File 12 | 13 | The Project Manifest file is an entry point to your project. It defines most of the details on how SubQuery will index and transform the chain data. 14 | 15 | 16 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/mapping-intro.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | ## Add a Mapping Function 4 | 5 | Mapping functions define how blockchain data is transformed into the optimised GraphQL entities that we previously defined in the `schema.graphql` file. 6 | 7 | 8 | 9 | 10 | 11 | #### Add a Mapping Function 12 | 13 | Mapping functions define how blockchain data is transformed into the optimised GraphQL entities that we previously defined in the `schema.graphql` file. 14 | 15 | 16 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/near-codegen.md: -------------------------------------------------------------------------------- 1 | SubQuery simplifies and ensures type-safety when working with GraphQL entities, actions, and transactions. 2 | 3 | 4 | 5 | Now that you have made essential changes to the GraphQL Schema file, let’s move forward to the next file. 6 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/near-handlers.md: -------------------------------------------------------------------------------- 1 | - [BlockHandler](../../build/manifest/near.md#mapping-handlers-and-filters): On each and every block, run a mapping function 2 | - [TransactionHandlers](../../build/manifest/near.md#mapping-handlers-and-filters): On each and every transaction that matches optional filter criteria, run a mapping function 3 | - [ActionHandlers](../../build/manifest/near.md#mapping-handlers-and-filters): On each and every transaction action that matches optional filter criteria, run a mapping function 4 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/near-manifest-intro.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | For NEAR, there are three types of mapping handlers (and you can have more than one in each project): 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | For NEAR, there are three types of mapping handlers (and you can have more than one in each project): 16 | 17 | 18 | 19 | 20 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/near-manifest-note.md: -------------------------------------------------------------------------------- 1 | Check out our [Manifest File](../../build/manifest/near.md) documentation to get more information about the Project Manifest (`project.ts`) file. 2 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/near-mapping-intro.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | ::: tip Note 4 | Check out our [Mappings](../../build/mapping/near.md) documentation to get more information on mapping functions. 5 | ::: 6 | 7 | Navigate to the default mapping function in the `src/mappings` directory. You will be able to see three exported functions: `handleBlock`, `handleAction`, and `handleAction`. Delete both the `handleBlock` and `handleAction` functions as you will only deal with the `handleAction` function. 8 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/near-mapping-note.md: -------------------------------------------------------------------------------- 1 | ::: tip Note 2 | For more information on mapping functions, please refer to our [Mappings](../../build/mapping/near.md) documentation. 3 | ::: 4 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/near-quickstart-reference.md: -------------------------------------------------------------------------------- 1 | Please initialise a NEAR Network project. Now, let's move forward and update these configurations. 2 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/note-on-entity-relationships.md: -------------------------------------------------------------------------------- 1 | ::: tip Note 2 | Importantly, these relationships can not only establish one-to-many connections but also extend to include many-to-many associations. To delve deeper into entity relationships, you can refer to [this section](../../build/graphql.md#entity-relationships). If you prefer a more example-based approach, our dedicated [Hero Course Module](../../academy/herocourse/module3.md) can provide further insights. 3 | ::: 4 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/polkadot-handlers.md: -------------------------------------------------------------------------------- 1 | - [BlockHanders](../../build/manifest/polkadot.md#mapping-handlers-and-filters): On each and every block, run a mapping function 2 | - [EventHandlers](../../build/manifest/polkadot.md#mapping-handlers-and-filters): On each and every Event that matches optional filter criteria, run a mapping function 3 | - [CallHanders](../../build/manifest/polkadot.md#mapping-handlers-and-filters): On each and every extrinsic call that matches optional filter criteria, run a mapping function 4 | 5 | Note that the manifest file has already been set up correctly and doesn’t require significant changes, but you need to change the datasource handlers. This section lists the triggers that look for on the blockchain to start indexing. 6 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/polkadot-manifest-intro.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | For Polkadot, there are three types of mapping handlers (and you can have more than one in each project): 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | For Polkadot, there are three types of mapping handlers (and you can have more than one in each project): 16 | 17 | 18 | 19 | 20 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/polkadot-manifest-note.md: -------------------------------------------------------------------------------- 1 | Check out our [Manifest File](../../build/manifest/polkadot.md) documentation to get more information about the Project Manifest (`project.ts`) file. 2 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/polkadot-mapping-note.md: -------------------------------------------------------------------------------- 1 | ::: tip Note 2 | For more information on mapping functions, please refer to our [Mappings](../../build/mapping/polkadot.md) documentation. 3 | ::: 4 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/polygon-manifest-note.md: -------------------------------------------------------------------------------- 1 | Check out our [Manifest File](../../build/manifest/polygon.md) documentation to get more information about the Project Manifest (`project.ts`) file. 2 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/polygon-mapping-note.md: -------------------------------------------------------------------------------- 1 | ::: tip Note 2 | For more information on mapping functions, please refer to our [Mappings](../../build/mapping/polygon.md) documentation. 3 | ::: 4 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/query-intro.md: -------------------------------------------------------------------------------- 1 | ## Query your Project 2 | 3 | Next, let's query our project. Follow these three simple steps to query your SubQuery project: 4 | 5 | 1. Open your browser and head to `http://localhost:3000`. 6 | 7 | 2. You will see a GraphQL playground in the browser and the schemas which are ready to query. 8 | 9 | 3. Find the _Docs_ tab on the right side of the playground which should open a documentation drawer. This documentation is automatically generated and it helps you find what entities and methods you can query. 10 | 11 | Try the following queries to understand how it works for your new SubQuery starter project. Don’t forget to learn more about the [GraphQL Query language](../../run_publish/query/graphql.md). 12 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/quickstart-reference.md: -------------------------------------------------------------------------------- 1 | In the earlier [Quickstart](../quickstart.md) section , you should have taken note of three crucial files. To initiate the setup of a project from scratch, you can proceed to follow the steps outlined in the [initialisation description](../quickstart.md#2-initialise-a-new-subquery-project). 2 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/run-locally.md: -------------------------------------------------------------------------------- 1 | Whenever you create a new SubQuery Project, first, you must run it locally on your computer and test it and using Docker is the easiest and quickiest way to do this. 2 | 3 | ## Run Your Project Locally with Docker 4 | 5 | The `docker-compose.yml` file defines all the configurations that control how a SubQuery node runs. For a new project, which you have just initialised, you won't need to change anything. 6 | 7 | However, visit the [Running SubQuery Locally](../../run_publish/run.md) to get more information on the file and the settings. 8 | 9 | Run the following command under the project directory: 10 | 11 | ::: code-tabs 12 | @tab:active yarn 13 | 14 | ```shell 15 | yarn start:docker 16 | ``` 17 | 18 | @tab npm 19 | 20 | ```shell 21 | npm run-script start:docker 22 | ``` 23 | 24 | ::: 25 | 26 | ::: tip Note 27 | It may take a few minutes to download the required images and start the various nodes and Postgres databases. 28 | ::: 29 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/schema-intro.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | ## Update Your GraphQL Schema File 4 | 5 | The `schema.graphql` file determines the shape of your data from SubQuery due to the mechanism of the GraphQL query language. Hence, updating the GraphQL Schema file is the perfect place to start. It allows you to define your end goal right at the start. 6 | 7 | 8 | 9 | 10 | 11 | #### Update Your GraphQL Schema File 12 | 13 | The `schema.graphql` file determines the shape of your data from SubQuery due to the mechanism of the GraphQL query language. Hence, updating the GraphQL Schema file is the perfect place to start. It allows you to define your end goal right at the start. 14 | 15 | 16 | 17 | 18 | 19 | #### Update Your GraphQL Schema File 20 | 21 | The `schema.graphql` file determines the shape of your data from SubQuery due to the mechanism of the GraphQL query language. Hence, updating the GraphQL Schema file is the perfect place to start. It allows you to define your end goal right at the start. 22 | 23 | 24 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/schema-note.md: -------------------------------------------------------------------------------- 1 | Check out the [GraphQL Schema](../../build/graphql.md) documentation to get in-depth information on `schema.graphql` file. 2 | 3 | Now that you have made essential changes to the GraphQL Schema file, let’s proceed ahead with the Mapping Function’s configuration. 4 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/stellar-codegen.md: -------------------------------------------------------------------------------- 1 | SubQuery simplifies and ensures type-safety when working with GraphQL entities, smart contracts, events, transactions, operation and effects. 2 | 3 | 4 | 5 | You can conveniently import all these types: 6 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/stellar-handlers.md: -------------------------------------------------------------------------------- 1 | - [BlockHandler](../../build/manifest/stellar.md#mapping-handlers-and-filters): On each and every block, run a mapping function 2 | - [TransactionHandlers](../../build/manifest/stellar.md#mapping-handlers-and-filters): On each and every Stellar/Soroban transaction that matches optional filter criteria, run a mapping function 3 | - [OperationHandler](../../build/manifest/stellar.md#mapping-handlers-and-filters): On each and every Stellar operation action that matches optional filter criteria, run a mapping function 4 | - [EffectHandler](../../build/manifest/stellar.md#mapping-handlers-and-filters): On each and every Stellar effect action that matches optional filter criteria, run a mapping function 5 | - [EventHandler](../../build/manifest/stellar.md#mapping-handlers-and-filters): On each and every Soroban event action that matches optional filter criteria, run a mapping function 6 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/stellar-manifest-intro.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | For Stellar, there are several types of mapping handlers (and you can have more than one in each project): 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | For Stellar, there are several types of mapping handlers (and you can have more than one in each project): 16 | 17 | 18 | 19 | 20 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/stellar-manifest-note.md: -------------------------------------------------------------------------------- 1 | ::: tip Note 2 | 3 | Check out our [Manifest File](../../build/manifest/stellar.md) documentation to get more information about the Project Manifest (`project.ts`) file. 4 | ::: 5 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/stellar-mapping-note.md: -------------------------------------------------------------------------------- 1 | ::: tip Note 2 | Check out our [Mappings](../../build/mapping/stellar.md) documentation to get more information on mapping functions. 3 | ::: 4 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/types-regeneration-warning.md: -------------------------------------------------------------------------------- 1 | ::: warning Important 2 | When you make any changes to the schema file, please ensure that you regenerate your types directory. 3 | ::: 4 | -------------------------------------------------------------------------------- /docs/indexer/quickstart/snippets/whats-next.md: -------------------------------------------------------------------------------- 1 | ## What's next? 2 | 3 | Congratulations! You have now a locally running SubQuery project that accepts GraphQL API requests for transferring data. 4 | 5 | ::: tip Tip 6 | 7 | Find out how to build a performant SubQuery project and avoid common mistakes in [Project Optimisation](../../build/optimisation.md). 8 | 9 | ::: 10 | 11 | Click [here](../../quickstart/whats-next.md) to learn what should be your **next step** in your SubQuery journey. 12 | -------------------------------------------------------------------------------- /docs/miscellaneous/branding.md: -------------------------------------------------------------------------------- 1 | # Branding Materials 2 | 3 | **All of SubQuery’s brand features are proprietary and we take our brand extremely seriously.** 4 | 5 | If you opt to use any trademarks, logos, designs, or other brand features, please carefully follow the guidelines here or reach out to us via social media for clarification. 6 | 7 | If in doubt, please ask! 8 | 9 | ## Exportable Figma File 10 | 11 | Our Figma file has a full collection of all brand assets (logos, fonts, colours, imagery etc) for export. 12 | 13 | [Figma - SubQuery Brand Resources](https://www.figma.com/file/AaCXaOcElrlbxq8fz39sJU/SubQuery-Brand-Resources?node-id=3%3A2) 14 | 15 | ## Brand Assets Package 16 | 17 | A smaller ZIP package of brand assets: [public_branding.zip](https://static.subquery.network/public_branding.zip). 18 | -------------------------------------------------------------------------------- /docs/subquery_network/consumers/faq.md: -------------------------------------------------------------------------------- 1 | # Frequently Asked Questions 2 | 3 | ## As a Consumer, can I select 1 Indexer or multiple Indexers? 4 | 5 | Depending on demand, there will often be multiple Indexers indexing a given SubQuery project and multiple RPC providers for each network. Consumers have the choice when deciding which Node Operator to make agreements with. Typically Consumers would select Node Operators from a combination of cost, reliability, and latency. Consumers could also incorporate automatic failover and read data from another Node Operator if the first one times out or is not responsive. 6 | 7 | ## What happens if a Node Operator goes offline? 8 | 9 | Unless a Closed Service Agreement is being used, and if there is more than one Data Indexer/RPC provider serving your SubQuery project, it would simply be a matter of switching to another Node Operator. The ideal scenario would be include strategies like alert monitoring to be notified of potential issues and intelligent routing and caching. 10 | -------------------------------------------------------------------------------- /docs/subquery_network/consumers/playground.md: -------------------------------------------------------------------------------- 1 | # Playground 2 | 3 | The Playground is a place where you can run readily available queries (from any of your purchased plans). You can directly run or test the GraphQL queries right in the playground and retrieve the data for analysis on an ad-hoc basis. 4 | 5 | Once you have purchased an offer using any of the above methods, head to `Plan & Offer`-> `My Service Agreements` tab. 6 | 7 | Under the `Ongoing` tab, you will see a list of service agreements for respective purchased plans. Select the playground of your preferred plan in the last column `Action`. 8 | 9 | ![Service Agreements](/assets/img/network/service_agreement.png) 10 | 11 | You will be redirected to a page, known as the Playground. 12 | 13 | You will then see a code that you can directly use as the query and get the chain data for your project. You can also modify this query as per your requirements and retrieve the data in the desired format. 14 | 15 | ::: tip Note 16 | You can visit the expired plan's service agreement under the `Expired` tab. 17 | ::: 18 | -------------------------------------------------------------------------------- /docs/subquery_network/data_node/run.md: -------------------------------------------------------------------------------- 1 | # Run a SubQuery Data Node 2 | 3 | Running SubQuery data nodes is the same as running the unforked nodes, but there is an additional option for exposing the new RPCs. You can find the documentation for [Geth](https://geth.ethereum.org/docs/getting-started) and [OP-Geth](https://docs.optimism.io/builders/node-operators/overview) 4 | 5 | ## Enabling Enhanced RPC Endpoints 6 | 7 | To enable the new RPCs, add the "subql" namespace to `--http.api` and `--ws.api` flags or in your `toml` config to enable these RPCs. E.g `--http.api="eth,net,web3,subql" --ws.api="eth,net,web3,subql"` or in the below `.toml` 8 | 9 | ```toml 10 | [Node] 11 | DataDir = "/mnt/eth-data/.ethereum/sepolia" 12 | IPCPath = "geth.ipc" 13 | HTTPHost = "" 14 | HTTPPort = 8545 15 | HTTPVirtualHosts = ["localhost"] 16 | HTTPModules = ["net", "web3", "eth", "subql"] 17 | AuthAddr = "localhost" 18 | AuthPort = 8551 19 | AuthVirtualHosts = ["localhost"] 20 | WSHost = "" 21 | WSPort = 8546 22 | WSModules = ["net", "web3", "eth", "subql"] 23 | GraphQLVirtualHosts = ["localhost"] 24 | BatchRequestLimit = 1000 25 | BatchResponseMaxSize = 25000000 26 | ``` 27 | -------------------------------------------------------------------------------- /docs/subquery_network/foundation.md: -------------------------------------------------------------------------------- 1 | # The SubQuery Foundation 2 | 3 | The SubQuery Foundation serves to manage and develop the SubQuery Network and its ecosystem. Its purpose is to foster and guide the development and growth of the SubQuery Network and provide support for users and developers to build their own SubQuery Projects. 4 | 5 | The SubQuery Foundation is the first step towards decentralising ownership over the SubQuery Network. 6 | 7 | You can read more about the SubQuery Foundation at its offical website [https://subquery.foundation](https://subquery.foundation). 8 | -------------------------------------------------------------------------------- /docs/subquery_network/introduction/era.md: -------------------------------------------------------------------------------- 1 | # The Era 2 | 3 | The SubQuery Network is oriented around a single constant heartbeat or period - this is called the **Era**. 4 | 5 | Currently the Era is 7 days ([confirm this on our network parameters page](../parameters.md)). The Era represents a period that many settings and actions within the SubQuery Network are orientated around including: 6 | 7 | - Network reward allocations are made at the end of an Era 8 | - The length of Plans are represented in a number of Era 9 | - Any re-staging or re-delegation actions will be queued up for the end of the Era 10 | - Changes to the Node Operator Commission Rate (NOCR) will be queued up for the end of the Era (or the subsequent Era in some cases) 11 | -------------------------------------------------------------------------------- /docs/subquery_network/node_operators/introduction.md: -------------------------------------------------------------------------------- 1 | ## Node Operators 2 | 3 | SubQuery has a commitment to expanding the SubQuery Network to decentralise both Data Indexers, as well as supercharging RPCs to address a much broader centralisation issue throughout Web3 infrastructure. The SubQuery network will see thousands of decentralised Indexers and RPC providers (together called Node Operators) simplify the data layer for a myriad of applications and use cases. 4 | 5 | ![The vision for SubQuery Network to encompass key web3 infrastructure components in a completely decentralised manner](/assets/img/network/technical_stack.png) 6 | 7 | ## Take the next step 8 | 9 | - [Learn how Node Operators are rewarded](./rewards.md) 10 | - [Follow the guide to become a Node Operator](./setup/becoming-a-node-operator.md) 11 | - [Delegate to a Node Operator instead](../delegators/delegating.md) 12 | -------------------------------------------------------------------------------- /docs/subquery_network/token/bridge.md: -------------------------------------------------------------------------------- 1 | # Bridging Tokens to Base 2 | 3 | Although SQT is an ERC20 token minted on Ethereum Mainnet, the SubQuery Network operates on the Base Network. You will need to bridge your tokens between these networks, thankfully this is quite straightforward. 4 | 5 | SubQuery provides an offical Bridge UI on our [offical Network App](https://app.subquery.network/bridge) that supports bridging from Eth -> Base (will will later add support for Base -> Eth). This allows you to bridge any free SQT from Ethereum to Base and is built using the same contracts and messaging protocols as the official [Base Bridge](https://bridge.base.org/deposit). 6 | 7 | ![Offical Bridge UI](/assets/img/network/bridge.jpg) 8 | 9 | ## Other Bridges 10 | 11 | The official bridge, [Base Bridge](https://bridge.base.org/deposit), does not yet support SubQuery and there are other [quicker third-party bridges](https://base.org/ecosystem?tag=bridge), for example [superbridge.app](https://superbridge.app/), SubQuery can't be responsible for the use of any third party bridges. 12 | -------------------------------------------------------------------------------- /package.json: -------------------------------------------------------------------------------- 1 | { 2 | "name": "subql-docs", 3 | "private": true, 4 | "scripts": { 5 | "build:serve": "http-server -a localhost docs/.vuepress/dist -o", 6 | "docs:dev": "cross-env NODE_OPTIONS=--max_old_space_size=4096 vuepress dev docs", 7 | "docs:build": "cross-env NODE_OPTIONS=--max_old_space_size=4096 vuepress build docs" 8 | }, 9 | "packageManager": "pnpm@8.10.2", 10 | "devDependencies": { 11 | "@vuepress/bundler-vite": "2.0.0-rc.8", 12 | "@vuepress/helper": "2.0.0-rc.15", 13 | "@vuepress/plugin-docsearch": "2.0.0-rc.19", 14 | "@vuepress/plugin-google-analytics": "2.0.0-rc.15", 15 | "@vuepress/plugin-register-components": "2.0.0-rc.21", 16 | "cross-env": "7.0.3", 17 | "http-server": "14.1.1", 18 | "vue": "^3.4.19", 19 | "vuepress": "2.0.0-rc.8", 20 | "vuepress-plugin-redirect": "2.0.0-rc.19", 21 | "vuepress-theme-hope": "2.0.0-rc.25" 22 | }, 23 | "dependencies": { 24 | "vue-router": "^4.3.0" 25 | } 26 | } 27 | --------------------------------------------------------------------------------