# Introduction

## **Cross-chain Routing API, Omnichain Messaging & ZK Light-Client Infrastructure**

Butter Network provides developer infrastructure for building secure, fully onchain cross-chain applications.

These docs explain how to integrate cross-chain swaps, omnichain messaging, and interoperability flows powered by Butter’s ZK light-client technology.

Butter is designed for developers building wallets, DEXs, dApps, and protocols that require trust-minimized cross-chain execution — without multisigs, external validators, or centralized relayers.

***

## **Getting started**

If you are new to Butter Network, start with:

1. [**About Butter Network**](https://docs.butternetwork.io/about-butter-network)
2. [**Understanding the ZK Light Client**](https://docs.butternetwork.io/zk-light-client/understanding-light-client)
3. [**Cross-chain Flow & Omnichain Development**](https://docs.butternetwork.io/omnichain-development/cross-chain-flow)
4. [**Integration Guides for APIs and smart contracts**](https://docs.butternetwork.io/butter-bridge-integration/integration)

***

## **What you can build with Butter Network**

Using Butter Network, developers can:

* Enable **one-step cross-chain swaps** across Bitcoin, EVM chains, Solana, and TRON
* Integrate **cross-chain routing** that combines bridging and onchain swapping into a single flow
* Build **omnichain applications** with verified cross-chain execution
* Access **non-custodial liquidity routing** sourced directly from onchain DEX and AMM pools
* Leverage **ZK light-client verification** for secure, trust-minimized settlement

Butter’s architecture is optimized for composability, safety, and production-ready integrations.

***

## **Core documentation sections**

### **🔥** [**About Butter Network**](https://docs.butternetwork.io/about-butter-network)

High-level overview of Butter’s architecture, design philosophy, and role as an omnichain interoperability hub.

### **🔥** [**ZK Light Client**](https://docs.butternetwork.io/zk-light-client/understanding-light-client)

Learn how Butter uses ZK-powered light-client verification to validate source-chain state and enable secure cross-chain execution.

### **🔥** [**Omnichain Development**](https://docs.butternetwork.io/omnichain-development/cross-chain-flow)

Understand cross-chain flows, omnichain isomorphism, and how to design applications that operate seamlessly across multiple blockchains.

### **🔥** [**Omnichain Messaging Integration**](https://docs.butternetwork.io/butter-omnichain-messaging-integration/butter-omnichain-service)

Guides for integrating omnichain messaging, including API usage, contracts, and deployment references.

### **🔥** [**Butter Bridge & Routing Integration**](https://docs.butternetwork.io/butter-bridge-integration/integration)

Step-by-step guides for integrating cross-chain swaps, routing APIs, contract interfaces, fee models, and deployed contracts.

***

## **Who should use these docs**

These docs are intended for:

* Wallet teams integrating cross-chain swaps
* DEXs and aggregators expanding cross-chain support
* dApp developers building omnichain products
* Infrastructure teams requiring secure cross-chain execution
* Protocols looking to integrate Bitcoin and non-EVM chains into their stack

For integration support or partnership inquiries, visit the [**Integrations**](https://www.butternetwork.io/en/integrations) page on the main site.


---

# 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.butternetwork.io/readme.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.