Skip to content

feat: mention artela specific stuff when running full node and connecting m… #504

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 7 commits into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion .vitepress/config.ts
Original file line number Diff line number Diff line change
Expand Up @@ -280,7 +280,6 @@ function sidebarHome() {
text: "EVM",
collapsed: true,
items: [
{ text: "Omni Octane EVM", link: "/tutorials/octane-evm" },
{ text: "BeaconKit EVM", link: "/tutorials/beaconkit" },
{
text: "Artela EVM++",
Expand Down
2 changes: 1 addition & 1 deletion guides/full-node.md
Original file line number Diff line number Diff line change
Expand Up @@ -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 (or using Docker), as some EVM clients does not have a configurable data directory.
:::


Expand Down
1 change: 1 addition & 0 deletions tutorials/artela-evm-plus-plus.md
Original file line number Diff line number Diff line change
Expand Up @@ -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 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.
Expand Down