CipherLabs
/
besu
mirror of https://github.com/hyperledger/besu
2
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
An enterprise-grade Java-based, Apache 2.0 licensed Ethereum client https://wiki.hyperledger.org/display/besu
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
1443 Commits
44 Branches
214 Tags
200 MiB
 
 
Tag: Branch: Tree: 1d59f90486
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '1d59f90486'
${ noResults }
besu/docs/Privacy/How-To/EEA-Compliant.md

1.6 KiB
Raw Blame History

description: JSON-RPC methods to use for EEA-compliant privacy

Using EEA-compliant Privacy

When using EEA-compliant privacy, the group of nodes specified by privateFromand privateFor form a privacy group and are given a unique privacy group ID by Orion.

Enable the EEA API methods using the --rpc-http-api or --rpc-ws-api command line options.

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

Privacy Group Type

Privacy groups created when specifying privateFrom and privateFor are identified as type LEGACY when returned by priv_findPrivacyGroup.

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