Skip to content
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
2 changes: 1 addition & 1 deletion MKDOCS-MARKDOWN-GUIDE.md
Original file line number Diff line number Diff line change
Expand Up @@ -333,7 +333,7 @@ enables displaying a list as a checklist.

For writing code examples inside the documentation, refer to the developer style guides:

- Java : refer to Hyperledger Besu [coding convention](https://github.com/hyperledger/besus/blob/master/CODING-CONVENTIONS.md).
- Java : refer to Hyperledger Besu [coding convention](https://github.com/hyperledger/besu/blob/master/CODING-CONVENTIONS.md).
- JSON : use https://jsonformatter.curiousconcept.com/ to format your JSON code.
- TOML : we follow version 0.5.0 language definition.
- JavaScript : see [Google JavaScript Style Guide](https://google.github.io/styleguide/jsguide.html).
Expand Down
5 changes: 4 additions & 1 deletion docs/Concepts/Privacy/Privacy-Overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,10 @@ Other participants cannot access the transaction content or list of participants

!!! important
For production systems requiring private transactions, we recommend using a network
with a consensus mechanism supporting transaction finality. For example, [IBFT 2.0](../../HowTo/Configure-Besu/Consensus-Protocols/IBFT.md). All private transaction participants must be online for a private transaction to be successfully distributed. If any participants are offline when the private transaction is submitted, the transaction is not attempted and must be resubmitted.
with a consensus mechanism supporting transaction finality. For example, [IBFT 2.0](../../HowTo/Configure/Consensus-Protocols/IBFT.md).
All private transaction participants must be online for a private transaction to be successfully distributed.
If any participants are offline when the private transaction is submitted, the transaction is
not attempted and must be resubmitted.

## Private Transaction Manager

Expand Down
2 changes: 1 addition & 1 deletion docs/HowTo/Interact/APIs/GraphQL.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ description: How to access the Hyperledger Besu API using GraphQL
GraphQL can reduce the overhead needed for common queries. For example, instead of querying each receipt in a
block, GraphQL can obtain the same result with a single query for the entire block.

The GraphQL implementation for Ethereum is described in the [schema](https://github.com/hyperledger/besu/blob/master/ethereum/graphql/src/main/resources/schema.graphqls).
The GraphQL implementation for Ethereum is described in the [schema](https://github.com/hyperledger/besu/blob/master/ethereum/api/src/main/resources/schema.graphqls).
The GraphQL service is enabled using the [command line options](API.md#enabling-api-access).

!!! note
Expand Down
2 changes: 1 addition & 1 deletion docs/Reference/API-Methods.md
Original file line number Diff line number Diff line change
Expand Up @@ -479,7 +479,7 @@ None

!!! note
Methods with an equivalent [GraphQL](../HowTo/Interact/APIs/GraphQL.md) query include a GraphQL request and result in the method example.
The parameter and result descriptions apply to the JSON-RPC requests. The GraphQL specification is defined in the [schema](https://github.com/hyperledger/besu/blob/master/ethereum/graphql/src/main/resources/schema.graphqls).
The parameter and result descriptions apply to the JSON-RPC requests. The GraphQL specification is defined in the [schema](https://github.com/hyperledger/besu/blob/master/ethereum/api/src/main/resources/schema.graphqls).

### eth_syncing

Expand Down