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/Explanation/Privacy-Overview.md

2.6 KiB
Raw Blame History

description: Privacy

Privacy

Privacy in Pantheon refers to the ability to keep transactions private between the involved parties. Other parties cannot access the transaction content, sending party, or list of participating parties.

!!! important For production systems requiring private transactions, we recommend using a network with a consensus mechanism supporting transaction finality. For example, IBFT 2.0.

Private Transaction Manager

Pantheon uses a Private Transaction Manager to implement privacy. For example, Orion.
Each Pantheon node that sends or receives private transactions requires an associated Orion node.

Orion Nodes

Private transactions are passed from the Pantheon node to the associated Orion node. The Orion node encrypts and directly distributes (that is, point to point) the private transaction to Orion nodes participating in the transaction.

!!! tip Private Transaction Managers are also known as Enclaves.

Private Transaction Attributes

Private transactions have additional attributes to public Ethereum transactions:

  • privateFrom - Orion public key of transaction sender

  • privateFor - Orion public keys of transaction recipients or privacyGroupId - Privacy group to receive transaction

  • restriction - Private transactions are restricted or unrestricted:

    • In restricted private transactions the payload of the private transaction is received and stored only by the nodes participating in the transaction.

    • In unrestricted private transactions the payload of the private transaction is transmitted to all nodes in the network but is readable only by nodes participating in the transaction.

    !!! important Pantheon implements restricted private transactions only.

Pantheon and Orion Keys

Pantheon and Orion nodes both have public/private key pairs identifying them. The private transaction submitted from the Pantheon node to the Orion node is signed with the Pantheon node private key. The privateFrom and privateFor attributes specified in the RLP-encoded transaction string for eea_sendRawTransaction are the public keys of the Orion nodes sending and receiving the transaction.

!!! important The mapping of Pantheon node addresses to Orion node public keys is off-chain. That is, the sender of a private transaction must know the Orion node public key of the recipient.