Improve visual sequence output of corpus files in `SolCalldata` format
- Dominant language
- Haskell
- Stars
- 3.2k
- Forks
- 432
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 5
Description
### Describe the desired feature
Example corpus file:
```
[
{
"call": {
"tag": "SolCalldata",
"contents": "\"\\227\\147\\216k\\0\\0\\0\\0\\0\\0\\0\\0\\0\\0\\0\\0\\0\\0\\0\\0\\0\\0\\0\\0\\0\\0\\0\\0\\0\\0\\0\\0\\0\\0\\0R\\255\\255\\255\\255\\255\\255\\255\\255\\255\\255\\255\\255\\255\\255\\255\\255\\255\\255\\255\\255\\255\\255\\255\\255\\255\\255\\255\\255\\255\\255\\255\\254\""
},
"src": "0x0000000000000000000000000000000000020000",
"dst": "0x00a329c0648769a73afac7f9381e08fb43dbea72",
"gas": 12500000,
"gasprice": "0x0000000000000000000000000000000000000000000000000000000000000001",
"value": "0x0000000000000000000000000000000000000000000000000000000000000000",
"delay": [
"0x000000000000000000000000000000000000000000000000000000000000005f",
"0x0000000000000000000000000000000000000000000000000000000000000028"
]
}
]
```
Current output:
Expected output:
Full ABI information containing function signature, etc.
Contributor guide
Research direction
Start with the example corpus in the issue and compare its current visual output with the requested output. Find where sequence visualization handles the `SolCalldata` format, then trace what ABI information is available there; done means the visualization shows the full ABI information, including the function signature.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell, solidity
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100