Private transactions have additional attributes to public Ethereum transactions:
privateFrom- The Orion public key of the transaction sender
privateFor- The Orion public keys of the transaction recipients, or
privacyGroupId- The privacy group to receive the transaction
restriction- Whether the private transaction is
restrictedprivate transactions, only the nodes participating in the transaction receive and store the payload of the private transaction.
unrestrictedprivate transactions, all nodes in the network receive the payload of the private transaction, but only the nodes participating in the transaction can read the transaction.
restrictedprivate transactions only.
For more information about creating and sending private transactions, see the How To documentation.
Besu and Orion keys
Besu and Orion nodes both have public/private key pairs identifying them. A Besu node sending a
private transaction to an Orion node signs the transaction with the Besu node private key. The
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.
The mapping of Besu 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.