The problem wSup solves

One of the biggest takeaways I’ve had while building wSup is that I don’t want to reinvent the wheel or ‘compete’ with everyone else—I want to add to the ecosystem. I realized that if people already have test tokens or other assets on different chains, the best thing I can do is wrap or bridge them into Supra and let them fully participate in lending, borrowing, and DeFi here.

That’s exactly what I’ve built: rather than spinning up an entirely new bridging protocol to rival existing ones, I’ve integrated approaches like Dexlyn’s open-source solution and layered on top of Supra’s Move-based architecture, which already thrives on aggregator tables, typed references, and modular design. By embracing Move—the language Supra’s ecosystem uses—I’m able to unify all these previously scattered assets into a single environment. People can borrow, swap, or stake tokens they’ve brought in via bridging and get a cohesive experience.

Ultimately, this approach solves the fragmentation problem: if you’re locked into one chain’s assets, wSup’s bridging and wrapping setup opens the door to new liquidity and utility. My personal goal was never to compete head-to-head with big bridging or DEX protocols, but to augment them—taking advantage of their strengths and building a user-friendly layer on top. That’s how we all grow the ecosystem together, and that’s how I see Supra’s Move architecture shining: it unites everything in one place, rather than forcing us to build silos that battle each other.

yeah chatgpt ahh moment cause I was rushed now that you're reading this its actually me.

This has been actually the most fun I've had building ever. I really wanna build here and Im probably going to persue this after the fact.

But yo - shoutout to @supraholders on telegram and also shout out to yong he's helped me I've helped him and we're friends now which is sick! I've also got so much more planned and I wish I got todo all of the things I wanted todo but I didnt have enough time :(

Challenges I ran into

Honestly, building wSup was a rollercoaster. It wasn't like I had a clear path or a roadmap from the start. I knew the problem—people's tokens were locked up, they wanted to use them, and I had an idea about a ‘wrapped’ version—but the how part was really messy.

First, I had this notion that I could build my own wrapping system using Taos. I was completely off the mark; I wasn't using those concepts correctly. Then, I tried working with aggregators and fungible assets directly, but those parts of the Supra framework hadn't been fully implemented yet. I felt like I was constantly hitting dead ends. It was frustrating because for a while, I had only one half-baked contract called ‘wSup’, and none of the supporting infrastructure I needed.

I spent a lot of late nights reading code from projects that never even went to mainnet. I was hunting for some piece or pattern that would unlock how to build my own bridging, my own aggregator functions, my own stable swaps. I’d spend hours coding, then realize I’d been tackling a problem completely wrong. It got pretty stressful, to be honest. It wasn't just about the code; it was also this feeling of being stuck, of running in circles.

The biggest turning point was when Nolan & Jatin pointed out that I was misusing some of the core parts of the Supra framework, and that the functionality I wanted wasn't fully added yet. That was huge because it made me rethink my approach entirely. I realized I had to stop trying to force everything into one single giant contract, and started to think about modularizing instead. That’s why I landed on those three modules: price_oracle, lending_market, and obligation.

Then, there was the whole bridging issue. I was dead set on creating wrapped tokens for everything, but it felt like I was starting from scratch. When I saw Dexlyn had open-sourced their bridge, it was like a lightbulb went off. I didn't need to reinvent that; I could integrate it, build on top of it.