Updated 2019-10-30
Using Hyperledger Besu-extended Privacy
Hyperledger Besu provides an extended implementation of privacy by allowing a privacy group to be created for a set of participants. The privacy group ID must be specified when sending private transactions.
Using the --rpc-http-api
or --rpc-ws-api
command line options enable:
Use priv_createPrivacyGroup
to
create the privacy group containing the recipients of the private transaction.
Specify privacyGroupId
when creating the signed transaction passed as an input parameter to eea_sendRawTransaction
to create an EEA-compliant private transaction.
Note
Support for specifying privacyGroupId
when using eea_sendTransaction
with EthSigner will be available in
a future EthSigner release.
Privacy Group Type
Privacy groups created using priv_createPrivacyGroup
are identified as type BESU
when returned by priv_findPrivacyGroup
.
Example
{ "jsonrpc": "2.0", "id": 1, "result": [ { "privacyGroupId": "GpK3ErNO0xF27T0sevgkJ3+4qk9Z+E3HtXYxcKIBKX8=", "name": "Group B", "description": "Description of Group B", "type": "BESU", "members": [ "negmDcN2P4ODpqn/6WkJ02zT/0w0bjhGpkZ8UP6vARk=", "g59BmTeJIn7HIcnq8VQWgyh/pDbvbt2eyP0Ii60aDDw=" ] } ] }