update archive doc and snapshot url

envestcc · envestcc · commit e324786170e5 · 2026-01-06T10:51:15.000+08:00
diff --git a/README.md b/README.md
@@ -57,52 +57,24 @@ curl https://raw.githubusercontent.com/iotexproject/iotex-bootstrap/v2.3.3/trie.
 4. Start from a **baseline snapshot** (rather than sync from the genesis block), run the following commands:
 
 ```
-curl -L https://t.iotex.me/mainnet-data-snapshot-latest > $IOTEX_HOME/data.tar.gz
+curl -L https://storage.iotex.io/mainnet-data-e-20251228-042459-core.tar.gz > $IOTEX_HOME/data.tar.gz
 ```
 
-or download from another website:
+5. Extract the data package:
 
 ```
-curl -L https://storage.iotex.io/mainnet-data-snapshot-latest.tar.gz > $IOTEX_HOME/data.tar.gz
-```
-
-**We will update the baseline snapshot on the 1st of every month**. 
-
-5. Download the latest **incremental data** (Optional):
-
-```
-curl -L https://storage.iotex.io/mainnet-data-incr-latest.tar.gz > $IOTEX_HOME/incr.tar.gz
-```
-
-**We will update the incremental snapshot everyday**. 
-
-We also provide incremental packages from the **past 7 days**.
-You can choose any day within this period.
-For example, if you want to use the data from April 27, 2025, the incremental package file name will be `mainnet-data-incr-2025-04-27.tar.gz`.
-
-The file named **latest** corresponds to today’s data.
-
-To restore, you only need the full baseline package of the same month and the incremental package of the selected date.
-
-6. Extract the data packages in the correct order.
-It is essential to extract the baseline package first, followed by the incremental package.
-
-```
-tar -xzf $IOTEX_HOME/data.tar.gz -C $IOTEX_HOME/data/ && tar -xzf $IOTEX_HOME/incr.tar.gz -C $IOTEX_HOME/data/
+tar -xzf $IOTEX_HOME/data.tar.gz -C $IOTEX_HOME/data/
 ```
 
 For advanced users, there are three options to consider:
 
 - Option 1: If you plan to run your node as a [gateway](#gateway), please use the snapshot with index data:
-https://t.iotex.me/mainnet-data-with-idx-latest.
-
-  or download from another website:
 ```
-curl -L https://storage.iotex.io/mainnet-data-with-idx-latest.tar.gz > $IOTEX_HOME/data.tar.gz
-tar -xzf data.tar.gz
+curl -L https://storage.iotex.io/mainnet-data-e-20251228-042459-gateway.tar.gz > $IOTEX_HOME/data_index.tar.gz
+tar -xzf data_index.tar.gz
 ```
 
-> mainnet-data-with-idx-latest.tar.gz will be update on Monday every week
+If you need to run your node in archive mode to provide full historical data, please go to [Archive Node](./archive-node.md).
 
 - Optional 2: If you only want to sync chain data from 0 height without relaying on legacy delegate election data from Ethereum, you can setup legacy delegate election data with following command:
 ```bash
@@ -111,7 +83,7 @@ curl -L https://storage.iotex.io/poll.mainnet.tar.gz > $IOTEX_HOME/poll.tar.gz;
 
 - Optional 3: If you want to sync the chain from 0 height and also fetching legacy delegate election data from Ethereum, please change the `gravityChainAPIs` in config.yaml to use your infura key with Ethereum archive mode supported or change the API endpoint to an Ethereum archive node which you can access.
 
-5. Run the following command to start a node:
+6. Run the following command to start a node:
 
 ```
 docker run -d --restart on-failure --name iotex \
@@ -149,7 +121,7 @@ docker run -d --restart on-failure --name iotex \
         -plugin=gateway
 ```
 
-6. Ensure that TCP ports `4689` and `8080` are open on your firewall and load balancer (if applicable). Additionally, if you intend to use the node as a gateway, make sure the following ports are open:
+7. Ensure that TCP ports `4689` and `8080` are open on your firewall and load balancer (if applicable). Additionally, if you intend to use the node as a gateway, make sure the following ports are open:
 - `14014` for the IoTeX native gRPC API
 - `15014` for the Ethereum JSON API
 - `16014` for the Ethereum WebSocket
diff --git a/README_CN.md b/README_CN.md
@@ -56,42 +56,24 @@ curl https://raw.githubusercontent.com/iotexproject/iotex-bootstrap/v2.3.3/trie.
 
 4. 下载全量数据快照, 请运行以下命令:
 ```
-curl -L https://t.iotex.me/mainnet-data-snapshot-latest > $IOTEX_HOME/data.tar.gz
+curl -L https://storage.iotex.io/mainnet-data-e-20251228-042459-core.tar.gz > $IOTEX_HOME/data.tar.gz
 ```
-或者 请运行以下命令
-```
-curl -L https://storage.iotex.io/mainnet-data-snapshot-latest.tar.gz > $IOTEX_HOME/data.tar.gz
-```
-
-**我们将会在每月一日更新全量数据快照**。
-
-5. 下载最新增量数据, 请运行以下命令(可选):
-
-```
-curl -L https://storage.iotex.io/mainnet-data-incr-latest.tar.gz > $IOTEX_HOME/incr.tar.gz
-```
-
-**我们将会每天更新一次增量数据快照**。
 
-同时我们提供7日内的增量包下载，你可以选择这期间中任意一天。比如你想使用2025.4.27日的数据， 那么增量包的文件名称为`mainnet-data-incr-2025-04-27.tar.gz`， latest为今日的数据。 还原的时候只需当月的全量包 + 当日的增量包即可。
-
-6. 解压数据包, 请注意解压顺序, 必须先解压全量包, 再解压增量包
+5. 解压数据包
 
 ```
-tar -xzf $IOTEX_HOME/data.tar.gz -C $IOTEX_HOME/data/ && tar -xzf $IOTEX_HOME/incr.tar.gz -C $IOTEX_HOME/data/
+tar -xzf $IOTEX_HOME/data.tar.gz -C $IOTEX_HOME/data/
 ```
 
 对于高级用户，可以考虑以下三个选项：
 
-- 选项1：如果计划将节点作为[网关](#gateway)运行，请使用带有索引数据的快照：https://t.iotex.me/mainnet-data-with-idx-latest.
-
-  或从另一个站点下载:
+- 选项1：如果计划将节点作为[网关](#gateway)运行，还需要额外下载带有索引数据的快照
 ```
-curl -L https://storage.iotex.io/mainnet-data-with-idx-latest.tar.gz > $IOTEX_HOME/data.tar.gz
-tar -xzf data.tar.gz
+curl -L https://storage.iotex.io/mainnet-data-e-20251228-042459-gateway.tar.gz > $IOTEX_HOME/data_index.tar.gz
+tar -xzf data_index.tar.gz
 ```
 
-> mainnet-data-with-idx-latest.tar.gz 在每周一会打新的压缩包
+如果需要以 archive 模式运行提供全量历史数据，请转到 [Archive Node](./archive-node.md)
 
 - 选择2：如果计划从 0 区块高度开始同步链上数据而不使用来自以太坊旧的节点代表数据，执行以下命令设置旧的节点代表数据：
 ```
@@ -100,7 +82,7 @@ curl -L https://storage.iotex.io/poll.mainnet.tar.gz > $IOTEX_HOME/poll.tar.gz;
 
 - 选择3：如果计划从 0 区块高度开始同步链并从以太坊获取旧的节点代表数据，请更改 config.yaml 中的 `gravityChainAPIs`并在支持以太坊存档模式的情况下使用您的 infura 密钥，或将 API 端点更改为您有权限访问的以太坊存档节点。
 
-7. 运行以下命令以启动节点:
+6. 运行以下命令以启动节点:
 
 ```
 docker run -d --restart on-failure --name iotex \
diff --git a/README_CN_testnet.md b/README_CN_testnet.md
@@ -53,54 +53,33 @@ curl https://raw.githubusercontent.com/iotexproject/iotex-bootstrap/v2.3.3/genes
 3. 编辑 `$IOTEX_HOME/etc/config.yaml`, 查找 `externalHost` 和 `producerPrivKey`, 取消注释行并填写您的外部 IP 和私钥。如果`producerPrivKey`放空，你的节点将被分配一个随机密钥。
 
 4. 下载全量数据快照, 请运行以下命令:
-```
-curl -L https://t.iotex.me/testnet-data-snapshot-latest > $IOTEX_HOME/data.tar.gz
-tar -xzf data.tar.gz
-```
-或者 请运行以下命令
-```
-curl -L https://storage.iotex.io/testnet-data-snapshot-latest.tar.gz > $IOTEX_HOME/data.tar.gz
-tar -xzf data.tar.gz
-```
-
-**我们将会在每月一日更新全量数据快照**。
-
-5. 下载最新增量数据, 请运行以下命令(可选):
 
 ```
-curl -L https://storage.iotex.io/testnet-data-incr-latest.tar.gz > $IOTEX_HOME/incr.tar.gz
+curl -L https://storage.iotex.io/testnet-data-e-20260105-042459-core.tar.gz > $IOTEX_HOME/data.tar.gz
 ```
 
-**我们将会每天更新一次增量数据快照**。
-
-同时我们提供7日内的增量包下载，你可以选择这期间中任意一天。比如你想使用2025.4.27日的数据， 那么增量包的文件名称为`testnet-data-incr-2025-04-27.tar.gz`， latest为今日的数据。 还原的时候只需当月的全量包 + 当日的增量包即可。
-
-6. 解压数据包, 请注意解压顺序, 必须先解压全量包, 再解压增量包
+5. 解压数据包
 
 ```
-tar -xzf $IOTEX_HOME/data.tar.gz -C $IOTEX_HOME/data/ && tar -xzf $IOTEX_HOME/incr.tar.gz -C $IOTEX_HOME/data/
+tar -xzf $IOTEX_HOME/data.tar.gz -C $IOTEX_HOME/data/
 ```
 
 对于高级用户，可以考虑以下三个选项：
 
-- 选项1：如果计划将节点作为[网关](#gateway)运行，请使用带有索引数据的快照：https://t.iotex.me/testnet-data-with-idx-latest.
-
-  或从另一个站点下载:
+- 选项1：如果计划将节点作为[网关](#gateway)运行，请额外下载带有索引数据的快照
 ```
-curl -L https://storage.iotex.io/testnet-data-with-idx-latest.tar.gz > $IOTEX_HOME/data.tar.gz
-tar -xzf data.tar.gz
+curl -L https://storage.iotex.io/testnet-data-e-20260105-042459-gateway.tar.gz > $IOTEX_HOME/data_index.tar.gz
+tar -xzf data_index.tar.gz
 ```
 
-> testnet-data-with-idx-latest.tar.gz 在每周一会打新的压缩包
-
 - 选择2：如果计划从 0 区块高度开始同步链上数据而不使用来自以太坊旧的节点代表数据，执行以下命令设置旧的节点代表数据：
 ```
 curl -L https://storage.iotex.io/poll.testnet.tar.gz > $IOTEX_HOME/poll.tar.gz; tar -xzf $IOTEX_HOME/poll.tar.gz --directory $IOTEX_HOME/data
 ```
 
 - 选择3：如果计划从 0 区块高度开始同步链并从以太坊获取旧的节点代表数据，请更改 config.yaml 中的 `gravityChainAPIs`并在支持以太坊存档模式的情况下使用您的 infura 密钥，或将 API 端点更改为您有权限访问的以太坊存档节点。
 
-5. 运行以下命令以启动节点:
+6. 运行以下命令以启动节点:
 
 ```
 docker run -d --restart on-failure --name iotex \
@@ -135,7 +114,7 @@ docker run -d --restart on-failure --name iotex \
         -plugin=gateway
 ```
 
-6. 确保您的防火墙和负载均衡器（如果有）上的TCP端口4689, 8080（14014如果节点启用了网关）已打开。
+7. 确保您的防火墙和负载均衡器（如果有）上的TCP端口4689, 8080（14014如果节点启用了网关）已打开。
 
 ## <a name="testnet_native"/>不使用Docker加入测试网
 
diff --git a/README_testnet.md b/README_testnet.md
@@ -55,63 +55,32 @@ curl https://raw.githubusercontent.com/iotexproject/iotex-bootstrap/v2.3.3/genes
 4. Start from a **baseline snapshot** (rather than sync from the genesis block), run the following commands:
 
 ```
-curl -L https://t.iotex.me/testnet-data-snapshot-latest > $IOTEX_HOME/data.tar.gz
-tar -xzf data.tar.gz
+curl -L https://storage.iotex.io/testnet-data-e-20260105-042459-core.tar.gz > $IOTEX_HOME/data.tar.gz
 ```
 
-or download from another website:
-```
-curl -L https://storage.iotex.io/testnet-data-snapshot-latest.tar.gz > $IOTEX_HOME/data.tar.gz
-tar -xzf data.tar.gz
-```
-
-**We will update the baseline snapshot on the 1st of every month**. 
-
-5. Download the latest **incremental data** (Optional):
-
-```
-curl -L https://storage.iotex.io/testnet-data-incr-latest.tar.gz > $IOTEX_HOME/incr.tar.gz
-```
-
-**We will update the incremental snapshot everyday**. 
-
-We also provide incremental packages from the **past 7 days**.
-You can choose any day within this period.
-For example, if you want to use the data from April 27, 2025, the incremental package file name will be `testnet-data-incr-2025-04-27.tar.gz`.
-
-The file named **latest** corresponds to today’s data.
-
-To restore, you only need the full baseline package of the same month and the incremental package of the selected date.
-
-6. Extract the data packages in the correct order.
-It is essential to extract the baseline package first, followed by the incremental package.
+5. Extract the data package:
 
 ```
-tar -xzf $IOTEX_HOME/data.tar.gz -C $IOTEX_HOME/data/ && tar -xzf $IOTEX_HOME/incr.tar.gz -C $IOTEX_HOME/data/
+tar -xzf $IOTEX_HOME/data.tar.gz -C $IOTEX_HOME/data/
 ```
 
 For advanced users, there are three options to consider:
 
 - Option 1: If you plan to run your node as a [gateway](#gateway), please use the snapshot with index data:
-https://t.iotex.me/testnet-data-with-idx-latest.
-
-   or download from another website:
 
 ```
-curl -L https://storage.iotex.io/testnet-data-with-idx-latest.tar.gz > $IOTEX_HOME/data.tar.gz
-tar -xzf data.tar.gz
+curl -L https://storage.iotex.io/testnet-data-e-20260105-042459-gateway.tar.gz > $IOTEX_HOME/data_index.tar.gz
+tar -xzf data_index.tar.gz
 ```
 
-> testnet-data-with-idx-latest.tar.gz will be update on Monday every week
-
 - Optional 2: If you only want to sync chain data from 0 height without relaying on legacy delegate election data from Ethereum, you can setup legacy delegate election data with following command:
 ```bash
 curl -L https://storage.iotex.io/poll.testnet.tar.gz > $IOTEX_HOME/poll.tar.gz; tar -xzf $IOTEX_HOME/poll.tar.gz --directory $IOTEX_HOME/data
 ```
 
 - Optional 3: If you want to sync the chain from 0 height and also fetching legacy delegate election data from Ethereum, please change the `gravityChainAPIs` in config.yaml to use your infura key with Ethereum archive mode supported or change the API endpoint to an Ethereum archive node which you can access.
 
-5. Run the following command to start a node:
+6. Run the following command to start a node:
 
 ```
 docker run -d --restart on-failure --name iotex \
@@ -148,7 +117,7 @@ docker run -d --restart on-failure --name iotex \
         -plugin=gateway
 ```
 
-6. Make sure TCP ports 4689, 8080 (also 14014 if used) are open on your firewall and load balancer (if any).
+7. Make sure TCP ports 4689, 8080 (also 14014 if used) are open on your firewall and load balancer (if any).
 
 ## <a name="testnet_native"/>Join Testnet without using Docker
 This is not the preferred way to start an IoTeX node
diff --git a/archive-node.md b/archive-node.md
@@ -8,8 +8,7 @@ time the tx was originally executed.
 
 This archive node is an **optimized version** with significant performance improvements and storage optimizations. However, please note that:
 
-- **Data files from previous archive node versions are NOT compatible** with this optimized version
-- If you are upgrading from a previous archive node setup, you **cannot** reuse existing data files
+- **Data files from any previous archive node builds (including earlier test/archive branches) are NOT compatible**, so you **cannot** reuse existing data files
 - You **MUST** either:
   - **Download the provided snapshot data** (recommended for faster setup)
   - Or **perform a complete resync from genesis** (time-consuming but ensures full verification)
@@ -19,9 +18,12 @@ The following instrcutions will guide you through setting up an IoTeX archive no
   - [Important Notice - Optimized Archive Node Version](#important-notice---optimized-archive-node-version)
   - [System Requirements](#system-requirements)
   - [Prepare Home Directory](#prepare-home-directory)
-  - [Download Data(Optional)](#download-data)
+  - [Download Data](#download-data)
   - [Running Node using Docker](#running-node-using-docker)
   - [Running Node using Binary](#running-node-using-binary)
+    - [Pre-Requisites](#pre-requisites)
+    - [Build Binary](#build-binary)
+    - [Start Node](#start-node)
 
 
 ## <a name="system"/>System Requirements
@@ -63,10 +65,16 @@ need to download and uncompress this file.
 In the $IOTEX_HOME folder, run the following commands:
 ```
 #download the data files and uncompress it
-curl -LO https://storage.iotex.io/mainnet-archive-data-e-20250625.tar.gz
-tar -xzf mainnet-archive-data-e-20250625.tar.gz
+curl -LO https://storage.iotex.io/mainnet-data-e-20251228-042459-core.tar.gz
+tar -xzf mainnet-data-e-20251228-042459-core.tar.gz
+
+curl -LO https://storage.iotex.io/mainnet-data-e-20251228-042459-gateway.tar.gz
+tar -xzf mainnet-data-e-20251228-042459-gateway.tar.gz
+
+curl -LO https://storage.iotex.io/mainnet-data-e-20251228-042459-trie-history.tar.gz
+tar -xzf mainnet-data-e-20251228-042459-trie-history.tar.gz
 ```
->Note: the snapshot has a size of 300GB at this moment.
+>Note: the snapshot has a size of 450GB at this moment.
 Please take measures (for example use `nohup` at the front) to prevent possible interruption of the download process.
 
 After successful download and uncompress operations, the $IOTEX_HOME/data folder
@@ -138,7 +146,7 @@ docker run -d --restart on-failure --name iotex \
         -v=$IOTEX_HOME/log:/var/iotex-archive/log:rw \
         -v=$IOTEX_HOME/etc/config.yaml:/etc/iotex/config_override.yaml:ro \
         -v=$IOTEX_HOME/etc/genesis.yaml:/etc/iotex/genesis.yaml:ro \
-        iotex/iotex-core:archive \
+        iotex/iotex-core:v2.3.3 \
         iotex-server \
         -config-path=/etc/iotex/config_override.yaml \
         -genesis-path=/etc/iotex/genesis.yaml \
@@ -181,7 +189,7 @@ git clone https://github.com/iotexproject/iotex-core.git
 cd iotex-core
 
 #checkout the code branch for archive node
-git checkout origin/archive
+git checkout v2.3.3
 
 #build binary
 make build
diff --git a/changelog/v2.3.3-release-note.md b/changelog/v2.3.3-release-note.md
@@ -13,9 +13,14 @@ restart your node with the new v2.3.3 image.
 ### 1. Archive Mode Support
 v2.3.3 officially introduces **Archive Mode**, which stores complete historical state data for all blocks. This mode is essential for applications that need to query historical blockchain states at any point in time.
 
+To enable archive mode, set `chain.historyIndexPath` in `config.yaml` to the directory where historical state files will be stored.
+
+
 ### 2. Prune Mode Support
 v2.3.3 introduces **Prune Mode**, which maintains only the most recent 256 blocks of historical state data. This mode significantly reduces storage requirements while still providing recent state access for most operational needs.
 
+To enable prune mode, first enable archive mode, then set `chain.historyBlockRetention` in `config.yaml` to the number of recent blocks whose state you want to retain.
+
 ### 3. Block Synchronization Optimization
 Significant improvements have been made to the block synchronization mechanism to enhance sync speed, reliability, and network efficiency.
 
