crytic / crytic/tealer

Creation of a regex system to allow querying Tealer’s API and internal information

Open
#84 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
63
Forks
13
PR merge metrics
No merged PRs in 30d

Description

Creating detectors can be a difficult and long task, as it requires knowing about Tealer’s internals and Python. However, most of the existing detectors work by exploring the paths of the contracts and look for incorrect patterns (ex: all the paths check for canDelete). To ease the creation of detectors and custom rules for developers, we could create a DSL that will allow developers to query Tealer’s information without the need to know Tealer’s internals.

I don't have a clear view of what the DSL would like, but I think we can try to at least express the existing detectors in some form, and iterate over the format.

Plan
- [ ] Extract high-level patterns from existing detectors
- [ ] Design a DSL
- [ ] Create a query API

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.