Closed aion-kelvin closed 5 years ago
@JayT106 can we get resolution and someone assigned to this task?
Also just to confirm:
This is not part of the Ethereum JSON-RPC spec, but an assumption in web3.js 1.0. We've made the decision for maximum compatibility with existing web3 features, so will be implementing this.
@kzeine candidate for bounty
Issue Status: 1. Open 2. Started 3. Submitted 4. Done
This issue now has a funding of 205.0 AION (87.53 USD @ $0.43/AION) attached to it as part of the Aion Foundation fund.
Issue Status: 1. Open 2. Started 3. Submitted 4. Done
Work has been started.
These users each claimed they can complete the work by 2 weeks, 6 days from now. Please review their action plans below:
1) satran004 has been approved to start work.
Hi, I have looked into the issue and went through the codebase. I plan to start working on this issue.
Planned Steps:
Introduce a new method "eth_signTransaction" in ApiWeb3Aion.java Add a mapping for the new method in RpcMethods.java Write the test for new method. Verify test case. Test from web3 js console.
Questions / Clarification:
My expectation for method parameters are as follows: Please verify.
If _params is an array -> First elemenent is a txn object, Second element is an address as string. If _params is an JSON Object -> the method will look for "transaction" and "address" attribute in the json object.
Please also verify the following: If the address argument is empty or null, txn.getFrom() will be used to sign the transaction.
Thanks.
Learn more on the Gitcoin Issue Details page.
@satran004 Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!
Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days
I have started working on this enhancement.
Issue Status: 1. Open 2. Started 3. Submitted 4. Done
Work for 205.0 AION (87.02 USD @ $0.42/AION) has been submitted by:
@kzeine please take a look at the submitted work:
Issue Status: 1. Open 2. Started 3. Submitted 4. Done
The funding of 205.0 AION (87.02 USD @ $0.42/AION) attached to this issue has been approved & issued to @satran004.
Updated by @qoire and @kzeine :
Introduction
The Web3 1.0 has a method named
eth.signTransaction
, that calls an RPC method namedeth_signTransaction
.eth_signTransaction
is not implemented in the kernel. The purpose of it is to ask the kernel to sign a given transaction, but not send it (unlikeeth_sendTransaction
), so that the client can have the signed transaction to send at a later time (viaeth_sendRawTranaction
).Current situation
This feature is missing in the current Aion implementation. The following error occurs: Web3 1.0 JS invocation:
Log from kernel:
Task Description
We're asking for contributors to implement this feature for https://github.com/aionnetwork/aion. Correct implementation should receive a transaction, sign it, and return the signed transaction as described here: https://web3js.readthedocs.io/en/1.0/web3-eth.html#signtransaction.
Acceptance Criteria
Required Skill
Participants needs to have experience in Java software development, and have basic knowledge about blockchain system. Participants might need to read Ethereum's documentation to understand the task.
Guidance
Technical support is available through Gitter.
Original post:
Before filing a new issue, please provide the following information.
Your issue description goes here below. Try to include actual vs. expected behavior and steps to reproduce the issue.
The Web3 1.0 has a method named
eth.signTransaction
, that calls an RPC method namedeth_signTransaction
.eth_signTransaction
is not implemented in the kernel. The purpose of it is to ask the kernel to sign a given transaction, but not send it (unlikeeth_sendTransaction
), so that the client can have the signed transaction to send at a later time (viaeth_sendRawTranaction
).Since there's still other ways to send transaction or sign transactions, this isn't very high priority, just making an issue to keep track of it
Web3 1.0 JS invocation:
Log from kernel: