Remove privacy and onchain permissioning content (#1833)

* Document truststore options

Signed-off-by: Alexandra Tran <[email protected]>

* add more context to descriptions

Signed-off-by: Alexandra Tran <[email protected]>

* Remove privacy and onchain permissioning content

Signed-off-by: Alexandra Tran <[email protected]>

* address reviewer feedback

Signed-off-by: Alexandra Tran <[email protected]>

* remove privacy core from architecture diagram

Signed-off-by: Alexandra Tran <[email protected]>

* eth_getWork -> debug_traceCall

Signed-off-by: Alexandra Tran <[email protected]>

---------

Signed-off-by: Alexandra Tran <[email protected]>
Co-authored-by: Alexandra Tran <[email protected]>

Author: alexandratran

docs/assets/images/PermissioningFlow.png

@@ -10,14 +10,12 @@ tags:
 
 A permissioned network enables node permissioning and account permissioning, allowing only specified nodes and accounts to access the network.
 
-:::caution Permissioning is not privacy
+:::caution Permissioning in peer-to-peer networks: challenges and enforcement
 
-In peer-to-peer networks, node permissioning enforces rules on nodes you control.
+In peer-to-peer networks, permissioning enforces rules on nodes you control.
 
 Permissioning requires a distributed network of trust across the network where participants agree to follow the rules. One bad actor can decide not to follow the rules. Nodes can take action to prevent the bad actor from adding to the chain but they cannot prevent the bad actor from allowing access to the chain.
 
-Besu also implements [privacy](../privacy/index.md).
-
 :::
 
 ## Node permissioning
@@ -36,36 +34,16 @@ Use account permissioning to:
 
 ![Account Permissioning](../../../assets/images/enterprise-ethereum-account-permissioning.png)
 
-## Specify permissioning
-
-You can specify permissioning [locally](#local) or [onchain](#onchain-deprecated).
-
-### Local
+## Specify local permissioning
 
-[Local permissioning](../../how-to/use-permissioning/local.md) works at the node level. Each node in the network has a [permissions configuration file].
+[Local permissioning](../../how-to/use-local-permissioning.md) works at the node level. Each node in the network has a [permissions configuration file], which can be used to configure node and/or account permissioning rules.
 
 Local permissioning affects your node but not the rest of the network. Use local permissioning to restrict use of your node (that is, the resources under your control). For example, customers are able to access your node.
 
 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 (Deprecated)
-
-:::caution
-
-Onchain permissioning is deprecated in Besu version 24.12.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.
-
-Onchain permissioning requires coordination to update the rules. The network might not be able to act immediately (for example, the smart contract might enforce a minimum number of votes before changing permissioning rules).
-
-When you update onchain permissioning, the update applies across the network and new blocks abide by the updated rules. For example, blocked accounts can no longer add transactions to the chain.
-
-The following diagram illustrates applying local and onchain permissioning rules.
-
-![Permissioning Flow](../../../assets/images/PermissioningFlow.png)
+To implement more complex permissioning rules, you can [write your own plugin](plugin.md).
 
 <!-- Links -->
 
-[permissions configuration file]: ../../how-to/use-permissioning/local.md#permissions-configuration-file
+[permissions configuration file]: ../../how-to/use-local-permissioning.md#permissions-configuration-file