@aztec/archiver 3.0.0-nightly.20250912 → 3.0.0-nightly.20250913
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +4 -4
- package/package.json +13 -13
package/README.md
CHANGED
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
# Archiver
|
|
2
2
|
|
|
3
|
-
Archiver is a service which is used to fetch data
|
|
3
|
+
Archiver is a service which is used to fetch data onchain data and present them in a nice-to-consume form.
|
|
4
4
|
|
|
5
|
-
The
|
|
5
|
+
The onchain data specifically are the following events:
|
|
6
6
|
|
|
7
7
|
1. `L2BlockProposed` event emitted on Rollup contract,
|
|
8
8
|
2. `MessageAdded` event emitted on Inbox contract,
|
|
@@ -19,12 +19,12 @@ After the implementation of [delayed attestation verification](https://github.co
|
|
|
19
19
|
|
|
20
20
|
Whenever the archiver detects a block with invalid attestations, it skips it. These blocks are not meant to be part of the chain, so the archiver ignores them and continues processing the next blocks. It is expected that an honest proposer will eventually invalidate these blocks, removing them from the chain on L1, and then resume the sequence of valid blocks.
|
|
21
21
|
|
|
22
|
-
> [!WARNING]
|
|
22
|
+
> [!WARNING]
|
|
23
23
|
> If the committee for the epoch is also malicious and attests to a descendant of an invalid block, nodes should also ignore these descendants, unless they become proven. This is currently not implemented. Nodes assume that the majority of the committee is honest.
|
|
24
24
|
|
|
25
25
|
When the current node is elected as proposer, the `sequencer` needs to know whether there is an invalid block in L1 that needs to be purged before posting their own block. To support this, the archiver exposes a `pendingChainValidationStatus`, which is the state of the tip of the pending chain. This status can be valid in the happy path, or invalid if the tip of the pending chain has invalid attestations. If invalid, this status also contains all the data needed for purging the block from L1 via an `invalidate` call to the Rollup contract. Note that, if the head of the chain has more than one invalid consecutive block, this status will reference the earliest one that needs to be purged, since a call to purge an invalid block will automatically purge all descendants. Refer to the [InvalidateLib.sol](`l1-contracts/src/core/libraries/rollup/InvalidateLib.sol`) for more info.
|
|
26
26
|
|
|
27
|
-
> [!TIP]
|
|
27
|
+
> [!TIP]
|
|
28
28
|
> The archiver can be configured to `skipValidateBlockAttestations`, which will make it skip this validation. This cannot be set via environment variables, only via a call to `nodeAdmin_setConfig`. This setting is only meant for testing purposes.
|
|
29
29
|
|
|
30
30
|
As an example, let's say the chain has been progressing normally up until block 10, and then:
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@aztec/archiver",
|
|
3
|
-
"version": "3.0.0-nightly.
|
|
3
|
+
"version": "3.0.0-nightly.20250913",
|
|
4
4
|
"type": "module",
|
|
5
5
|
"exports": {
|
|
6
6
|
".": "./dest/index.js",
|
|
@@ -66,18 +66,18 @@
|
|
|
66
66
|
]
|
|
67
67
|
},
|
|
68
68
|
"dependencies": {
|
|
69
|
-
"@aztec/blob-lib": "3.0.0-nightly.
|
|
70
|
-
"@aztec/blob-sink": "3.0.0-nightly.
|
|
71
|
-
"@aztec/constants": "3.0.0-nightly.
|
|
72
|
-
"@aztec/epoch-cache": "3.0.0-nightly.
|
|
73
|
-
"@aztec/ethereum": "3.0.0-nightly.
|
|
74
|
-
"@aztec/foundation": "3.0.0-nightly.
|
|
75
|
-
"@aztec/kv-store": "3.0.0-nightly.
|
|
76
|
-
"@aztec/l1-artifacts": "3.0.0-nightly.
|
|
77
|
-
"@aztec/noir-protocol-circuits-types": "3.0.0-nightly.
|
|
78
|
-
"@aztec/protocol-contracts": "3.0.0-nightly.
|
|
79
|
-
"@aztec/stdlib": "3.0.0-nightly.
|
|
80
|
-
"@aztec/telemetry-client": "3.0.0-nightly.
|
|
69
|
+
"@aztec/blob-lib": "3.0.0-nightly.20250913",
|
|
70
|
+
"@aztec/blob-sink": "3.0.0-nightly.20250913",
|
|
71
|
+
"@aztec/constants": "3.0.0-nightly.20250913",
|
|
72
|
+
"@aztec/epoch-cache": "3.0.0-nightly.20250913",
|
|
73
|
+
"@aztec/ethereum": "3.0.0-nightly.20250913",
|
|
74
|
+
"@aztec/foundation": "3.0.0-nightly.20250913",
|
|
75
|
+
"@aztec/kv-store": "3.0.0-nightly.20250913",
|
|
76
|
+
"@aztec/l1-artifacts": "3.0.0-nightly.20250913",
|
|
77
|
+
"@aztec/noir-protocol-circuits-types": "3.0.0-nightly.20250913",
|
|
78
|
+
"@aztec/protocol-contracts": "3.0.0-nightly.20250913",
|
|
79
|
+
"@aztec/stdlib": "3.0.0-nightly.20250913",
|
|
80
|
+
"@aztec/telemetry-client": "3.0.0-nightly.20250913",
|
|
81
81
|
"lodash.groupby": "^4.6.0",
|
|
82
82
|
"lodash.omit": "^4.5.0",
|
|
83
83
|
"tsc-watch": "^6.0.0",
|