# Introduction

### Overview <a href="#overview" id="overview"></a>

The Enso intent engine is the worlds first shared network state for building transactable data across any blockchain framework.

Enabling developers to build products that interact with any Smart Contracts on any blockchain framework with ease.

\
**Problem: Usability**

Developers before using Enso were required to manually integrate blockchain frameworks, and write smart contracts to interact with other smart contracts, understand each smart contract’s nuances and build customized infrastructure to maintain their integration. This process is time-consuming, error-prone, and requires a deep understanding of the underlying blockchain framework where the smart contract’s are deployed.

### [​](https://docs.enso.build/content/get-started/introduction#solution-enso)Solution: Enso <a href="#solution-enso" id="solution-enso"></a>

Now with Enso, developers can interact with one source that abstracts all complexities of interacting with smart contracts. This is achieved through a shared network state that stores and builds all smart contract interactions across blockchains, rollups and rollapps to be consumed for execution. Below we give a brief insight into the evolution of the blockchain ecosystem, presenting the continued challenges for developers to build applications.

The Enso infrastructure is available through a centralized API as of today, and the decentralized network is currently in testnet phase. The Enso network is as a layer-1 tendermint based blockchain built using the cosmos sdk.


---

# Agent Instructions: 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:

```
GET https://docs.ensoai.pro/get-started/introduction.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.