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.
Last update: April 6, 2021

Signing privacy marker transactions

You can sign privacy marker transactions with either a random key or a specified key. To sign privacy marker transactions with a specified private key, use --privacy-marker-transaction-signing-key-file when starting Hyperledger Besu.

In networks where you pay gas, you must specify a key and the associated account must contain adequate funds.

In free gas networks, to provide further anonymity by signing each privacy marker transaction with a different random key, exclude the --privacy-marker-transaction-signing-key-file command line option when starting Besu.

Using account permissioning and privacy

You cannot use Account permissioning with random key signing.

If using account permissioning and privacy, a signing key must be specified using the --privacy-marker-transaction-signing-key-file command line option and the corresponding public key included in the accounts allowlist.

Note

Besu signs privacy marker transactions during the private transaction process.

Questions or feedback? You can discuss issues and obtain free support on Hyperledger Besu chat channel.
For Hyperledger Besu community support, contact the mailing list besu@lists.hyperledger.org