A library to transform any EVM transaction into a human-readable format. It consists of 2 parts:
⚠️ The Transaction Interpreter is still under development and breaking changes are expected.
Head to the documentation to read and learn more about the Loop Decoder, or check out our playground to see it in action.
If you're familiar with a specific contract or protocol, or want your own contracts to appear in human-readable interpretations, please contribute to Transaction Interpreter! Check out our Contribution Guide to learn how to get started.
Transaction decoding is a crucial component of many dApps. Our goal is to create a library that can be integrated into any application without introducing any external infrastructure dependencies. This will allow developers to integrate decoding and interpretation into their stack without enforcing any data sources.
Currently, the available EVM transaction decoders require developers to use specific databases or provide a lower-level API that requires maintenance. The Loop Decoder, however, can be used as a plug-and-play component in any layer of dApp infrastructure.
The open-source nature of the Loop Decoder allows developers to also integrate new chains as they see fit. While using a third party closed-source decoder, developers are limited to the chains that the provider supports. This can be a significant burden for developers who want to support multiple emerging chains.
- Transaction Decoder: Decoder automates the decoding of any transaction data, event log and trace, in a unified format. We leverage multiple data sources for contract metadata and ABI resolution. With an unified interface to decode transactions across any protocol, developers don't have to manually understand and decode each individual transactions.
- Transaction Interpreter: Interpreter is a flexible layer that allows developers to define custom interpretation of a decoded transactions. In context of this library, an interpretation is a transformation from a decoded transaction to a human-readable format. It is used to extract the most significant information that can be directly displayed to a non techincal user.
- Can be used in any JavaScript environment
- Minimal external dependencies - connect your own storage
- Predefined ABI and Contract metadata resolvers
- Resolves contract proxise and multicalls
- Flexible interpreter that allows you to define any custom interpretation of EVM transactions.
- Decoder HTTP Server - A simple HTTP server that exposes an REST API to decode transactions.
- Firebase Push Notifications - Firebase Cloud Function that sends push notifications with decoded transactions.
- Farcaster Bot - Farcaster Bot for human-readable transaction alerts
- Telegram Bot - Telegram Bot for human-readable transaction alerts
- Next.JS Playground - Interactive playground to decode and interpret transactions
appspackages- transaction-decoder - Transaction decoder package
- transaction-interpreter - Transaction interpreters
Please let us know about your use cases and how this project can help you. You can reach us on Twitter @nastyarods and @Ferossgp, or through email at [email protected].