Method ID caching and common-lookups
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 184
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 4
Description
### Overview
Ape is pretty cool in that it caches and auto-fetches contract types which help identify transaction methods-called.
However, it could be better.
Cache method IDs individually.
Benefits:
1. Works even when ape-etherscan is not installed
2. Faster - don't need to always look up a contract to know the name of the method (if the name of the method is all you need)
there are probably more benefits too
### Specification
* ship with common method IDs out the gate
* add new ones to the cache
* utilize the lookups anywhere, such as in tracing when we couldnt get a contract type/name but we still have the method id bytes
### Dependencies
Include links to any open issues that must be resolved before this feature can be implemented.
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by locating the existing contract-type and method-ID lookup paths, including tracing, then determine how common IDs and newly discovered IDs should be cached. Done means lookups work without ape-etherscan where possible and tracing can use a method ID when no contract type or name is available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- blockchain, devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100