crypto-com / crypto-com/chain-indexing
Problem: missing signer parser for MsgEthereumTx
- Dominant language
- Go
- Stars
- 34
- Forks
- 32
- PR merge metrics
- No merged PRs in 30d
Description
The Signer of `MsgEthereumTx` should be the `from` address. However, a valid `MsgEthereumTx` should have an empty `from` address in Tx Messages, possibly deprecated in `LegacyTx` (Ref: https://github.com/evmos/ethermint/blob/main/x/evm/types/msg.go#L364).
The code shows that `ValidateBasic` function in `Ethermint` is not empty and it could be a good starting point (Ref: https://github.com/evmos/ethermint/blob/main/x/evm/types/msg.go#L165).
Contributor guide
No contributing guide indexed for this repository
Research direction
Read Ethermint's x/evm/types/msg.go, starting with ValidateBasic and the referenced LegacyTx section. Trace the chain-indexing entry point for MsgEthereumTx signer parsing, then verify that valid transaction messages retain an empty from address while the signer resolves it correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100