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.

Updated on September 24, 2020

Using EEA-compliant privacy

When using Hyperledger Besu EEA-compliant privacy, the group of nodes specified by privateFrom and privateFor form a privacy group, to which Orion assigns a unique privacy group ID.

To enable the EEA API methods, use the --rpc-http-api or --rpc-ws-api command line options.

To create an EEA-compliant private transaction, specify privateFor when creating the signed transaction passed as an input parameter to eea_sendRawTransaction.

Privacy group type

Privacy groups created when specifying privateFrom and privateFor have a LEGACY privacy group type when returned by priv_findPrivacyGroup.

Example

{
    "jsonrpc": "2.0",
    "id": 1,
    "result": [
      {
         "privacyGroupId": "68/Cq0mVjB8FbXDLE1tbDRAvD/srluIok137uFOaClM=",
         "name": "legacy",
         "description": "Privacy groups to support the creation of groups by privateFor and privateFrom",
         "type": "LEGACY",
         "members": [
            "g59BmTeJIn7HIcnq8VQWgyh/pDbvbt2eyP0Ii60aDDw=",
            "negmDcN2P4ODpqn/6WkJ02zT/0w0bjhGpkZ8UP6vARk="
         ]
      }
    ]
}
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