From dc06dc060bd9104d2c40929b4b05c3855cae5467 Mon Sep 17 00:00:00 2001 From: Yarik Bratashchuk Date: Wed, 13 Nov 2024 19:15:27 +0000 Subject: [PATCH 1/4] Mention artela specific stuff when running full node and connecting metamask to rpc --- guides/full-node.md | 2 +- tutorials/artela-evm-plus-plus.md | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/guides/full-node.md b/guides/full-node.md index 517f8e92d..a8debf4f9 100644 --- a/guides/full-node.md +++ b/guides/full-node.md @@ -82,7 +82,7 @@ After starting your full node, you should see output similar to: This output indicates that your full node is successfully connecting to the network and processing blocks. :::tip -If your rollup uses EVM as an execution layar and you see an error like `datadir already used by another process`, it means you have to remove all the state from rollup data directory (`/root/.yourrollup_fn/data/`) and specify a different data directory for the EVM client. +If your rollup uses EVM as an execution layar and you see an error like `datadir already used by another process`, it means you have to remove all the state from rollup data directory (`/root/.yourrollup_fn/data/`) and specify a different data directory for the EVM client. Preferrably to run a full node on a different machine, as some EVM clients does not have a configurable data directory. ::: diff --git a/tutorials/artela-evm-plus-plus.md b/tutorials/artela-evm-plus-plus.md index 06c60c508..fc247d85c 100644 --- a/tutorials/artela-evm-plus-plus.md +++ b/tutorials/artela-evm-plus-plus.md @@ -106,6 +106,7 @@ When you are following the Contract interaction tutorial, you need to make the f 1. Use https://github.com/artela-network/gm-portal.git instead of the original `gm-portal` repo. 2. Use the private key you obtained from the previous step in this tutorial instead of the one used in the Contract interaction tutorial. 3. The contract address should be `0x9fcEbD70654D360b41ccD123dADAAad6ce13C788` instead of the one starts with `0x18D...`. +4. When specifying the chain ID in the metamask you just 11820. ::: 👉 [Quick Start for Aspect on EVM++](https://docs.artela.network/develop/get-started/dev-aspect): Try your first [Aspect](https://docs.artela.network/develop/core-concepts/aspect-programming) with Artela rollup node. From 37de0e644a892ab347a361d526e76253992e9f95 Mon Sep 17 00:00:00 2001 From: Yarik Bratashchuk Date: Thu, 14 Nov 2024 11:10:53 +0100 Subject: [PATCH 2/4] Update tutorials/artela-evm-plus-plus.md Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> --- tutorials/artela-evm-plus-plus.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tutorials/artela-evm-plus-plus.md b/tutorials/artela-evm-plus-plus.md index fc247d85c..4f180aa9d 100644 --- a/tutorials/artela-evm-plus-plus.md +++ b/tutorials/artela-evm-plus-plus.md @@ -106,7 +106,7 @@ When you are following the Contract interaction tutorial, you need to make the f 1. Use https://github.com/artela-network/gm-portal.git instead of the original `gm-portal` repo. 2. Use the private key you obtained from the previous step in this tutorial instead of the one used in the Contract interaction tutorial. 3. The contract address should be `0x9fcEbD70654D360b41ccD123dADAAad6ce13C788` instead of the one starts with `0x18D...`. -4. When specifying the chain ID in the metamask you just 11820. +4. When adding a new network in MetaMask, use chain ID `11820` for connecting to the local rollup node. ::: 👉 [Quick Start for Aspect on EVM++](https://docs.artela.network/develop/get-started/dev-aspect): Try your first [Aspect](https://docs.artela.network/develop/core-concepts/aspect-programming) with Artela rollup node. From 9a564fa0e0933c3fed16449b47bfce5565106281 Mon Sep 17 00:00:00 2001 From: Yarik Bratashchuk Date: Thu, 14 Nov 2024 10:41:00 +0000 Subject: [PATCH 3/4] Remove omni tut --- .vitepress/config.ts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.vitepress/config.ts b/.vitepress/config.ts index d318f9730..714ecd855 100644 --- a/.vitepress/config.ts +++ b/.vitepress/config.ts @@ -278,7 +278,7 @@ function sidebarHome() { text: "EVM", collapsed: true, items: [ - { text: "Omni Octane EVM", link: "/tutorials/octane-evm" }, + //{ text: "Omni Octane EVM", link: "/tutorials/octane-evm" }, { text: "BeaconKit EVM", link: "/tutorials/beaconkit" }, { text: "Artela EVM++", link: "/tutorials/artela-evm-plus-plus" }, { text: "Contract interaction", link: "/tutorials/evm-contract-interaction" }, From 426a635236466067f725601dc898ed5b68b91c8d Mon Sep 17 00:00:00 2001 From: Yarik Bratashchuk Date: Mon, 18 Nov 2024 17:38:53 +0100 Subject: [PATCH 4/4] Update full-node.md --- guides/full-node.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guides/full-node.md b/guides/full-node.md index a8debf4f9..8b3dea3dd 100644 --- a/guides/full-node.md +++ b/guides/full-node.md @@ -82,7 +82,7 @@ After starting your full node, you should see output similar to: This output indicates that your full node is successfully connecting to the network and processing blocks. :::tip -If your rollup uses EVM as an execution layar and you see an error like `datadir already used by another process`, it means you have to remove all the state from rollup data directory (`/root/.yourrollup_fn/data/`) and specify a different data directory for the EVM client. Preferrably to run a full node on a different machine, as some EVM clients does not have a configurable data directory. +If your rollup uses EVM as an execution layar and you see an error like `datadir already used by another process`, it means you have to remove all the state from rollup data directory (`/root/.yourrollup_fn/data/`) and specify a different data directory for the EVM client. Preferrably to run a full node on a different machine (or using Docker), as some EVM clients does not have a configurable data directory. :::