Repository: ethereum/go-ethereum (language: go)

Issue:
[Website] Put a disclaimer in the doc for the deprecation of clique
# Rationale

As from v1.14, clique is now deprecated, the documentation need a disclaimer to inform the user clique has been removed.

# Implementation

PR to come very soon with a proposition


Discussion / hints:

Fix patch:
diff --git a/docs/fundamentals/private-network.md b/docs/fundamentals/private-network.md
index b2dc471f6c64..02b0d3e79296 100644
--- a/docs/fundamentals/private-network.md
+++ b/docs/fundamentals/private-network.md
@@ -31,6 +31,10 @@ Geth's PoW algorithm, [Ethash](https://ethereum.org/en/developers/docs/consensus
 
 #### Clique {#clique}
 
+> ⚠️
+> **Since geth v1.14 clique has been deprecated**
+
+
 Clique consensus is a PoA system where new blocks can be created by authorized 'signers' only. The clique consensus protocol is specified in [EIP-225](https://eips.ethereum.org/EIPS/eip-225). The initial set of authorized signers is configured in the genesis block. Signers can be authorized and de-authorized using a voting mechanism, thus allowing the set of signers to change while the blockchain operates. Clique can be configured to target any block time (within reasonable limits) since it isn't tied to the difficulty adjustment.
 
 ### Creating The Genesis Block {#creating-genesis-block}
@@ -45,6 +49,9 @@ Every blockchain starts with a genesis block. When Geth is run with default sett
 
 #### Clique Example {#clique-example}
 
+> ⚠️
+> **Since geth v1.14 clique has been deprecated**
+
 Below is an example of a `genesis.json` file for a PoA network. The `config` section ensures that all known protocol changes are available and configures the 'clique' engine to be used for consensus. Note that the initial signer set must be configured through the `extradata` field. This field is required for Clique to work.
 
 The signer account keys can be generated using the [geth account](/docs/fundamentals/account-management) command (this command can be run multiple times to create more than one signer key).
@@ -203,6 +210,8 @@ geth attach data2/geth.ipc --exec admin.peers
 
 ### Running A Signer (Clique) {#running-a-signer}
 
+> :> [!WARNING] **Since geth v1.14 clique is not an option anymore**
+
 To set up Geth for signing blocks in Clique, a signer account must be available. The account must already be available as a keyfile in the keystore. To use it for signing blocks, it must be unlocked. The following command, for address `0x7df9a875a174b3bc565e6424a0050ebc1b2d1d82` will prompt for the account password, then start signing blocks:
 
 ```sh
diff --git a/docs/interacting-with-geth/rpc/ns-clique.md b/docs/interacting-with-geth/rpc/ns-clique.md
index 06bdeca5d270..8f6218fdcd76 100644
--- a/docs/interacting-with-geth/rpc/ns-clique.md
+++ b/docs/interacting-with-geth/rpc/ns-clique.md
@@ -3,6 +3,9 @@ title: clique Namespace
 description: Documentation for the JSON-RPC API "clique" namespace
 ---
 
+> ⚠️
+> **Since geth v1.14 clique has been deprecated**
+
 The `clique` API provides access to the state of the clique consensus engine. This API can be used to manage signer votes and to check the health of a private network.
 
 ## clique_getSnapshot {#clique-getsnapshot}
diff --git a/docs/tools/clef/clique-signing.md b/docs/tools/clef/clique-signing.md
index ff23b9507c96..3e6f363ffda4 100644
--- a/docs/tools/clef/clique-signing.md
+++ b/docs/tools/clef/clique-signing.md
@@ -3,6 +3,9 @@ title: Clique signing
 description: Instructions for setting up Clef to seal blocks on a Clique network
 ---
 
+> ⚠️
+> **Since geth v1.14 clique has been deprecated**
+
 Clique is a proof-of-authority system where new blocks can be created by authorized ‘signers’ only. The initial set of authorized signers is configured in the genesis block. Signers can be authorized and de-authorized using a voting mechanism, thus allowing the set of signers to change while the blockchain operates. Signing blocks in Clique networks classically uses the "unlock" feature of Geth so that each node is always ready to sign without requiring a user to manually provide authorization.
 
 However, using the `--unlock` flag is generally a highly dangerous thing to do because it is indiscriminate, i.e. if an account is unlocked and an attacker obtains access to the RPC api, the attacker can sign anything without supplying a password.


Test patch: