Skip to content
You are reading Hyperledger Besu development version documentation and some displayed features may not be available in the stable release. You can switch to stable version using the version box at screen bottom.
Date of last update: August 18, 2022

Private transaction processing

Warning

Orion features have been merged into Tessera! Read our Orion to Tessera migration guide and about all the new Tessera features.

Processing private transactions involves the following:

Private transaction processing is illustrated and described in the following diagram.

Processing Private Transactions

  1. Submit a private transaction using eea_sendRawTransaction. The signed transaction includes transaction parameters specific to private transactions, including:

    • privateFor or privacyGroupId, which specifies the list of recipients.
    • privateFrom, which specifies the sender.
    • restriction, which specifies the transaction is restricted to the transaction participants.
  2. The JSON-RPC endpoint passes the private transaction to the Private Transaction Handler.

  3. The Private Transaction Handler sends the private transaction to Tessera.

  4. Tessera distributes the private transaction directly (that is, point-to-point) to the Tessera nodes specified in privateFor or belonging to the privacy group identified by privacyGroupId. All recipient Tessera nodes store the transaction. Tessera associates the stored transaction with the transaction hash and privacy group ID.

  5. Tessera returns the transaction hash to the Private Transaction Handler.

  6. The Private Transaction Handler creates a PMT for the private transaction. The Private Transaction Handler propagates the PMT using devP2P in the same way as any other public Ethereum transaction.

    Tip

    If you want to sign the PMT outside of Besu, use priv_distributeRawTransaction instead of eea_sendRawTransaction.

  7. Besu mines the PMT into a block and the PMT is distributed to all Ethereum nodes in the network.

  8. The Mainnet Transaction Processor processes the PMT in the same way as any other public transaction. On nodes containing the privacy precompile contract specified in the to attribute of the PMT, the Mainnet Transaction Processor passes the PMT to the privacy precompile contract.

    Note

    Nodes receiving the PMT that don’t contain the privacy precompile contract ignore the PMT.

  9. The privacy precompile contract queries Tessera for the private transaction and privacy group ID using the transaction hash.

  10. The privacy precompile contract passes the private transaction to the Private Transaction Processor. The privacy group ID specifies the private world state to use.

  11. The Private Transaction Processor executes the transaction. The Private Transaction Processor can read and write to the private world state, and read from the public world state.

Important

Using private transactions with pruning or fast sync is not supported.