# Overview

All key components of the Chainspot protocol you can find on the scheme below:

<figure><img src="/files/ywm3l3RvIplDWHccZ9wr" alt=""><figcaption><p>Chainspot architecture overview</p></figcaption></figure>

## Intro

**Our goal** was not only to simplify and accelerate user and business access to DeFi but also to do so with optimal efficiency regarding blockchain fees and liquidity movement (swap/bridge). \
To achieve this, we found an effective balance between on-chain and off-chain modules, minimizing fee costs, streamlining DeFi position management, and ensuring security, even if control over the off-chain components is compromised.

**The core business logic** for handling user funds is executed through smart contracts, providing a reliable and predictable protocol in all use cases. \
The off-chain component acts as an interface for smart contracts and is responsible for generating the most efficient route for user fund transfers (like a “skyscanner” for liquidity) based on integrated liquidity providers. It also handles callData and payload assembly and supports analytical tasks and cross-chain messaging (cross-chain native token standard) via the Asterizm infrastructure.

Additionally, the **B2B Integration Kit** is developed and delivered from the off-chain module, facilitating seamless partner integrations.

## Components

The Chainspot protocol infrastructure consists of multiple on-chain and off-chain modules.

### **On-chain**

* Set of liquidity manager smart contracts: execution of the on-chain and cross-chain swaps via third party liquidity providers + multihop features.
* Set of yield manager smart contracts: connectors to the third party yield vaults, execution of DeFi positions management(deposit/withdrawal/claim) + auto compounding.
* Set of LP token manager smart contracts: wrapping of vault LP tokens into omnichain standard with Asterizm infrastructure, bridgeless transfers across EVM and non-EVM chains.
* Set of loyalty manager smart contracts: cashback and referral payouts claimer, NFT membership and some business logic related to the loyalty program of the Chainspot.

### Off-chain

* [Liquidity routing engine](/architecture/liquidity-routing.md)[: ](/architecture/liquidity-routing.md)a module for finding and assembling the most efficient route for asset swaps across any supported blockchains. It generates the callData and payload.
* [Yield routing engine:](/architecture/yield-routing.md) a module for assembling callData and payload for managing DeFi positions, tracking positions data, accumulating statistics on yield vaults, and performing additional calculations.
* [Gamification module:](/architecture/gamification-module.md) a module for calculating loyalty program metrics, including user experience and level assessment, referral system management, and tracking cashback and referral payout balances.
* [Enterprise module:](/architecture/enterprise-module.md) a module necessary for providing fintech partners with all relevant legal data and additional technical services. It performs AML checks before transactions and maintains required reporting for exchanges and yield positions.
* [Asterizm Client Server Module](/architecture/asterizm-client-server-module.md): a module necessary for the secure execution of cross-chain payload transfers within the omnichain vault LP tokens standard. The decentralized cross-chain messaging protocol Asterizm guarantees the security of omnichain DeFi positions.
* [B2B integration kit module](/integration/overview.md): this module implements APIs and SDKs in various formats for convenient use of Chainspot by both web3 projects and traditional fintech applications.


---

# 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.chainspot.io/architecture/overview.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.