Skip to main content

Use EEA-compliant privacy (Deprecated)

caution

Tessera-based privacy is deprecated in Besu version 24.12.0 and later. Please read this blog post for more context on the rationale behind this decision as well as alternative options.

When using Besu EEA-compliant privacy, the group of nodes specified by privateFrom and privateFor form a privacy group, to which Tessera 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.

{
  "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="
      ]
    }
  ]
}