You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is not brainstorming ideas. If you have an idea you'd like to discuss, please open a new discussion on the lotus forum and select the category as Ideas.
I have a specific, actionable, and well motivated feature request to propose.
Lotus component
lotus daemon - chain sync
lotus fvm/fevm - Lotus FVM and FEVM interactions
lotus miner/worker - sealing
lotus miner - proving(WindowPoSt/WinningPoSt)
lotus JSON-RPC API
lotus message management (mpool)
Other
What is the motivation behind this feature request? Is your feature request related to a problem? Please describe.
This issue has been created to add support for legacy transactions to Filecoin so that contracts and user transactions are not scoped to a specific chain. Specifically, this issue tracks FIP discussion at filecoin-project/FIPs#962.
"We could also prepend a transaction type byte to the signature field (for Ethereum transactions only). IMO, this is the best solution, but it may break any tooling manually signing/validating messages from Ethereum accounts. On the other hand, I'm doubtful any tooling like this exists, so we're probably fine."
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Just to clarify, when we support legacy transactions - do we mean
Transactions without Chain ID OR
Transactions without ChainID AND without any of the EIP-1599 gas stuff params ?
Hm. It's going to have to be the latter, I think (needs to be bit for bit compatible). I think we need to set the GasPremium to GasFeeCap when translating from the EthTxn to the Filecoin message.
aarshkshah1992
changed the title
Filecoin should support legacy Ethereum transactions
Filecoin should support legacy Homstead and legacy EIP-155 Ethereum transactions
May 6, 2024
Checklist
Ideas
.Lotus component
What is the motivation behind this feature request? Is your feature request related to a problem? Please describe.
This issue has been created to add support for legacy transactions to Filecoin so that contracts and user transactions are not scoped to a specific chain. Specifically, this issue tracks FIP discussion at filecoin-project/FIPs#962.
Describe the solution you'd like
Option #3 on filecoin-project/FIPs#962
"We could also prepend a transaction type byte to the signature field (for Ethereum transactions only). IMO, this is the best solution, but it may break any tooling manually signing/validating messages from Ethereum accounts. On the other hand, I'm doubtful any tooling like this exists, so we're probably fine."
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: