Merge branch 'main' of github.com:hyperledger/besu-docs

Alexandra Tran · Alexandra Tran · commit c618eb1f7c61 · 2025-03-18T11:01:14.000-07:00
diff --git a/docs/private-networks/concepts/node-sync-private.md b/docs/private-networks/concepts/node-sync-private.md
@@ -22,18 +22,9 @@ To sync Besu on a private network:
 The following is an overview of the private network sync modes.
 Select the sync mode based on your network's requirements and node purposes.
 
-| Sync mode                                                                            | Description                                                                                                                                                                         | Requirements | Limitations |
-|--------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|-------------|
-| [Snap](../../public-networks/concepts/node-sync.md#snap-synchronization)             | Recommended for fastest sync and lowest storage requirements on Mainnet. Downloads as many leaves of the trie as possible and reconstructs the trie locally. Faster than fast sync. | Besu version 24.3.0 or later | Cannot switch from fast sync to snap sync mid-process. |
+| Sync mode                                                                            | Description                                                                                                                                                                         | Requirements                 | Limitations                                                                     |
+|--------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|---------------------------------------------------------------------------------|
+| [Snap](../../public-networks/concepts/node-sync.md#snap-synchronization)             | Recommended for fastest sync and lowest storage requirements on Mainnet. Downloads as many leaves of the trie as possible and reconstructs the trie locally. Faster than fast sync. | Besu version 24.3.0 or later | Cannot switch from fast sync to snap sync mid-process.                          |
 | [Checkpoint](../../public-networks/concepts/node-sync.md#checkpoint-synchronization) | Syncs from a specific checkpoint block configured in the genesis file. Fastest sync mode with lowest storage requirements.                                                          | Besu version 22.4.3 or later | Not supported for QBFT or IBFT 2.0 networks without a checkpoint configuration. |
-| [Fast](../../public-networks/concepts/node-sync.md#fast-synchronization-deprecated)             | Downloads block headers and transaction receipts, verifies chain from genesis block.                                                                                                | None | Deprecated. Not supported with private transactions. |
-| [Full](../../public-networks/concepts/node-sync.md#full-synchronization)             | Default for all private networks. Downloads and verifies the entire blockchain and state from genesis block, building an archive node with full state history.                      | None | Slowest sync mode, requires the most disk space. |
-
-:::warning Early access feature 
-
-`--Xsnapsync-bft-enabled` is an early access feature available in Besu version 24.7.1 and later.
-It is not stable, so use this option with caution.
-
-Use `--Xsnapsync-bft-enabled` with `--sync-mode=SNAP` to enable snap sync in QBFT and IBFT 2.0 private networks.
-
-:::
+| [Fast](../../public-networks/concepts/node-sync.md#fast-synchronization-deprecated)  | Downloads block headers and transaction receipts, verifies chain from genesis block.                                                                                                | None                         | Deprecated. Not supported with private transactions.                            |
+| [Full](../../public-networks/concepts/node-sync.md#full-synchronization)             | Default for all private networks. Downloads and verifies the entire blockchain and state from genesis block, building an archive node with full state history.                      | None                         | Slowest sync mode, requires the most disk space.                                |
diff --git a/docs/private-networks/concepts/permissioning/plugin.md b/docs/private-networks/concepts/permissioning/plugin.md
@@ -10,12 +10,16 @@ tags:
 
 You can define complex [permissioning](index.md) solutions by building a plugin that extends Besu functionality.
 
-The plugin API provides a `PermissioningService` interface that currently supports connection permissioning and message permissioning.
+The plugin API provides a `PermissioningService` interface that currently supports connection (node) permissioning, transaction permissioning and message permissioning.
 
-## Connection permissioning
+## Connection (node) permissioning
 
 Use connection permissioning when deciding whether to restrict node access to known participants only.
 
+## Transaction permissioning
+
+Use transaction permissioning when deciding whether to restrict transaction processing based on transaction properties.
+
 ## Message permissioning
 
 Use message permissioning to propagate different types of devP2P messages to particular nodes. For example, this can be used to prevent pending transactions from being forwarded to other nodes.
diff --git a/docs/private-networks/how-to/configure/consensus/ibft.md b/docs/private-networks/how-to/configure/consensus/ibft.md
@@ -33,16 +33,6 @@ You can use a plugin to securely store a validator's key using the [`--security-
 
 :::
 
-:::info Early access feature 
-
-`--Xsnapsync-bft-enabled` is an early access feature available in Besu version 24.7.1 and later.
-It is not stable, so use this option with caution.
-
-Use `--Xsnapsync-bft-enabled` with `--sync-mode=SNAP` to enable
-[snap sync](../../../concepts/node-sync-private.md) in IBFT 2.0 networks.
-
-:::
-
 ## Genesis file
 
 To use IBFT 2.0, Besu requires an IBFT 2.0 [genesis file](../../../../public-networks/concepts/genesis-file.md). The genesis file defines properties specific to IBFT 2.0.
diff --git a/docs/private-networks/how-to/configure/consensus/qbft.md b/docs/private-networks/how-to/configure/consensus/qbft.md
@@ -33,16 +33,6 @@ You can use a plugin to securely store a validator's key using the [`--security-
 
 :::
 
-:::info Early access feature
-
-`--Xsnapsync-bft-enabled` is an early access feature available in Besu version 24.7.1 and later.
-It is not stable, so use this option with caution.
-
-Use `--Xsnapsync-bft-enabled` with `--sync-mode=SNAP` to enable
-[snap sync](../../../concepts/node-sync-private.md) in QBFT networks.
-
-:::
-
 ## Genesis file
 
 To use QBFT, define a [genesis file](../../../../public-networks/concepts/genesis-file.md) that contains the QBFT properties.
diff --git a/docs/public-networks/reference/cli/options.md b/docs/public-networks/reference/cli/options.md
@@ -5802,15 +5802,6 @@ The synchronization mode. Use `SNAP` for [snap sync](../../concepts/node-sync.md
 
 :::
 
-:::warning Early access feature
-
-`--Xsnapsync-bft-enabled` is an early access feature available in Besu version 24.7.1 and later.
-It is not stable, so use this option with caution.
-
-Use `--Xsnapsync-bft-enabled` with `--sync-mode=SNAP` to enable snap sync in QBFT and IBFT 2.0 private networks.
-
-:::
-
 ### `target-gas-limit`
 
 <Tabs>
diff --git a/docs/public-networks/reference/cli/subcommands.md b/docs/public-networks/reference/cli/subcommands.md
@@ -449,6 +449,79 @@ You can configure the retention limit using [`--bonsai-historical-block-limit`](
 The retention limit should match the configuration used with [`--bonsai-limit-trie-logs-enabled`](options.md#bonsai-limit-trie-logs-enabled). 
 The default limit is `512`.
 
+#### `export`
+
+<Tabs>
+
+<TabItem value="Syntax" label="Syntax" default>
+
+```bash
+besu --config-file <PATH-TO-CONFIG-FILE> storage trie-log export [--trie-log-block-hash=<list>] [--trie-log-file-path=<file>]
+```
+
+</TabItem>
+
+<TabItem value="Example exporting single trie log">
+
+```bash
+besu --config-file config.toml storage trie-log export --trie-log-block-hash=0x0dcfa528de7d12df63673d0ebbd103dbf3a9464fae7eeb89e0934678cd05d64b
+```
+
+:::note
+This example exports the trie log corresponding to a particular block hash into a file in the default location, `<data-dir>/trie-logs.bin`.
+:::
+
+</TabItem>
+
+<TabItem value="Example exporting list">
+
+```bash
+besu --config-file config.toml storage trie-log export --trie-log-file-path=/tmp/list_of_trielogs.bin --trie-log-block-hash=0x0dcfa528de7d12df63673d0ebbd103dbf3a9464fae7eeb89e0934678cd05d64b,0xe8c3e77a6eaf6c87552aee07b86ecf4aacba43650b1d6aac32a44fa3ca97780d,0x86df7008b32fee67baac103846931c58454fc1b391e7d826c4886ba8580ba169
+```
+
+:::note
+This example exports trie logs corresponding to a list of block hashes into a specific file location.
+:::
+
+</TabItem>
+
+</Tabs>
+
+Exports the trie logs of blocks specified by hash to a binary file.
+
+By default, Bonsai trie logs are regularly pruned, so the trie log for a given block might not be present if it has been pruned.
+If you need to manually import or export trie logs, we recommend temporarily disabling trie log pruning by setting
+[`--bonsai-limit-trie-logs-enabled`](options.md#bonsai-limit-trie-logs-enabled) to `false`.
+
+#### `import`
+
+<Tabs>
+
+<TabItem value="Syntax" label="Syntax" default>
+
+```bash
+besu --config-file <PATH-TO-CONFIG-FILE> storage trie-log import [--trie-log-file-path=<file>]
+```
+
+</TabItem>
+
+<TabItem value="Example">
+
+```bash
+besu --config-file config.toml storage trie-log import --trie-log-file-path=/tmp/list_of_trielogs.bin 
+```
+
+</TabItem>
+
+</Tabs>
+
+Imports trie logs from a binary trie log export file.
+
+By default, Bonsai trie logs are regularly pruned.
+If pruning is enabled, Besu might subsequently prune the imported trie logs.
+If you need to manually import or export trie logs, we recommend temporarily disabling trie log pruning by setting
+[`--bonsai-limit-trie-logs-enabled`](options.md#bonsai-limit-trie-logs-enabled) to `false`.
+
 ## `validate-config`
 
 <Tabs>
