Permissioning (onchain) deprecation

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.
 

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.
 

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)
 

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).
 

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.