From 0630c7ec22935b67ac6d46210ee37d9688e1506d Mon Sep 17 00:00:00 2001 From: m4sterbunny Date: Thu, 25 Jul 2024 16:09:53 +0100 Subject: [PATCH] responds to link issues https://github.com/hyperledger/besu-docs/actions/runs/10095001531/job/27914102000\?pr\=1644 Signed-off-by: m4sterbunny --- .../how-to/configure-besu/index.md | 12 +++++------ docs/public-networks/reference/cli/options.md | 21 +++++++++---------- .../tutorials/besu-teku-testnet.md | 2 +- 3 files changed, 17 insertions(+), 18 deletions(-) diff --git a/docs/public-networks/how-to/configure-besu/index.md b/docs/public-networks/how-to/configure-besu/index.md index ab1b76c5e70..a54cf025b23 100644 --- a/docs/public-networks/how-to/configure-besu/index.md +++ b/docs/public-networks/how-to/configure-besu/index.md @@ -88,29 +88,29 @@ For example, using the [Staker profile](profile.md#staker-profile) with the boil |Command|Default|Notes| |---------------------------|--------------------|------------------------------------------| -|[`config-file`](../../reference/cli/options/#config-file)|None|Vanilla Besu assumes no configuration file| +|[`config-file`](../../reference/cli/options.md#config-file)|None|Vanilla Besu assumes no configuration file| ### Peering |Command|Default|Notes| |---------------------------|--------------------|------------------------------------------| -|[`discovery-enabled`](../../reference/cli/options/#discovery-enabled)|True|Besu assumes the node will automatically discover other Ethereum nodes using P2P| -|[`p2p-enabled`](../../reference/cli/options/#discovery-enabled)|True|Besu assumes the node will connect P2P| -|[`engine-rpc-enabled`](../../reference/cli/options/#engine-rpc-enabled)|True|Besu assumes the Engine API will be required to communicate with the consensus layer| +|[`discovery-enabled`](../../reference/cli/options.md#discovery-enabled)|True|Besu assumes the node will automatically discover other Ethereum nodes using P2P| +|[`p2p-enabled`](../../reference/cli/options.md#discovery-enabled)|True|Besu assumes the node will connect P2P| +|[`engine-rpc-enabled`](../../reference/cli/options.md#engine-rpc-enabled)|True|Besu assumes the Engine API will be required to communicate with the consensus layer| ### Storage |Command|Default|Notes| |---------------------------|--------------------|------------------------------------------| -|[`data-storage-format`](../../reference/cli/options/#data-storage-format)|BONSAI|Besu applies the most space-efficient storage method| +|[`data-storage-format`](../../reference/cli/options.md#data-storage-format)|BONSAI|Besu applies the most space-efficient storage method| ### Sync |Command|Default|Notes| |---------------------------|--------------------|------------------------------------------| -|[`sync-mode`](../../reference/cli/options/#sync-mode)|SNAP|Besu applies the [snap sync mode](../../get-started/connect/sync-node#snap-synchronization) as the most time-efficient sync method| +|[`sync-mode`](../../reference/cli/options.md#sync-mode)|SNAP|Besu applies the [snap sync mode](../../get-started/connect/sync-node#snap-synchronization) as the most time-efficient sync method| :::note For a comprehensive understanding, all defaults are provided in the [reference](../../reference/cli/options.md). diff --git a/docs/public-networks/reference/cli/options.md b/docs/public-networks/reference/cli/options.md index 501ce9010c9..3cf51b8e3e1 100644 --- a/docs/public-networks/reference/cli/options.md +++ b/docs/public-networks/reference/cli/options.md @@ -5177,11 +5177,11 @@ tx-pool="sequenced" Type of [transaction pool](../../concepts/transactions/pool.md) to use. -Set to `layered` to use the [layered transaction pool](../../concepts/transactions/pool#layered-transaction-pool) implementation. +Set to `layered` to use the [layered transaction pool](../../concepts/transactions/pool.md#layered-transaction-pool) implementation. The default is `layered`. -Set to `sequenced` to use the [sequenced transaction pool](../../concepts/transactions/pool#sequenced-transaction-pool). -The default is `sequenced` for the [enterprise/private profile](../../how-to/use-configuration-file/profile#enterpriseprivate-profile). +Set to `sequenced` to use the [sequenced transaction pool](../../concepts/transactions/pool.md#sequenced-transaction-pool). +The default is `sequenced` for the [enterprise/private profile](../../how-to/use-configuration-file/profile.md#enterpriseprivate-profile). ### `tx-pool-blob-price-bump` @@ -5307,8 +5307,7 @@ tx-pool-layer-max-capacity="20000000" -Maximum amount of memory (in bytes) that any layer within the [layered transaction -pool](../../concepts/transactions/pool#layered-transaction-pool) can occupy. +Maximum amount of memory (in bytes) that any layer within the [layered transaction pool](../../concepts/transactions/pool.md#layered-transaction-pool) can occupy. The default is `12500000`, or 12.5 MB. There are two memory-limited layers in the transaction pool, so the expected memory consumption is @@ -5358,7 +5357,7 @@ Accepted values are in the range `(0–1]`. The default is `.001`, or 0.1% of transactions from a single sender to be kept in the pool. :::caution -- With the [layered transaction pool](../../concepts/transactions/pool#layered-transaction-pool) +- With the [layered transaction pool](../../concepts/transactions/pool.md#layered-transaction-pool) implementation, this option is not applicable. Replace this option with [`--tx-pool-max-future-by-sender`](#tx-pool-max-future-by-sender) to specify the maximum number of sequential transactions from a single sender kept in the pool. @@ -5409,7 +5408,7 @@ tx-pool-max-future-by-sender="250" The maximum number of sequential transactions from a single sender kept in the -[layered transaction pool](../../concepts/transactions/pool#layered-transaction-pool). +[layered transaction pool](../../concepts/transactions/pool.md#layered-transaction-pool). The default is `200`. Increase this value to allow a single sender to fit more transactions in a single block. @@ -5455,7 +5454,7 @@ tx-pool-max-prioritized="1500" The maximum number of transactions that are prioritized in the -[layered transaction pool](../../concepts/transactions/pool#layered-transaction-pool). +[layered transaction pool](../../concepts/transactions/pool.md#layered-transaction-pool). The default is `2000`. For private networks, we recommend setting this value to the maximum number of transactions that fit @@ -5499,7 +5498,7 @@ tx-pool-max-prioritized-by-type="BLOB=6" -The maximum number of transactions of a specific [transaction type](../../concepts/transactions/types.md) that are prioritized in the [layered transaction pool](../../concepts/transactions/pool#layered-transaction-pool). +The maximum number of transactions of a specific [transaction type](../../concepts/transactions/types.md) that are prioritized in the [layered transaction pool](../../concepts/transactions/pool.md#layered-transaction-pool). This option is mostly useful for tuning the amount of prioritized [blob transactions](../../concepts/transactions/types#blob-transactions) in the transaction pool. Keeping the prioritized layer sorted is costly, and only a few blob transactions can fit in a block (currently a maximum of six). @@ -5548,7 +5547,7 @@ The maximum number of transactions kept in the [transaction pool](../../concepts The default is `4096`. :::caution -With the [layered transaction pool](../../concepts/transactions/pool#layered-transaction-pool) +With the [layered transaction pool](../../concepts/transactions/pool.md#layered-transaction-pool) implementation, this option is not applicable because the layered pool is limited by memory size instead of the number of transactions. To configure the maximum memory capacity, use [`--tx-pool-layer-max-capacity`](#tx-pool-layer-max-capacity). @@ -5765,7 +5764,7 @@ The maximum period (in hours) to hold pending transactions in the [transaction p The default is `13`. :::caution -With the [layered transaction pool](../../concepts/transactions/pool#layered-transaction-pool) +With the [layered transaction pool](../../concepts/transactions/pool.md#layered-transaction-pool) implementation, this option is not applicable because old transactions will expire when the memory cache is full. ::: diff --git a/docs/public-networks/tutorials/besu-teku-testnet.md b/docs/public-networks/tutorials/besu-teku-testnet.md index 15762ba3369..7b554f08043 100644 --- a/docs/public-networks/tutorials/besu-teku-testnet.md +++ b/docs/public-networks/tutorials/besu-teku-testnet.md @@ -45,7 +45,7 @@ If you're also running Teku as a validator client, create a test Ethereum addres :::note -If you can't get ETH using the faucet, you can ask for help on the [EthStaker Discord](https://discord.io/ethstaker). +If you can't get ETH using the faucet, you can ask for help on the [EthStaker Discord](https://discord.com/invite/ethstaker). :::