-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Open
Labels
C-castCommand: castCommand: castT-featureType: featureType: featurefirst issueA good way to start contributingA good way to start contributing
Description
Component
Cast
Describe the feature you would like
for reference, this is what i wish to achieve using foundry tools
https://medium.com/@LucasJennings/a-step-by-step-guide-to-generating-raw-ethereum-transactions-c3292ad36ab4
Thanks to the newly introduced --raw-unsigned
flag, I am able to create a raw RLP transaction, hash it and sign it using cast wallet sign
what is left is to be able to use the signature to create a new RLP transaction, which now includes the created signature using cast mktx
to create a raw ethereum transaction
As per the medium article reference, Step 4 is to be tackled.
Hope this was enough information, let me know if this is feasable
Thanks
Additional context
No response
Metadata
Metadata
Assignees
Labels
C-castCommand: castCommand: castT-featureType: featureType: featurefirst issueA good way to start contributingA good way to start contributing
Type
Projects
Status
Todo
Activity
AdvayAgrawal commentedon Mar 25, 2025
hi @zerosnacks. Is this feature feasible?
zerosnacks commentedon Mar 25, 2025
Yes it is, we've marked it as a good first issue
cc @yash-atreya
[-]Feature request: Add field in `cast mktx --raw-unsigned` to accept signatures to build an ethereum transaction[/-][+]feat(`cast mktx --raw-unsigned`): add way to accept signatures to build an ethereum transaction[/+][-]feat(`cast mktx --raw-unsigned`): add way to accept signatures to build an ethereum transaction[/-][+]feat(`cast mktx --raw-unsigned`): add way to accept signatures to build a transaction[/+]AdvayAgrawal commentedon Mar 25, 2025
great, glad to hear that. Thanks @zerosnacks
A-y-ush commentedon Mar 26, 2025
Hi, @zerosnacks is this issue available to work on?
I wanna know if I understand the problem correctly
When we create an unsigned transaction using the
cast mktx
command without the--raw-unsigned
flag, the transaction is EIP-2718 encoded. During this time, it gets both signed and encoded.But in the case of using the
--raw-unsigned
flag, the transaction misses the step of RLP encoding too along with the signing part.Am I understanding this correct?
AdvayAgrawal commentedon Apr 21, 2025
hi @zerosnacks @yash-atreya ,
Just wanted to know an update on this, has this issue been resolved, or is there a linked PR?
yash-atreya commentedon Apr 21, 2025
Hey, would you like to submit a PR for this?
4 remaining items