From 405cc644adf7c0b76a4e5e3b26c6710b63c40d14 Mon Sep 17 00:00:00 2001 From: Marcus Rein <64141593+marcusrein@users.noreply.github.com> Date: Fri, 21 Mar 2025 12:15:38 -0400 Subject: [PATCH 1/3] Add contract analyzer guide and update metadata --- .../src/pages/en/subgraphs/guides/_meta.js | 1 + .../en/subgraphs/guides/contract-analyzer.mdx | 103 ++++++++++++++++++ 2 files changed, 104 insertions(+) create mode 100644 website/src/pages/en/subgraphs/guides/contract-analyzer.mdx diff --git a/website/src/pages/en/subgraphs/guides/_meta.js b/website/src/pages/en/subgraphs/guides/_meta.js index e642f12ef11d..37e18bc51651 100644 --- a/website/src/pages/en/subgraphs/guides/_meta.js +++ b/website/src/pages/en/subgraphs/guides/_meta.js @@ -8,4 +8,5 @@ export default { enums: '', 'secure-api-keys-nextjs': '', polymarket: '', + 'contract-analyzer': '', } diff --git a/website/src/pages/en/subgraphs/guides/contract-analyzer.mdx b/website/src/pages/en/subgraphs/guides/contract-analyzer.mdx new file mode 100644 index 000000000000..22bc4ee94dae --- /dev/null +++ b/website/src/pages/en/subgraphs/guides/contract-analyzer.mdx @@ -0,0 +1,103 @@ +--- +title: Smart Contract Analysis with Cana CLI +--- + +# Cana CLI: Quick & Efficient Contract Analysis + +**Cana CLI** is a command-line tool that streamlines smart contract analysis across multiple EVM-compatible chains. + +## 📌 Key Features + +- Detect deployment blocks +- Verify source code +- Extract ABIs & event signatures +- Identify proxy and implementation contracts +- Support multiple chains + +## 🚀 Installation & Setup + +Install Cana globally using npm: + +```bash +npm install -g contract-analyzer +``` + +Set up a blockchain for analysis: + +```bash +cana setup +``` + +Provide the required block explorer API and block explorer endpoint URL details when prompted. + +Running `cana setup` creates a configuration file at `~/.contract-analyzer/config.json`. This file stores your block explorer API credentials, endpoint URLs, and chain selection preferences for future use. + +## 🍳 Usage + +### 🔹 Chain Selection + +Cana supports multiple EVM-compatible chains. + +List chains added with: + +```bash +cana chains +``` + +Then select a chain with: + +```bash +cana chains --switch +``` + +Once a chain is selected, all subsequent contract analases will continue on that chain. + +### 🔹 Basic Contract Analysis + +Analyze a contract with: + +```bash +cana analyze 0xContractAddress +``` + +or + +```bash +cana -a 0xContractAddress +``` + +This command displays essential contract information in the terminal using a clear, organized format. + +### 🔹 Understanding Output + +Cana organizes results into the terminal as well as into a structured directory when detailed contract data is successfully retrieved: + +``` +contracts-analyzed/ +└── ContractName_chainName_YYYY-MM-DD/ + ├── contract/ # Folder for individual contract files + ├── abi.json # Contract ABI + └── event-information.json # Event signatures and examples +``` + +### 🔹 Chain Management + +Add and manage chains: + +```bash +cana setup # Add a new chain +cana chains # List configured chains +cana chains -s # Swich chains. +``` + +## ⚠️ Troubleshooting + +- **Missing Data**: Ensure the contract address is correct, verified on the block explorer, and that your API key has the required permissions. + +## ✅ Requirements + +- Node.js v16+ +- npm v6+ +- Block explorer API keys + +Keep your contract analyses efficient and well-organized. 🚀 From c51ee0e5a47b5d34fbca044082bb40e06b2de79a Mon Sep 17 00:00:00 2001 From: Marcus Rein <64141593+marcusrein@users.noreply.github.com> Date: Fri, 21 Mar 2025 12:31:02 -0400 Subject: [PATCH 2/3] feat: add contract analyzer guide to subgraph documentation --- website/src/pages/en/subgraphs/guides/contract-analyzer.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/src/pages/en/subgraphs/guides/contract-analyzer.mdx b/website/src/pages/en/subgraphs/guides/contract-analyzer.mdx index 22bc4ee94dae..387c74dec54a 100644 --- a/website/src/pages/en/subgraphs/guides/contract-analyzer.mdx +++ b/website/src/pages/en/subgraphs/guides/contract-analyzer.mdx @@ -4,7 +4,7 @@ title: Smart Contract Analysis with Cana CLI # Cana CLI: Quick & Efficient Contract Analysis -**Cana CLI** is a command-line tool that streamlines smart contract analysis across multiple EVM-compatible chains. +**Cana CLI** is a command-line tool that streamlines helpful smart contract metadata analysis specific to subgraph development across multiple EVM-compatible chains. ## 📌 Key Features From 8f53fc849ebea588c8d8dcd99087e09318e6bed5 Mon Sep 17 00:00:00 2001 From: Idalith Bustos Date: Fri, 21 Mar 2025 16:29:10 -0700 Subject: [PATCH 3/3] Updating branch --- website/route-lockfile.txt | 462 +++++++++--------- .../src/pages/ar/subgraphs/guides/_meta.js | 1 + .../ar/subgraphs/guides/contract-analyzer.mdx | 103 ++++ .../src/pages/cs/subgraphs/guides/_meta.js | 1 + .../cs/subgraphs/guides/contract-analyzer.mdx | 103 ++++ .../src/pages/de/subgraphs/guides/_meta.js | 1 + .../de/subgraphs/guides/contract-analyzer.mdx | 103 ++++ .../en/subgraphs/guides/contract-analyzer.mdx | 76 +-- .../subgraphs/querying/graph-client/README.md | 2 +- .../subgraphs/querying/graph-client/live.md | 2 +- .../src/pages/es/subgraphs/guides/_meta.js | 1 + .../es/subgraphs/guides/contract-analyzer.mdx | 103 ++++ .../src/pages/fr/subgraphs/guides/_meta.js | 1 + .../fr/subgraphs/guides/contract-analyzer.mdx | 103 ++++ .../src/pages/hi/subgraphs/guides/_meta.js | 1 + .../hi/subgraphs/guides/contract-analyzer.mdx | 103 ++++ .../src/pages/it/subgraphs/guides/_meta.js | 1 + .../it/subgraphs/guides/contract-analyzer.mdx | 103 ++++ .../src/pages/ja/subgraphs/guides/_meta.js | 1 + .../ja/subgraphs/guides/contract-analyzer.mdx | 103 ++++ .../src/pages/ko/subgraphs/guides/_meta.js | 1 + .../ko/subgraphs/guides/contract-analyzer.mdx | 103 ++++ .../src/pages/mr/subgraphs/guides/_meta.js | 1 + .../mr/subgraphs/guides/contract-analyzer.mdx | 103 ++++ .../src/pages/nl/subgraphs/guides/_meta.js | 1 + .../nl/subgraphs/guides/contract-analyzer.mdx | 103 ++++ .../src/pages/pl/subgraphs/guides/_meta.js | 1 + .../pl/subgraphs/guides/contract-analyzer.mdx | 103 ++++ .../src/pages/pt/subgraphs/guides/_meta.js | 1 + .../pt/subgraphs/guides/contract-analyzer.mdx | 103 ++++ .../src/pages/ro/subgraphs/guides/_meta.js | 1 + .../ro/subgraphs/guides/contract-analyzer.mdx | 103 ++++ .../src/pages/ru/subgraphs/guides/_meta.js | 1 + .../ru/subgraphs/guides/contract-analyzer.mdx | 103 ++++ .../src/pages/sv/subgraphs/guides/_meta.js | 1 + .../sv/subgraphs/guides/contract-analyzer.mdx | 103 ++++ .../src/pages/tr/subgraphs/guides/_meta.js | 1 + .../tr/subgraphs/guides/contract-analyzer.mdx | 103 ++++ .../src/pages/uk/subgraphs/guides/_meta.js | 1 + .../uk/subgraphs/guides/contract-analyzer.mdx | 103 ++++ .../src/pages/ur/subgraphs/guides/_meta.js | 1 + .../ur/subgraphs/guides/contract-analyzer.mdx | 103 ++++ .../src/pages/vi/subgraphs/guides/_meta.js | 1 + .../vi/subgraphs/guides/contract-analyzer.mdx | 103 ++++ .../src/pages/zh/subgraphs/guides/_meta.js | 1 + .../zh/subgraphs/guides/contract-analyzer.mdx | 103 ++++ 46 files changed, 2451 insertions(+), 275 deletions(-) create mode 100644 website/src/pages/ar/subgraphs/guides/contract-analyzer.mdx create mode 100644 website/src/pages/cs/subgraphs/guides/contract-analyzer.mdx create mode 100644 website/src/pages/de/subgraphs/guides/contract-analyzer.mdx create mode 100644 website/src/pages/es/subgraphs/guides/contract-analyzer.mdx create mode 100644 website/src/pages/fr/subgraphs/guides/contract-analyzer.mdx create mode 100644 website/src/pages/hi/subgraphs/guides/contract-analyzer.mdx create mode 100644 website/src/pages/it/subgraphs/guides/contract-analyzer.mdx create mode 100644 website/src/pages/ja/subgraphs/guides/contract-analyzer.mdx create mode 100644 website/src/pages/ko/subgraphs/guides/contract-analyzer.mdx create mode 100644 website/src/pages/mr/subgraphs/guides/contract-analyzer.mdx create mode 100644 website/src/pages/nl/subgraphs/guides/contract-analyzer.mdx create mode 100644 website/src/pages/pl/subgraphs/guides/contract-analyzer.mdx create mode 100644 website/src/pages/pt/subgraphs/guides/contract-analyzer.mdx create mode 100644 website/src/pages/ro/subgraphs/guides/contract-analyzer.mdx create mode 100644 website/src/pages/ru/subgraphs/guides/contract-analyzer.mdx create mode 100644 website/src/pages/sv/subgraphs/guides/contract-analyzer.mdx create mode 100644 website/src/pages/tr/subgraphs/guides/contract-analyzer.mdx create mode 100644 website/src/pages/uk/subgraphs/guides/contract-analyzer.mdx create mode 100644 website/src/pages/ur/subgraphs/guides/contract-analyzer.mdx create mode 100644 website/src/pages/vi/subgraphs/guides/contract-analyzer.mdx create mode 100644 website/src/pages/zh/subgraphs/guides/contract-analyzer.mdx diff --git a/website/route-lockfile.txt b/website/route-lockfile.txt index 8e34d8b11b86..afcddca4a3cb 100644 --- a/website/route-lockfile.txt +++ b/website/route-lockfile.txt @@ -35,17 +35,6 @@ /ar/subgraphs/best-practices/pruning/ /ar/subgraphs/best-practices/timeseries/ /ar/subgraphs/billing/ -/ar/subgraphs/cookbook/arweave/ -/ar/subgraphs/cookbook/enums/ -/ar/subgraphs/cookbook/grafting/ -/ar/subgraphs/cookbook/near/ -/ar/subgraphs/cookbook/polymarket/ -/ar/subgraphs/cookbook/secure-api-keys-nextjs/ -/ar/subgraphs/cookbook/subgraph-composition-three-sources/ -/ar/subgraphs/cookbook/subgraph-composition/ -/ar/subgraphs/cookbook/subgraph-debug-forking/ -/ar/subgraphs/cookbook/subgraph-uncrashable/ -/ar/subgraphs/cookbook/transfer-to-the-graph/ /ar/subgraphs/developing/creating/advanced/ /ar/subgraphs/developing/creating/assemblyscript-mappings/ /ar/subgraphs/developing/creating/graph-ts/CHANGELOG/ @@ -66,6 +55,16 @@ /ar/subgraphs/developing/publishing/publishing-a-subgraph/ /ar/subgraphs/developing/subgraphs/ /ar/subgraphs/explorer/ +/ar/subgraphs/guides/arweave/ +/ar/subgraphs/guides/contract-analyzer/ +/ar/subgraphs/guides/enums/ +/ar/subgraphs/guides/grafting/ +/ar/subgraphs/guides/near/ +/ar/subgraphs/guides/polymarket/ +/ar/subgraphs/guides/secure-api-keys-nextjs/ +/ar/subgraphs/guides/subgraph-debug-forking/ +/ar/subgraphs/guides/subgraph-uncrashable/ +/ar/subgraphs/guides/transfer-to-the-graph/ /ar/subgraphs/querying/best-practices/ /ar/subgraphs/querying/distributed-systems/ /ar/subgraphs/querying/from-an-application/ @@ -122,17 +121,6 @@ /cs/subgraphs/best-practices/pruning/ /cs/subgraphs/best-practices/timeseries/ /cs/subgraphs/billing/ -/cs/subgraphs/cookbook/arweave/ -/cs/subgraphs/cookbook/enums/ -/cs/subgraphs/cookbook/grafting/ -/cs/subgraphs/cookbook/near/ -/cs/subgraphs/cookbook/polymarket/ -/cs/subgraphs/cookbook/secure-api-keys-nextjs/ -/cs/subgraphs/cookbook/subgraph-composition-three-sources/ -/cs/subgraphs/cookbook/subgraph-composition/ -/cs/subgraphs/cookbook/subgraph-debug-forking/ -/cs/subgraphs/cookbook/subgraph-uncrashable/ -/cs/subgraphs/cookbook/transfer-to-the-graph/ /cs/subgraphs/developing/creating/advanced/ /cs/subgraphs/developing/creating/assemblyscript-mappings/ /cs/subgraphs/developing/creating/graph-ts/CHANGELOG/ @@ -153,6 +141,16 @@ /cs/subgraphs/developing/publishing/publishing-a-subgraph/ /cs/subgraphs/developing/subgraphs/ /cs/subgraphs/explorer/ +/cs/subgraphs/guides/arweave/ +/cs/subgraphs/guides/contract-analyzer/ +/cs/subgraphs/guides/enums/ +/cs/subgraphs/guides/grafting/ +/cs/subgraphs/guides/near/ +/cs/subgraphs/guides/polymarket/ +/cs/subgraphs/guides/secure-api-keys-nextjs/ +/cs/subgraphs/guides/subgraph-debug-forking/ +/cs/subgraphs/guides/subgraph-uncrashable/ +/cs/subgraphs/guides/transfer-to-the-graph/ /cs/subgraphs/querying/best-practices/ /cs/subgraphs/querying/distributed-systems/ /cs/subgraphs/querying/from-an-application/ @@ -207,17 +205,6 @@ /de/subgraphs/best-practices/pruning/ /de/subgraphs/best-practices/timeseries/ /de/subgraphs/billing/ -/de/subgraphs/cookbook/arweave/ -/de/subgraphs/cookbook/enums/ -/de/subgraphs/cookbook/grafting/ -/de/subgraphs/cookbook/near/ -/de/subgraphs/cookbook/polymarket/ -/de/subgraphs/cookbook/secure-api-keys-nextjs/ -/de/subgraphs/cookbook/subgraph-composition-three-sources/ -/de/subgraphs/cookbook/subgraph-composition/ -/de/subgraphs/cookbook/subgraph-debug-forking/ -/de/subgraphs/cookbook/subgraph-uncrashable/ -/de/subgraphs/cookbook/transfer-to-the-graph/ /de/subgraphs/developing/creating/advanced/ /de/subgraphs/developing/creating/assemblyscript-mappings/ /de/subgraphs/developing/creating/graph-ts/CHANGELOG/ @@ -238,6 +225,16 @@ /de/subgraphs/developing/publishing/publishing-a-subgraph/ /de/subgraphs/developing/subgraphs/ /de/subgraphs/explorer/ +/de/subgraphs/guides/arweave/ +/de/subgraphs/guides/contract-analyzer/ +/de/subgraphs/guides/enums/ +/de/subgraphs/guides/grafting/ +/de/subgraphs/guides/near/ +/de/subgraphs/guides/polymarket/ +/de/subgraphs/guides/secure-api-keys-nextjs/ +/de/subgraphs/guides/subgraph-debug-forking/ +/de/subgraphs/guides/subgraph-uncrashable/ +/de/subgraphs/guides/transfer-to-the-graph/ /de/subgraphs/querying/best-practices/ /de/subgraphs/querying/distributed-systems/ /de/subgraphs/querying/from-an-application/ @@ -294,17 +291,6 @@ /en/subgraphs/best-practices/pruning/ /en/subgraphs/best-practices/timeseries/ /en/subgraphs/billing/ -/en/subgraphs/cookbook/arweave/ -/en/subgraphs/cookbook/enums/ -/en/subgraphs/cookbook/grafting/ -/en/subgraphs/cookbook/near/ -/en/subgraphs/cookbook/polymarket/ -/en/subgraphs/cookbook/secure-api-keys-nextjs/ -/en/subgraphs/cookbook/subgraph-composition-three-sources/ -/en/subgraphs/cookbook/subgraph-composition/ -/en/subgraphs/cookbook/subgraph-debug-forking/ -/en/subgraphs/cookbook/subgraph-uncrashable/ -/en/subgraphs/cookbook/transfer-to-the-graph/ /en/subgraphs/developing/creating/advanced/ /en/subgraphs/developing/creating/assemblyscript-mappings/ /en/subgraphs/developing/creating/graph-ts/CHANGELOG/ @@ -325,6 +311,16 @@ /en/subgraphs/developing/publishing/publishing-a-subgraph/ /en/subgraphs/developing/subgraphs/ /en/subgraphs/explorer/ +/en/subgraphs/guides/arweave/ +/en/subgraphs/guides/contract-analyzer/ +/en/subgraphs/guides/enums/ +/en/subgraphs/guides/grafting/ +/en/subgraphs/guides/near/ +/en/subgraphs/guides/polymarket/ +/en/subgraphs/guides/secure-api-keys-nextjs/ +/en/subgraphs/guides/subgraph-debug-forking/ +/en/subgraphs/guides/subgraph-uncrashable/ +/en/subgraphs/guides/transfer-to-the-graph/ /en/subgraphs/querying/best-practices/ /en/subgraphs/querying/distributed-systems/ /en/subgraphs/querying/from-an-application/ @@ -381,17 +377,6 @@ /es/subgraphs/best-practices/pruning/ /es/subgraphs/best-practices/timeseries/ /es/subgraphs/billing/ -/es/subgraphs/cookbook/arweave/ -/es/subgraphs/cookbook/enums/ -/es/subgraphs/cookbook/grafting/ -/es/subgraphs/cookbook/near/ -/es/subgraphs/cookbook/polymarket/ -/es/subgraphs/cookbook/secure-api-keys-nextjs/ -/es/subgraphs/cookbook/subgraph-composition-three-sources/ -/es/subgraphs/cookbook/subgraph-composition/ -/es/subgraphs/cookbook/subgraph-debug-forking/ -/es/subgraphs/cookbook/subgraph-uncrashable/ -/es/subgraphs/cookbook/transfer-to-the-graph/ /es/subgraphs/developing/creating/advanced/ /es/subgraphs/developing/creating/assemblyscript-mappings/ /es/subgraphs/developing/creating/graph-ts/CHANGELOG/ @@ -412,6 +397,16 @@ /es/subgraphs/developing/publishing/publishing-a-subgraph/ /es/subgraphs/developing/subgraphs/ /es/subgraphs/explorer/ +/es/subgraphs/guides/arweave/ +/es/subgraphs/guides/contract-analyzer/ +/es/subgraphs/guides/enums/ +/es/subgraphs/guides/grafting/ +/es/subgraphs/guides/near/ +/es/subgraphs/guides/polymarket/ +/es/subgraphs/guides/secure-api-keys-nextjs/ +/es/subgraphs/guides/subgraph-debug-forking/ +/es/subgraphs/guides/subgraph-uncrashable/ +/es/subgraphs/guides/transfer-to-the-graph/ /es/subgraphs/querying/best-practices/ /es/subgraphs/querying/distributed-systems/ /es/subgraphs/querying/from-an-application/ @@ -468,17 +463,6 @@ /fr/subgraphs/best-practices/pruning/ /fr/subgraphs/best-practices/timeseries/ /fr/subgraphs/billing/ -/fr/subgraphs/cookbook/arweave/ -/fr/subgraphs/cookbook/enums/ -/fr/subgraphs/cookbook/grafting/ -/fr/subgraphs/cookbook/near/ -/fr/subgraphs/cookbook/polymarket/ -/fr/subgraphs/cookbook/secure-api-keys-nextjs/ -/fr/subgraphs/cookbook/subgraph-composition-three-sources/ -/fr/subgraphs/cookbook/subgraph-composition/ -/fr/subgraphs/cookbook/subgraph-debug-forking/ -/fr/subgraphs/cookbook/subgraph-uncrashable/ -/fr/subgraphs/cookbook/transfer-to-the-graph/ /fr/subgraphs/developing/creating/advanced/ /fr/subgraphs/developing/creating/assemblyscript-mappings/ /fr/subgraphs/developing/creating/graph-ts/CHANGELOG/ @@ -499,6 +483,16 @@ /fr/subgraphs/developing/publishing/publishing-a-subgraph/ /fr/subgraphs/developing/subgraphs/ /fr/subgraphs/explorer/ +/fr/subgraphs/guides/arweave/ +/fr/subgraphs/guides/contract-analyzer/ +/fr/subgraphs/guides/enums/ +/fr/subgraphs/guides/grafting/ +/fr/subgraphs/guides/near/ +/fr/subgraphs/guides/polymarket/ +/fr/subgraphs/guides/secure-api-keys-nextjs/ +/fr/subgraphs/guides/subgraph-debug-forking/ +/fr/subgraphs/guides/subgraph-uncrashable/ +/fr/subgraphs/guides/transfer-to-the-graph/ /fr/subgraphs/querying/best-practices/ /fr/subgraphs/querying/distributed-systems/ /fr/subgraphs/querying/from-an-application/ @@ -555,17 +549,6 @@ /hi/subgraphs/best-practices/pruning/ /hi/subgraphs/best-practices/timeseries/ /hi/subgraphs/billing/ -/hi/subgraphs/cookbook/arweave/ -/hi/subgraphs/cookbook/enums/ -/hi/subgraphs/cookbook/grafting/ -/hi/subgraphs/cookbook/near/ -/hi/subgraphs/cookbook/polymarket/ -/hi/subgraphs/cookbook/secure-api-keys-nextjs/ -/hi/subgraphs/cookbook/subgraph-composition-three-sources/ -/hi/subgraphs/cookbook/subgraph-composition/ -/hi/subgraphs/cookbook/subgraph-debug-forking/ -/hi/subgraphs/cookbook/subgraph-uncrashable/ -/hi/subgraphs/cookbook/transfer-to-the-graph/ /hi/subgraphs/developing/creating/advanced/ /hi/subgraphs/developing/creating/assemblyscript-mappings/ /hi/subgraphs/developing/creating/graph-ts/CHANGELOG/ @@ -586,6 +569,16 @@ /hi/subgraphs/developing/publishing/publishing-a-subgraph/ /hi/subgraphs/developing/subgraphs/ /hi/subgraphs/explorer/ +/hi/subgraphs/guides/arweave/ +/hi/subgraphs/guides/contract-analyzer/ +/hi/subgraphs/guides/enums/ +/hi/subgraphs/guides/grafting/ +/hi/subgraphs/guides/near/ +/hi/subgraphs/guides/polymarket/ +/hi/subgraphs/guides/secure-api-keys-nextjs/ +/hi/subgraphs/guides/subgraph-debug-forking/ +/hi/subgraphs/guides/subgraph-uncrashable/ +/hi/subgraphs/guides/transfer-to-the-graph/ /hi/subgraphs/querying/best-practices/ /hi/subgraphs/querying/distributed-systems/ /hi/subgraphs/querying/from-an-application/ @@ -642,17 +635,6 @@ /it/subgraphs/best-practices/pruning/ /it/subgraphs/best-practices/timeseries/ /it/subgraphs/billing/ -/it/subgraphs/cookbook/arweave/ -/it/subgraphs/cookbook/enums/ -/it/subgraphs/cookbook/grafting/ -/it/subgraphs/cookbook/near/ -/it/subgraphs/cookbook/polymarket/ -/it/subgraphs/cookbook/secure-api-keys-nextjs/ -/it/subgraphs/cookbook/subgraph-composition-three-sources/ -/it/subgraphs/cookbook/subgraph-composition/ -/it/subgraphs/cookbook/subgraph-debug-forking/ -/it/subgraphs/cookbook/subgraph-uncrashable/ -/it/subgraphs/cookbook/transfer-to-the-graph/ /it/subgraphs/developing/creating/advanced/ /it/subgraphs/developing/creating/assemblyscript-mappings/ /it/subgraphs/developing/creating/graph-ts/CHANGELOG/ @@ -673,6 +655,16 @@ /it/subgraphs/developing/publishing/publishing-a-subgraph/ /it/subgraphs/developing/subgraphs/ /it/subgraphs/explorer/ +/it/subgraphs/guides/arweave/ +/it/subgraphs/guides/contract-analyzer/ +/it/subgraphs/guides/enums/ +/it/subgraphs/guides/grafting/ +/it/subgraphs/guides/near/ +/it/subgraphs/guides/polymarket/ +/it/subgraphs/guides/secure-api-keys-nextjs/ +/it/subgraphs/guides/subgraph-debug-forking/ +/it/subgraphs/guides/subgraph-uncrashable/ +/it/subgraphs/guides/transfer-to-the-graph/ /it/subgraphs/querying/best-practices/ /it/subgraphs/querying/distributed-systems/ /it/subgraphs/querying/from-an-application/ @@ -729,17 +721,6 @@ /ja/subgraphs/best-practices/pruning/ /ja/subgraphs/best-practices/timeseries/ /ja/subgraphs/billing/ -/ja/subgraphs/cookbook/arweave/ -/ja/subgraphs/cookbook/enums/ -/ja/subgraphs/cookbook/grafting/ -/ja/subgraphs/cookbook/near/ -/ja/subgraphs/cookbook/polymarket/ -/ja/subgraphs/cookbook/secure-api-keys-nextjs/ -/ja/subgraphs/cookbook/subgraph-composition-three-sources/ -/ja/subgraphs/cookbook/subgraph-composition/ -/ja/subgraphs/cookbook/subgraph-debug-forking/ -/ja/subgraphs/cookbook/subgraph-uncrashable/ -/ja/subgraphs/cookbook/transfer-to-the-graph/ /ja/subgraphs/developing/creating/advanced/ /ja/subgraphs/developing/creating/assemblyscript-mappings/ /ja/subgraphs/developing/creating/graph-ts/CHANGELOG/ @@ -760,6 +741,16 @@ /ja/subgraphs/developing/publishing/publishing-a-subgraph/ /ja/subgraphs/developing/subgraphs/ /ja/subgraphs/explorer/ +/ja/subgraphs/guides/arweave/ +/ja/subgraphs/guides/contract-analyzer/ +/ja/subgraphs/guides/enums/ +/ja/subgraphs/guides/grafting/ +/ja/subgraphs/guides/near/ +/ja/subgraphs/guides/polymarket/ +/ja/subgraphs/guides/secure-api-keys-nextjs/ +/ja/subgraphs/guides/subgraph-debug-forking/ +/ja/subgraphs/guides/subgraph-uncrashable/ +/ja/subgraphs/guides/transfer-to-the-graph/ /ja/subgraphs/querying/best-practices/ /ja/subgraphs/querying/distributed-systems/ /ja/subgraphs/querying/from-an-application/ @@ -814,17 +805,6 @@ /ko/subgraphs/best-practices/pruning/ /ko/subgraphs/best-practices/timeseries/ /ko/subgraphs/billing/ -/ko/subgraphs/cookbook/arweave/ -/ko/subgraphs/cookbook/enums/ -/ko/subgraphs/cookbook/grafting/ -/ko/subgraphs/cookbook/near/ -/ko/subgraphs/cookbook/polymarket/ -/ko/subgraphs/cookbook/secure-api-keys-nextjs/ -/ko/subgraphs/cookbook/subgraph-composition-three-sources/ -/ko/subgraphs/cookbook/subgraph-composition/ -/ko/subgraphs/cookbook/subgraph-debug-forking/ -/ko/subgraphs/cookbook/subgraph-uncrashable/ -/ko/subgraphs/cookbook/transfer-to-the-graph/ /ko/subgraphs/developing/creating/advanced/ /ko/subgraphs/developing/creating/assemblyscript-mappings/ /ko/subgraphs/developing/creating/graph-ts/CHANGELOG/ @@ -845,6 +825,16 @@ /ko/subgraphs/developing/publishing/publishing-a-subgraph/ /ko/subgraphs/developing/subgraphs/ /ko/subgraphs/explorer/ +/ko/subgraphs/guides/arweave/ +/ko/subgraphs/guides/contract-analyzer/ +/ko/subgraphs/guides/enums/ +/ko/subgraphs/guides/grafting/ +/ko/subgraphs/guides/near/ +/ko/subgraphs/guides/polymarket/ +/ko/subgraphs/guides/secure-api-keys-nextjs/ +/ko/subgraphs/guides/subgraph-debug-forking/ +/ko/subgraphs/guides/subgraph-uncrashable/ +/ko/subgraphs/guides/transfer-to-the-graph/ /ko/subgraphs/querying/best-practices/ /ko/subgraphs/querying/distributed-systems/ /ko/subgraphs/querying/from-an-application/ @@ -901,17 +891,6 @@ /mr/subgraphs/best-practices/pruning/ /mr/subgraphs/best-practices/timeseries/ /mr/subgraphs/billing/ -/mr/subgraphs/cookbook/arweave/ -/mr/subgraphs/cookbook/enums/ -/mr/subgraphs/cookbook/grafting/ -/mr/subgraphs/cookbook/near/ -/mr/subgraphs/cookbook/polymarket/ -/mr/subgraphs/cookbook/secure-api-keys-nextjs/ -/mr/subgraphs/cookbook/subgraph-composition-three-sources/ -/mr/subgraphs/cookbook/subgraph-composition/ -/mr/subgraphs/cookbook/subgraph-debug-forking/ -/mr/subgraphs/cookbook/subgraph-uncrashable/ -/mr/subgraphs/cookbook/transfer-to-the-graph/ /mr/subgraphs/developing/creating/advanced/ /mr/subgraphs/developing/creating/assemblyscript-mappings/ /mr/subgraphs/developing/creating/graph-ts/CHANGELOG/ @@ -932,6 +911,16 @@ /mr/subgraphs/developing/publishing/publishing-a-subgraph/ /mr/subgraphs/developing/subgraphs/ /mr/subgraphs/explorer/ +/mr/subgraphs/guides/arweave/ +/mr/subgraphs/guides/contract-analyzer/ +/mr/subgraphs/guides/enums/ +/mr/subgraphs/guides/grafting/ +/mr/subgraphs/guides/near/ +/mr/subgraphs/guides/polymarket/ +/mr/subgraphs/guides/secure-api-keys-nextjs/ +/mr/subgraphs/guides/subgraph-debug-forking/ +/mr/subgraphs/guides/subgraph-uncrashable/ +/mr/subgraphs/guides/transfer-to-the-graph/ /mr/subgraphs/querying/best-practices/ /mr/subgraphs/querying/distributed-systems/ /mr/subgraphs/querying/from-an-application/ @@ -986,17 +975,6 @@ /nl/subgraphs/best-practices/pruning/ /nl/subgraphs/best-practices/timeseries/ /nl/subgraphs/billing/ -/nl/subgraphs/cookbook/arweave/ -/nl/subgraphs/cookbook/enums/ -/nl/subgraphs/cookbook/grafting/ -/nl/subgraphs/cookbook/near/ -/nl/subgraphs/cookbook/polymarket/ -/nl/subgraphs/cookbook/secure-api-keys-nextjs/ -/nl/subgraphs/cookbook/subgraph-composition-three-sources/ -/nl/subgraphs/cookbook/subgraph-composition/ -/nl/subgraphs/cookbook/subgraph-debug-forking/ -/nl/subgraphs/cookbook/subgraph-uncrashable/ -/nl/subgraphs/cookbook/transfer-to-the-graph/ /nl/subgraphs/developing/creating/advanced/ /nl/subgraphs/developing/creating/assemblyscript-mappings/ /nl/subgraphs/developing/creating/graph-ts/CHANGELOG/ @@ -1017,6 +995,16 @@ /nl/subgraphs/developing/publishing/publishing-a-subgraph/ /nl/subgraphs/developing/subgraphs/ /nl/subgraphs/explorer/ +/nl/subgraphs/guides/arweave/ +/nl/subgraphs/guides/contract-analyzer/ +/nl/subgraphs/guides/enums/ +/nl/subgraphs/guides/grafting/ +/nl/subgraphs/guides/near/ +/nl/subgraphs/guides/polymarket/ +/nl/subgraphs/guides/secure-api-keys-nextjs/ +/nl/subgraphs/guides/subgraph-debug-forking/ +/nl/subgraphs/guides/subgraph-uncrashable/ +/nl/subgraphs/guides/transfer-to-the-graph/ /nl/subgraphs/querying/best-practices/ /nl/subgraphs/querying/distributed-systems/ /nl/subgraphs/querying/from-an-application/ @@ -1071,17 +1059,6 @@ /pl/subgraphs/best-practices/pruning/ /pl/subgraphs/best-practices/timeseries/ /pl/subgraphs/billing/ -/pl/subgraphs/cookbook/arweave/ -/pl/subgraphs/cookbook/enums/ -/pl/subgraphs/cookbook/grafting/ -/pl/subgraphs/cookbook/near/ -/pl/subgraphs/cookbook/polymarket/ -/pl/subgraphs/cookbook/secure-api-keys-nextjs/ -/pl/subgraphs/cookbook/subgraph-composition-three-sources/ -/pl/subgraphs/cookbook/subgraph-composition/ -/pl/subgraphs/cookbook/subgraph-debug-forking/ -/pl/subgraphs/cookbook/subgraph-uncrashable/ -/pl/subgraphs/cookbook/transfer-to-the-graph/ /pl/subgraphs/developing/creating/advanced/ /pl/subgraphs/developing/creating/assemblyscript-mappings/ /pl/subgraphs/developing/creating/graph-ts/CHANGELOG/ @@ -1102,6 +1079,16 @@ /pl/subgraphs/developing/publishing/publishing-a-subgraph/ /pl/subgraphs/developing/subgraphs/ /pl/subgraphs/explorer/ +/pl/subgraphs/guides/arweave/ +/pl/subgraphs/guides/contract-analyzer/ +/pl/subgraphs/guides/enums/ +/pl/subgraphs/guides/grafting/ +/pl/subgraphs/guides/near/ +/pl/subgraphs/guides/polymarket/ +/pl/subgraphs/guides/secure-api-keys-nextjs/ +/pl/subgraphs/guides/subgraph-debug-forking/ +/pl/subgraphs/guides/subgraph-uncrashable/ +/pl/subgraphs/guides/transfer-to-the-graph/ /pl/subgraphs/querying/best-practices/ /pl/subgraphs/querying/distributed-systems/ /pl/subgraphs/querying/from-an-application/ @@ -1158,17 +1145,6 @@ /pt/subgraphs/best-practices/pruning/ /pt/subgraphs/best-practices/timeseries/ /pt/subgraphs/billing/ -/pt/subgraphs/cookbook/arweave/ -/pt/subgraphs/cookbook/enums/ -/pt/subgraphs/cookbook/grafting/ -/pt/subgraphs/cookbook/near/ -/pt/subgraphs/cookbook/polymarket/ -/pt/subgraphs/cookbook/secure-api-keys-nextjs/ -/pt/subgraphs/cookbook/subgraph-composition-three-sources/ -/pt/subgraphs/cookbook/subgraph-composition/ -/pt/subgraphs/cookbook/subgraph-debug-forking/ -/pt/subgraphs/cookbook/subgraph-uncrashable/ -/pt/subgraphs/cookbook/transfer-to-the-graph/ /pt/subgraphs/developing/creating/advanced/ /pt/subgraphs/developing/creating/assemblyscript-mappings/ /pt/subgraphs/developing/creating/graph-ts/CHANGELOG/ @@ -1189,6 +1165,16 @@ /pt/subgraphs/developing/publishing/publishing-a-subgraph/ /pt/subgraphs/developing/subgraphs/ /pt/subgraphs/explorer/ +/pt/subgraphs/guides/arweave/ +/pt/subgraphs/guides/contract-analyzer/ +/pt/subgraphs/guides/enums/ +/pt/subgraphs/guides/grafting/ +/pt/subgraphs/guides/near/ +/pt/subgraphs/guides/polymarket/ +/pt/subgraphs/guides/secure-api-keys-nextjs/ +/pt/subgraphs/guides/subgraph-debug-forking/ +/pt/subgraphs/guides/subgraph-uncrashable/ +/pt/subgraphs/guides/transfer-to-the-graph/ /pt/subgraphs/querying/best-practices/ /pt/subgraphs/querying/distributed-systems/ /pt/subgraphs/querying/from-an-application/ @@ -1243,17 +1229,6 @@ /ro/subgraphs/best-practices/pruning/ /ro/subgraphs/best-practices/timeseries/ /ro/subgraphs/billing/ -/ro/subgraphs/cookbook/arweave/ -/ro/subgraphs/cookbook/enums/ -/ro/subgraphs/cookbook/grafting/ -/ro/subgraphs/cookbook/near/ -/ro/subgraphs/cookbook/polymarket/ -/ro/subgraphs/cookbook/secure-api-keys-nextjs/ -/ro/subgraphs/cookbook/subgraph-composition-three-sources/ -/ro/subgraphs/cookbook/subgraph-composition/ -/ro/subgraphs/cookbook/subgraph-debug-forking/ -/ro/subgraphs/cookbook/subgraph-uncrashable/ -/ro/subgraphs/cookbook/transfer-to-the-graph/ /ro/subgraphs/developing/creating/advanced/ /ro/subgraphs/developing/creating/assemblyscript-mappings/ /ro/subgraphs/developing/creating/graph-ts/CHANGELOG/ @@ -1274,6 +1249,16 @@ /ro/subgraphs/developing/publishing/publishing-a-subgraph/ /ro/subgraphs/developing/subgraphs/ /ro/subgraphs/explorer/ +/ro/subgraphs/guides/arweave/ +/ro/subgraphs/guides/contract-analyzer/ +/ro/subgraphs/guides/enums/ +/ro/subgraphs/guides/grafting/ +/ro/subgraphs/guides/near/ +/ro/subgraphs/guides/polymarket/ +/ro/subgraphs/guides/secure-api-keys-nextjs/ +/ro/subgraphs/guides/subgraph-debug-forking/ +/ro/subgraphs/guides/subgraph-uncrashable/ +/ro/subgraphs/guides/transfer-to-the-graph/ /ro/subgraphs/querying/best-practices/ /ro/subgraphs/querying/distributed-systems/ /ro/subgraphs/querying/from-an-application/ @@ -1330,17 +1315,6 @@ /ru/subgraphs/best-practices/pruning/ /ru/subgraphs/best-practices/timeseries/ /ru/subgraphs/billing/ -/ru/subgraphs/cookbook/arweave/ -/ru/subgraphs/cookbook/enums/ -/ru/subgraphs/cookbook/grafting/ -/ru/subgraphs/cookbook/near/ -/ru/subgraphs/cookbook/polymarket/ -/ru/subgraphs/cookbook/secure-api-keys-nextjs/ -/ru/subgraphs/cookbook/subgraph-composition-three-sources/ -/ru/subgraphs/cookbook/subgraph-composition/ -/ru/subgraphs/cookbook/subgraph-debug-forking/ -/ru/subgraphs/cookbook/subgraph-uncrashable/ -/ru/subgraphs/cookbook/transfer-to-the-graph/ /ru/subgraphs/developing/creating/advanced/ /ru/subgraphs/developing/creating/assemblyscript-mappings/ /ru/subgraphs/developing/creating/graph-ts/CHANGELOG/ @@ -1361,6 +1335,16 @@ /ru/subgraphs/developing/publishing/publishing-a-subgraph/ /ru/subgraphs/developing/subgraphs/ /ru/subgraphs/explorer/ +/ru/subgraphs/guides/arweave/ +/ru/subgraphs/guides/contract-analyzer/ +/ru/subgraphs/guides/enums/ +/ru/subgraphs/guides/grafting/ +/ru/subgraphs/guides/near/ +/ru/subgraphs/guides/polymarket/ +/ru/subgraphs/guides/secure-api-keys-nextjs/ +/ru/subgraphs/guides/subgraph-debug-forking/ +/ru/subgraphs/guides/subgraph-uncrashable/ +/ru/subgraphs/guides/transfer-to-the-graph/ /ru/subgraphs/querying/best-practices/ /ru/subgraphs/querying/distributed-systems/ /ru/subgraphs/querying/from-an-application/ @@ -1417,17 +1401,6 @@ /sv/subgraphs/best-practices/pruning/ /sv/subgraphs/best-practices/timeseries/ /sv/subgraphs/billing/ -/sv/subgraphs/cookbook/arweave/ -/sv/subgraphs/cookbook/enums/ -/sv/subgraphs/cookbook/grafting/ -/sv/subgraphs/cookbook/near/ -/sv/subgraphs/cookbook/polymarket/ -/sv/subgraphs/cookbook/secure-api-keys-nextjs/ -/sv/subgraphs/cookbook/subgraph-composition-three-sources/ -/sv/subgraphs/cookbook/subgraph-composition/ -/sv/subgraphs/cookbook/subgraph-debug-forking/ -/sv/subgraphs/cookbook/subgraph-uncrashable/ -/sv/subgraphs/cookbook/transfer-to-the-graph/ /sv/subgraphs/developing/creating/advanced/ /sv/subgraphs/developing/creating/assemblyscript-mappings/ /sv/subgraphs/developing/creating/graph-ts/CHANGELOG/ @@ -1448,6 +1421,16 @@ /sv/subgraphs/developing/publishing/publishing-a-subgraph/ /sv/subgraphs/developing/subgraphs/ /sv/subgraphs/explorer/ +/sv/subgraphs/guides/arweave/ +/sv/subgraphs/guides/contract-analyzer/ +/sv/subgraphs/guides/enums/ +/sv/subgraphs/guides/grafting/ +/sv/subgraphs/guides/near/ +/sv/subgraphs/guides/polymarket/ +/sv/subgraphs/guides/secure-api-keys-nextjs/ +/sv/subgraphs/guides/subgraph-debug-forking/ +/sv/subgraphs/guides/subgraph-uncrashable/ +/sv/subgraphs/guides/transfer-to-the-graph/ /sv/subgraphs/querying/best-practices/ /sv/subgraphs/querying/distributed-systems/ /sv/subgraphs/querying/from-an-application/ @@ -1504,17 +1487,6 @@ /tr/subgraphs/best-practices/pruning/ /tr/subgraphs/best-practices/timeseries/ /tr/subgraphs/billing/ -/tr/subgraphs/cookbook/arweave/ -/tr/subgraphs/cookbook/enums/ -/tr/subgraphs/cookbook/grafting/ -/tr/subgraphs/cookbook/near/ -/tr/subgraphs/cookbook/polymarket/ -/tr/subgraphs/cookbook/secure-api-keys-nextjs/ -/tr/subgraphs/cookbook/subgraph-composition-three-sources/ -/tr/subgraphs/cookbook/subgraph-composition/ -/tr/subgraphs/cookbook/subgraph-debug-forking/ -/tr/subgraphs/cookbook/subgraph-uncrashable/ -/tr/subgraphs/cookbook/transfer-to-the-graph/ /tr/subgraphs/developing/creating/advanced/ /tr/subgraphs/developing/creating/assemblyscript-mappings/ /tr/subgraphs/developing/creating/graph-ts/CHANGELOG/ @@ -1535,6 +1507,16 @@ /tr/subgraphs/developing/publishing/publishing-a-subgraph/ /tr/subgraphs/developing/subgraphs/ /tr/subgraphs/explorer/ +/tr/subgraphs/guides/arweave/ +/tr/subgraphs/guides/contract-analyzer/ +/tr/subgraphs/guides/enums/ +/tr/subgraphs/guides/grafting/ +/tr/subgraphs/guides/near/ +/tr/subgraphs/guides/polymarket/ +/tr/subgraphs/guides/secure-api-keys-nextjs/ +/tr/subgraphs/guides/subgraph-debug-forking/ +/tr/subgraphs/guides/subgraph-uncrashable/ +/tr/subgraphs/guides/transfer-to-the-graph/ /tr/subgraphs/querying/best-practices/ /tr/subgraphs/querying/distributed-systems/ /tr/subgraphs/querying/from-an-application/ @@ -1589,17 +1571,6 @@ /uk/subgraphs/best-practices/pruning/ /uk/subgraphs/best-practices/timeseries/ /uk/subgraphs/billing/ -/uk/subgraphs/cookbook/arweave/ -/uk/subgraphs/cookbook/enums/ -/uk/subgraphs/cookbook/grafting/ -/uk/subgraphs/cookbook/near/ -/uk/subgraphs/cookbook/polymarket/ -/uk/subgraphs/cookbook/secure-api-keys-nextjs/ -/uk/subgraphs/cookbook/subgraph-composition-three-sources/ -/uk/subgraphs/cookbook/subgraph-composition/ -/uk/subgraphs/cookbook/subgraph-debug-forking/ -/uk/subgraphs/cookbook/subgraph-uncrashable/ -/uk/subgraphs/cookbook/transfer-to-the-graph/ /uk/subgraphs/developing/creating/advanced/ /uk/subgraphs/developing/creating/assemblyscript-mappings/ /uk/subgraphs/developing/creating/graph-ts/CHANGELOG/ @@ -1620,6 +1591,16 @@ /uk/subgraphs/developing/publishing/publishing-a-subgraph/ /uk/subgraphs/developing/subgraphs/ /uk/subgraphs/explorer/ +/uk/subgraphs/guides/arweave/ +/uk/subgraphs/guides/contract-analyzer/ +/uk/subgraphs/guides/enums/ +/uk/subgraphs/guides/grafting/ +/uk/subgraphs/guides/near/ +/uk/subgraphs/guides/polymarket/ +/uk/subgraphs/guides/secure-api-keys-nextjs/ +/uk/subgraphs/guides/subgraph-debug-forking/ +/uk/subgraphs/guides/subgraph-uncrashable/ +/uk/subgraphs/guides/transfer-to-the-graph/ /uk/subgraphs/querying/best-practices/ /uk/subgraphs/querying/distributed-systems/ /uk/subgraphs/querying/from-an-application/ @@ -1676,17 +1657,6 @@ /ur/subgraphs/best-practices/pruning/ /ur/subgraphs/best-practices/timeseries/ /ur/subgraphs/billing/ -/ur/subgraphs/cookbook/arweave/ -/ur/subgraphs/cookbook/enums/ -/ur/subgraphs/cookbook/grafting/ -/ur/subgraphs/cookbook/near/ -/ur/subgraphs/cookbook/polymarket/ -/ur/subgraphs/cookbook/secure-api-keys-nextjs/ -/ur/subgraphs/cookbook/subgraph-composition-three-sources/ -/ur/subgraphs/cookbook/subgraph-composition/ -/ur/subgraphs/cookbook/subgraph-debug-forking/ -/ur/subgraphs/cookbook/subgraph-uncrashable/ -/ur/subgraphs/cookbook/transfer-to-the-graph/ /ur/subgraphs/developing/creating/advanced/ /ur/subgraphs/developing/creating/assemblyscript-mappings/ /ur/subgraphs/developing/creating/graph-ts/CHANGELOG/ @@ -1707,6 +1677,16 @@ /ur/subgraphs/developing/publishing/publishing-a-subgraph/ /ur/subgraphs/developing/subgraphs/ /ur/subgraphs/explorer/ +/ur/subgraphs/guides/arweave/ +/ur/subgraphs/guides/contract-analyzer/ +/ur/subgraphs/guides/enums/ +/ur/subgraphs/guides/grafting/ +/ur/subgraphs/guides/near/ +/ur/subgraphs/guides/polymarket/ +/ur/subgraphs/guides/secure-api-keys-nextjs/ +/ur/subgraphs/guides/subgraph-debug-forking/ +/ur/subgraphs/guides/subgraph-uncrashable/ +/ur/subgraphs/guides/transfer-to-the-graph/ /ur/subgraphs/querying/best-practices/ /ur/subgraphs/querying/distributed-systems/ /ur/subgraphs/querying/from-an-application/ @@ -1761,17 +1741,6 @@ /vi/subgraphs/best-practices/pruning/ /vi/subgraphs/best-practices/timeseries/ /vi/subgraphs/billing/ -/vi/subgraphs/cookbook/arweave/ -/vi/subgraphs/cookbook/enums/ -/vi/subgraphs/cookbook/grafting/ -/vi/subgraphs/cookbook/near/ -/vi/subgraphs/cookbook/polymarket/ -/vi/subgraphs/cookbook/secure-api-keys-nextjs/ -/vi/subgraphs/cookbook/subgraph-composition-three-sources/ -/vi/subgraphs/cookbook/subgraph-composition/ -/vi/subgraphs/cookbook/subgraph-debug-forking/ -/vi/subgraphs/cookbook/subgraph-uncrashable/ -/vi/subgraphs/cookbook/transfer-to-the-graph/ /vi/subgraphs/developing/creating/advanced/ /vi/subgraphs/developing/creating/assemblyscript-mappings/ /vi/subgraphs/developing/creating/graph-ts/CHANGELOG/ @@ -1792,6 +1761,16 @@ /vi/subgraphs/developing/publishing/publishing-a-subgraph/ /vi/subgraphs/developing/subgraphs/ /vi/subgraphs/explorer/ +/vi/subgraphs/guides/arweave/ +/vi/subgraphs/guides/contract-analyzer/ +/vi/subgraphs/guides/enums/ +/vi/subgraphs/guides/grafting/ +/vi/subgraphs/guides/near/ +/vi/subgraphs/guides/polymarket/ +/vi/subgraphs/guides/secure-api-keys-nextjs/ +/vi/subgraphs/guides/subgraph-debug-forking/ +/vi/subgraphs/guides/subgraph-uncrashable/ +/vi/subgraphs/guides/transfer-to-the-graph/ /vi/subgraphs/querying/best-practices/ /vi/subgraphs/querying/distributed-systems/ /vi/subgraphs/querying/from-an-application/ @@ -1848,17 +1827,6 @@ /zh/subgraphs/best-practices/pruning/ /zh/subgraphs/best-practices/timeseries/ /zh/subgraphs/billing/ -/zh/subgraphs/cookbook/arweave/ -/zh/subgraphs/cookbook/enums/ -/zh/subgraphs/cookbook/grafting/ -/zh/subgraphs/cookbook/near/ -/zh/subgraphs/cookbook/polymarket/ -/zh/subgraphs/cookbook/secure-api-keys-nextjs/ -/zh/subgraphs/cookbook/subgraph-composition-three-sources/ -/zh/subgraphs/cookbook/subgraph-composition/ -/zh/subgraphs/cookbook/subgraph-debug-forking/ -/zh/subgraphs/cookbook/subgraph-uncrashable/ -/zh/subgraphs/cookbook/transfer-to-the-graph/ /zh/subgraphs/developing/creating/advanced/ /zh/subgraphs/developing/creating/assemblyscript-mappings/ /zh/subgraphs/developing/creating/graph-ts/CHANGELOG/ @@ -1879,6 +1847,16 @@ /zh/subgraphs/developing/publishing/publishing-a-subgraph/ /zh/subgraphs/developing/subgraphs/ /zh/subgraphs/explorer/ +/zh/subgraphs/guides/arweave/ +/zh/subgraphs/guides/contract-analyzer/ +/zh/subgraphs/guides/enums/ +/zh/subgraphs/guides/grafting/ +/zh/subgraphs/guides/near/ +/zh/subgraphs/guides/polymarket/ +/zh/subgraphs/guides/secure-api-keys-nextjs/ +/zh/subgraphs/guides/subgraph-debug-forking/ +/zh/subgraphs/guides/subgraph-uncrashable/ +/zh/subgraphs/guides/transfer-to-the-graph/ /zh/subgraphs/querying/best-practices/ /zh/subgraphs/querying/distributed-systems/ /zh/subgraphs/querying/from-an-application/ diff --git a/website/src/pages/ar/subgraphs/guides/_meta.js b/website/src/pages/ar/subgraphs/guides/_meta.js index e642f12ef11d..37e18bc51651 100644 --- a/website/src/pages/ar/subgraphs/guides/_meta.js +++ b/website/src/pages/ar/subgraphs/guides/_meta.js @@ -8,4 +8,5 @@ export default { enums: '', 'secure-api-keys-nextjs': '', polymarket: '', + 'contract-analyzer': '', } diff --git a/website/src/pages/ar/subgraphs/guides/contract-analyzer.mdx b/website/src/pages/ar/subgraphs/guides/contract-analyzer.mdx new file mode 100644 index 000000000000..084ac8d28a00 --- /dev/null +++ b/website/src/pages/ar/subgraphs/guides/contract-analyzer.mdx @@ -0,0 +1,103 @@ +--- +title: Smart Contract Analysis with Cana CLI +--- + +# Cana CLI: Quick & Efficient Contract Analysis + +**Cana CLI** is a command-line tool that streamlines helpful smart contract metadata analysis specific to subgraph development across multiple EVM-compatible chains. + +## 📌 Key Features + +- Detect deployment blocks +- Verify source code +- Extract ABIs & event signatures +- Identify proxy and implementation contracts +- Support multiple chains + +## 🚀 Installation & Setup + +Install Cana globally using npm: + +```bash +npm install -g contract-analyzer +``` + +Set up a blockchain for analysis: + +```bash +cana setup +``` + +Provide the required block explorer API and block explorer endpoint URL details when prompted. + +Running `cana setup` creates a configuration file at `~/.contract-analyzer/config.json`. This file stores your block explorer API credentials, endpoint URLs, and chain selection preferences for future use. + +## 🍳 Usage + +### 🔹 Chain Selection + +Cana supports multiple EVM-compatible chains. + +List chains added with: + +```bash +cana chains +``` + +Then select a chain with: + +```bash +cana chains --switch +``` + +Once a chain is selected, all subsequent contract analases will continue on that chain. + +### 🔹 Basic Contract Analysis + +Analyze a contract with: + +```bash +cana analyze 0xContractAddress +``` + +or + +```bash +cana -a 0xContractAddress +``` + +This command displays essential contract information in the terminal using a clear, organized format. + +### 🔹 Understanding Output + +Cana organizes results into the terminal as well as into a structured directory when detailed contract data is successfully retrieved: + +``` +contracts-analyzed/ +└── ContractName_chainName_YYYY-MM-DD/ + ├── contract/ # Folder for individual contract files + ├── abi.json # Contract ABI + └── event-information.json # Event signatures and examples +``` + +### 🔹 Chain Management + +Add and manage chains: + +```bash +cana setup # Add a new chain +cana chains # List configured chains +cana chains -s # Swich chains. +``` + +## ⚠️ Troubleshooting + +- **Missing Data**: Ensure the contract address is correct, verified on the block explorer, and that your API key has the required permissions. + +## ✅ Requirements + +- Node.js v16+ +- npm v6+ +- Block explorer API keys + +Keep your contract analyses efficient and well-organized. 🚀 diff --git a/website/src/pages/cs/subgraphs/guides/_meta.js b/website/src/pages/cs/subgraphs/guides/_meta.js index e642f12ef11d..37e18bc51651 100644 --- a/website/src/pages/cs/subgraphs/guides/_meta.js +++ b/website/src/pages/cs/subgraphs/guides/_meta.js @@ -8,4 +8,5 @@ export default { enums: '', 'secure-api-keys-nextjs': '', polymarket: '', + 'contract-analyzer': '', } diff --git a/website/src/pages/cs/subgraphs/guides/contract-analyzer.mdx b/website/src/pages/cs/subgraphs/guides/contract-analyzer.mdx new file mode 100644 index 000000000000..084ac8d28a00 --- /dev/null +++ b/website/src/pages/cs/subgraphs/guides/contract-analyzer.mdx @@ -0,0 +1,103 @@ +--- +title: Smart Contract Analysis with Cana CLI +--- + +# Cana CLI: Quick & Efficient Contract Analysis + +**Cana CLI** is a command-line tool that streamlines helpful smart contract metadata analysis specific to subgraph development across multiple EVM-compatible chains. + +## 📌 Key Features + +- Detect deployment blocks +- Verify source code +- Extract ABIs & event signatures +- Identify proxy and implementation contracts +- Support multiple chains + +## 🚀 Installation & Setup + +Install Cana globally using npm: + +```bash +npm install -g contract-analyzer +``` + +Set up a blockchain for analysis: + +```bash +cana setup +``` + +Provide the required block explorer API and block explorer endpoint URL details when prompted. + +Running `cana setup` creates a configuration file at `~/.contract-analyzer/config.json`. This file stores your block explorer API credentials, endpoint URLs, and chain selection preferences for future use. + +## 🍳 Usage + +### 🔹 Chain Selection + +Cana supports multiple EVM-compatible chains. + +List chains added with: + +```bash +cana chains +``` + +Then select a chain with: + +```bash +cana chains --switch +``` + +Once a chain is selected, all subsequent contract analases will continue on that chain. + +### 🔹 Basic Contract Analysis + +Analyze a contract with: + +```bash +cana analyze 0xContractAddress +``` + +or + +```bash +cana -a 0xContractAddress +``` + +This command displays essential contract information in the terminal using a clear, organized format. + +### 🔹 Understanding Output + +Cana organizes results into the terminal as well as into a structured directory when detailed contract data is successfully retrieved: + +``` +contracts-analyzed/ +└── ContractName_chainName_YYYY-MM-DD/ + ├── contract/ # Folder for individual contract files + ├── abi.json # Contract ABI + └── event-information.json # Event signatures and examples +``` + +### 🔹 Chain Management + +Add and manage chains: + +```bash +cana setup # Add a new chain +cana chains # List configured chains +cana chains -s # Swich chains. +``` + +## ⚠️ Troubleshooting + +- **Missing Data**: Ensure the contract address is correct, verified on the block explorer, and that your API key has the required permissions. + +## ✅ Requirements + +- Node.js v16+ +- npm v6+ +- Block explorer API keys + +Keep your contract analyses efficient and well-organized. 🚀 diff --git a/website/src/pages/de/subgraphs/guides/_meta.js b/website/src/pages/de/subgraphs/guides/_meta.js index e642f12ef11d..37e18bc51651 100644 --- a/website/src/pages/de/subgraphs/guides/_meta.js +++ b/website/src/pages/de/subgraphs/guides/_meta.js @@ -8,4 +8,5 @@ export default { enums: '', 'secure-api-keys-nextjs': '', polymarket: '', + 'contract-analyzer': '', } diff --git a/website/src/pages/de/subgraphs/guides/contract-analyzer.mdx b/website/src/pages/de/subgraphs/guides/contract-analyzer.mdx new file mode 100644 index 000000000000..084ac8d28a00 --- /dev/null +++ b/website/src/pages/de/subgraphs/guides/contract-analyzer.mdx @@ -0,0 +1,103 @@ +--- +title: Smart Contract Analysis with Cana CLI +--- + +# Cana CLI: Quick & Efficient Contract Analysis + +**Cana CLI** is a command-line tool that streamlines helpful smart contract metadata analysis specific to subgraph development across multiple EVM-compatible chains. + +## 📌 Key Features + +- Detect deployment blocks +- Verify source code +- Extract ABIs & event signatures +- Identify proxy and implementation contracts +- Support multiple chains + +## 🚀 Installation & Setup + +Install Cana globally using npm: + +```bash +npm install -g contract-analyzer +``` + +Set up a blockchain for analysis: + +```bash +cana setup +``` + +Provide the required block explorer API and block explorer endpoint URL details when prompted. + +Running `cana setup` creates a configuration file at `~/.contract-analyzer/config.json`. This file stores your block explorer API credentials, endpoint URLs, and chain selection preferences for future use. + +## 🍳 Usage + +### 🔹 Chain Selection + +Cana supports multiple EVM-compatible chains. + +List chains added with: + +```bash +cana chains +``` + +Then select a chain with: + +```bash +cana chains --switch +``` + +Once a chain is selected, all subsequent contract analases will continue on that chain. + +### 🔹 Basic Contract Analysis + +Analyze a contract with: + +```bash +cana analyze 0xContractAddress +``` + +or + +```bash +cana -a 0xContractAddress +``` + +This command displays essential contract information in the terminal using a clear, organized format. + +### 🔹 Understanding Output + +Cana organizes results into the terminal as well as into a structured directory when detailed contract data is successfully retrieved: + +``` +contracts-analyzed/ +└── ContractName_chainName_YYYY-MM-DD/ + ├── contract/ # Folder for individual contract files + ├── abi.json # Contract ABI + └── event-information.json # Event signatures and examples +``` + +### 🔹 Chain Management + +Add and manage chains: + +```bash +cana setup # Add a new chain +cana chains # List configured chains +cana chains -s # Swich chains. +``` + +## ⚠️ Troubleshooting + +- **Missing Data**: Ensure the contract address is correct, verified on the block explorer, and that your API key has the required permissions. + +## ✅ Requirements + +- Node.js v16+ +- npm v6+ +- Block explorer API keys + +Keep your contract analyses efficient and well-organized. 🚀 diff --git a/website/src/pages/en/subgraphs/guides/contract-analyzer.mdx b/website/src/pages/en/subgraphs/guides/contract-analyzer.mdx index 387c74dec54a..ab5076c5ebf4 100644 --- a/website/src/pages/en/subgraphs/guides/contract-analyzer.mdx +++ b/website/src/pages/en/subgraphs/guides/contract-analyzer.mdx @@ -2,11 +2,15 @@ title: Smart Contract Analysis with Cana CLI --- -# Cana CLI: Quick & Efficient Contract Analysis +Improve smart contract analysis with **Cana CLI**. It's fast, efficient, and designed specifically for EVM chains. -**Cana CLI** is a command-line tool that streamlines helpful smart contract metadata analysis specific to subgraph development across multiple EVM-compatible chains. +## Overview -## 📌 Key Features +**Cana CLI** is a command-line tool that streamlines helpful smart contract metadata analysis specific to subgraph development across multiple EVM-compatible chains. It simplifies retrieving contract details, detecting proxy implementations, extracting ABIs, and more. + +### Key Features + +With Cana CLI, you can: - Detect deployment blocks - Verify source code @@ -14,47 +18,59 @@ title: Smart Contract Analysis with Cana CLI - Identify proxy and implementation contracts - Support multiple chains -## 🚀 Installation & Setup +### Prerequisites + +Before installing Cana CLI, make sure you have: + +- [Node.js v16+](https://nodejs.org/en) +- [npm v6+](https://docs.npmjs.com/cli/v11/commands/npm-install) +- Block explorer API keys + +### Installation & Setup -Install Cana globally using npm: +1. Install Cana CLI + +Use npm to install it globally: ```bash npm install -g contract-analyzer ``` -Set up a blockchain for analysis: +2. Configure Cana CLI + +Set up a blockchain environment for analysis: ```bash cana setup ``` -Provide the required block explorer API and block explorer endpoint URL details when prompted. +During setup, you'll be prompted to provide the required block explorer API key and block explorer endpoint URL. -Running `cana setup` creates a configuration file at `~/.contract-analyzer/config.json`. This file stores your block explorer API credentials, endpoint URLs, and chain selection preferences for future use. +After setup, Cana CLI creates a configuration file at `~/.contract-analyzer/config.json`. This file stores your block explorer API credentials, endpoint URLs, and chain selection preferences for future use. -## 🍳 Usage +### Steps: Using Cana CLI for Smart Contract Analysis -### 🔹 Chain Selection +#### 1. Select a Chain -Cana supports multiple EVM-compatible chains. +Cana CLI supports multiple EVM-compatible chains. -List chains added with: +For a list of chains added run this command: ```bash cana chains ``` -Then select a chain with: +Then select a chain with this command: ```bash cana chains --switch ``` -Once a chain is selected, all subsequent contract analases will continue on that chain. +Once a chain is selected, all subsequent contract analyses will continue on that chain. -### 🔹 Basic Contract Analysis +#### 2. Basic Contract Analysis -Analyze a contract with: +Run the following command to analyze a contract: ```bash cana analyze 0xContractAddress @@ -66,11 +82,11 @@ or cana -a 0xContractAddress ``` -This command displays essential contract information in the terminal using a clear, organized format. +This command fetches and displays essential contract information in the terminal using a clear, organized format. -### 🔹 Understanding Output +#### 3. Understanding the Output -Cana organizes results into the terminal as well as into a structured directory when detailed contract data is successfully retrieved: +Cana CLI organizes results into the terminal and into a structured directory when detailed contract data is successfully retrieved: ``` contracts-analyzed/ @@ -80,24 +96,22 @@ contracts-analyzed/ └── event-information.json # Event signatures and examples ``` -### 🔹 Chain Management +This format makes it easy to reference contract metadata, event signatures, and ABIs for subgraph development. + +#### 4. Chain Management Add and manage chains: ```bash -cana setup # Add a new chain -cana chains # List configured chains -cana chains -s # Swich chains. +cana setup # Add a new chain +cana chains # List configured chains +cana chains -s # Switch chains ``` -## ⚠️ Troubleshooting +### Troubleshooting -- **Missing Data**: Ensure the contract address is correct, verified on the block explorer, and that your API key has the required permissions. +Missing Data? Ensure that the contract address is correct, that it's verified on the block explorer, and that your API key has the required permissions. -## ✅ Requirements - -- Node.js v16+ -- npm v6+ -- Block explorer API keys +### Conclusion -Keep your contract analyses efficient and well-organized. 🚀 +With Cana CLI, you can efficiently analyze smart contracts, extract crucial metadata, and support subgraph development with ease. diff --git a/website/src/pages/en/subgraphs/querying/graph-client/README.md b/website/src/pages/en/subgraphs/querying/graph-client/README.md index a796c1b3ebb1..416cadc13c6f 100644 --- a/website/src/pages/en/subgraphs/querying/graph-client/README.md +++ b/website/src/pages/en/subgraphs/querying/graph-client/README.md @@ -235,7 +235,7 @@ All `fetch` strategies can be combined to create the ultimate execution flow. The `retry` mechanism allow you to specify the retry attempts for a single GraphQL endpoint/source. -The retry flow will execute in both conditions: a network error, or due to a runtime error (indexing issue/unavailability of the indexer). +The retry flow will execute in both conditions: a netword error, or due to a runtime error (indexing issue/inavailability of the indexer). ```yaml sources: diff --git a/website/src/pages/en/subgraphs/querying/graph-client/live.md b/website/src/pages/en/subgraphs/querying/graph-client/live.md index 44a265055509..e6f726cb4352 100644 --- a/website/src/pages/en/subgraphs/querying/graph-client/live.md +++ b/website/src/pages/en/subgraphs/querying/graph-client/live.md @@ -38,6 +38,6 @@ query ExampleQuery @live(interval: 5000) { ## Integrations -Since the entire network layer (along with the `@live` mechanism) is implemented inside `graph-client` core, you can use Live queries with every GraphQL client (such as Urql or Apollo-Client), as long as it supports stream responses (`AsyncIterable`). +Since the entire network layer (along with the `@live` mechanism) is implemented inside `graph-client` core, you can use Live queries with every GraphQL client (such as Urql or Apollo-Client), as long as it supports streame responses (`AsyncIterable`). No additional setup is required for GraphQL clients cache updates. diff --git a/website/src/pages/es/subgraphs/guides/_meta.js b/website/src/pages/es/subgraphs/guides/_meta.js index e642f12ef11d..37e18bc51651 100644 --- a/website/src/pages/es/subgraphs/guides/_meta.js +++ b/website/src/pages/es/subgraphs/guides/_meta.js @@ -8,4 +8,5 @@ export default { enums: '', 'secure-api-keys-nextjs': '', polymarket: '', + 'contract-analyzer': '', } diff --git a/website/src/pages/es/subgraphs/guides/contract-analyzer.mdx b/website/src/pages/es/subgraphs/guides/contract-analyzer.mdx new file mode 100644 index 000000000000..084ac8d28a00 --- /dev/null +++ b/website/src/pages/es/subgraphs/guides/contract-analyzer.mdx @@ -0,0 +1,103 @@ +--- +title: Smart Contract Analysis with Cana CLI +--- + +# Cana CLI: Quick & Efficient Contract Analysis + +**Cana CLI** is a command-line tool that streamlines helpful smart contract metadata analysis specific to subgraph development across multiple EVM-compatible chains. + +## 📌 Key Features + +- Detect deployment blocks +- Verify source code +- Extract ABIs & event signatures +- Identify proxy and implementation contracts +- Support multiple chains + +## 🚀 Installation & Setup + +Install Cana globally using npm: + +```bash +npm install -g contract-analyzer +``` + +Set up a blockchain for analysis: + +```bash +cana setup +``` + +Provide the required block explorer API and block explorer endpoint URL details when prompted. + +Running `cana setup` creates a configuration file at `~/.contract-analyzer/config.json`. This file stores your block explorer API credentials, endpoint URLs, and chain selection preferences for future use. + +## 🍳 Usage + +### 🔹 Chain Selection + +Cana supports multiple EVM-compatible chains. + +List chains added with: + +```bash +cana chains +``` + +Then select a chain with: + +```bash +cana chains --switch +``` + +Once a chain is selected, all subsequent contract analases will continue on that chain. + +### 🔹 Basic Contract Analysis + +Analyze a contract with: + +```bash +cana analyze 0xContractAddress +``` + +or + +```bash +cana -a 0xContractAddress +``` + +This command displays essential contract information in the terminal using a clear, organized format. + +### 🔹 Understanding Output + +Cana organizes results into the terminal as well as into a structured directory when detailed contract data is successfully retrieved: + +``` +contracts-analyzed/ +└── ContractName_chainName_YYYY-MM-DD/ + ├── contract/ # Folder for individual contract files + ├── abi.json # Contract ABI + └── event-information.json # Event signatures and examples +``` + +### 🔹 Chain Management + +Add and manage chains: + +```bash +cana setup # Add a new chain +cana chains # List configured chains +cana chains -s # Swich chains. +``` + +## ⚠️ Troubleshooting + +- **Missing Data**: Ensure the contract address is correct, verified on the block explorer, and that your API key has the required permissions. + +## ✅ Requirements + +- Node.js v16+ +- npm v6+ +- Block explorer API keys + +Keep your contract analyses efficient and well-organized. 🚀 diff --git a/website/src/pages/fr/subgraphs/guides/_meta.js b/website/src/pages/fr/subgraphs/guides/_meta.js index e642f12ef11d..37e18bc51651 100644 --- a/website/src/pages/fr/subgraphs/guides/_meta.js +++ b/website/src/pages/fr/subgraphs/guides/_meta.js @@ -8,4 +8,5 @@ export default { enums: '', 'secure-api-keys-nextjs': '', polymarket: '', + 'contract-analyzer': '', } diff --git a/website/src/pages/fr/subgraphs/guides/contract-analyzer.mdx b/website/src/pages/fr/subgraphs/guides/contract-analyzer.mdx new file mode 100644 index 000000000000..084ac8d28a00 --- /dev/null +++ b/website/src/pages/fr/subgraphs/guides/contract-analyzer.mdx @@ -0,0 +1,103 @@ +--- +title: Smart Contract Analysis with Cana CLI +--- + +# Cana CLI: Quick & Efficient Contract Analysis + +**Cana CLI** is a command-line tool that streamlines helpful smart contract metadata analysis specific to subgraph development across multiple EVM-compatible chains. + +## 📌 Key Features + +- Detect deployment blocks +- Verify source code +- Extract ABIs & event signatures +- Identify proxy and implementation contracts +- Support multiple chains + +## 🚀 Installation & Setup + +Install Cana globally using npm: + +```bash +npm install -g contract-analyzer +``` + +Set up a blockchain for analysis: + +```bash +cana setup +``` + +Provide the required block explorer API and block explorer endpoint URL details when prompted. + +Running `cana setup` creates a configuration file at `~/.contract-analyzer/config.json`. This file stores your block explorer API credentials, endpoint URLs, and chain selection preferences for future use. + +## 🍳 Usage + +### 🔹 Chain Selection + +Cana supports multiple EVM-compatible chains. + +List chains added with: + +```bash +cana chains +``` + +Then select a chain with: + +```bash +cana chains --switch +``` + +Once a chain is selected, all subsequent contract analases will continue on that chain. + +### 🔹 Basic Contract Analysis + +Analyze a contract with: + +```bash +cana analyze 0xContractAddress +``` + +or + +```bash +cana -a 0xContractAddress +``` + +This command displays essential contract information in the terminal using a clear, organized format. + +### 🔹 Understanding Output + +Cana organizes results into the terminal as well as into a structured directory when detailed contract data is successfully retrieved: + +``` +contracts-analyzed/ +└── ContractName_chainName_YYYY-MM-DD/ + ├── contract/ # Folder for individual contract files + ├── abi.json # Contract ABI + └── event-information.json # Event signatures and examples +``` + +### 🔹 Chain Management + +Add and manage chains: + +```bash +cana setup # Add a new chain +cana chains # List configured chains +cana chains -s # Swich chains. +``` + +## ⚠️ Troubleshooting + +- **Missing Data**: Ensure the contract address is correct, verified on the block explorer, and that your API key has the required permissions. + +## ✅ Requirements + +- Node.js v16+ +- npm v6+ +- Block explorer API keys + +Keep your contract analyses efficient and well-organized. 🚀 diff --git a/website/src/pages/hi/subgraphs/guides/_meta.js b/website/src/pages/hi/subgraphs/guides/_meta.js index e642f12ef11d..37e18bc51651 100644 --- a/website/src/pages/hi/subgraphs/guides/_meta.js +++ b/website/src/pages/hi/subgraphs/guides/_meta.js @@ -8,4 +8,5 @@ export default { enums: '', 'secure-api-keys-nextjs': '', polymarket: '', + 'contract-analyzer': '', } diff --git a/website/src/pages/hi/subgraphs/guides/contract-analyzer.mdx b/website/src/pages/hi/subgraphs/guides/contract-analyzer.mdx new file mode 100644 index 000000000000..084ac8d28a00 --- /dev/null +++ b/website/src/pages/hi/subgraphs/guides/contract-analyzer.mdx @@ -0,0 +1,103 @@ +--- +title: Smart Contract Analysis with Cana CLI +--- + +# Cana CLI: Quick & Efficient Contract Analysis + +**Cana CLI** is a command-line tool that streamlines helpful smart contract metadata analysis specific to subgraph development across multiple EVM-compatible chains. + +## 📌 Key Features + +- Detect deployment blocks +- Verify source code +- Extract ABIs & event signatures +- Identify proxy and implementation contracts +- Support multiple chains + +## 🚀 Installation & Setup + +Install Cana globally using npm: + +```bash +npm install -g contract-analyzer +``` + +Set up a blockchain for analysis: + +```bash +cana setup +``` + +Provide the required block explorer API and block explorer endpoint URL details when prompted. + +Running `cana setup` creates a configuration file at `~/.contract-analyzer/config.json`. This file stores your block explorer API credentials, endpoint URLs, and chain selection preferences for future use. + +## 🍳 Usage + +### 🔹 Chain Selection + +Cana supports multiple EVM-compatible chains. + +List chains added with: + +```bash +cana chains +``` + +Then select a chain with: + +```bash +cana chains --switch +``` + +Once a chain is selected, all subsequent contract analases will continue on that chain. + +### 🔹 Basic Contract Analysis + +Analyze a contract with: + +```bash +cana analyze 0xContractAddress +``` + +or + +```bash +cana -a 0xContractAddress +``` + +This command displays essential contract information in the terminal using a clear, organized format. + +### 🔹 Understanding Output + +Cana organizes results into the terminal as well as into a structured directory when detailed contract data is successfully retrieved: + +``` +contracts-analyzed/ +└── ContractName_chainName_YYYY-MM-DD/ + ├── contract/ # Folder for individual contract files + ├── abi.json # Contract ABI + └── event-information.json # Event signatures and examples +``` + +### 🔹 Chain Management + +Add and manage chains: + +```bash +cana setup # Add a new chain +cana chains # List configured chains +cana chains -s # Swich chains. +``` + +## ⚠️ Troubleshooting + +- **Missing Data**: Ensure the contract address is correct, verified on the block explorer, and that your API key has the required permissions. + +## ✅ Requirements + +- Node.js v16+ +- npm v6+ +- Block explorer API keys + +Keep your contract analyses efficient and well-organized. 🚀 diff --git a/website/src/pages/it/subgraphs/guides/_meta.js b/website/src/pages/it/subgraphs/guides/_meta.js index e642f12ef11d..37e18bc51651 100644 --- a/website/src/pages/it/subgraphs/guides/_meta.js +++ b/website/src/pages/it/subgraphs/guides/_meta.js @@ -8,4 +8,5 @@ export default { enums: '', 'secure-api-keys-nextjs': '', polymarket: '', + 'contract-analyzer': '', } diff --git a/website/src/pages/it/subgraphs/guides/contract-analyzer.mdx b/website/src/pages/it/subgraphs/guides/contract-analyzer.mdx new file mode 100644 index 000000000000..084ac8d28a00 --- /dev/null +++ b/website/src/pages/it/subgraphs/guides/contract-analyzer.mdx @@ -0,0 +1,103 @@ +--- +title: Smart Contract Analysis with Cana CLI +--- + +# Cana CLI: Quick & Efficient Contract Analysis + +**Cana CLI** is a command-line tool that streamlines helpful smart contract metadata analysis specific to subgraph development across multiple EVM-compatible chains. + +## 📌 Key Features + +- Detect deployment blocks +- Verify source code +- Extract ABIs & event signatures +- Identify proxy and implementation contracts +- Support multiple chains + +## 🚀 Installation & Setup + +Install Cana globally using npm: + +```bash +npm install -g contract-analyzer +``` + +Set up a blockchain for analysis: + +```bash +cana setup +``` + +Provide the required block explorer API and block explorer endpoint URL details when prompted. + +Running `cana setup` creates a configuration file at `~/.contract-analyzer/config.json`. This file stores your block explorer API credentials, endpoint URLs, and chain selection preferences for future use. + +## 🍳 Usage + +### 🔹 Chain Selection + +Cana supports multiple EVM-compatible chains. + +List chains added with: + +```bash +cana chains +``` + +Then select a chain with: + +```bash +cana chains --switch +``` + +Once a chain is selected, all subsequent contract analases will continue on that chain. + +### 🔹 Basic Contract Analysis + +Analyze a contract with: + +```bash +cana analyze 0xContractAddress +``` + +or + +```bash +cana -a 0xContractAddress +``` + +This command displays essential contract information in the terminal using a clear, organized format. + +### 🔹 Understanding Output + +Cana organizes results into the terminal as well as into a structured directory when detailed contract data is successfully retrieved: + +``` +contracts-analyzed/ +└── ContractName_chainName_YYYY-MM-DD/ + ├── contract/ # Folder for individual contract files + ├── abi.json # Contract ABI + └── event-information.json # Event signatures and examples +``` + +### 🔹 Chain Management + +Add and manage chains: + +```bash +cana setup # Add a new chain +cana chains # List configured chains +cana chains -s # Swich chains. +``` + +## ⚠️ Troubleshooting + +- **Missing Data**: Ensure the contract address is correct, verified on the block explorer, and that your API key has the required permissions. + +## ✅ Requirements + +- Node.js v16+ +- npm v6+ +- Block explorer API keys + +Keep your contract analyses efficient and well-organized. 🚀 diff --git a/website/src/pages/ja/subgraphs/guides/_meta.js b/website/src/pages/ja/subgraphs/guides/_meta.js index e642f12ef11d..37e18bc51651 100644 --- a/website/src/pages/ja/subgraphs/guides/_meta.js +++ b/website/src/pages/ja/subgraphs/guides/_meta.js @@ -8,4 +8,5 @@ export default { enums: '', 'secure-api-keys-nextjs': '', polymarket: '', + 'contract-analyzer': '', } diff --git a/website/src/pages/ja/subgraphs/guides/contract-analyzer.mdx b/website/src/pages/ja/subgraphs/guides/contract-analyzer.mdx new file mode 100644 index 000000000000..084ac8d28a00 --- /dev/null +++ b/website/src/pages/ja/subgraphs/guides/contract-analyzer.mdx @@ -0,0 +1,103 @@ +--- +title: Smart Contract Analysis with Cana CLI +--- + +# Cana CLI: Quick & Efficient Contract Analysis + +**Cana CLI** is a command-line tool that streamlines helpful smart contract metadata analysis specific to subgraph development across multiple EVM-compatible chains. + +## 📌 Key Features + +- Detect deployment blocks +- Verify source code +- Extract ABIs & event signatures +- Identify proxy and implementation contracts +- Support multiple chains + +## 🚀 Installation & Setup + +Install Cana globally using npm: + +```bash +npm install -g contract-analyzer +``` + +Set up a blockchain for analysis: + +```bash +cana setup +``` + +Provide the required block explorer API and block explorer endpoint URL details when prompted. + +Running `cana setup` creates a configuration file at `~/.contract-analyzer/config.json`. This file stores your block explorer API credentials, endpoint URLs, and chain selection preferences for future use. + +## 🍳 Usage + +### 🔹 Chain Selection + +Cana supports multiple EVM-compatible chains. + +List chains added with: + +```bash +cana chains +``` + +Then select a chain with: + +```bash +cana chains --switch +``` + +Once a chain is selected, all subsequent contract analases will continue on that chain. + +### 🔹 Basic Contract Analysis + +Analyze a contract with: + +```bash +cana analyze 0xContractAddress +``` + +or + +```bash +cana -a 0xContractAddress +``` + +This command displays essential contract information in the terminal using a clear, organized format. + +### 🔹 Understanding Output + +Cana organizes results into the terminal as well as into a structured directory when detailed contract data is successfully retrieved: + +``` +contracts-analyzed/ +└── ContractName_chainName_YYYY-MM-DD/ + ├── contract/ # Folder for individual contract files + ├── abi.json # Contract ABI + └── event-information.json # Event signatures and examples +``` + +### 🔹 Chain Management + +Add and manage chains: + +```bash +cana setup # Add a new chain +cana chains # List configured chains +cana chains -s # Swich chains. +``` + +## ⚠️ Troubleshooting + +- **Missing Data**: Ensure the contract address is correct, verified on the block explorer, and that your API key has the required permissions. + +## ✅ Requirements + +- Node.js v16+ +- npm v6+ +- Block explorer API keys + +Keep your contract analyses efficient and well-organized. 🚀 diff --git a/website/src/pages/ko/subgraphs/guides/_meta.js b/website/src/pages/ko/subgraphs/guides/_meta.js index e642f12ef11d..37e18bc51651 100644 --- a/website/src/pages/ko/subgraphs/guides/_meta.js +++ b/website/src/pages/ko/subgraphs/guides/_meta.js @@ -8,4 +8,5 @@ export default { enums: '', 'secure-api-keys-nextjs': '', polymarket: '', + 'contract-analyzer': '', } diff --git a/website/src/pages/ko/subgraphs/guides/contract-analyzer.mdx b/website/src/pages/ko/subgraphs/guides/contract-analyzer.mdx new file mode 100644 index 000000000000..084ac8d28a00 --- /dev/null +++ b/website/src/pages/ko/subgraphs/guides/contract-analyzer.mdx @@ -0,0 +1,103 @@ +--- +title: Smart Contract Analysis with Cana CLI +--- + +# Cana CLI: Quick & Efficient Contract Analysis + +**Cana CLI** is a command-line tool that streamlines helpful smart contract metadata analysis specific to subgraph development across multiple EVM-compatible chains. + +## 📌 Key Features + +- Detect deployment blocks +- Verify source code +- Extract ABIs & event signatures +- Identify proxy and implementation contracts +- Support multiple chains + +## 🚀 Installation & Setup + +Install Cana globally using npm: + +```bash +npm install -g contract-analyzer +``` + +Set up a blockchain for analysis: + +```bash +cana setup +``` + +Provide the required block explorer API and block explorer endpoint URL details when prompted. + +Running `cana setup` creates a configuration file at `~/.contract-analyzer/config.json`. This file stores your block explorer API credentials, endpoint URLs, and chain selection preferences for future use. + +## 🍳 Usage + +### 🔹 Chain Selection + +Cana supports multiple EVM-compatible chains. + +List chains added with: + +```bash +cana chains +``` + +Then select a chain with: + +```bash +cana chains --switch +``` + +Once a chain is selected, all subsequent contract analases will continue on that chain. + +### 🔹 Basic Contract Analysis + +Analyze a contract with: + +```bash +cana analyze 0xContractAddress +``` + +or + +```bash +cana -a 0xContractAddress +``` + +This command displays essential contract information in the terminal using a clear, organized format. + +### 🔹 Understanding Output + +Cana organizes results into the terminal as well as into a structured directory when detailed contract data is successfully retrieved: + +``` +contracts-analyzed/ +└── ContractName_chainName_YYYY-MM-DD/ + ├── contract/ # Folder for individual contract files + ├── abi.json # Contract ABI + └── event-information.json # Event signatures and examples +``` + +### 🔹 Chain Management + +Add and manage chains: + +```bash +cana setup # Add a new chain +cana chains # List configured chains +cana chains -s # Swich chains. +``` + +## ⚠️ Troubleshooting + +- **Missing Data**: Ensure the contract address is correct, verified on the block explorer, and that your API key has the required permissions. + +## ✅ Requirements + +- Node.js v16+ +- npm v6+ +- Block explorer API keys + +Keep your contract analyses efficient and well-organized. 🚀 diff --git a/website/src/pages/mr/subgraphs/guides/_meta.js b/website/src/pages/mr/subgraphs/guides/_meta.js index e642f12ef11d..37e18bc51651 100644 --- a/website/src/pages/mr/subgraphs/guides/_meta.js +++ b/website/src/pages/mr/subgraphs/guides/_meta.js @@ -8,4 +8,5 @@ export default { enums: '', 'secure-api-keys-nextjs': '', polymarket: '', + 'contract-analyzer': '', } diff --git a/website/src/pages/mr/subgraphs/guides/contract-analyzer.mdx b/website/src/pages/mr/subgraphs/guides/contract-analyzer.mdx new file mode 100644 index 000000000000..084ac8d28a00 --- /dev/null +++ b/website/src/pages/mr/subgraphs/guides/contract-analyzer.mdx @@ -0,0 +1,103 @@ +--- +title: Smart Contract Analysis with Cana CLI +--- + +# Cana CLI: Quick & Efficient Contract Analysis + +**Cana CLI** is a command-line tool that streamlines helpful smart contract metadata analysis specific to subgraph development across multiple EVM-compatible chains. + +## 📌 Key Features + +- Detect deployment blocks +- Verify source code +- Extract ABIs & event signatures +- Identify proxy and implementation contracts +- Support multiple chains + +## 🚀 Installation & Setup + +Install Cana globally using npm: + +```bash +npm install -g contract-analyzer +``` + +Set up a blockchain for analysis: + +```bash +cana setup +``` + +Provide the required block explorer API and block explorer endpoint URL details when prompted. + +Running `cana setup` creates a configuration file at `~/.contract-analyzer/config.json`. This file stores your block explorer API credentials, endpoint URLs, and chain selection preferences for future use. + +## 🍳 Usage + +### 🔹 Chain Selection + +Cana supports multiple EVM-compatible chains. + +List chains added with: + +```bash +cana chains +``` + +Then select a chain with: + +```bash +cana chains --switch +``` + +Once a chain is selected, all subsequent contract analases will continue on that chain. + +### 🔹 Basic Contract Analysis + +Analyze a contract with: + +```bash +cana analyze 0xContractAddress +``` + +or + +```bash +cana -a 0xContractAddress +``` + +This command displays essential contract information in the terminal using a clear, organized format. + +### 🔹 Understanding Output + +Cana organizes results into the terminal as well as into a structured directory when detailed contract data is successfully retrieved: + +``` +contracts-analyzed/ +└── ContractName_chainName_YYYY-MM-DD/ + ├── contract/ # Folder for individual contract files + ├── abi.json # Contract ABI + └── event-information.json # Event signatures and examples +``` + +### 🔹 Chain Management + +Add and manage chains: + +```bash +cana setup # Add a new chain +cana chains # List configured chains +cana chains -s # Swich chains. +``` + +## ⚠️ Troubleshooting + +- **Missing Data**: Ensure the contract address is correct, verified on the block explorer, and that your API key has the required permissions. + +## ✅ Requirements + +- Node.js v16+ +- npm v6+ +- Block explorer API keys + +Keep your contract analyses efficient and well-organized. 🚀 diff --git a/website/src/pages/nl/subgraphs/guides/_meta.js b/website/src/pages/nl/subgraphs/guides/_meta.js index e642f12ef11d..37e18bc51651 100644 --- a/website/src/pages/nl/subgraphs/guides/_meta.js +++ b/website/src/pages/nl/subgraphs/guides/_meta.js @@ -8,4 +8,5 @@ export default { enums: '', 'secure-api-keys-nextjs': '', polymarket: '', + 'contract-analyzer': '', } diff --git a/website/src/pages/nl/subgraphs/guides/contract-analyzer.mdx b/website/src/pages/nl/subgraphs/guides/contract-analyzer.mdx new file mode 100644 index 000000000000..084ac8d28a00 --- /dev/null +++ b/website/src/pages/nl/subgraphs/guides/contract-analyzer.mdx @@ -0,0 +1,103 @@ +--- +title: Smart Contract Analysis with Cana CLI +--- + +# Cana CLI: Quick & Efficient Contract Analysis + +**Cana CLI** is a command-line tool that streamlines helpful smart contract metadata analysis specific to subgraph development across multiple EVM-compatible chains. + +## 📌 Key Features + +- Detect deployment blocks +- Verify source code +- Extract ABIs & event signatures +- Identify proxy and implementation contracts +- Support multiple chains + +## 🚀 Installation & Setup + +Install Cana globally using npm: + +```bash +npm install -g contract-analyzer +``` + +Set up a blockchain for analysis: + +```bash +cana setup +``` + +Provide the required block explorer API and block explorer endpoint URL details when prompted. + +Running `cana setup` creates a configuration file at `~/.contract-analyzer/config.json`. This file stores your block explorer API credentials, endpoint URLs, and chain selection preferences for future use. + +## 🍳 Usage + +### 🔹 Chain Selection + +Cana supports multiple EVM-compatible chains. + +List chains added with: + +```bash +cana chains +``` + +Then select a chain with: + +```bash +cana chains --switch +``` + +Once a chain is selected, all subsequent contract analases will continue on that chain. + +### 🔹 Basic Contract Analysis + +Analyze a contract with: + +```bash +cana analyze 0xContractAddress +``` + +or + +```bash +cana -a 0xContractAddress +``` + +This command displays essential contract information in the terminal using a clear, organized format. + +### 🔹 Understanding Output + +Cana organizes results into the terminal as well as into a structured directory when detailed contract data is successfully retrieved: + +``` +contracts-analyzed/ +└── ContractName_chainName_YYYY-MM-DD/ + ├── contract/ # Folder for individual contract files + ├── abi.json # Contract ABI + └── event-information.json # Event signatures and examples +``` + +### 🔹 Chain Management + +Add and manage chains: + +```bash +cana setup # Add a new chain +cana chains # List configured chains +cana chains -s # Swich chains. +``` + +## ⚠️ Troubleshooting + +- **Missing Data**: Ensure the contract address is correct, verified on the block explorer, and that your API key has the required permissions. + +## ✅ Requirements + +- Node.js v16+ +- npm v6+ +- Block explorer API keys + +Keep your contract analyses efficient and well-organized. 🚀 diff --git a/website/src/pages/pl/subgraphs/guides/_meta.js b/website/src/pages/pl/subgraphs/guides/_meta.js index e642f12ef11d..37e18bc51651 100644 --- a/website/src/pages/pl/subgraphs/guides/_meta.js +++ b/website/src/pages/pl/subgraphs/guides/_meta.js @@ -8,4 +8,5 @@ export default { enums: '', 'secure-api-keys-nextjs': '', polymarket: '', + 'contract-analyzer': '', } diff --git a/website/src/pages/pl/subgraphs/guides/contract-analyzer.mdx b/website/src/pages/pl/subgraphs/guides/contract-analyzer.mdx new file mode 100644 index 000000000000..084ac8d28a00 --- /dev/null +++ b/website/src/pages/pl/subgraphs/guides/contract-analyzer.mdx @@ -0,0 +1,103 @@ +--- +title: Smart Contract Analysis with Cana CLI +--- + +# Cana CLI: Quick & Efficient Contract Analysis + +**Cana CLI** is a command-line tool that streamlines helpful smart contract metadata analysis specific to subgraph development across multiple EVM-compatible chains. + +## 📌 Key Features + +- Detect deployment blocks +- Verify source code +- Extract ABIs & event signatures +- Identify proxy and implementation contracts +- Support multiple chains + +## 🚀 Installation & Setup + +Install Cana globally using npm: + +```bash +npm install -g contract-analyzer +``` + +Set up a blockchain for analysis: + +```bash +cana setup +``` + +Provide the required block explorer API and block explorer endpoint URL details when prompted. + +Running `cana setup` creates a configuration file at `~/.contract-analyzer/config.json`. This file stores your block explorer API credentials, endpoint URLs, and chain selection preferences for future use. + +## 🍳 Usage + +### 🔹 Chain Selection + +Cana supports multiple EVM-compatible chains. + +List chains added with: + +```bash +cana chains +``` + +Then select a chain with: + +```bash +cana chains --switch +``` + +Once a chain is selected, all subsequent contract analases will continue on that chain. + +### 🔹 Basic Contract Analysis + +Analyze a contract with: + +```bash +cana analyze 0xContractAddress +``` + +or + +```bash +cana -a 0xContractAddress +``` + +This command displays essential contract information in the terminal using a clear, organized format. + +### 🔹 Understanding Output + +Cana organizes results into the terminal as well as into a structured directory when detailed contract data is successfully retrieved: + +``` +contracts-analyzed/ +└── ContractName_chainName_YYYY-MM-DD/ + ├── contract/ # Folder for individual contract files + ├── abi.json # Contract ABI + └── event-information.json # Event signatures and examples +``` + +### 🔹 Chain Management + +Add and manage chains: + +```bash +cana setup # Add a new chain +cana chains # List configured chains +cana chains -s # Swich chains. +``` + +## ⚠️ Troubleshooting + +- **Missing Data**: Ensure the contract address is correct, verified on the block explorer, and that your API key has the required permissions. + +## ✅ Requirements + +- Node.js v16+ +- npm v6+ +- Block explorer API keys + +Keep your contract analyses efficient and well-organized. 🚀 diff --git a/website/src/pages/pt/subgraphs/guides/_meta.js b/website/src/pages/pt/subgraphs/guides/_meta.js index e642f12ef11d..37e18bc51651 100644 --- a/website/src/pages/pt/subgraphs/guides/_meta.js +++ b/website/src/pages/pt/subgraphs/guides/_meta.js @@ -8,4 +8,5 @@ export default { enums: '', 'secure-api-keys-nextjs': '', polymarket: '', + 'contract-analyzer': '', } diff --git a/website/src/pages/pt/subgraphs/guides/contract-analyzer.mdx b/website/src/pages/pt/subgraphs/guides/contract-analyzer.mdx new file mode 100644 index 000000000000..084ac8d28a00 --- /dev/null +++ b/website/src/pages/pt/subgraphs/guides/contract-analyzer.mdx @@ -0,0 +1,103 @@ +--- +title: Smart Contract Analysis with Cana CLI +--- + +# Cana CLI: Quick & Efficient Contract Analysis + +**Cana CLI** is a command-line tool that streamlines helpful smart contract metadata analysis specific to subgraph development across multiple EVM-compatible chains. + +## 📌 Key Features + +- Detect deployment blocks +- Verify source code +- Extract ABIs & event signatures +- Identify proxy and implementation contracts +- Support multiple chains + +## 🚀 Installation & Setup + +Install Cana globally using npm: + +```bash +npm install -g contract-analyzer +``` + +Set up a blockchain for analysis: + +```bash +cana setup +``` + +Provide the required block explorer API and block explorer endpoint URL details when prompted. + +Running `cana setup` creates a configuration file at `~/.contract-analyzer/config.json`. This file stores your block explorer API credentials, endpoint URLs, and chain selection preferences for future use. + +## 🍳 Usage + +### 🔹 Chain Selection + +Cana supports multiple EVM-compatible chains. + +List chains added with: + +```bash +cana chains +``` + +Then select a chain with: + +```bash +cana chains --switch +``` + +Once a chain is selected, all subsequent contract analases will continue on that chain. + +### 🔹 Basic Contract Analysis + +Analyze a contract with: + +```bash +cana analyze 0xContractAddress +``` + +or + +```bash +cana -a 0xContractAddress +``` + +This command displays essential contract information in the terminal using a clear, organized format. + +### 🔹 Understanding Output + +Cana organizes results into the terminal as well as into a structured directory when detailed contract data is successfully retrieved: + +``` +contracts-analyzed/ +└── ContractName_chainName_YYYY-MM-DD/ + ├── contract/ # Folder for individual contract files + ├── abi.json # Contract ABI + └── event-information.json # Event signatures and examples +``` + +### 🔹 Chain Management + +Add and manage chains: + +```bash +cana setup # Add a new chain +cana chains # List configured chains +cana chains -s # Swich chains. +``` + +## ⚠️ Troubleshooting + +- **Missing Data**: Ensure the contract address is correct, verified on the block explorer, and that your API key has the required permissions. + +## ✅ Requirements + +- Node.js v16+ +- npm v6+ +- Block explorer API keys + +Keep your contract analyses efficient and well-organized. 🚀 diff --git a/website/src/pages/ro/subgraphs/guides/_meta.js b/website/src/pages/ro/subgraphs/guides/_meta.js index e642f12ef11d..37e18bc51651 100644 --- a/website/src/pages/ro/subgraphs/guides/_meta.js +++ b/website/src/pages/ro/subgraphs/guides/_meta.js @@ -8,4 +8,5 @@ export default { enums: '', 'secure-api-keys-nextjs': '', polymarket: '', + 'contract-analyzer': '', } diff --git a/website/src/pages/ro/subgraphs/guides/contract-analyzer.mdx b/website/src/pages/ro/subgraphs/guides/contract-analyzer.mdx new file mode 100644 index 000000000000..084ac8d28a00 --- /dev/null +++ b/website/src/pages/ro/subgraphs/guides/contract-analyzer.mdx @@ -0,0 +1,103 @@ +--- +title: Smart Contract Analysis with Cana CLI +--- + +# Cana CLI: Quick & Efficient Contract Analysis + +**Cana CLI** is a command-line tool that streamlines helpful smart contract metadata analysis specific to subgraph development across multiple EVM-compatible chains. + +## 📌 Key Features + +- Detect deployment blocks +- Verify source code +- Extract ABIs & event signatures +- Identify proxy and implementation contracts +- Support multiple chains + +## 🚀 Installation & Setup + +Install Cana globally using npm: + +```bash +npm install -g contract-analyzer +``` + +Set up a blockchain for analysis: + +```bash +cana setup +``` + +Provide the required block explorer API and block explorer endpoint URL details when prompted. + +Running `cana setup` creates a configuration file at `~/.contract-analyzer/config.json`. This file stores your block explorer API credentials, endpoint URLs, and chain selection preferences for future use. + +## 🍳 Usage + +### 🔹 Chain Selection + +Cana supports multiple EVM-compatible chains. + +List chains added with: + +```bash +cana chains +``` + +Then select a chain with: + +```bash +cana chains --switch +``` + +Once a chain is selected, all subsequent contract analases will continue on that chain. + +### 🔹 Basic Contract Analysis + +Analyze a contract with: + +```bash +cana analyze 0xContractAddress +``` + +or + +```bash +cana -a 0xContractAddress +``` + +This command displays essential contract information in the terminal using a clear, organized format. + +### 🔹 Understanding Output + +Cana organizes results into the terminal as well as into a structured directory when detailed contract data is successfully retrieved: + +``` +contracts-analyzed/ +└── ContractName_chainName_YYYY-MM-DD/ + ├── contract/ # Folder for individual contract files + ├── abi.json # Contract ABI + └── event-information.json # Event signatures and examples +``` + +### 🔹 Chain Management + +Add and manage chains: + +```bash +cana setup # Add a new chain +cana chains # List configured chains +cana chains -s # Swich chains. +``` + +## ⚠️ Troubleshooting + +- **Missing Data**: Ensure the contract address is correct, verified on the block explorer, and that your API key has the required permissions. + +## ✅ Requirements + +- Node.js v16+ +- npm v6+ +- Block explorer API keys + +Keep your contract analyses efficient and well-organized. 🚀 diff --git a/website/src/pages/ru/subgraphs/guides/_meta.js b/website/src/pages/ru/subgraphs/guides/_meta.js index e642f12ef11d..37e18bc51651 100644 --- a/website/src/pages/ru/subgraphs/guides/_meta.js +++ b/website/src/pages/ru/subgraphs/guides/_meta.js @@ -8,4 +8,5 @@ export default { enums: '', 'secure-api-keys-nextjs': '', polymarket: '', + 'contract-analyzer': '', } diff --git a/website/src/pages/ru/subgraphs/guides/contract-analyzer.mdx b/website/src/pages/ru/subgraphs/guides/contract-analyzer.mdx new file mode 100644 index 000000000000..084ac8d28a00 --- /dev/null +++ b/website/src/pages/ru/subgraphs/guides/contract-analyzer.mdx @@ -0,0 +1,103 @@ +--- +title: Smart Contract Analysis with Cana CLI +--- + +# Cana CLI: Quick & Efficient Contract Analysis + +**Cana CLI** is a command-line tool that streamlines helpful smart contract metadata analysis specific to subgraph development across multiple EVM-compatible chains. + +## 📌 Key Features + +- Detect deployment blocks +- Verify source code +- Extract ABIs & event signatures +- Identify proxy and implementation contracts +- Support multiple chains + +## 🚀 Installation & Setup + +Install Cana globally using npm: + +```bash +npm install -g contract-analyzer +``` + +Set up a blockchain for analysis: + +```bash +cana setup +``` + +Provide the required block explorer API and block explorer endpoint URL details when prompted. + +Running `cana setup` creates a configuration file at `~/.contract-analyzer/config.json`. This file stores your block explorer API credentials, endpoint URLs, and chain selection preferences for future use. + +## 🍳 Usage + +### 🔹 Chain Selection + +Cana supports multiple EVM-compatible chains. + +List chains added with: + +```bash +cana chains +``` + +Then select a chain with: + +```bash +cana chains --switch +``` + +Once a chain is selected, all subsequent contract analases will continue on that chain. + +### 🔹 Basic Contract Analysis + +Analyze a contract with: + +```bash +cana analyze 0xContractAddress +``` + +or + +```bash +cana -a 0xContractAddress +``` + +This command displays essential contract information in the terminal using a clear, organized format. + +### 🔹 Understanding Output + +Cana organizes results into the terminal as well as into a structured directory when detailed contract data is successfully retrieved: + +``` +contracts-analyzed/ +└── ContractName_chainName_YYYY-MM-DD/ + ├── contract/ # Folder for individual contract files + ├── abi.json # Contract ABI + └── event-information.json # Event signatures and examples +``` + +### 🔹 Chain Management + +Add and manage chains: + +```bash +cana setup # Add a new chain +cana chains # List configured chains +cana chains -s # Swich chains. +``` + +## ⚠️ Troubleshooting + +- **Missing Data**: Ensure the contract address is correct, verified on the block explorer, and that your API key has the required permissions. + +## ✅ Requirements + +- Node.js v16+ +- npm v6+ +- Block explorer API keys + +Keep your contract analyses efficient and well-organized. 🚀 diff --git a/website/src/pages/sv/subgraphs/guides/_meta.js b/website/src/pages/sv/subgraphs/guides/_meta.js index e642f12ef11d..37e18bc51651 100644 --- a/website/src/pages/sv/subgraphs/guides/_meta.js +++ b/website/src/pages/sv/subgraphs/guides/_meta.js @@ -8,4 +8,5 @@ export default { enums: '', 'secure-api-keys-nextjs': '', polymarket: '', + 'contract-analyzer': '', } diff --git a/website/src/pages/sv/subgraphs/guides/contract-analyzer.mdx b/website/src/pages/sv/subgraphs/guides/contract-analyzer.mdx new file mode 100644 index 000000000000..084ac8d28a00 --- /dev/null +++ b/website/src/pages/sv/subgraphs/guides/contract-analyzer.mdx @@ -0,0 +1,103 @@ +--- +title: Smart Contract Analysis with Cana CLI +--- + +# Cana CLI: Quick & Efficient Contract Analysis + +**Cana CLI** is a command-line tool that streamlines helpful smart contract metadata analysis specific to subgraph development across multiple EVM-compatible chains. + +## 📌 Key Features + +- Detect deployment blocks +- Verify source code +- Extract ABIs & event signatures +- Identify proxy and implementation contracts +- Support multiple chains + +## 🚀 Installation & Setup + +Install Cana globally using npm: + +```bash +npm install -g contract-analyzer +``` + +Set up a blockchain for analysis: + +```bash +cana setup +``` + +Provide the required block explorer API and block explorer endpoint URL details when prompted. + +Running `cana setup` creates a configuration file at `~/.contract-analyzer/config.json`. This file stores your block explorer API credentials, endpoint URLs, and chain selection preferences for future use. + +## 🍳 Usage + +### 🔹 Chain Selection + +Cana supports multiple EVM-compatible chains. + +List chains added with: + +```bash +cana chains +``` + +Then select a chain with: + +```bash +cana chains --switch +``` + +Once a chain is selected, all subsequent contract analases will continue on that chain. + +### 🔹 Basic Contract Analysis + +Analyze a contract with: + +```bash +cana analyze 0xContractAddress +``` + +or + +```bash +cana -a 0xContractAddress +``` + +This command displays essential contract information in the terminal using a clear, organized format. + +### 🔹 Understanding Output + +Cana organizes results into the terminal as well as into a structured directory when detailed contract data is successfully retrieved: + +``` +contracts-analyzed/ +└── ContractName_chainName_YYYY-MM-DD/ + ├── contract/ # Folder for individual contract files + ├── abi.json # Contract ABI + └── event-information.json # Event signatures and examples +``` + +### 🔹 Chain Management + +Add and manage chains: + +```bash +cana setup # Add a new chain +cana chains # List configured chains +cana chains -s # Swich chains. +``` + +## ⚠️ Troubleshooting + +- **Missing Data**: Ensure the contract address is correct, verified on the block explorer, and that your API key has the required permissions. + +## ✅ Requirements + +- Node.js v16+ +- npm v6+ +- Block explorer API keys + +Keep your contract analyses efficient and well-organized. 🚀 diff --git a/website/src/pages/tr/subgraphs/guides/_meta.js b/website/src/pages/tr/subgraphs/guides/_meta.js index e642f12ef11d..37e18bc51651 100644 --- a/website/src/pages/tr/subgraphs/guides/_meta.js +++ b/website/src/pages/tr/subgraphs/guides/_meta.js @@ -8,4 +8,5 @@ export default { enums: '', 'secure-api-keys-nextjs': '', polymarket: '', + 'contract-analyzer': '', } diff --git a/website/src/pages/tr/subgraphs/guides/contract-analyzer.mdx b/website/src/pages/tr/subgraphs/guides/contract-analyzer.mdx new file mode 100644 index 000000000000..084ac8d28a00 --- /dev/null +++ b/website/src/pages/tr/subgraphs/guides/contract-analyzer.mdx @@ -0,0 +1,103 @@ +--- +title: Smart Contract Analysis with Cana CLI +--- + +# Cana CLI: Quick & Efficient Contract Analysis + +**Cana CLI** is a command-line tool that streamlines helpful smart contract metadata analysis specific to subgraph development across multiple EVM-compatible chains. + +## 📌 Key Features + +- Detect deployment blocks +- Verify source code +- Extract ABIs & event signatures +- Identify proxy and implementation contracts +- Support multiple chains + +## 🚀 Installation & Setup + +Install Cana globally using npm: + +```bash +npm install -g contract-analyzer +``` + +Set up a blockchain for analysis: + +```bash +cana setup +``` + +Provide the required block explorer API and block explorer endpoint URL details when prompted. + +Running `cana setup` creates a configuration file at `~/.contract-analyzer/config.json`. This file stores your block explorer API credentials, endpoint URLs, and chain selection preferences for future use. + +## 🍳 Usage + +### 🔹 Chain Selection + +Cana supports multiple EVM-compatible chains. + +List chains added with: + +```bash +cana chains +``` + +Then select a chain with: + +```bash +cana chains --switch +``` + +Once a chain is selected, all subsequent contract analases will continue on that chain. + +### 🔹 Basic Contract Analysis + +Analyze a contract with: + +```bash +cana analyze 0xContractAddress +``` + +or + +```bash +cana -a 0xContractAddress +``` + +This command displays essential contract information in the terminal using a clear, organized format. + +### 🔹 Understanding Output + +Cana organizes results into the terminal as well as into a structured directory when detailed contract data is successfully retrieved: + +``` +contracts-analyzed/ +└── ContractName_chainName_YYYY-MM-DD/ + ├── contract/ # Folder for individual contract files + ├── abi.json # Contract ABI + └── event-information.json # Event signatures and examples +``` + +### 🔹 Chain Management + +Add and manage chains: + +```bash +cana setup # Add a new chain +cana chains # List configured chains +cana chains -s # Swich chains. +``` + +## ⚠️ Troubleshooting + +- **Missing Data**: Ensure the contract address is correct, verified on the block explorer, and that your API key has the required permissions. + +## ✅ Requirements + +- Node.js v16+ +- npm v6+ +- Block explorer API keys + +Keep your contract analyses efficient and well-organized. 🚀 diff --git a/website/src/pages/uk/subgraphs/guides/_meta.js b/website/src/pages/uk/subgraphs/guides/_meta.js index e642f12ef11d..37e18bc51651 100644 --- a/website/src/pages/uk/subgraphs/guides/_meta.js +++ b/website/src/pages/uk/subgraphs/guides/_meta.js @@ -8,4 +8,5 @@ export default { enums: '', 'secure-api-keys-nextjs': '', polymarket: '', + 'contract-analyzer': '', } diff --git a/website/src/pages/uk/subgraphs/guides/contract-analyzer.mdx b/website/src/pages/uk/subgraphs/guides/contract-analyzer.mdx new file mode 100644 index 000000000000..084ac8d28a00 --- /dev/null +++ b/website/src/pages/uk/subgraphs/guides/contract-analyzer.mdx @@ -0,0 +1,103 @@ +--- +title: Smart Contract Analysis with Cana CLI +--- + +# Cana CLI: Quick & Efficient Contract Analysis + +**Cana CLI** is a command-line tool that streamlines helpful smart contract metadata analysis specific to subgraph development across multiple EVM-compatible chains. + +## 📌 Key Features + +- Detect deployment blocks +- Verify source code +- Extract ABIs & event signatures +- Identify proxy and implementation contracts +- Support multiple chains + +## 🚀 Installation & Setup + +Install Cana globally using npm: + +```bash +npm install -g contract-analyzer +``` + +Set up a blockchain for analysis: + +```bash +cana setup +``` + +Provide the required block explorer API and block explorer endpoint URL details when prompted. + +Running `cana setup` creates a configuration file at `~/.contract-analyzer/config.json`. This file stores your block explorer API credentials, endpoint URLs, and chain selection preferences for future use. + +## 🍳 Usage + +### 🔹 Chain Selection + +Cana supports multiple EVM-compatible chains. + +List chains added with: + +```bash +cana chains +``` + +Then select a chain with: + +```bash +cana chains --switch +``` + +Once a chain is selected, all subsequent contract analases will continue on that chain. + +### 🔹 Basic Contract Analysis + +Analyze a contract with: + +```bash +cana analyze 0xContractAddress +``` + +or + +```bash +cana -a 0xContractAddress +``` + +This command displays essential contract information in the terminal using a clear, organized format. + +### 🔹 Understanding Output + +Cana organizes results into the terminal as well as into a structured directory when detailed contract data is successfully retrieved: + +``` +contracts-analyzed/ +└── ContractName_chainName_YYYY-MM-DD/ + ├── contract/ # Folder for individual contract files + ├── abi.json # Contract ABI + └── event-information.json # Event signatures and examples +``` + +### 🔹 Chain Management + +Add and manage chains: + +```bash +cana setup # Add a new chain +cana chains # List configured chains +cana chains -s # Swich chains. +``` + +## ⚠️ Troubleshooting + +- **Missing Data**: Ensure the contract address is correct, verified on the block explorer, and that your API key has the required permissions. + +## ✅ Requirements + +- Node.js v16+ +- npm v6+ +- Block explorer API keys + +Keep your contract analyses efficient and well-organized. 🚀 diff --git a/website/src/pages/ur/subgraphs/guides/_meta.js b/website/src/pages/ur/subgraphs/guides/_meta.js index e642f12ef11d..37e18bc51651 100644 --- a/website/src/pages/ur/subgraphs/guides/_meta.js +++ b/website/src/pages/ur/subgraphs/guides/_meta.js @@ -8,4 +8,5 @@ export default { enums: '', 'secure-api-keys-nextjs': '', polymarket: '', + 'contract-analyzer': '', } diff --git a/website/src/pages/ur/subgraphs/guides/contract-analyzer.mdx b/website/src/pages/ur/subgraphs/guides/contract-analyzer.mdx new file mode 100644 index 000000000000..084ac8d28a00 --- /dev/null +++ b/website/src/pages/ur/subgraphs/guides/contract-analyzer.mdx @@ -0,0 +1,103 @@ +--- +title: Smart Contract Analysis with Cana CLI +--- + +# Cana CLI: Quick & Efficient Contract Analysis + +**Cana CLI** is a command-line tool that streamlines helpful smart contract metadata analysis specific to subgraph development across multiple EVM-compatible chains. + +## 📌 Key Features + +- Detect deployment blocks +- Verify source code +- Extract ABIs & event signatures +- Identify proxy and implementation contracts +- Support multiple chains + +## 🚀 Installation & Setup + +Install Cana globally using npm: + +```bash +npm install -g contract-analyzer +``` + +Set up a blockchain for analysis: + +```bash +cana setup +``` + +Provide the required block explorer API and block explorer endpoint URL details when prompted. + +Running `cana setup` creates a configuration file at `~/.contract-analyzer/config.json`. This file stores your block explorer API credentials, endpoint URLs, and chain selection preferences for future use. + +## 🍳 Usage + +### 🔹 Chain Selection + +Cana supports multiple EVM-compatible chains. + +List chains added with: + +```bash +cana chains +``` + +Then select a chain with: + +```bash +cana chains --switch +``` + +Once a chain is selected, all subsequent contract analases will continue on that chain. + +### 🔹 Basic Contract Analysis + +Analyze a contract with: + +```bash +cana analyze 0xContractAddress +``` + +or + +```bash +cana -a 0xContractAddress +``` + +This command displays essential contract information in the terminal using a clear, organized format. + +### 🔹 Understanding Output + +Cana organizes results into the terminal as well as into a structured directory when detailed contract data is successfully retrieved: + +``` +contracts-analyzed/ +└── ContractName_chainName_YYYY-MM-DD/ + ├── contract/ # Folder for individual contract files + ├── abi.json # Contract ABI + └── event-information.json # Event signatures and examples +``` + +### 🔹 Chain Management + +Add and manage chains: + +```bash +cana setup # Add a new chain +cana chains # List configured chains +cana chains -s # Swich chains. +``` + +## ⚠️ Troubleshooting + +- **Missing Data**: Ensure the contract address is correct, verified on the block explorer, and that your API key has the required permissions. + +## ✅ Requirements + +- Node.js v16+ +- npm v6+ +- Block explorer API keys + +Keep your contract analyses efficient and well-organized. 🚀 diff --git a/website/src/pages/vi/subgraphs/guides/_meta.js b/website/src/pages/vi/subgraphs/guides/_meta.js index e642f12ef11d..37e18bc51651 100644 --- a/website/src/pages/vi/subgraphs/guides/_meta.js +++ b/website/src/pages/vi/subgraphs/guides/_meta.js @@ -8,4 +8,5 @@ export default { enums: '', 'secure-api-keys-nextjs': '', polymarket: '', + 'contract-analyzer': '', } diff --git a/website/src/pages/vi/subgraphs/guides/contract-analyzer.mdx b/website/src/pages/vi/subgraphs/guides/contract-analyzer.mdx new file mode 100644 index 000000000000..084ac8d28a00 --- /dev/null +++ b/website/src/pages/vi/subgraphs/guides/contract-analyzer.mdx @@ -0,0 +1,103 @@ +--- +title: Smart Contract Analysis with Cana CLI +--- + +# Cana CLI: Quick & Efficient Contract Analysis + +**Cana CLI** is a command-line tool that streamlines helpful smart contract metadata analysis specific to subgraph development across multiple EVM-compatible chains. + +## 📌 Key Features + +- Detect deployment blocks +- Verify source code +- Extract ABIs & event signatures +- Identify proxy and implementation contracts +- Support multiple chains + +## 🚀 Installation & Setup + +Install Cana globally using npm: + +```bash +npm install -g contract-analyzer +``` + +Set up a blockchain for analysis: + +```bash +cana setup +``` + +Provide the required block explorer API and block explorer endpoint URL details when prompted. + +Running `cana setup` creates a configuration file at `~/.contract-analyzer/config.json`. This file stores your block explorer API credentials, endpoint URLs, and chain selection preferences for future use. + +## 🍳 Usage + +### 🔹 Chain Selection + +Cana supports multiple EVM-compatible chains. + +List chains added with: + +```bash +cana chains +``` + +Then select a chain with: + +```bash +cana chains --switch +``` + +Once a chain is selected, all subsequent contract analases will continue on that chain. + +### 🔹 Basic Contract Analysis + +Analyze a contract with: + +```bash +cana analyze 0xContractAddress +``` + +or + +```bash +cana -a 0xContractAddress +``` + +This command displays essential contract information in the terminal using a clear, organized format. + +### 🔹 Understanding Output + +Cana organizes results into the terminal as well as into a structured directory when detailed contract data is successfully retrieved: + +``` +contracts-analyzed/ +└── ContractName_chainName_YYYY-MM-DD/ + ├── contract/ # Folder for individual contract files + ├── abi.json # Contract ABI + └── event-information.json # Event signatures and examples +``` + +### 🔹 Chain Management + +Add and manage chains: + +```bash +cana setup # Add a new chain +cana chains # List configured chains +cana chains -s # Swich chains. +``` + +## ⚠️ Troubleshooting + +- **Missing Data**: Ensure the contract address is correct, verified on the block explorer, and that your API key has the required permissions. + +## ✅ Requirements + +- Node.js v16+ +- npm v6+ +- Block explorer API keys + +Keep your contract analyses efficient and well-organized. 🚀 diff --git a/website/src/pages/zh/subgraphs/guides/_meta.js b/website/src/pages/zh/subgraphs/guides/_meta.js index e642f12ef11d..37e18bc51651 100644 --- a/website/src/pages/zh/subgraphs/guides/_meta.js +++ b/website/src/pages/zh/subgraphs/guides/_meta.js @@ -8,4 +8,5 @@ export default { enums: '', 'secure-api-keys-nextjs': '', polymarket: '', + 'contract-analyzer': '', } diff --git a/website/src/pages/zh/subgraphs/guides/contract-analyzer.mdx b/website/src/pages/zh/subgraphs/guides/contract-analyzer.mdx new file mode 100644 index 000000000000..084ac8d28a00 --- /dev/null +++ b/website/src/pages/zh/subgraphs/guides/contract-analyzer.mdx @@ -0,0 +1,103 @@ +--- +title: Smart Contract Analysis with Cana CLI +--- + +# Cana CLI: Quick & Efficient Contract Analysis + +**Cana CLI** is a command-line tool that streamlines helpful smart contract metadata analysis specific to subgraph development across multiple EVM-compatible chains. + +## 📌 Key Features + +- Detect deployment blocks +- Verify source code +- Extract ABIs & event signatures +- Identify proxy and implementation contracts +- Support multiple chains + +## 🚀 Installation & Setup + +Install Cana globally using npm: + +```bash +npm install -g contract-analyzer +``` + +Set up a blockchain for analysis: + +```bash +cana setup +``` + +Provide the required block explorer API and block explorer endpoint URL details when prompted. + +Running `cana setup` creates a configuration file at `~/.contract-analyzer/config.json`. This file stores your block explorer API credentials, endpoint URLs, and chain selection preferences for future use. + +## 🍳 Usage + +### 🔹 Chain Selection + +Cana supports multiple EVM-compatible chains. + +List chains added with: + +```bash +cana chains +``` + +Then select a chain with: + +```bash +cana chains --switch +``` + +Once a chain is selected, all subsequent contract analases will continue on that chain. + +### 🔹 Basic Contract Analysis + +Analyze a contract with: + +```bash +cana analyze 0xContractAddress +``` + +or + +```bash +cana -a 0xContractAddress +``` + +This command displays essential contract information in the terminal using a clear, organized format. + +### 🔹 Understanding Output + +Cana organizes results into the terminal as well as into a structured directory when detailed contract data is successfully retrieved: + +``` +contracts-analyzed/ +└── ContractName_chainName_YYYY-MM-DD/ + ├── contract/ # Folder for individual contract files + ├── abi.json # Contract ABI + └── event-information.json # Event signatures and examples +``` + +### 🔹 Chain Management + +Add and manage chains: + +```bash +cana setup # Add a new chain +cana chains # List configured chains +cana chains -s # Swich chains. +``` + +## ⚠️ Troubleshooting + +- **Missing Data**: Ensure the contract address is correct, verified on the block explorer, and that your API key has the required permissions. + +## ✅ Requirements + +- Node.js v16+ +- npm v6+ +- Block explorer API keys + +Keep your contract analyses efficient and well-organized. 🚀