[PAN-3139] Add privDistributeRawTransaction endpoint #23
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Joshua Richardson <[email protected]>
Signed-off-by: Joshua Richardson <[email protected]>
Signed-off-by: Joshua Richardson <[email protected]>
Signed-off-by: Joshua Richardson <[email protected]>
josh-richardson
force-pushed
the
pan-3139
branch
from
2fcfeae to
f882eff
Compare
Signed-off-by: Joshua Richardson <[email protected]>
Signed-off-by: Joshua Richardson <[email protected]>
.../hyperledger/besu/ethereum/api/jsonrpc/internal/privacy/methods/AbstractSendTransaction.java
Outdated
Show resolved
Hide resolved
...esu/ethereum/api/jsonrpc/internal/privacy/methods/priv/PrivDistributeRawTransactionTest.java
Outdated
Show resolved
Hide resolved
Signed-off-by: Joshua Richardson <[email protected]>
Signed-off-by: Joshua Richardson <[email protected]>
Signed-off-by: Joshua Richardson <[email protected]>
edwardmack
added a commit
that referenced
this pull request
Feb 20, 2020
* Update SLOAD_GAS cost to 200 in Aztlan Gas Calculator Change SLOAD_GAS cost in Aztlan Gas Calculator from 800 to 200 and update functions that use SLOAD_GAS. Signed-off-by: edwardmack <[email protected]> * Update SLOAD_GAS cost to 200 in Aztlan Gas Calculator Change SLOAD_GAS cost in Aztlan Gas Calculator from 800 to 200 and update functions that use SLOAD_GAS. Signed-off-by: edwardmack <[email protected]> Signed-off-by: Edward Mack <[email protected]> * remove overrides removed overrides of calculateStorageCost and calculateStorageRefundAmount in AztlanGasCalculator because these were causing aztlan fork not to sync with kotti testnet. Signed-off-by: Edward Mack <[email protected]> * merge Signed-off-by: Edward Mack <[email protected]>
garyschulte
pushed a commit
to garyschulte/besu
that referenced
this pull request
Jan 5, 2024
store acceptance test results
fab-10
added a commit
to fab-10/besu
that referenced
this pull request
Jan 10, 2024
Signed-off-by: Fabio Di Fabio <[email protected]>
fab-10
added a commit
to fab-10/besu
that referenced
this pull request
Jan 10, 2024
Signed-off-by: Fabio Di Fabio <[email protected]>
siladu
pushed a commit
to siladu/besu
that referenced
this pull request
Oct 28, 2024
* split spec into multiple files * update readme to new assembled spec
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR description
As a user I want to be able to submit and sign my private transaction and my privacy marker transaction separately. This allows finer grained control over where the signing keys are stored and the signing is done for each transaction.
Add priv_distributeRawTransaction endpoint. This endpoint will pass the private transaction to Orion to encrypt and distribute to all participants
Parameters - signed, RLP-encoded private transaction as for eea_sendRawTransaction. privateFor is either a list of Orion public keys or privacy group ID
Returns - Private Transaction hash when private transaction successfully distributed to all participants. Otherwise returns an error.
This is steps 1 - 5 on this diagram (eea_sendRawTransaction would be priv_distributeRawTransaction) - https://docs.pantheon.pegasys.tech/en/latest/Concepts/Privacy/Private-Transaction-Processing/
Note: This endpoint is in addition to not replacing eea_sendRawTransaction.