revisions

.snippets/code/builders/ethereum/dev-env/ape/ape-config.yaml

@@ -0,0 +1,27 @@
+# ape-config.yaml
+name: ape-demo
+
+default_ecosystem: ethereum
+
+ethereum:
+  default_network: local_moonbeam
+
+  local_moonbeam:
+    default_transaction_type: 0
+    gas_limit: "auto"
+    block_time: 6
+    transaction_acceptance_timeout: 60
+    max_receipt_retries: 10
+
+networks:
+  custom:
+    - name: local_moonbeam
+      chain_id: 1281                    
+      ecosystem: ethereum
+      base_ecosystem_plugin: ethereum
+      default_provider: node
+
+node:
+  ethereum:
+    local_moonbeam:
+      uri: http://127.0.0.1:9944

builders/ethereum/dev-env/ape.md

@@ -347,7 +347,9 @@ Congratulations! You have successfully deployed and interacted with a contract u
 
 There are some nuances associated with using Ape with a local Moonbeam node. As a Moonbeam local node is not included as a preset network with Ape, you'll need to customize your `ape-config.yaml` before using Ape with a local Moonbeam node. Adjust your `ape-config.yaml` as follows: 
 
---8<-- 'code/builders/ethereum/dev-env/ape/terminal/ape-config.yaml'
+```bash
+--8<-- 'code/builders/ethereum/dev-env/ape/ape-config.yaml'
+```
 
 After configuring your `ape-config.yaml`, you can target your local Moonbeam node by appending the following network configuration flag to your Ape command: