Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix broken links #1673

Merged
merged 2 commits into from
Aug 20, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -94,8 +94,6 @@ You can manage private nonces in multiple ways:

:::

- Use [Orchestrate](https://docs.orchestrate.consensys.net/en/stable/) for nonce management. We recommend this for enterprise use.

:::tip

The [web3js-quorum library includes an example](https://github.com/ConsenSys/web3js-quorum/blob/9a0f9eb1b91a4a0d93801f77782b509ae2e7314c/example/concurrentPrivateTransactions/concurrentPrivateTransactions.js) of nonce management when [sending concurrent private transactions](../../../how-to/send-transactions/concurrent-private-transactions.md). The example calculates the correct nonces for the private transactions and PMTs outside of Besu.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -40,11 +40,11 @@ When distributing a new private transaction between Tessera nodes, the overall t

Management of public and private nonces in web3js-quorum is stateless: before a transaction is sent, web3js-quorum has to query for those nonces. This is increasing latency, the node's load, and is a source of fragility due to nonce collision when multiple senders try to use the same account concurrently.

For performance and reliability it is advantageous to manage nonces in a stateful manner on the client side instead of querying them for every transaction. If custom code for this is not an option, [Orchestrate](https://consensys.net/codefi/orchestrate/) can be used.
For performance and reliability it is advantageous to manage nonces in a stateful manner on the client side instead of querying them for every transaction.

### Use random senders for privacy marker transactions

To avoid public nonce management, privacy marker transactions can be sent using a [random account per transaction](https://besu.hyperledger.org/en/stable/Reference/CLI/CLI-Syntax/#privacy-marker-transaction-signing-key-file). This option is only available for zero gas networks.
To avoid public nonce management, privacy marker transactions can be sent using a [random account per transaction](../../../private-networks/reference/cli/options.md#privacy-marker-transaction-signing-key-file). This option is only available for zero gas networks.

### Avoid queuing transactions in Tessera

Expand Down
2 changes: 1 addition & 1 deletion docs/private-networks/tutorials/privacy/quickstart.md
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@ To create the docker-compose file and artifacts, run:
npx quorum-dev-quickstart
```

Follow the prompts displayed to run Hyperledger Besu, private transactions, and [logging with ELK](../../how-to/monitor/elastic-stack.md). Enter `n` for [Codefi Orchestrate](https://docs.orchestrate.consensys.net/en/stable/).
Follow the prompts displayed to run Hyperledger Besu, private transactions, and [logging with ELK](../../how-to/monitor/elastic-stack.md). Enter `n` for Codefi Orchestrate.

### 2. Start the network

Expand Down
2 changes: 1 addition & 1 deletion docs/private-networks/tutorials/quickstart.md
Original file line number Diff line number Diff line change
Expand Up @@ -51,7 +51,7 @@ To create the tutorial `docker-compose` files and artifacts, run:
npx quorum-dev-quickstart
```

Follow the prompts displayed to run Hyperledger Besu and [logging with ELK](../how-to/monitor/elastic-stack.md). Enter `n` for [Codefi Orchestrate](https://docs.orchestrate.consensys.net/en/stable/) and [private transactions](../concepts/privacy/index.md).
Follow the prompts displayed to run Hyperledger Besu and [logging with ELK](../how-to/monitor/elastic-stack.md). Enter `n` for Codefi Orchestrate and [private transactions](../concepts/privacy/index.md).

:::note

Expand Down
2 changes: 1 addition & 1 deletion docs/public-networks/how-to/bonsai-limit-trie-logs.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ import TabItem from '@theme/TabItem';

# Reduce storage for Bonsai Tries

When using the [Bonsai Tries](../concepts/data-storage-formats#bonsai-tries) data storage format,
When using the [Bonsai Tries](../concepts/data-storage-formats.md#bonsai-tries) data storage format,
[`--bonsai-limit-trie-logs-enabled`](../reference/cli/options.md#bonsai-limit-trie-logs-enabled) is
enabled by default.
When enabled, this feature can reduce database growth by more than 3 GB each week on Mainnet.
Expand Down
4 changes: 2 additions & 2 deletions docs/public-networks/how-to/use-besu-api/authenticate.md
Original file line number Diff line number Diff line change
Expand Up @@ -171,9 +171,9 @@ The [key algorithm](https://datatracker.ietf.org/doc/html/rfc7518#section-3.1) c

The default value for Besu is `RS256`.
When you use a different key algorithm, you must specify the
[`--rcp-http-authentication-jwt-algorithm`](../../reference/cli/options#rpc-http-authentication-jwt-algorithm)
[`--rcp-http-authentication-jwt-algorithm`](../../reference/cli/options.md#rpc-http-authentication-jwt-algorithm)
option and/or the
[`--rcp-ws-authentication-jwt-algorithm`](../../reference/cli/options#rpc-ws-authentication-jwt-algorithm)
[`--rcp-ws-authentication-jwt-algorithm`](../../reference/cli/options.md#rpc-ws-authentication-jwt-algorithm)
option depending on your needs.

<Tabs>
Expand Down
10 changes: 1 addition & 9 deletions docs/public-networks/how-to/use-pow/mining.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ Hyperledger Besu supports CPU and GPU mining, which are configured using command

GPU mining tests used [Ethminer](https://github.com/ethereum-mining/ethminer) with the `stratum+tcp` and `getwork` schemes.

Ethminer has been used with Hyperledger Besu to mine blocks on the [Ropsten testnet](https://ropsten.etherscan.io/address/0x2f14582947E292a2eCd20C430B46f2d27CFE213c#mine), [ETC Mainnet (uncle block only)](https://etc.tokenview.com/en/uncleblock/10555173) and Mordor ETC testnet.
Ethminer has been used with Hyperledger Besu to mine blocks on the Ropsten testnet, ETC Mainnet (uncle block only) and Mordor ETC testnet.

:::note
- Some mining software supports the `getwork` scheme as the `http` scheme.
Expand Down Expand Up @@ -71,14 +71,6 @@ The JSON-RPC API methods for mining are:
- [`eth_getWork`](../../reference/api/index.md#eth_getwork) to get the hash of the current block, the seed hash, and the target boundary condition. Only used when using the `getwork` scheme.
- [`eth_submitWork`](../../reference/api/index.md#eth_submitwork) to submit the PoW solution. Only used when using the `getwork` scheme.

## Besu mined blocks

Besu has successfully mined blocks on the Ropsten testnet, ETC Mainnet (uncle block only) and Mordor ETC testnet. Blocks mined by the Hyperledger Besu team contain the version number used in the block's `extraData` field. The following accounts have been used to mine on public networks with Hyperledger Besu:

- **Ropsten**: [`0x2f14582947E292a2eCd20C430B46f2d27CFE213c`](https://ropsten.etherscan.io/address/0x2f14582947E292a2eCd20C430B46f2d27CFE213c#mine)
- **ETC**: [`0x3125309aa670f5e60493b50884a7e7abf9ebb701`](https://etc.tokenview.com/en/address/0x3125309aa670f5e60493b50884a7e7abf9ebb701)
- **Mordor**: `0x2f14582947E292a2eCd20C430B46f2d27CFE213c`

## Troubleshoot

### Check block creation
Expand Down
2 changes: 1 addition & 1 deletion docs/public-networks/reference/genesis-items.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ Network configuration items are specified in the genesis file in the `config` ob
| `ecCurve` | Specifies [the elliptic curve to use](../../private-networks/how-to/configure/curves.md). Default is `secp256k1`. |
| `discovery` | Specifies [discovery configuration items](#discovery-configuration-items). The `discovery` object can be left empty. |
| `zeroBaseFee` | Specifies a base fee of `0` for [free gas networks](../../private-networks/how-to/configure/free-gas.md#4-enable-zero-base-fee-if-using-london-fork-or-later). |
| `fixedBaseFee` | Specifies a constant base fee for blocks, overriding the dynamic base fee calculation of [EIP-1559](../concepts/transactions/types#eip1559-transactions). |
| `fixedBaseFee` | Specifies a constant base fee for blocks, overriding the dynamic base fee calculation of [EIP-1559](../concepts/transactions/types.md#eip1559-transactions). |

## Genesis block parameters

Expand Down
Loading