> For the complete documentation index, see [llms.txt](https://leandexer.gitbook.io/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://leandexer.gitbook.io/home/technical/technical-architecture.md).

# Technical Architecture  

Leandexer offers an easy to use yet complex service through a highly available and robust architecture.

<figure><img src="/files/v3lKmC9Fv32wWTuP3P3X" alt=""><figcaption><p>Leandexer high-level architecture</p></figcaption></figure>

In the above diagram, you can see the high-level view of the architecture:

* app.leandexer.com: The web application, written in Vue.js
* Authentication Service: relying on AWS Cognito to safely store emails and passwords
* Leandexer API: Storing the project, streams, networks and notifications configuration, written in Node.js
* Leandexer Indexing Engine: where the magic happens. See below for a breakdown of this component architecture

The Indexing Engine is where the business logic of listening to the blockchain and filtering the events happens. This key component of the solution is constantly calling the networks RPC to feed on the new blocks, reading the information contained in the blocks and filtering per smart contracts defined in your projects.

In order to be highly available and scalable, the Indexing Engine is creating separated process per smart contract and per blockchain network, allowing for a better usage of resources and preventing interlocking between two indexing.

<figure><img src="/files/1PlmroSaHdk636ukPFNF" alt=""><figcaption><p>Leandexer Indexing Engine architecture</p></figcaption></figure>

The Indexing Engine is composed of two main parts:

* The Orchestrator: connecting to the network RPC, it is listening to all new blocks incoming and filters the data for the smart contract configured in its database, sending the raw data to the Log Worker
* The Log Worker: getting the raw data from the blockchain, it is decoding the payload and making it easily digestible by a system. The decoded payload is then sent to the consumer

In the current architecture, the consumer is a micro-service responsible for managing the notification channels defined by the user in the web application, sending the data over email or webhooks.&#x20;


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://leandexer.gitbook.io/home/technical/technical-architecture.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.