Zellic proudly announces the EVM trackooor, a modular tool for monitoring arbitrary actions on chain.
With the amount of data that blockchains contain, it’s difficult to query and process anything that isn’t indexed event fields.
This is why we built EVM trackooor 🧵👇
With the amount of data that blockchains contain, it’s difficult to query and process anything that isn’t indexed event fields.
This is why we built EVM trackooor 🧵👇
What is the EVM trackooor? The EVM trackooor is a framework for tracking any kind of data on a blockchain, including event logs, transactions, and blocks mined.
The EVM trackooor allows you to register what data you want from a blockchain and define what happens when you receive the data, such as processing it and recording it in a database or sending an alert through a webhook.
The EVM trackooor allows you to register what data you want from a blockchain and define what happens when you receive the data, such as processing it and recording it in a database or sending an alert through a webhook.
The EVM trackooor features the following:
- Real-time data monitoring, including event logs, transactions, and blocks mined
- The ability to request historical data, such as past events or transactions that occurred within a block range
- A modular approach to request and process data for any purpose
- Event and function-ABI fetching to automatically decode event logs and transaction calldata
- Real-time data monitoring, including event logs, transactions, and blocks mined
- The ability to request historical data, such as past events or transactions that occurred within a block range
- A modular approach to request and process data for any purpose
- Event and function-ABI fetching to automatically decode event logs and transaction calldata
Why did we make the EVM trackooor? Creating a new project every time you want to query and filter data is troublesome.
The EVM trackooor simplifies this process. By being a generic framework for querying and filtering data — all you need to do is tell it what data you’re looking for, and it provides the data directly to you
The EVM trackooor simplifies this process. By being a generic framework for querying and filtering data — all you need to do is tell it what data you’re looking for, and it provides the data directly to you
Let’s look at an example.
Let’s say there’s an address `0xcafe…` holding native ETH and some ERC-20 tokens, and you want to be alerted when it moves those funds.
With the EVM trackooor, all you need to do is provide the address you want to monitor and a callback function that the EVM trackooor will call with your requested data to process.
Then in the callback function, you can implement checking the value and sending alerts.
Let’s say there’s an address `0xcafe…` holding native ETH and some ERC-20 tokens, and you want to be alerted when it moves those funds.
With the EVM trackooor, all you need to do is provide the address you want to monitor and a callback function that the EVM trackooor will call with your requested data to process.
Then in the callback function, you can implement checking the value and sending alerts.
How has the EVM trackooor been used? We’ve already used the EVM trackooor to…
Monitor for potential exploits funded by Tornado Cash,
Monitor for potential exploits funded by Tornado Cash,
Graph funding paths to visualize movements of funds, including native ETH and ERC-20 tokens,
And listen for ownership transfers and proxy upgrades for high-value contracts.
The EVM trackooor is a command-line tool, and you can access it on GitHub. There, you can review its documentation with more info on usage, including how to use preexisting modules or create your own module: github.com/Zellic/EVM-tra…
For a more in-depth look at the EVM trackooor, including example code for a sample use case, check out the full announcement on our blog: zellic.io/blog/evm-track…
Also, go over to the January edition of the Zellic Security Roundup where we cover the latest news in Web3 security: newsletter.zellic.io/p/zellic-secur…
• • •
Missing some Tweet in this thread? You can try to
force a refresh
