Welcome to the world of ettE, the EVM-based blockchain indexer designed for businesses and developers looking to harness real-time notifications and historical data querying. If you’re eager to get started, this guide will walk you through the installation process, usage, and troubleshooting tips to ensure you have a smooth experience. Let’s dive in!

Why Did You Build ettE?

The inspiration behind ettE is simple: the need for a reliable tool to stay in sync with the latest developments on EVM-based blockchains. Many existing solutions fell short in offering comprehensive indexing, real-time notifications, and user-friendly APIs. Thus, ettE was born to keep track of blockchain activities effortlessly.

What Do I Need to Have to Use It?

• Go installed (version 1.15 or later)
• PostgreSQL set up with the pgcrypto extension enabled
• Redis installed (version 6.0.6 required)
• Access to both HTTP and WebSocket connection URLs for blockchain nodes

How to Install ettE?

1. Clone the repository:

   git clone git@github.com:username/ette.git

2. Navigate to the directory:

   cd ette

3. Create a `.env` configuration file and set up all necessary variables including database credentials and mode settings.
4. Create another file named `.plans.json` to manage subscription plans for your API keys.
5. Build the project:

   make build

6. Run the binary:

   ./ette

For production deployment, consider using systemd to manage your instance as a service.

How to Use It?

ettE offers an array of functionalities encompassing:

Historical Data

• Queries via REST and GraphQL APIs for blockchain data like block, transaction, and event data.

Real-time Data

• Subscribe to real-time notifications for mined blocks, transactions, and event logs.

Snapshotting

• Take snapshots of your database for easy migrations or instance creation.

Historical Data Queries

For example, suppose you want to query historical block data. Imagine the Ethereum blockchain as a library where each block is a book. To check the contents of a particular book (block), you would need to specify the book’s unique identifier (hash or number) to retrieve the information, just like querying the library catalog. A similar analogy applies when querying for transaction and event data.

Troubleshooting

If you encounter any issues while using ettE, consider the following troubleshooting ideas:

• Ensure all necessary software (Go, PostgreSQL, Redis) is correctly installed and configured.
• Verify the connection URLs for blockchain nodes are accurate.
• Check your API key usage; rate limits are enforced on requests.
• For real-time notifications, ensure your WebSocket connections are stable and subscribed correctly.

For more insights, updates, or to collaborate on AI development projects, stay connected with fxis.ai.

Conclusion

At fxis.ai, we believe that such advancements are crucial for the future of AI, as they enable more comprehensive and effective solutions. Our team is continually exploring new methodologies to push the envelope in artificial intelligence, ensuring that our clients benefit from the latest technological innovations.