Every Web3 developer building user-facing dApps faces a common challenge: how to display transactions in a clear and understandable way. Developers typically have two options for solving this problem:

- Implement an in-house transaction decoder: This requires significant expertise and time to develop, and often leads to problems with data enrichment and ongoing support for new types of transactions. Developers are required to understand and implement the decoding and interpretation individually for each contract they want to support. Such an example could be seen in the popular OSS portfolio tracker [Rotki](https://github.com/rotki/rotki/tree/develop/rotkehlchen/chain/evm/decoding).
- Use a third-party API: While this provides indexed and readable data, it can quickly become costly, especially for early-stage projects.

With a Loop Decoder, developers can decode transactions into a human-readable format, on both the client and server side, without needing in-depth knowledge of EVM transaction decoding. We have implemented examples of the decoder in action for the following use cases

- Real-time push notifications to mobile apps: https://github.com/3loop/example-push-notifications
- A Telegram bot for new transaction notifications: https://github.com/3loop/example-tg-bot