How To Deploy No Code Cross Chain Infrastructure by Chris Lott & Viveik Vivekananthan

no code crosschain infrastructure started quickly about the agenda for today's call uh meeting uh we're going to talk about crosschain challenges that crosschain developers are facing what is swing and how it works some use cases uh that we built around swing and then a quick demo at the end on how to use our no code crosschain infrastructure so quickly about swing swing was was founded by Silicon Valley alumni myself and two other members from Apple Amazon on LinkedIn. We're backed by some of the best. Republic Capital, Arrington Capital, a sense of assets, Avalanche, seller. We've been in the crypto space for a little while uh as far back as 2016 where we started building smart contract applications. We started we built Ethereum plasma scaling solutions in 2018.

Personally involved in that and we also launched ERC504 which was the upgradeable smart contract standard that developers are all widely using. We've I also personally founded the Silicon Valley blockchain consortium in 2017. You can see our team members have pretty strong backgrounds from Apple to Spotlight to Amazon, IBM, Blackberry and we do have all the all our notable invest investors at the bottom. So to kind of dive into some of the challenges that we've seen with crosschain developers, number one, fragmentation. As as blockchain ecosystems continue to grow, what we've noticed is that the liquidity fragmentation problem also continues to grow.

Number two, teams that rely on a single bridge integration end up being extremely vulnerable. Reality is we've had $2 billion worth of hacks over the last two years. And that's because they were connected to a single bridge and and they're absolutely compromised. The number of bridges, number three, are just growing rapidly. Over 70 bridges today to to connect to all these different blockchain ecosystems.

And we've been probably getting hit up every week for the last six months about a new bridge project that's coming online. And number four, it's just really timeconuming to integrate bridges into your application. If you're trying to bridge between Polygon to Avalanche, Avalanche to Salana, Salana to Cosmos, that's three separate bridge integrations and you have to maintain every single one. The go to market is just absolutely long in general weeks to months is what we're talking about. So what is the problem that we that we've identified?

There needs to be a unified solution for crypto liquidity. We we're looking to connect the bridges and blockchains of the world to the web two and web three applications of the world. We've realized that a liquidity layer that sits in between could actually be very beneficial for the entire ecosystem. So what what are we doing at swing? We've built out a set of APIs, SDKs, and a front-facing widget uh to help you handle crosschain capabilities and we've deployed smart contracts across all the different chains that we support today.

Here's an example if you look of our widget product on the right hand side where we're moving uh USDC from Avalanche to Polygon. That's that's actually a real quote. It cost 50 cents to do this transaction. Some key features about swing. Number one, omni chain liquidity.

We source liquidity from dexes, aggregators, and also liquidity available in the bridges. Number two, chain agnostic smart routing. We have we we've built out a liquidity routing layer across all the different chains that we support and we help find the best price execution for any swap that you're trying to do any token to any token. And last but not least, we also support contract calls across chains. This means that you can build complex logic into multiol smart smart contracts to build things like crossing swaps, crossing uh NFT purchases, crossing wallets, list goes on and on.

Some of the bridges that we support today uh about 10 today and this this is growing every day every uh quarter. Stellar, axelar, hop, hyphen, dbridge, synapse, across, multi-chain, connect. If you are a bridge team, feel free to reach out to us. We do have an evaluation process and on the bridges that we want to select to add. Uh but this list is definitely growing.

I mean out of the 80 plus bridges that we've seen, we've identified these so far as the bridges that we'd like to work with. Some of the connected chains that we have uh on on swing support over 30 blockchains today uh majority of them today are on the EVM world but we also are now charting a path into the non-EVM side. We currently support uh 10 plus chains on the Cosmos side and we're looking to tap other ecosystems like Salana uh and others as well. You please pay attention to our socials. We'll be doing some of these announcements over the coming months.

some of the connected wallets quickly. MetaMask, Brave Wallet, Wallet Connect, Coinbase Wallet, and Kepler specifically for the Cosmos ecosystem. Uh we are looking to add more wallets and if you are a wallet team, feel free to reach out. We're happy to talk to you. Security audits, we have been working on we've done about four security audits to date.

Um Halburn and Pex are our partners in that in this space. Every single time we make major code changes, we like to kind of kick off an audit. uh because we are doing a crosschain and all the security concerns involved in this doing regular audits is a a common practice within our team. So let's say let's talk a little bit about how this actually works. So at the core it's liquidity aggregation is what we're solving here at swing.

But let's talk about an example where we start with let's say unis swap on ethereum and we want to end it with BNB token on binance smart chain. So typically the way that this works is we first tap our liquidity partners 1 inch parasop or unis swap to initially kick off the original swap from unis swap into a stable coin. Uh this could mean um we usually will look across all the different liquidity pools. Sometimes we may go directly to unis swap if there's concentrate volume in some of the tokens that we're looking for. Once the USCC is on the Ethereum side, we will then send that to a bridge aggregator, our bridge aggregator where we we will then compare all the different prices across the different bridges that offer this this particular swap.

And we like to work with bridges that provide native canonical tokens. We're not looking to uh move wrapped assets. The intention is to have native USC on Ethereum and also to be delivered native USC on the Binance SmartChain side. So in this scenario, we have USC now sitting on Binance Smart Chain and again we tap our liquidity partners 1 in Paris swap and pancake swap among other dexes as well to then do that swap from USDC into the final token BNB token. Uh and so this is an example of kind of how we handle liquidity aggregation.

You can replace you know the Ethereum blockchain or the Binance marching with any of the chains that we support and it's fundamentally the same kind of flow in terms of how we handle these swaps. Especially for non EVM swaps, it's also a similar process, but we're just utilizing a different bridge in the middle to make that swap happen. Some of the use cases that we currently support, uh these are use cases that been identified from our by talking to customers. Crosschain staking, crosschain swaps, crosschain wallets, gamefy, and metaverse. On the crosschain staking side, we're working with teams especially with POS coming online pretty soon with Ethereum.

uh oneclick liquidity deposits directly from any chain into Ethereum staking pools. On the crosschain swap side, we just did that example where I just showed you how it works. Uh for wallets, they can accept deposits from any chain or they can even integrate swaps directly into their into their application. GameFi and Metaverse where we allow them to move assets or skin digital NFT assets within the game between chains as well. So over the last I would say 24 months we've spoken to a lot of teams and I think some of the issues that we've identified um are essentially summarizing these four points.

Number one, technical skills are primarily required to launch a bridge and there's clearly a lack of customization in terms of which tokens you want you can support, what kind of bridges you want to enable in your application. Number two, there's a high cost of integration maintenance. If you if a bridge goes down or if you want to add a new bridge, typically this takes dev cycles and could take weeks or months to get get this resolved. Number three, there's a lack of access to transactions and metrics. It's not really easy to know, you know, what kind of volume is moving through your bridge, which bridge is moving the most volume for you, uh what are the top pairs that maybe your users are currently transacting with.

It's all it's all very kind of a it's bit of a black box today the way it's kind of being handled. And number four, the most important point, teams are absolutely vulnerable during security breaches. There's no way to mitigate a problem. If a bridge gets hacked, you're essentially a sitting duck. There's not really much you can do.

If the developers are not awake, it's the middle of the night. Your your protocol is compromised. There must be a better way. I'm excited today to announce that ETH Denver 2023, the launch of our swing platform. I'm gonna stop right here.

I'm going to stop right here and uh call upon our wizard and software architect Chris Lot to do a demonstration of the entire platform. Thank you guys. Uh all right. So I'm going to do a quick demo of the uh the platform that we just launched today. Uh so after you create your account, uh you come to the uh project creation screen.

Uh so we currently have uh three different integration types that you can choose from. Uh so we have our uh our embeddible widget. Uh we have a a JavaScript uh SDK. Uh and we have a an HTTP API. Um obviously if you're not ready to uh build your integration yet, uh you can skip this step.

Uh but for the sake of the demo here, we'll do the uh we'll do the widget. Uh the next screen you're presented with is a a page where you actually, you know, you can name your project. of the most important piece here is your uh project identifier. So your project identifier basically just tells uh tell tells us uh uh uh to associate whichever transactions are going through your uh integration uh that they should be associated with your project. So then after you create your uh uh project uh when you log in uh you'll be landed on the uh the dashboard page.

Uh so the dashboard page gives you a breakdown of all of your uh all of your key metrics. Uh so key metrics are say your uh the total volume that's been sent through your uh project's integration. uh the total number of transactions, total number of uh unique wallets. So these are you know uni unique users that are actually using your uh uh your application. Uh the total volume per chain, the top pairs, so these are you know what what are users actually sending, what are they receiving, how much volume, how many transactions for each of these individual pairs and then a breakdown of the uh top bridges.

Uh so these are the uh uh you know the bridges that are uh the transactions are actually being routed through and you can see the total volume being routed through each bridge and the total number of transactions. Um obviously you can uh click at the top here we have a share button so you can invite your uh team members if you want to give other people on your team access to your uh metrics and data. If I click over here to the bridge tab uh this is where you can see a list of all the bridges that we have enabled. So by default uh every project starts out with all bridges enabled. But let's say for example if a bridge gets hacked uh you can quickly come in here and disable that bridge or if a bridge is operating pretty slowly we make it very easy for you to disable it.

Or if for example if you have a partnership with one particular bridge uh you can disable all the other bridges and just have that one uh enabled. Uh if we change projects here we can switch over to the transactions tab. Uh so the transactions tab is actually a live uh updating list of all the transactions that are flowing through your uh project's integration. Uh you'll get uh live statuses like uh you know if the uh transactions in progress, if it's failed, why it failed, if it's completed, you get a breakdown of what the actual pair was. So what did the user send, what did they receive, how much did they receive, which bridge was it routed through, and what's the user's uh wallet address?

So if we switch back over here to the uh configure screen, uh this is actually where you'll be able to configure your uh uh integration. Uh so you can configure it by creating uh individual rules that limit the uh send side and the receive side uh to basically limit what users can send and receive. If we click on the try configuration, you can see uh we have our widget embedded in here uh with the default configuration loaded. And one of the main benefits of our noode platform is we actually host uh a version of your uh configuration uh live on a in a hosted environment. So if we click over here and open this up, you can see that uh it's really just re rendering our widget with the default configuration loaded.

Uh the default configuration just means that users can send uh from any chain, any token and receive uh on any chain and any token. Well, let's imagine that we're a uh a token project and we're trying to uh allow users to move liquidity from any chain, any token into our specific token on Ethereum. How would we do that? So, if we come back over here to the configure screen, we we would create a new rule. Um let's keep the send side the same.

So, allow users to pick any chain and any token. And then let's say let's scroll down to Ethereum. So let's just allow people to send to the Ethereum chain and then we'll pick a token. So let's pick let's say 1 in. We'll save this rule.

Go back to the configuration. Open up our hosted project. And you can see uh that the configuration's already been loaded. So what this means is uh just like before users can pick any chain and any token but on the receiving side they can only actually choose Ethereum and 1. But now let's say for example we want to enable this for multiple blockchains.

We can come back over here to the configure screen. Let's disable this rule here for uh for for an example. Open up create a new rule and let's say let's do Ethereum and let's pick uh a this time. And then for another blockchain maybe we'll do Polygon and we'll also pick a we'll save this. We'll reopen up our hosted configuration.

And just like before, you can see that the configuration's already been loaded and the receive side is locked down to a polygon and Ethereum uh a cool. And then we'll head back over here. And uh last but not least, uh uh this is only available to our uh uh select customers, but if if you want access to this feature uh you can request access right within the application. Uh but it's uh the ability to monetize your project. Uh so you can monetize it by enabling fees uh that will be added on top of every single one of your users transactions.

Cool. And uh like we said before, this is all available now. So you can go to platform.sw.xyz or scan this QR code uh and sign up and uh create account.

Cool. [Music]