# CryptoLink DEX

## Foundation

The CryptoLink any-to-any swap DEX will use an adapted version of the Balancer v2 DEX. At our core, CryptoLink is using the Balancer DEX coupled with our [instant cross-chain bridge ](/printer.financial/components/instant-cross-chain-bridge.md)to fulfil our ultimate goal: To bring the blockchains together and allow crypto users to seamlessly transfer value across blockchains. 

We chose Balancer because it adopts powerful features to slash gas costs, super-charge capital efficiency, unlock intrachain arbitrage with zero-token starting capital, and it allows for many forms of customization. 

Please reference <https://docs.balancer.fi/> for more information.&#x20;

## DEX Aggregation

The CryptoLink DEX will enable both intrachain and cross-chain DEX aggregation. This means that projects don't need to host liquidity with us to benefit from our technology. &#x20;

Our proprietary aggregation technology will find your desired token and efficiently route that token swap to its intended destination. For cross-chain transfers, our aggregator will route through our instant cross-chain bridge. **Swapping has never been easier.**&#x20;

## PAPER-Native\* Liquidity Pools

The PAPER-Native liquidity pool is how all the magic happens. This liquidity pool will be hosted on CryptoLink's DEX on all chains that we are on. As stated in [PAPER](/printer.financial/tokens/paper.md) section, the $PAPER token is CryptoLink's bridging token. $PAPER is burned on the source chain and minted on the destination chain, it is then swapped into the PAPER-Native liquidity pool and the swap is then further routed to its destination. &#x20;

Anyone providing LP to Paper-Native would be doing so on CryptoLink's DEX, and receiving the LP rewards from all swaps in and out of $PAPER on CryptoLink's DEX.

See [Fee Structure](/printer.financial/components/any-any-swap/fee-structure.md) and [Liquidity Structure](/printer.financial/components/any-any-swap/liquidity-structure.md) for information on LP rewards and their value.&#x20;

## Hosting Other Pairs

**At the initial launch of the cross-chain any-to-any DEX, CryptoLink will not be allowing external parties to host liquidity with us. We will enable this functionality sometime after launch.**&#x20;

In the meantime, we will happily accept requests once the functionality is available. Please see the link [Work With Us](/printer.financial/b2b-service-suite/work-with-us.md) to submit information about your Project.&#x20;

In the future, LPs hosted on CryptoLink's DEX would be subject to CryptoLink's [Fee Structure](/printer.financial/components/any-any-swap/fee-structure.md) and [Liquidity Structure](/printer.financial/components/any-any-swap/liquidity-structure.md).&#x20;

Benefits:

1. Hosting Liquidity on our DEX will reward in Blockchain Native tokens, as opposed to Project tokens. All fees taken on CryptoLink's Any-Any Swap will be in Blockchain Native tokens. See [Fee Structure](/printer.financial/components/any-any-swap/fee-structure.md) for more info.
2. Hosting liquidity on CryptoLink's DEX will result in less fees incurred upon users swapping in and out of any given LP. If Liquidity is hosted on a different DEX and a user makes a swap in or out of that pair on CryptoLink's Any-Any Swap, the user will incur a minimum fee for using the platform on top of any fees from the DEX that liquidity is being hosted on.

**“PAPER-native LP” refers to the “blockchain native token” paired with $PAPER on a given blockchain. For example, on the Avalanche blockchain, the native token is AVAX. On the Polygon blockchain, the native token is MATIC.**


---

# 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://printer-financial.gitbook.io/printer.financial/components/any-any-swap/cryptolink-dex.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.