# Copy of Bridging Map
### Infrastructure Layers
#### Supernet (e.g. Banana1 Supernet)
**Supernets** represent the top layer within a Layer-1 Multi-Chain Network. Each Supernet serves as a unified infrastructure layer that interconnects and manages multiple Layer-1 blockchains, providing seamless interoperability, shared security, and coordinated scalability across the entire network.
#### L1 Multi-Chain Network (e.g. Juneo Primiray Network)
Each **Layer-1 Multi-Chain Network** operates independently, designed to address specific use cases or applications. These networks remain interconnected through shared infrastructure such as bridges, wallets, and explorers, as well as common governance. Together, they form a unified, scalable, and collaborative ecosystem within the Juneogo framework.
#### Blockchain/VM (e.g. JUNE-Chain)
At the heart of every Layer 1 is the **JUNE-Chain**, a blockchain powered by a custom virtual machine. This foundational layer manages the consensus, executes smart contracts, and validates transactions, forming the backbone of the network’s functionality.
***
### **Prefixes: m, k, w**
Some tokens have prefixes **m** (mili), **k** (kilo), **w** (wrapped).
Examples:
* mBTC
* kPEPE
* wJUNE
### **Native Tokens: 1**
Tokens with **1** in the end of their name represent versions of a native coin.
Examples:
* USD1
* SGD1
* EUR1
***
### **Bridge Ratio**
The **Bridging Ratio** defines the conversion rate between an existing ERC-20 token and its representation as a native coin on a new Layer 1 blockchain within the Juneo Supernet.\
\
For example:
* A **1:1** ratio means **1 ERC-20 token = 1 native coin**.
* A **1000:1** ratio means **1000 ERC-20 tokens = 1 native coin**.
* A **1:1000** ratio means **1 ERC-20 token = 1000 native coins**.
This ratio is defined at the time of deployment and applies across the bridging and unbridging processes to maintain a transparent and predictable asset relationship.
***
## Destination: JUNE-Chain
| Category | Name |
| ---------------------- | ----------------- |
| Supernet | Juneo Supernet |
| L1 Multi-Chain Network | Juneo Primary MCN |
| Blockchain / VM | JUNE-Chain |
***
## Destination: BANANA1-Chain
| Category | Name |
| ---------------------- | ------------------- |
| Supernet | Banana1 Supernet |
| L1 Multi-Chain Network | Banana1 Primary MCN |
| Blockchain / VM | BANANA1-Chain |
***
## Destination: BLUEBYTE1-Chain
| Category | Name |
| ---------------------- | --------------------- |
| Supernet | Bluebyte1 Supernet |
| L1 Multi-Chain Network | Bluebyte1 Primary MCN |
| Blockchain / VM | BLUEBYTE1-Chain |
***
## Destination: FUSION1-Chain
| Category | Name |
| ---------------------- | ------------------- |
| Supernet | Fusion1 Supernet |
| L1 Multi-Chain Network | Fusion1 Primary MCN |
| Blockchain / VM | FUSION1-Chain |
***
The Supernet Bridge should only be used through its official UI, available [he](https://supernetbridge.io/)
The Supernet Bridge should only be used through its official UI, available [here](https://supernetbridge.io/). Funds sent directly to Supernet Bridge contract addresses will be permanently lost and cannot be recovered.
---
# 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.juneo.com/intro/bridge/copy-of-bridging-map.md?ask=
```
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.