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

Author: Alexandra Tran

SECURITY.md

@@ -7,7 +7,7 @@ hear from you. We will take all security bugs seriously and if confirmed upon in
 patch it within a reasonable amount of time and release a public security bulletin discussing the
 impact and credit the discoverer.
 
-You can report a security bug in two ways. The easiest is to email a description of the flaw and
+You can report a security bug by emailing a description of the flaw and
 any related information (for example reproduction steps, version) to
 [Hyperledger security email address`](mailto:security@hyperledger.org).
 

docs/private-networks/concepts/permissioning/index.md

@@ -38,7 +38,7 @@ Use account permissioning to:
 
 ## Specify permissioning
 
-You can specify permissioning [locally](#local) or [onchain](#onchain).
+You can specify permissioning [locally](#local) or [onchain](#onchain-deprecated).
 
 ### Local
 

docs/private-networks/concepts/privacy/flexible-privacy.md

@@ -66,22 +66,22 @@ Using multi-tenancy with flexible privacy groups is more complex than with [offc
 
 In particular, when multi-tenancy is enabled and a user requests access to a privacy group they were once a member of but later removed from, Besu allows the user access to the following functionality and data associated with the privacy group:
 
-- Private transactions using `priv_getTransaction` and private transaction receipts using [`priv_getTransactionReceipt`](../../../public-networks/reference/api/index.md#priv_gettransactionreceipt) from blocks up to (and including) the removal block.
+- Private transactions using `priv_getTransaction` and private transaction receipts using [`priv_getTransactionReceipt`](../../reference/api/index.md#priv_gettransactionreceipt) from blocks up to (and including) the removal block.
 
   :::note
 
   A removed group member may have access to some private transactions after the removal PMT in the same block.
 
   :::
 
-- Using [`priv_call`](../../../public-networks/reference/api/index.md#priv_call) on blocks up to (and including) the removal block.
+- Using [`priv_call`](../../reference/api/index.md#priv_call) on blocks up to (and including) the removal block.
 
-- Private logs using [`priv_getLogs`](../../../public-networks/reference/api/index.md#priv_getlogs) for blocks up to (and including) the removal block. When the `toBlock` is greater than the removal block, `priv_getLogs` still returns logs up to the removal block.
+- Private logs using [`priv_getLogs`](../../reference/api/index.md#priv_getlogs) for blocks up to (and including) the removal block. When the `toBlock` is greater than the removal block, `priv_getLogs` still returns logs up to the removal block.
 
   :::note
 
   When a user is removed from a privacy group, any log filters they've created are also removed and can't be accessed. A user can only create and access filters for a privacy group they are currently a member of.
 
   :::
 
-All other [`PRIV` API methods](../../../public-networks/reference/api/index.md#priv-methods) fail for the removed group member.
+All other [`PRIV` API methods](../../reference/api/index.md#priv-methods) fail for the removed group member.

docs/private-networks/concepts/privacy/index.md

@@ -21,7 +21,7 @@ For production environments requiring private transactions:
 - We recommend using a network with a consensus mechanism supporting transaction finality. For example, [IBFT 2.0](../../how-to/configure/consensus/ibft.md).
 - Tessera must be [highly available and run in a separate instance to Besu].
 
-Using private transactions with [pruning] or [fast sync](../../../public-networks/reference/cli/options.md#sync-mode) isn't supported.
+Using private transactions with [fast sync](../../../public-networks/reference/cli/options.md#sync-mode) isn't supported.
 
 :::
 
@@ -74,4 +74,3 @@ Do not use private transactions in production environments using consensus mecha
 <!-- Links -->
 
 [highly available and run in a separate instance to Besu]: ../../how-to/use-privacy/tessera.md
-[pruning]: ../../../public-networks/concepts/data-storage-formats.md#pruning

docs/private-networks/concepts/privacy/multi-tenancy.md

@@ -30,7 +30,7 @@ Ensure the multi-tenant Tessera node client API is configured to allow access on
 
 If not configured to allow access only by the multi-tenant Besu node, other Tessera clients, including other Besu nodes, might be able to access tenant data.
 
-To secure access, you can [configure TLS between Besu and Tessera](../../how-to/configure/tls/client-and-server.md) with the [`WHITELIST`](https://docs.tessera.consensys.net/en/stable/HowTo/Configure/TLS/#whitelist) trust mode.
+To secure access, you can [configure TLS between Besu and Tessera](../../how-to/configure/tls.md) with the [`WHITELIST`](https://docs.tessera.consensys.net/en/stable/HowTo/Configure/TLS/#whitelist) trust mode.
 
 :::
 

docs/private-networks/concepts/privacy/plugin.md

@@ -34,7 +34,7 @@ Besu doesn't need to know how the private transaction is distributed, it just ne
 
 ### Send transactions
 
-When submitting a private transaction using [`eea_sendRawTransaction`](../../../public-networks/reference/api/index.md#eea_sendrawtransaction), the signed transaction must be sent to `0x000000000000000000000000000000000000007a` to indicate which [privacy precompiled contract](private-transactions/processing.md) is being used.
+When submitting a private transaction using [`eea_sendRawTransaction`](../../reference/api/index.md#eea_sendrawtransaction), the signed transaction must be sent to `0x000000000000000000000000000000000000007a` to indicate which [privacy precompiled contract](private-transactions/processing.md) is being used.
 
 The transaction flow is as follows:
 
@@ -48,7 +48,7 @@ The transaction flow is as follows:
 
 The process of mining transactions happens in reverse to sending transactions.
 
-1.  The Mainnet transaction processor processes the PMT in the same way as any other public transaction. On nodes containing the [privacy precompile contract](../../../public-networks/reference/api/index.md#priv_getprivacyprecompileaddress) specified in the `to` attribute of the PMT, the Mainnet transaction processor passes the PMT to the privacy precompile contract.
+1.  The Mainnet transaction processor processes the PMT in the same way as any other public transaction. On nodes containing the [privacy precompile contract](../../reference/api/index.md#priv_getprivacyprecompileaddress) specified in the `to` attribute of the PMT, the Mainnet transaction processor passes the PMT to the privacy precompile contract.
 
     :::note
 

docs/private-networks/concepts/privacy/privacy-groups.md

@@ -70,7 +70,7 @@ To send private transactions between A, C, and D, C initializes a different cont
 
 ### Besu-extended privacy
 
-The Besu-extended privacy implementation creates a privacy group using [`priv_createPrivacyGroup`](../../../public-networks/reference/api/index.md#priv_createprivacygroup) with private transactions sent to the privacy group ID.
+The Besu-extended privacy implementation creates a privacy group using [`priv_createPrivacyGroup`](../../reference/api/index.md#priv_createprivacygroup) with private transactions sent to the privacy group ID.
 
 Using the same privacy groups as in the previous example.
 

docs/private-networks/concepts/privacy/private-transactions/processing.md

@@ -67,12 +67,11 @@ Private transaction processing is illustrated and described in the following dia
 - We recommend using a network with a consensus mechanism supporting transaction finality. For example, [IBFT 2.0](../../../how-to/configure/consensus/ibft.md).
 - Tessera must be [highly available and run in a separate instance to Besu](../../../how-to/use-privacy/tessera.md).
 
-Using private transactions with [pruning] or [fast sync](../../../../public-networks/reference/cli/options.md#sync-mode) is not supported.
+Using private transactions with [fast sync](../../../../public-networks/reference/cli/options.md#sync-mode) is not supported.
 
 :::
 
 <!-- Links -->
 
 [signed with a random key or the key specified on the command line]: ../../../how-to/use-privacy/sign-pmts.md
-[highly available and run in a separate instance to Besu]: ../../../how-to/use-privacy/tessera.md
-[pruning]: ../../../../public-networks/concepts/data-storage-formats.md#pruning
+[highly available and run in a separate instance to Besu]: ../../../how-to/use-privacy/tessera.md

docs/private-networks/how-to/configure/consensus/ibft.md

@@ -198,7 +198,7 @@ The methods to add or remove validators are:
 - [`ibft_proposeValidatorVote`](../../../reference/api/index.md#ibft_proposevalidatorvote).
 - [`ibft_discardValidatorVote`](../../../reference/api/index.md#ibft_discardvalidatorvote).
 
-To view validator metrics for a specified block range, use [`ibft_getSignerMetrics`](../../../../public-networks/reference/api/index.md#ibft_getsignermetrics).
+To view validator metrics for a specified block range, use [`ibft_getSignerMetrics`](../../../reference/api/index.md#ibft_getsignermetrics).
 
 :::note
 

docs/private-networks/how-to/configure/curves.md

@@ -16,7 +16,7 @@ Configuring alternative elliptic curves is an early access feature.
 
 By default, Besu uses the Ethereum standard `secp256k1` elliptic curve (EC). However, when running nodes in a private network, it is possible to configure an alternative elliptic curve.
 
-The configuration for what elliptic curve Besu will use is done in the network configuration section of genesis file, using the [`ecCurve`](../../../public-networks/reference/genesis-items.md#Configuration_Items) key:
+The configuration for what elliptic curve Besu will use is done in the network configuration section of genesis file, using the [`ecCurve`](../../../public-networks/reference/genesis-items.md#configuration-items) key:
 
 ```bash
 {