Merge branch 'main' into dependabot/npm_and_yarn/cookbookdev/docsbot-…

…4.18.11

docs/contracts/contracts/LSP6KeyManager/LSP6KeyManager.md

@@ -176,7 +176,7 @@ Same as [`execute`](#execute) but execute a batch of payloads (abi-encoded funct
 
 :::tip Hint
 
-If you are looking to learn how to sign and execute relay transactions via the Key Manager, see our Javascript step by step guide [_"Execute Relay Transactions"_](../../../learn/key-manager/execute-relay-transactions.md). See the LSP6 Standard page for more details on how to [generate a valid signature for Execute Relay Call](../../../standards/universal-profile/lsp6-key-manager.md#how-to-sign-relay-transactions).
+If you are looking to learn how to sign and execute relay transactions via the Key Manager, see our Javascript step by step guide [_"Execute Relay Transactions"_](../../../learn/universal-profile/key-manager/execute-relay-transactions.md). See the LSP6 Standard page for more details on how to [generate a valid signature for Execute Relay Call](../../../standards/universal-profile/lsp6-key-manager.md#how-to-sign-relay-transactions).
 
 :::
 
@@ -657,7 +657,7 @@ Retrieve the permission required to set some AllowedCalls for a controller.
 | ---------------------------------------- | :-------: | ------------------------------------------------------------------------------------------- |
 | `controlledContract`                     | `address` | The address of the ERC725Y contract from which to fetch the value of `dataKey`.             |
 | `dataKey`                                | `bytes32` | A data key ion the format `AddressPermissions:AllowedCalls:<controller-address>`.           |
-| `dataValue`                              |  `bytes`  | The updated value for the `dataKey`. MUST be a bytes32[CompactBytesArray] of Allowed Calls. |
+| `dataValue`                              |  `bytes`  | The updated value for the `dataKey`. MUST be a `bytes[CompactBytesArray]` of Allowed Calls. |
 | `hasBothAddControllerAndEditPermissions` |  `bool`   | -                                                                                           |
 
 #### Returns
@@ -1537,13 +1537,13 @@ error InvalidEncodedAllowedERC725YDataKeys(bytes value, string context);
 
 _Error when reading the Allowed ERC725Y Data Keys. Reason: `context`, Allowed ERC725Y Data Keys value read: `value`._
 
-Reverts when `value` is not encoded properly as a `bytes32[CompactBytesArray]`. The `context` string provides context on when this error occurred (\_e.g: when fetching the `AllowedERC725YDataKeys` to verify the permissions of a controller, or when validating the `AllowedERC725YDataKeys` when setting them for a controller).
+Reverts when `value` is not encoded properly as a `bytes[CompactBytesArray]`. The `context` string provides context on when this error occurred (\_e.g: when fetching the `AllowedERC725YDataKeys` to verify the permissions of a controller, or when validating the `AllowedERC725YDataKeys` when setting them for a controller).
 
 #### Parameters
 
 | Name      |   Type   | Description                                                |
 | --------- | :------: | ---------------------------------------------------------- |
-| `value`   | `bytes`  | The value that is not a valid `bytes32[CompactBytesArray]` |
+| `value`   | `bytes`  | The value that is not a valid `bytes[CompactBytesArray]` |
 | `context` | `string` | A brief description of where the error occurred.           |
 
 <br/>

docs/contracts/deployed-contracts.md

@@ -1,15 +1,15 @@
 ---
-title: ⛓ Deployed Contracts
+title: ⛓ Deployed Base Contracts
 description: List of base implementation and factory contracts addresses deployed on LUKSO Mainnet.
 ---
 
-import { BaseContractsTable, FactoryContractsTable } from "../../src/components/DeployedContractsTable"
+import { BaseContractsTable, FactoryContractsTable } from "@site/src/components/DeployedContractsTable"
 
-# Deployed Contracts on LUKSO Mainnet
+# Deployed Base Contracts on LUKSO Mainnet
 
 :::success Deployment Guides
 
-Check our guide [**_🏭 Deploy Universal Profile + its Key Manager with LSP23 Factory_**](../learn/expert-guides/deploy-up-with-lsp23.md) if you are looking for a script to deploy with the LSP23 Factory using _ethers.js_.
+Check our guide [**_🏭 Deploy Universal Profile + its Key Manager with LSP23 Factory_**](../learn/universal-profile/advanced-guides/deploy-up-with-lsp23.md) if you are looking for a script to deploy with the LSP23 Factory using _ethers.js_.
 
 :::
 

docs/contracts/overview/KeyManager.md

@@ -59,7 +59,7 @@ If controller has `CALL` permission but has no `AllowedCalls`, controller will n
 
 :::
 
-Key Manager allows for restricting controller addresses to be able to call specific functions on specific addresses which should be of a specific standard. In order to achieve such functionallity one could encode a set of type calls, addresses, standards and functions to [`bytes32[CompactBytesArray]`](https://github.com/lukso-network/LIPs/blob/main/LSPs/LSP-2-ERC725YJSONSchema.md#bytesncompactbytesarray), and store them under the [Allowed Calls](../../standards/universal-profile/lsp6-key-manager.md#allowed-calls) data key.
+Key Manager allows for restricting controller addresses to be able to call specific functions on specific addresses which should be of a specific standard. In order to achieve such functionallity one could encode a set of type calls, addresses, standards and functions to [`bytes[CompactBytesArray]`](https://github.com/lukso-network/LIPs/blob/main/LSPs/LSP-2-ERC725YJSONSchema.md#bytesncompactbytesarray), and store them under the [Allowed Calls](../../standards/universal-profile/lsp6-key-manager.md#allowed-calls) data key.
 
 _E.g._
 

docs/faq/network/network-configuration.md

@@ -14,10 +14,12 @@ There are no extra rewards for being very quick. When the appointed time for a v
 
 You can find more information about firewall and port settings within the specifications of the supported blockchain clients:
 
-- [Lighthouse Port Specification](https://lighthouse-book.sigmaprime.io/advanced_networking.html#how-to-open-ports)
-- [Prysm Port Specification](https://docs.prylabs.network/docs/prysm-usage/p2p-host-ip#configure-your-firewall)
 - [Geth Port Specification](https://geth.ethereum.org/docs/fundamentals/security)
 - [Erigon Port Specification](https://github.com/ledgerwatch/erigon#default-ports-and-firewalls)
+- [Nethermind Port Specification](https://docs.nethermind.io/fundamentals/security/#networking-security)
+- [Besu Port Specification](https://besu.hyperledger.org/development/public-networks/how-to/connect/configure-ports)
+- [Prysm Port Specification](https://docs.prylabs.network/docs/prysm-usage/p2p-host-ip#configure-your-firewall)
+- [Lighthouse Port Specification](https://lighthouse-book.sigmaprime.io/advanced_networking.html#how-to-open-ports)
 - [Teku Port Specification](https://docs.teku.consensys.io/how-to/find-and-connect/improve-connectivity)
 
 ## Do the LUKSO mainnet and testnet use different ports?

docs/faq/network/node-setup.md

@@ -1,7 +1,7 @@
 ---
 sidebar_label: 'Node Setup'
 sidebar_position: 4
-description: 'LUKSO node setup and supported clients: Geth, Erigon, Prysm, Lighthouse.'
+description: 'LUKSO node setup and supported clients: Geth, Erigon, Nethermind, Besu, Prysm, Lighthouse, Teku.'
 ---
 
 # Node Setup
@@ -18,10 +18,16 @@ Currently, LUKSO officially supports Geth, Erigon, Lighthouse, and Prysm. All cl
 
 - **[Erigon](https://github.com/ledgerwatch/erigon)** is an Ethereum execution client that aims to offer a more efficient and faster alternative to Geth. It's written in Go and includes several optimizations to reduce the amount of data stored and improve processing speed. However, these optimizations can make Erigon more complex to maintain and update.
 
+- **[Nethermind](https://github.com/NethermindEth/nethermind)** is an Ethereum execution client built on .NET framework and developed by Nethermind. Its plugin system makes it especially easy to configure and use it. Combining this with a very stable runtime, this makes it a great client to use on the network.
+
+- **[Besu](https://github.com/hyperledger/besu)** is an Ethereum execution client written in Java and developed by Hyperledger. It supports both public and private networks, offering features like Proof of Authority and Proof of Work consensus, advanced privacy options, and robust monitoring tools.
+
 - **[Prysm](https://github.com/prysmaticlabs/prysm)** is an Ethereum consensus client written in Go and developed by Prysmatic Labs. Validators widely use it. Performance-wise, Prysm leverages optimized processes and data structures, offering a smooth experience for validators. The client had rigorous testing and auditing processes to ensure the client was secure against potential threats. It also comes with an excellent user-friendly terminal interface.
 
 - **[Lighthouse](https://github.com/sigp/lighthouse)** is an Ethereum consensus client written in Rust and developed by Sigma Prime. From a security perspective, Lighthouse leverages Rust's safety features and undergoes regular security audits to protect against potential vulnerabilities. Regarding efficiency, Lighthouse is designed to perform well even on low-spec hardware, making it accessible to a wide range of users with different skill levels.
 
+- **[Teku](https://github.com/Consensys/teku)** is an Ethereum consensus client written in Java and developed by Consensys. It provides users with a similar experience of running a node as with using other clients, but with additional features, such as external key management (using tools like [Web3signer](https://github.com/Consensys/web3signer)).
+
 ## Should I run an archive or a full node?
 
 A full node downloads the entire blockchain and validates all blocks and transactions against the network's consensus rules. It stores the **current state of the network, including account balances, contracts, storage, and other informatio**n. However, it does not keep all historical states. If you need to check the balance of an account at a specific block height in the past, a full node cannot provide this information directly.
@@ -32,7 +38,13 @@ If you are running a validator, it's the default and recommended option to go wi
 
 ## Can the LUKSO CLI run as an archive node?
 
-By default, the LUKSO CLI is running as a full node. However, you can modify the configuration files and pass any flags to the execution clients by adding the `--geth-[parameter]` or `--erigon-[parameter]` flags to the start command.
+By default, the LUKSO CLI is running as a full node. However, you can modify the configuration files and pass any flags to the clients by adding the `--[client-name]-[parameter]` flags to the start command. For example:
+
+```sh
+--geth-http.addr=localhost # same as running: geth --http.addr=localhost
+--erigon-ws.port=8080 # same as running: erigon --ws.port=8080
+--lighthouse-target-peers=70 # same as running: lighthouse --target-peers=70
+```
 
 ## How much storage does my node need?