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. 
- Use a third-party API: While this provides indexed and readable data, it can quickly become costly, especially for early stage projects and supporting a new chain requires the API provider to support it first.

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:

- Farcaster Frame for displaying transactions https://github.com/3loop/transaction-frame; used by people to read and share on-chain alerts posted on Farcaster https://warpcast.com/alertsbot
- A Farcaster bot for human-readable on-chain alerts https://github.com/3loop/farcaster-onchain-alerts-bot
- A Transaction Decoder REST API template https://github.com/3loop/decoder-api 
- Real-time push notifications to mobile applications: https://github.com/3loop/example-push-notifications
- A Telegram bot for human-readable on-chain alerts https://github.com/3loop/example-tg-bot