diff --git a/docs/private-networks/concepts/permissioning/index.md b/docs/private-networks/concepts/permissioning/index.md index a9e721f9d92..e1b9dd62c58 100644 --- a/docs/private-networks/concepts/permissioning/index.md +++ b/docs/private-networks/concepts/permissioning/index.md @@ -48,7 +48,13 @@ Local permissioning affects your node but not the rest of the network. Use local Local permissioning does not require coordination with the rest of the network and you can act immediately to protect your node. Your rules are not enforced in blocks produced by other nodes. -### Onchain +### Onchain (Deprecated) + +:::caution + +Onchain permissioning is deprecated in Besu version 24.11.0 and later. Please read this [blog post](https://www.lfdecentralizedtrust.org/blog/sunsetting-tessera-and-simplifying-hyperledger-besu) for more context on the rationale behind this decision as well as alternative options. + +::: [Onchain permissioning](onchain.md) works through a smart contract on the network. Specifying permissioning onchain enables all nodes to read and update permissioning configuration from one location. diff --git a/docs/private-networks/concepts/permissioning/onchain.md b/docs/private-networks/concepts/permissioning/onchain.md index 908a3418f9b..9c67dcc9cee 100644 --- a/docs/private-networks/concepts/permissioning/onchain.md +++ b/docs/private-networks/concepts/permissioning/onchain.md @@ -6,7 +6,13 @@ tags: - private networks --- -# Onchain permissioning +# Onchain permissioning (Deprecated) + +:::caution + +Onchain permissioning is deprecated in Besu version 24.11.0 and later. Please read this [blog post](https://www.lfdecentralizedtrust.org/blog/sunsetting-tessera-and-simplifying-hyperledger-besu) for more context on the rationale behind this decision as well as alternative options. + +::: Onchain [permissioning](index.md) uses smart contracts to store and administer the node, account, and admin allowlists. Using onchain permissioning enables all nodes to read the allowlists from a single source, the blockchain. diff --git a/docs/private-networks/concepts/privacy/flexible-privacy.md b/docs/private-networks/concepts/privacy/flexible-privacy.md index 9c074524920..1162c2a3acf 100644 --- a/docs/private-networks/concepts/privacy/flexible-privacy.md +++ b/docs/private-networks/concepts/privacy/flexible-privacy.md @@ -4,7 +4,13 @@ sidebar_position: 3 description: Flexible privacy groups --- -# Flexible privacy groups +# Flexible privacy groups (Deprecated) + +:::caution + +Tessera-based privacy is deprecated in Besu version 24.11.0 and later. Please read this [blog post](https://www.lfdecentralizedtrust.org/blog/sunsetting-tessera-and-simplifying-hyperledger-besu) for more context on the rationale behind this decision as well as alternative options. + +::: Flexible [privacy groups](privacy-groups.md) use smart contracts to store and maintain the group membership. You can [add and remove members to and from flexible privacy groups](../../how-to/use-privacy/flexible.md). diff --git a/docs/private-networks/concepts/privacy/index.md b/docs/private-networks/concepts/privacy/index.md index 0888bbe40e3..7fe9f47bab2 100644 --- a/docs/private-networks/concepts/privacy/index.md +++ b/docs/private-networks/concepts/privacy/index.md @@ -4,7 +4,13 @@ sidebar_position: 1 description: Privacy --- -# Privacy +# Privacy (Deprecated) + +:::caution + +Tessera-based privacy is deprecated in Besu version 24.11.0 and later. Please read this [blog post](https://www.lfdecentralizedtrust.org/blog/sunsetting-tessera-and-simplifying-hyperledger-besu) for more context on the rationale behind this decision as well as alternative options. + +::: In Besu, privacy refers to the ability to keep transactions private between the involved participants. Other participants cannot access the transaction content or list of participants. diff --git a/docs/private-networks/concepts/privacy/multi-tenancy.md b/docs/private-networks/concepts/privacy/multi-tenancy.md index d04b9606eb8..49959053c5d 100644 --- a/docs/private-networks/concepts/privacy/multi-tenancy.md +++ b/docs/private-networks/concepts/privacy/multi-tenancy.md @@ -4,7 +4,13 @@ sidebar_position: 4 description: Multi-tenancy --- -# Multi-tenancy +# Multi-tenancy (Deprecated) + +:::caution + +Tessera-based privacy is deprecated in Besu version 24.11.0 and later. Please read this [blog post](https://www.lfdecentralizedtrust.org/blog/sunsetting-tessera-and-simplifying-hyperledger-besu) for more context on the rationale behind this decision as well as alternative options. + +::: By default, each participant in a privacy network uses its own Besu and Tessera node. diff --git a/docs/private-networks/concepts/privacy/plugin.md b/docs/private-networks/concepts/privacy/plugin.md index ce3f574068c..f1424d9f50b 100644 --- a/docs/private-networks/concepts/privacy/plugin.md +++ b/docs/private-networks/concepts/privacy/plugin.md @@ -4,7 +4,13 @@ description: Privacy plugin sidebar_position: 5 --- -# Privacy plugin +# Privacy plugin (Deprecated) + +:::caution + +Tessera-based privacy is deprecated in Besu version 24.11.0 and later. Please read this [blog post](https://www.lfdecentralizedtrust.org/blog/sunsetting-tessera-and-simplifying-hyperledger-besu) for more context on the rationale behind this decision as well as alternative options. + +::: You can define your own strategy for private transactions by building a plugin that extends Besu functionality. diff --git a/docs/private-networks/concepts/privacy/privacy-groups.md b/docs/private-networks/concepts/privacy/privacy-groups.md index 8521efe7810..e2a85b1cf89 100644 --- a/docs/private-networks/concepts/privacy/privacy-groups.md +++ b/docs/private-networks/concepts/privacy/privacy-groups.md @@ -4,7 +4,13 @@ sidebar_position: 2 description: Privacy groups --- -# Privacy groups +# Privacy groups (Deprecated) + +:::caution + +Tessera-based privacy is deprecated in Besu version 24.11.0 and later. Please read this [blog post](https://www.lfdecentralizedtrust.org/blog/sunsetting-tessera-and-simplifying-hyperledger-besu) for more context on the rationale behind this decision as well as alternative options. + +::: A privacy group is a group of nodes identified by a unique privacy group ID by Tessera. Tessera stores each private transaction with the privacy group ID. diff --git a/docs/private-networks/concepts/privacy/private-transactions/index.md b/docs/private-networks/concepts/privacy/private-transactions/index.md index 0571268b995..e817e3920f7 100644 --- a/docs/private-networks/concepts/privacy/private-transactions/index.md +++ b/docs/private-networks/concepts/privacy/private-transactions/index.md @@ -2,7 +2,13 @@ description: Private transaction overview --- -# Private transactions +# Private transactions (Deprecated) + +:::caution + +Tessera-based privacy is deprecated in Besu version 24.11.0 and later. Please read this [blog post](https://www.lfdecentralizedtrust.org/blog/sunsetting-tessera-and-simplifying-hyperledger-besu) for more context on the rationale behind this decision as well as alternative options. + +::: Private transactions have the same parameters as public Ethereum transactions, with the following additions: diff --git a/docs/private-networks/concepts/privacy/private-transactions/processing.md b/docs/private-networks/concepts/privacy/private-transactions/processing.md index 196f2b9e7e0..a55c9535212 100644 --- a/docs/private-networks/concepts/privacy/private-transactions/processing.md +++ b/docs/private-networks/concepts/privacy/private-transactions/processing.md @@ -4,7 +4,13 @@ sidebar_position: 1 description: Private transaction processing --- -# Private transaction processing +# Private transaction processing (Deprecated) + +:::caution + +Tessera-based privacy is deprecated in Besu version 24.11.0 and later. Please read this [blog post](https://www.lfdecentralizedtrust.org/blog/sunsetting-tessera-and-simplifying-hyperledger-besu) for more context on the rationale behind this decision as well as alternative options. + +::: Processing [private transactions](index.md) involves the following: diff --git a/docs/private-networks/how-to/configure/bootnodes.md b/docs/private-networks/how-to/configure/bootnodes.md index 2805e7e1afc..b7bdb85e8ff 100644 --- a/docs/private-networks/how-to/configure/bootnodes.md +++ b/docs/private-networks/how-to/configure/bootnodes.md @@ -18,6 +18,9 @@ In production networks, [configure two or more nodes as bootnodes](#configure-bo Bootnodes and static nodes are parallel methods for finding peers. Depending on your use case, you can use only bootnodes, only static nodes, or both bootnodes and static nodes. +When connecting to bootnodes, Besu attempts to connect to all bootnodes at once, at startup. +When connecting to static nodes, Besu attempts to reconnect periodically, if the connection fails or is lost. + To find peers, configure one or more bootnodes. To configure a specific set of peer connections, use [static nodes](../../../public-networks/how-to/connect/static-nodes.md). ::: diff --git a/docs/private-networks/how-to/monitor/quorum-hibernate.md b/docs/private-networks/how-to/monitor/quorum-hibernate.md index 9eb390e4e5c..ef271456fa4 100644 --- a/docs/private-networks/how-to/monitor/quorum-hibernate.md +++ b/docs/private-networks/how-to/monitor/quorum-hibernate.md @@ -6,7 +6,13 @@ tags: - private networks --- -# Use Quorum Hibernate +# Use Quorum Hibernate (Deprecated) + +:::caution + +Tessera-based privacy is deprecated in Besu version 24.11.0 and later. Please read this [blog post](https://www.lfdecentralizedtrust.org/blog/sunsetting-tessera-and-simplifying-hyperledger-besu) for more context on the rationale behind this decision as well as alternative options. + +::: [Quorum Hibernate] is a proxy that monitors a node's API traffic and hibernates the node when inactive. This reduces infrastructure costs by ensuring only nodes receiving API requests or nodes required to establish consensus are running. diff --git a/docs/private-networks/how-to/send-transactions/concurrent-private-transactions.md b/docs/private-networks/how-to/send-transactions/concurrent-private-transactions.md index b14ca734c72..765d89b9a26 100644 --- a/docs/private-networks/how-to/send-transactions/concurrent-private-transactions.md +++ b/docs/private-networks/how-to/send-transactions/concurrent-private-transactions.md @@ -6,7 +6,13 @@ tags: - private networks --- -# Send concurrent private transactions +# Send concurrent private transactions (Deprecated) + +:::caution + +Tessera-based privacy is deprecated in Besu version 24.11.0 and later. Please read this [blog post](https://www.lfdecentralizedtrust.org/blog/sunsetting-tessera-and-simplifying-hyperledger-besu) for more context on the rationale behind this decision as well as alternative options. + +::: Private transaction processing involves two transactions, the private transaction and the [privacy marker transaction (PMT)](../../concepts/privacy/private-transactions/processing.md). The private transaction and the PMT each have their own [nonce](../../concepts/privacy/private-transactions/index.md#nonces). diff --git a/docs/private-networks/how-to/send-transactions/private-transactions.md b/docs/private-networks/how-to/send-transactions/private-transactions.md index 92f1d2a62a5..e67273c2fcf 100644 --- a/docs/private-networks/how-to/send-transactions/private-transactions.md +++ b/docs/private-networks/how-to/send-transactions/private-transactions.md @@ -6,7 +6,13 @@ tags: - private networks --- -# Create and send private transactions +# Create and send private transactions (Deprecated) + +:::caution + +Tessera-based privacy is deprecated in Besu version 24.11.0 and later. Please read this [blog post](https://www.lfdecentralizedtrust.org/blog/sunsetting-tessera-and-simplifying-hyperledger-besu) for more context on the rationale behind this decision as well as alternative options. + +::: Create and send [private transactions](../../concepts/privacy/index.md) using: diff --git a/docs/private-networks/how-to/use-permissioning/local.md b/docs/private-networks/how-to/use-permissioning/local.md index b9f3bce4154..53544af8770 100644 --- a/docs/private-networks/how-to/use-permissioning/local.md +++ b/docs/private-networks/how-to/use-permissioning/local.md @@ -112,7 +112,7 @@ Transaction validation against the accounts allowlist occurs at the following po After adding transactions to a block, the transactions are not validated against the allowlist when received by another node. That is, a node can synchronize and add blocks containing transactions from accounts that are not on the accounts allowlist of that node. -The following diagram illustrates applying local and onchain permissioning rules. +The following diagram illustrates applying local and [onchain permissioning] rules. ![Permissioning Flow](../../../assets/images/PermissioningFlow.png) diff --git a/docs/private-networks/how-to/use-permissioning/onchain.md b/docs/private-networks/how-to/use-permissioning/onchain.md index 46d8527db99..054062f9043 100644 --- a/docs/private-networks/how-to/use-permissioning/onchain.md +++ b/docs/private-networks/how-to/use-permissioning/onchain.md @@ -6,7 +6,13 @@ tags: - private networks --- -# Use onchain permissioning +# Use onchain permissioning (Deprecated) + +:::caution + +Onchain permissioning is deprecated in Besu version 24.11.0 and later. Please read this [blog post](https://www.lfdecentralizedtrust.org/blog/sunsetting-tessera-and-simplifying-hyperledger-besu) for more context on the rationale behind this decision as well as alternative options. + +::: This page contains some extra info if you're using [onchain permissioning](../../concepts/permissioning/onchain.md). diff --git a/docs/private-networks/how-to/use-privacy/access-private-transactions.md b/docs/private-networks/how-to/use-privacy/access-private-transactions.md index fa0e1e0a94c..c2b92771e1c 100644 --- a/docs/private-networks/how-to/use-privacy/access-private-transactions.md +++ b/docs/private-networks/how-to/use-privacy/access-private-transactions.md @@ -6,7 +6,13 @@ tags: - private networks --- -# Access private and privacy marker transactions +# Access private and privacy marker transactions (Deprecated) + +:::caution + +Tessera-based privacy is deprecated in Besu version 24.11.0 and later. Please read this [blog post](https://www.lfdecentralizedtrust.org/blog/sunsetting-tessera-and-simplifying-hyperledger-besu) for more context on the rationale behind this decision as well as alternative options. + +::: A Besu private transaction creates a [privacy marker transaction](../../concepts/privacy/private-transactions/processing.md) and the private transaction itself. diff --git a/docs/private-networks/how-to/use-privacy/besu-extended.md b/docs/private-networks/how-to/use-privacy/besu-extended.md index 4fb896542de..0731095381e 100644 --- a/docs/private-networks/how-to/use-privacy/besu-extended.md +++ b/docs/private-networks/how-to/use-privacy/besu-extended.md @@ -6,7 +6,13 @@ tags: - private networks --- -# Use Besu-extended privacy +# Use Besu-extended privacy (Deprecated) + +:::caution + +Tessera-based privacy is deprecated in Besu version 24.11.0 and later. Please read this [blog post](https://www.lfdecentralizedtrust.org/blog/sunsetting-tessera-and-simplifying-hyperledger-besu) for more context on the rationale behind this decision as well as alternative options. + +::: Besu provides an extended implementation of privacy allowing you to [create a privacy group for a set of participants](../../concepts/privacy/privacy-groups.md). You must specify the privacy group ID when sending private transactions. diff --git a/docs/private-networks/how-to/use-privacy/eea-compliant.md b/docs/private-networks/how-to/use-privacy/eea-compliant.md index 67ec058f0de..8eef82b5bd2 100644 --- a/docs/private-networks/how-to/use-privacy/eea-compliant.md +++ b/docs/private-networks/how-to/use-privacy/eea-compliant.md @@ -6,7 +6,13 @@ tags: - private networks --- -# Use EEA-compliant privacy +# Use EEA-compliant privacy (Deprecated) + +:::caution + +Tessera-based privacy is deprecated in Besu version 24.11.0 and later. Please read this [blog post](https://www.lfdecentralizedtrust.org/blog/sunsetting-tessera-and-simplifying-hyperledger-besu) for more context on the rationale behind this decision as well as alternative options. + +::: When using Besu [EEA-compliant privacy](../../concepts/privacy/privacy-groups.md), the group of nodes specified by `privateFrom` and `privateFor` form a privacy group, to which Tessera assigns a unique privacy group ID. diff --git a/docs/private-networks/how-to/use-privacy/flexible.md b/docs/private-networks/how-to/use-privacy/flexible.md index abf1892732b..c787822e9da 100644 --- a/docs/private-networks/how-to/use-privacy/flexible.md +++ b/docs/private-networks/how-to/use-privacy/flexible.md @@ -6,7 +6,13 @@ tags: - private networks --- -# Use flexible privacy groups +# Use flexible privacy groups (Deprecated) + +:::caution + +Tessera-based privacy is deprecated in Besu version 24.11.0 and later. Please read this [blog post](https://www.lfdecentralizedtrust.org/blog/sunsetting-tessera-and-simplifying-hyperledger-besu) for more context on the rationale behind this decision as well as alternative options. + +::: Use the [`web3js-quorum` library](https://github.com/ConsenSys/web3js-quorum) to create and update membership of [flexible privacy groups](../../concepts/privacy/flexible-privacy.md). diff --git a/docs/private-networks/how-to/use-privacy/performance-best-practices.md b/docs/private-networks/how-to/use-privacy/performance-best-practices.md index e75cfabc2c7..55e7df8377f 100644 --- a/docs/private-networks/how-to/use-privacy/performance-best-practices.md +++ b/docs/private-networks/how-to/use-privacy/performance-best-practices.md @@ -6,7 +6,13 @@ tags: - private networks --- -# Performance best practices +# Privacy performance best practices (Deprecated) + +:::caution + +Tessera-based privacy is deprecated in Besu version 24.11.0 and later. Please read this [blog post](https://www.lfdecentralizedtrust.org/blog/sunsetting-tessera-and-simplifying-hyperledger-besu) for more context on the rationale behind this decision as well as alternative options. + +::: This document collects deployment and usage tips to help you achieve high performance for private transactions. If transaction throughput or latency is not meeting your expectations, please consider the following before raising an issue. diff --git a/docs/private-networks/how-to/use-privacy/privacy-groups.md b/docs/private-networks/how-to/use-privacy/privacy-groups.md index 887d84cd53b..34ecf2ad94c 100644 --- a/docs/private-networks/how-to/use-privacy/privacy-groups.md +++ b/docs/private-networks/how-to/use-privacy/privacy-groups.md @@ -6,7 +6,13 @@ tags: - private networks --- -# Create and manage privacy groups +# Create and manage privacy groups (Deprecated) + +:::caution + +Tessera-based privacy is deprecated in Besu version 24.11.0 and later. Please read this [blog post](https://www.lfdecentralizedtrust.org/blog/sunsetting-tessera-and-simplifying-hyperledger-besu) for more context on the rationale behind this decision as well as alternative options. + +::: Besu-extended privacy provides JSON-RPC API methods for creating and managing privacy groups: diff --git a/docs/private-networks/how-to/use-privacy/sign-pmts.md b/docs/private-networks/how-to/use-privacy/sign-pmts.md index 1dea1b4ff63..9dbe134446c 100644 --- a/docs/private-networks/how-to/use-privacy/sign-pmts.md +++ b/docs/private-networks/how-to/use-privacy/sign-pmts.md @@ -6,7 +6,13 @@ tags: - private networks --- -# Sign privacy marker transactions +# Sign privacy marker transactions (Deprecated) + +:::caution + +Tessera-based privacy is deprecated in Besu version 24.11.0 and later. Please read this [blog post](https://www.lfdecentralizedtrust.org/blog/sunsetting-tessera-and-simplifying-hyperledger-besu) for more context on the rationale behind this decision as well as alternative options. + +::: You can sign privacy marker transactions (PMTs) with either a random key or a specified key. To sign privacy marker transactions with a specified private key, use [`--privacy-marker-transaction-signing-key-file`](../../reference/cli/options.md#privacy-marker-transaction-signing-key-file) when starting Besu. diff --git a/docs/private-networks/how-to/use-privacy/tessera.md b/docs/private-networks/how-to/use-privacy/tessera.md index adf67093c9f..47f1210173c 100644 --- a/docs/private-networks/how-to/use-privacy/tessera.md +++ b/docs/private-networks/how-to/use-privacy/tessera.md @@ -6,7 +6,13 @@ tags: - private networks --- -# Run Tessera with Besu +# Run Tessera with Besu (Deprecated) + +:::caution + +Tessera-based privacy is deprecated in Besu version 24.11.0 and later. Please read this [blog post](https://www.lfdecentralizedtrust.org/blog/sunsetting-tessera-and-simplifying-hyperledger-besu) for more context on the rationale behind this decision as well as alternative options. + +::: To enable [privacy functionality](../../concepts/privacy/index.md) in production systems, [Tessera](https://docs.tessera.consensys.net/) must be [highly available](#high-availability) and [run in a separate instance](#separate-instances) to Besu. diff --git a/docs/private-networks/how-to/use-privacy/web3js-quorum.md b/docs/private-networks/how-to/use-privacy/web3js-quorum.md index b3a83f2ec31..c9910cc51f6 100644 --- a/docs/private-networks/how-to/use-privacy/web3js-quorum.md +++ b/docs/private-networks/how-to/use-privacy/web3js-quorum.md @@ -9,7 +9,13 @@ tags: import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -# Use the web3js-quorum client library +# Use the web3js-quorum client library (Deprecated) + +:::caution + +Tessera-based privacy is deprecated in Besu version 24.11.0 and later. Please read this [blog post](https://www.lfdecentralizedtrust.org/blog/sunsetting-tessera-and-simplifying-hyperledger-besu) for more context on the rationale behind this decision as well as alternative options. + +::: [web3js-quorum](https://github.com/ConsenSys/web3js-quorum) is an Ethereum JavaScript library extending [web3.js](https://github.com/ethereum/web3.js/) that adds support for Besu-specific JSON-RPC APIs and features. Use the library to create and send RLP-encoded transactions using JSON-RPC. diff --git a/docs/private-networks/index.md b/docs/private-networks/index.md index 1f23e1a2d0f..1f2c0b7bd90 100644 --- a/docs/private-networks/index.md +++ b/docs/private-networks/index.md @@ -12,7 +12,7 @@ tags: You can use Besu to develop enterprise applications requiring secure, high-performance transaction processing in a private network. -A private network is a network not connected to Ethereum Mainnet or an Ethereum testnet. Private networks typically use a different [chain ID](../public-networks/concepts/network-and-chain-id.md) and proof of authority consensus ([QBFT](how-to/configure/consensus/qbft.md), [IBFT 2.0](how-to/configure/consensus/ibft.md), or [Clique](how-to/configure/consensus/clique.md)). +A private (also known as permissioned) network is a network not connected to Ethereum Mainnet or an Ethereum testnet. Private networks typically use a different [chain ID](../public-networks/concepts/network-and-chain-id.md) and proof of authority consensus ([QBFT](how-to/configure/consensus/qbft.md), [IBFT 2.0](how-to/configure/consensus/ibft.md), or [Clique](how-to/configure/consensus/clique.md)). You can also [create a local development network](tutorials/ethash.md) using proof of work (Ethash). diff --git a/docs/private-networks/tutorials/privacy/index.md b/docs/private-networks/tutorials/privacy/index.md index 4f57937691b..2977d778415 100644 --- a/docs/private-networks/tutorials/privacy/index.md +++ b/docs/private-networks/tutorials/privacy/index.md @@ -9,7 +9,13 @@ tags: import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -# Create a privacy-enabled network +# Create a privacy-enabled network (Deprecated) + +:::caution + +Tessera-based privacy is deprecated in Besu version 24.11.0 and later. Please read this [blog post](https://www.lfdecentralizedtrust.org/blog/sunsetting-tessera-and-simplifying-hyperledger-besu) for more context on the rationale behind this decision as well as alternative options. + +::: Configuring a network that supports private transactions requires starting a [Tessera] node for each Besu node. Besu command line options associate the Besu node with the Tessera node. diff --git a/docs/private-networks/tutorials/privacy/multi-tenancy.md b/docs/private-networks/tutorials/privacy/multi-tenancy.md index 7db1a5101df..4afb36dccf0 100644 --- a/docs/private-networks/tutorials/privacy/multi-tenancy.md +++ b/docs/private-networks/tutorials/privacy/multi-tenancy.md @@ -6,7 +6,13 @@ tags: - private networks --- -# Configure a multi-tenant node +# Configure a multi-tenant node (Deprecated) + +:::caution + +Tessera-based privacy is deprecated in Besu version 24.11.0 and later. Please read this [blog post](https://www.lfdecentralizedtrust.org/blog/sunsetting-tessera-and-simplifying-hyperledger-besu) for more context on the rationale behind this decision as well as alternative options. + +::: You can configure Besu and associated Tessera node in a privacy-enabled network to host [multiple tenants](../../concepts/privacy/multi-tenancy.md). diff --git a/docs/private-networks/tutorials/privacy/quickstart.md b/docs/private-networks/tutorials/privacy/quickstart.md index d01bc599ffa..980ee6cfc92 100644 --- a/docs/private-networks/tutorials/privacy/quickstart.md +++ b/docs/private-networks/tutorials/privacy/quickstart.md @@ -4,7 +4,13 @@ tags: - private networks --- -# Create a privacy-enabled network using the Quorum Developer Quickstart +# Create a privacy-enabled network using the Quorum Developer Quickstart (Deprecated) + +:::caution + +Tessera-based privacy is deprecated in Besu version 24.11.0 and later. Please read this [blog post](https://www.lfdecentralizedtrust.org/blog/sunsetting-tessera-and-simplifying-hyperledger-besu) for more context on the rationale behind this decision as well as alternative options. + +::: You can create a privacy-enabled network using the [Quorum Developer Quickstart](../quickstart.md). It runs a private Besu network that uses [Tessera](https://docs.tessera.consensys.net/en/stable/) as its private transaction manager. diff --git a/docs/private-networks/tutorials/privacy/web3js-quorum.md b/docs/private-networks/tutorials/privacy/web3js-quorum.md index b008bae0a56..36362926581 100644 --- a/docs/private-networks/tutorials/privacy/web3js-quorum.md +++ b/docs/private-networks/tutorials/privacy/web3js-quorum.md @@ -6,7 +6,13 @@ tags: - private networks --- -# Use the multi-node example in the web3js-quorum client library +# Use the multi-node example in the web3js-quorum client library (Deprecated) + +:::caution + +Tessera-based privacy is deprecated in Besu version 24.11.0 and later. Please read this [blog post](https://www.lfdecentralizedtrust.org/blog/sunsetting-tessera-and-simplifying-hyperledger-besu) for more context on the rationale behind this decision as well as alternative options. + +::: To use the examples provided in the web3js-quorum library with [your privacy network](index.md): diff --git a/docs/private-networks/tutorials/quickstart.md b/docs/private-networks/tutorials/quickstart.md index 4643ef8b7e1..0916e35e646 100644 --- a/docs/private-networks/tutorials/quickstart.md +++ b/docs/private-networks/tutorials/quickstart.md @@ -531,7 +531,7 @@ New nodes joining an existing network require the following: - The same genesis file used by all other nodes on the running network. - A list of nodes to connect to; this is done by specifying [bootnodes], or by providing a list of [static nodes]. -- A node key pair and optionally an account. If the running network is using permissions, then you need to add the new node's enode details to the [permissions file] used by existing nodes, or update the onchain permissioning contract. +- A node key pair and optionally an account. If the running network is using permissions, then you need to add the new node's enode details to the [permissions file] used by existing nodes. The following steps describe the process to add a new node to the Developer Quickstart. diff --git a/docs/public-networks/how-to/connect/static-nodes.md b/docs/public-networks/how-to/connect/static-nodes.md index bccef277804..81d67fddce5 100644 --- a/docs/public-networks/how-to/connect/static-nodes.md +++ b/docs/public-networks/how-to/connect/static-nodes.md @@ -17,6 +17,9 @@ Besu periodically initiates a connection to any unconnected static node. To miti Bootnodes and static nodes are both methods for finding peers. Depending on your use case, you can use only bootnodes, only static nodes, or both bootnodes and static nodes. +When connecting to bootnodes, Besu attempts to connect to all bootnodes at once, at startup. +When connecting to static nodes, Besu attempts to reconnect periodically, if the connection fails or is lost. + For example: * You run multiple nodes on Mainnet, using bootnodes for discovery, but want to ensure your nodes are always connected to each other, using static nodes. * You run a small network and want your nodes to reconnect if disconnected, using static nodes.