hyperledger/besu 1.4.5

on GitHub

Breaking change upcoming in v1.5

To maintain best security practices, we're changing the user:group on the Docker container to besu.

What this means for you:

• If you are running Besu as a binary, there is no impact.
• If you are running Besu as a Docker container and have a volume mount for data, ensure that the
  permissions on the directory allow other users and groups to r/w. Ideally this should be set to
  besu:besu as the owner.

Note that the besu user only exists within the container not outside it. The same user ID may match
a different user outside the image.

If you’re mounting local folders, it is best to set the user via the Docker —user argument. Use the
UID because the username may not exist inside the docker container. Ensure the directory being mounted
is owned by that user.

Upcoming 1.5 release

The 1.5 release is scheduled for early July.

1.4.5

Additions and Improvements

• Implemented WebSocket logs subscription for private contracts (priv_subscribe/priv_unsubscribe) [#762]
• Introduced SecurityModule plugin API. This allows use of a different security module as a plugin to
  provide cryptographic function that can be used by NodeKey (such as sign, ECDHKeyAgreement etc.). KeyPairSecurityModule
  is registered and used by default. The CLI option --security-module=<name> (defaults to localfile) can be used
  to identify the security module plugin name to use instead. #713
• Several testing related changes to improve compatibility with Hive and Retesteth.
  #806 and #845
• Native libraries for secp256k1 and Altbn128 encryption are enabled by default. To disable these libraries use
  --Xsecp256k1-native-enabled=false and --Xaltbn128-native-enabled=false. #775

Bug Fixes

• Fixed eth_estimateGas JSON RPC so it no longer returns gas estimates that are too low. #842
• Full help not displayed unless explicitly requested. #437
• Compatibility with undocumented Geth eth_subscribe fields. #654
• Current block number included as part of eth_getWork response. #849

Known Issues

Known issues are open issues categorized as Very High or High impact.

New known issues

• Scope of logs query causing Besu to crash. #944

Workaround - Limit the number of blocks queried by each eth_getLogs call.

Previously identified known issues

• Intrinsic gas exceeds gas limit returned when calling delete mapping[addr] or mapping[addr] = 0
• Eth/65 not backwards compatible
• Error full syncing with pruning
• Fast sync when running Besu on cloud providers
• Bootnodes must be validators when using onchain permissioning
• Privacy users with private transactions created using v1.3.4 or earlier