Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Node should handle eth_sendRawPrivateTransaction #392

Open
1 task
dolanor opened this issue Oct 20, 2021 · 0 comments
Open
1 task

Node should handle eth_sendRawPrivateTransaction #392

dolanor opened this issue Oct 20, 2021 · 0 comments
Milestone

Comments

@dolanor
Copy link
Contributor

dolanor commented Oct 20, 2021

Summary / User Story

eth_sendRawPrivateTransaction is used in goquorum to send initially preprocessed transaction (already signed, etc). They need to be exposed on the nodes interface so goquorum clients could send those kind of transaction.
As the transaction are pre-signed, they have to figure out aliases on their own if any. Therefore, no alias interpretation needs to be done for it.
Otherwise, goquorum uses eth_sendTransaction to send transactions, and based on private args, it will reroute to the private way.
Contrary to besu who would use eth_sendPrivateTransaction explicitely to send private transactions.

Business Value

It's needed for certain scenario (signing transaction with an external wallet)

Acceptance Criteria

  • QKM should expose a way to use a eth_sendRawPrivateTransaction directly that would be forwarded to the node.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants