Consider precompiles for creation verification
- Dominant language
- TypeScript
- Stars
- 949
- Forks
- 542
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 18
Description
Since precompiles don't have an onchain creation code, we can't verify them via the creation.
We are showing "No Match" which can be misleading. If we can find a way to know if a contract is a precompile we can show a more accurate message instead.
Example CreateX on Unichain https://repo.sourcify.dev/130/0xba5ed099633d3b313e4d5f7bdc1305d3c28ba5ed
cc @pcaversaccio
Contributor guide
No contributing guide indexed for this repository
Research direction
No files or tests are named. Start by tracing the creation-verification path that produces “No Match,” then compare its behavior with the CreateX example on Unichain. Done means recognized precompiles receive a more accurate message instead of “No Match,” while other unverifiable contracts retain the existing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100