You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+15Lines changed: 15 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,6 +12,17 @@ From root directory:
12
12
yarn install
13
13
```
14
14
15
+
## Environment Setup
16
+
17
+
To simplify providing environment variables across all tutorials, a helper script automates creating `.env` files from each existing `.env-sample`.
18
+
19
+
```bash
20
+
yarn setup-envs
21
+
22
+
# To update existing .env files as well
23
+
yarn setup-envs --update
24
+
```
25
+
15
26
## Testing
16
27
17
28
1. Start the nitro-testnode (you can find instructions [here](https://docs.arbitrum.io/run-arbitrum-node/run-local-full-chain-simulation)) with the following parameters:
@@ -26,6 +37,10 @@ yarn install
26
37
yarn run testAll
27
38
```
28
39
40
+
### Notes on RPCs and Finality
41
+
42
+
Using public testnet RPCs can be slow because many tutorials wait for transaction finality or multiple confirmations. Some tests may take 10–15 minutes to complete on testnets. For faster and more reliable execution, prefer running a local node and pointing your environment variables (`CHAIN_RPC`, `PARENT_CHAIN_RPC`, and `L1_RPC` when applicable) to local RPC endpoints.
Copy file name to clipboardExpand all lines: packages/block-verification-in-parent-chain-assertion/README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,12 +1,12 @@
1
1
# Block verification in an assertion posted on the parent chain
2
2
3
-
This tutorial shows how to verify whether a block of a chain has been processed as part of an RBlock assertion on its parent chain.
3
+
This tutorial shows how to verify whether a block of a chain has been processed as part of an assertion on its parent chain.
4
4
5
-
It uses the `Rollup` contract to find the latest confirmed (or created if configured in the script) RBlock/node, find the event that created it, and get the latest processed block hash of the child chain that's part of the assertion of that RBlock/node.
5
+
It uses the `Rollup` contract to find the latest confirmed assertion hash, find the `AssertionCreated`event that created it, and get the latest processed block hash of the child chain that's part of that assertion's `afterState`.
6
6
7
7
Then it checks whether the block number passed as argument was created before the latest block hash of the child chain processed.
8
8
9
-
See [./exec.js](./scripts/exec.js) for inline explanations.
9
+
See [./exec.ts](./scripts/exec.ts) for inline explanations.
0 commit comments