# Welcome to ApeBridge

## Introduction <a href="#id-636b" id="id-636b"></a>

Ape Bridge is an innovative endeavor aiming to unify the liquidity amongst Bitcoin network (BTC) and Avalanche networks.

Ape Bridge offers a secure and efficient bridging mechanism to allow for seamless cross-network transfers of tokens between the Avalanche chain and BTC network. Bridging Avalanche Token tokens with BRC20 tokens, the Ape Bridge enhances the liquidity of BRC20 tokens and promotes the growth and development of the Bitcoin ecosystem.

<figure><img src="/files/5PiJBRo8AvhNoQNVdoso" alt=""><figcaption></figcaption></figure>

## Merging Value with Versatility <a href="#ee4c" id="ee4c"></a>

Ape Bridge envisions leading the vanguard in cross-chain transfers across the blockchain universe. We are dedicated to ceaseless innovation and technological enhancements, all with the primary goal of providing a secure, efficient, and seamless cross-chain transfer experience for users.Ape Bridge interweaves the robust store of value characteristic of Bitcoin with the programmability of Avalanche’s Avalanche networks. Enhancing Bitcoin’s utility through interoperability, Ape Bridge aims to enrich the Avalanche ecosystem with a stable, significant assets. Spurring innovation and amplifying the potential of decentralized applications and DeFi. This symbiotic merger holds the promise of creating a vibrant, interconnected blockchain landscape, sparking a new era of growth in the crypto space driven by BRC20s

### BRC20 <a href="#id-3f0a" id="id-3f0a"></a>

The BRC-20 “token standard: is an experimental fungible token created using Ordinals and Inscriptions and saved on the bitcoin base chain. It utilises Ordinal inscriptions of JSON data to deploy token contracts, mint tokens, and transfer tokens.This is not a token standard like you’re used to with Avalanche chains, which create smart contracts that manage the token standard and its various rules, but simply is a way to store a script file in bitcoin and use that file as a way to attribute tokens to satoshis and then allow them to move from one user to another. The BRC-20 token was created by Twitter user [@domodata](https://twitter.com/domodata) on March 8th, 2023. The name is a play on Avalanche’s token standard, but they don’t have the ability to interact with smart contracts like the Avalanche standard it derivates its name from.

## Bridging BRC20 to Avalanche Ecosystem <a href="#id-1284" id="id-1284"></a>

Ape Bridge seamlessly bridges the gap between bitcoin ecosystem and Avalanche blockchains.

<figure><img src="/files/1fbK0f694MoN16hHxXku" alt=""><figcaption></figcaption></figure>

### Token Deposit <a href="#id-9e1a" id="id-9e1a"></a>

The journey begins when you deposit your Bitcoin RC-20 tokens (BRC20s) into a unique address provided by the Ape Bridge Protocol. Ape Bridge verifies the token deposits transactions.

### Token Minting <a href="#id-3c99" id="id-3c99"></a>

Following a successful verification, the Ape Bridge Protocol gets into action and mints an equivalent amount of tokens on **Avalanche** chain.

### Security <a href="#b7d1" id="b7d1"></a>

Periodically, the Ape Bridge Protocol gathers up tokens from all the unique addresses it’s given out. These tokens are securely moved to a unified cold wallet.

### Token Withdrawal <a href="#id-7cad" id="id-7cad"></a>

When you’re ready to withdraw your tokens, the Ape Bridge Protocol will remove (or “burn”) the corresponding amount of tokens from the Avalanche chain. It then transfers an equivalent value from the secure cold wallet back to you.

<br>

<br>


---

# 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://ape-bridge.gitbook.io/apebridge/welcome-to-apebridge.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.