wjmelements / wjmelements/josuke
`josuke audit`
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Find transactions emitting SelectorDelegated and DiamondDelegateCall going back until the contract was deployed. Group them by transaction hash and order them sequentially. Match them up with historical deployments declared in the josuke.json. Warn about any missing records. This method will require an archive node.
In tandem, we want to expand josuke.json to include a record of all historical facet deployments and accepted migrations. josuke audit can be used to verify the list is complete.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Begin by locating the josuke audit command and the historical deployment records in josuke.json. Use an archive node to inspect SelectorDelegated and DiamondDelegateCall transactions, group and order them by transaction hash, and compare them with facet deployments and accepted migrations. Done means the configuration covers the history and the command warns about missing records.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- blockchain, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100