Skip to content
You are reading Pantheon 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.

Using Pantheon-extended Privacy

Pantheon 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 PANTHEON 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": "PANTHEON",
       "members": [
         "negmDcN2P4ODpqn/6WkJ02zT/0w0bjhGpkZ8UP6vARk=",
         "g59BmTeJIn7HIcnq8VQWgyh/pDbvbt2eyP0Ii60aDDw="
       ]
     }
  ]
}
Questions or feedback? You can discuss issues and obtain free support on Pantheon Gitter channel.
For paid professional support by PegaSys, contact us at [email protected]