> For the complete documentation index, see [llms.txt](https://boringity.gitbook.io/wsup-mvp-draft/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://boringity.gitbook.io/wsup-mvp-draft/bridging-via-dexlyn-sdk.md).

# Bridging via Dexlyn / SDK

<figure><img src="/files/gdqj243bs2HRaO6wmDqW" alt=""><figcaption></figcaption></figure>

### **Bridging & Wrapping: The Early Days**

When I first started building this out, I wanted to let people **bring in** their existing tokens (Test ETH, Test BTC, Test SOL, etc.) into my own environment. The idea was simple: if they can deposit assets they already hold, they can borrow or stake them for additional rewards. **But** I ran into a roadblock: how do I properly **wrap** each token so it appears as a local coin in my environment?

I tried about a million things—wrapping **Test ETH**, wrapping **Test BTC**, bridging on my own. I even tried using **Atmos** for certain wrappers, but that quickly got complicated. That’s when I discovered **Dexlyn** had a bridging solution. I spent nearly a month just tinkering on my own, researching how their bridging worked. Then, about a week after I finally got the fundamentals in my head, **Dexlyn open-sourced** their code. *Perfect timing.*

***

### **Building a Bridge + Lending Pool**

At that point, I decided, *“Let’s just integrate their solution!”* Here’s how it unfolded:

1. **Bridging**:
   * I wired up a front end that calls **Dexlyn**’s bridge, letting users move tokens from **Base Sepolia** (an Ethereum test environment) over to **Supra**.
   * You need **MetaMask** with ETH on **Sepolia** plus **USDC** from the Circle faucet (linked below).
   * Once the user approves the transaction on Dexlyn’s side, they get a wrapped version of **USDC** on Supra (or any asset Dexlyn’s bridge supports).
2. **Lending Pool**:
   * On my side, I developed a **lending market** (paired to my price oracle) so you can deposit the bridged USDC (or other tokens) and borrow something else.
   * I wanted to also **reward** depositors with a native incentive token but ran out of time. The code’s mostly there, but bugs and time constraints got in my way.
3. **Issues with Dexlyn**:
   * Dexlyn’s bridge apparently went down for a while, and I tried contacting their team. No responses, which was frustrating. Many teams on Supra are either MIA or just not active right now.
   * In the meantime, I integrated what was available and tested it on my own front end. **If** Dexlyn is up, everything works. Otherwise, it’s stuck.

***

### **How It Works for You**

1. **Set Up MetaMask**:
   * You need **ETH** on **Sepolia** for gas.
   * Go to [faucet.circle.com](https://faucet.circle.com/) to get some test USDC.
   * Switch your MetaMask to the **Sepolia** network.
2. **Bridge to Supra**:
   * On my website, you’ll see an option to bridge USDC (or other tokens if Dexlyn supports them).

<figure><img src="/files/8N20fCzig2s8Lu9ENSb9" alt=""><figcaption></figcaption></figure>

* Approve the transaction on Sepolia.
* You should end up with a wrapped asset on Supra testnet.

<figure><img src="/files/Qu97GvR3wYqiQvzmycLe" alt=""><figcaption></figcaption></figure>

1. **Use wSup Lending**:
   * Now that you have the bridged token on Supra, deposit it into **my pool**.
   * Borrow something else (like wSup) to play around with DeFi.
   * If you need to go back, do the reverse process on Dexlyn.

I’m aware it’s **not** the smoothest process in the world, but it’s the best I could whip up in the limited hackathon timeframe. Eventually, I want to incorporate multiple wallets, streamline bridging UI, and add robust reward logic. For now, it’s functional enough to demonstrate **the concept**—**bridge** from Base Sepolia to Supra, then deposit those tokens in my environment to borrow, stake, or build on top of wSup.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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://boringity.gitbook.io/wsup-mvp-draft/bridging-via-dexlyn-sdk.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.