GMGM guys, thank you for joining in. We're just gonna be starting up shortly. Please hold up while our speakers join up. I'm gonna leave you with some tunes in the background. We'll wait.
Awesome, just connecting up with our speakers and we'll just be starting up Hey, thank you joining us. Yeah, thanks for having me excited to be here So let's get started. Thank you guys. We're joined here
today by Ferrin Network. And Nick from Ferrin Network and Shruti from Neon Labs. And my name is Zee. I'll be hosting tonight's AMA. So let's get started. Guys, Nick, Shruti, could you guys please give us a quick introduction about yourself and a bit about your background.
Yeah, absolutely. I can kick it off. My name is Nick Odeo, the Chief Growth Officer over at Ferram. I've been with the company for a little over two years now. I got started in crypto back in 2017.
Farum got started back in 2018, I joined the team in 2020. And I found Farum just through my research of DeFi platforms that I thought were adding a lot of value. I joined the governance committee from a pretty early stage as an investor.
helping the team make decisions around the direction of the company. It came to me that's why one of the team falls on the point here about four points. And now we've scaled the team from about four to
over 35 full-time employees now. So it's been quite a journey and here we are a few years later in a much better position to really change the landscape of interoperability and that focuses over and over and over.
Thank you, Eric. I was really inspired to hear Jenny. So hi guys. Thank you all for joining and thank you for having me. I'm sure they I am currently a devil and integration engineer at neon
and I've been in space since 2019 and since then I was quite intrigued by the technology and I started working with some startups, US-based and UK-based and currently we are South of India and yeah I've got deep interest in
and EVM based training for even based networks and I have worked with some projects related to it. So I've been in an industry space, deep ice space, basically on the development side of things. And recently I've been engaged in with the Pre-Community a lot.
manage to explore more roles other than development, for example, and develop relations and some marketing community stuff. So yeah, I joined Neon in December 2022 and it's been a great
journey to Laos and see how it looks forward to many of the integration and many other amazing people to work with. Awesome. Actually, it's awesome to hear such interesting journeys because you guys have Nick, you actually went
through the Dow and you're part of the community like from the early days so it's really nice and sure to keep them all your exposure. It's like it's pretty cool. You've actually been really helpful for us at Neon. But let's get going into Baron. So you know when we're discussing about this AMA, I
actually went back into some research on you guys and I was actually surprised that firm started pulled way back in 2018. So like, can you actually shed some light around why firm was created and like what is its purpose? Yeah, absolutely. So
We took a bit of a secured route to get to where we are today, but we started with the intention of really what we're building now, which is something that we're calling interoperability 2.0, which is the idea that, you know,
And the ability to move assets across networks while interoperability 2.0 is the ability to move information, data, and messaging across networks. So because blockchains in today's landscape are so isolated, we wanted to create an environment
which would allow developers to more seamlessly deploy multi-chain DApps across various networks. And so this was our vision back in 2018. However, when we launched the company, we raised a pretty humble amount of money. It was about 1.2 million at the time.
And we launched our token into the peak of the bull market and the market tanked shortly thereafter. And so we had to get very creative in figuring out a way to survive the impending crypto winter that ensued having only raised a pretty insignificant amount of money.
And so what we did was we started creating blockade as a service products that we could sell in a B2B fashion to other projects around the space our first product was a Smart Contract-based staking solution and this was before D5
was really even a word. So we were pretty ahead of the curve with this and we created these white labeled smart compact based taking solutions which we really just deployed for ourselves to help walk up some of the circulating supply and add some utility to the token while we built out our core product.
products in our core roadmap. What ended up happening was a lot of projects in our network started coming to us asking if we could deploy the same product for them. And so this is an opportunity to start deploying these staking as a service solutions is what we're calling
and a half for it's now a career-to-over 200 projects that we've launched these products for across various ecosystems, EVM and non-AVM compatible networks alike. That's kind of been our bread and butter. That eventually
Let us create a pretty substantial network that we call the iron alliance which is our ecosystem of partners in Latin phara means iron and so hence the name iron alliance and Through that there was a lot of other early stage projects getting ready to launch that started coming to us saying hey
you know you seem to navigate your way through through bull and bear markets pretty efficiently. You seem kind of like you know what you're doing. You've survived one crypto winter. Now it's been two that we've we've lived through and not only survived but thrived. And so a lot of these projects started asking us
if we could provide advisory or consultation services. And so we saw this as another opportunity. We created what's now called the decentralized incubator where we've taken in many early stage projects kind of under our wing, help them with everything from designing their token on and to
to raising funds through a decentralized system to get, introducing them to other tier 1 and tier 2 decentralized exchange introductions, Dex liquidity management, introductions to other projects in the Iron Alliance ecosystem, and really kind of help
their hands from very early stages until now, until the before and after they launch. And this was another B2B vertical for us that allowed us to generate revenue along with the stating as a service products that we created. And so
That revenue that we were able to generate was really the catalyst for us being able to scale the team through these bear markets. Like I mentioned earlier, we started off for about four to six employees an hour over 35 and so now we're in a position to focus on
that original ambition that we had, which was solving the problem of interoperability and us sharing a new era of true interoperability, which is what we're calling interoperability 2.0. And yeah, so when I talk about the securitous root that we took to get to where we are now,
That's what I'm referring to. It's been a long time coming that we're now able to focus on what our original intentions were. So now we're kind of in the process of pivoting to more of an infrastructure-related play rather than a blockchain as a service provider.
which is a really exciting time for us and that's why we're not partnering with Neon. So yeah, we started in 2018 and have done a lot of different things up until now and now we're in a position
to really take on what we consider as a much more ambitious undertaking and something that's a pretty noble cause for WM3 and an answer to the problem of these fragmented blockchains. So yeah, a little bit of where we
started where we've been and where we're headed now. That's awesome. Actually, yeah, like, um, uh, uh, uh, one of the organizations have also been the detective of airment. Um, uh, until then I happened to go into the project, but I don't know if it's actually read about it.
like it was started in 2018. So I was like oh god, yeah, I've been for a while in this space. So I just said like yeah, like at that time, I mean, D5 was really not even a term back then. So like how how much response did you get on these protocols and all these solutions?
Yeah, it's been pretty incredible the amount of interest in the man that we've had for these products throughout the year. And I think it's really a testament to the team's ability to continue their main relevance in a space that
that moves so quickly and constantly being able to innovate and provide solutions to projects that they need. There's no things that people want to use and I really think that's been our superpower throughout the
years, being able to build these solutions that people actually want to your point of view. There's been an overwhelming interest in demand. As I said, the Stakingness of Service alone, we've
Right now cost multiple different ecosystems. We're looking to bring those to the neon ecosystem and for product and allow product exploding. When the near guys is network to utilize these as well, there's been other products along the way like our iron bestie solution.
have these very customized best-wing solutions so that we could have gotten private in public grounds and team tokens and all these different categories that need the best differently. They can utilize this and it provides them with a
a claiming global directly on their site. It's just powered by our team technology. And so that's also been very such projects. And then we've incubated a platform.
We need to think about over 200 clients who are blocking service products, incubated old 3-dubbed and proffetics. We can see our solutions in a pretty high demand and the interest has been pretty overwhelming.
Definitely, definitely, and yeah, it's actually quite difficult to stay consistent in this space and like, you know, focus on 1 kg and weight in there because, uh, but trees like, uh, every day there's a new thing that comes up and you know, it's really difficult to not, uh, disfactor yourself and
you're working on that thing that you believe in. So yeah, it's really impressive. Thank you. You know, I was actually when you were describing this whole entire story, when on these spaces and in
web through when people talk about being agile and being fast and being able to pivot immediately when you hit a roadblock, that's what your team has done pretty much. It sounds like that. So it's really, really cool. Thanks, and so...
Yeah, um, yeah, okay, so like as we like we've been delving into like your product a bit of your history and What it is and how it was created? Let's like talk about some of its features So like all the audience here today can like understand a bit more about it. So when I was reading the docs like
It had a section called the quantum portal and it talks about asset transfer and stuff and how you how how that works. Could you explain how that works and a bit about what security features you have to handle this transfer to protect all the users and builders.
So Quantum Portal is basically, you give it a certain multi-chain messaging engine that's powering this interoperable layer one and you know keep them all thinking like oh they've got their own layer one isn't that kind of like competitive
other layer ones and that's not the case with what we're building. What we're building is something that's going to bring all of the other layer ones closer together. So it's going to allow developers across various different languages, various ecosystems to be able to
operate in a sort of build once deploy everywhere type of environment where they can build an application whatever image there and then deploy it across network where they may not so they may not be so privy to and so the way we're doing that is through
Quantum portal. Quantum portal is like I mentioned a multi chain messaging engine creation multi decentralized application. And so when I talk about inner and how that movement value across networks, a lot of people think about it.
interoperability is bridging. And bridging is just kind of the tip of the iceberg when it comes to interoperability. But you think about like when you order an Uber for example, you could order your Uber on iOS and a driver on Android Paying Up.
operating systems, right? And what we're attempting to do is what no JS did for Web 2, we're trying to do for Web 3. So allowing these kind of fragmented ecosystems to
have a little bit more of a seamless connection to each other because really in our view that's the biggest thing holding Web3 back is just the confusion that exists with the relevant standpoint, user standpoint. So you know, having a
to be recognized and sent on multiple works as an overview of the biggest hurdle of the Web 3. You can think about it from a capital inefficiency problem.
There's such a bottleneck for developers right now because if you're trying to find a select dev built in 10-bit or less devs to run a sub-strain or
would be, would it exist quite as much as this today?
Hey, sorry Nick, I think it's cutting out. Can you hear us?
Okay guys, it seems like we're having a bit of technical difficulties. It's kind of normal on Twitter. We'll wait for a next comeback. Okay, next back. One second.
Awesome, Nick, can you hear us? Sorry about that guys. I don't know, get disconnected somehow. Can you guys hear me? Yeah, perfect. Hi, sweet. So I think maybe where I got cut off was talking about some of the features, you know, and how really how we intend to secure such a
When you're talking about interoperability, the biggest vectors for... There's a lot of vectors for x-quites, put it that way, when you're talking about interoperability. That's been one of the
main storylines in bridging at least is all of these different vectors that exist for bad actors to kind of take advantage of these security flaws that exist when you're trying to connect to different networks. And so for us,
Security is always at the top of mind when we're creating something that has the amount of responsibility that an interoperability protocol has. And so a lot of the features that we've designed for a quantum portal rely pretty heavily on
So we've got something called multi-chain validator staking. We've got something called value constraint proof of stake. And these are all designed to, and more of this can be used to create a new
be kind of, we can dive into this in our white paper, which I would recommend everyone listening to this to go check out because it talks a lot about how we intend to secure the multi-chain messaging engine that is quantum portal. And so I would say like most
Most of the features that exist within Quantum Portal are designed to secure Quantum Portal. And then on top of that, just the ease of use for developers to be able to deploy multi-chain DApps and multi-chain smart contracts, imagine you can use this to deploy a multi-chain token standard that balances
that balances supply across networks without having to manually mint or burn tokens. You can create multi-chain NFT standards. You can create lending and borrowing platforms that allow you to loan money on
on one network and get paid back on another, borrow money on one network and pay it back on another. Multichained staking applications where you can stake tokens on one network and earn rewards on another. So really, it's going to be up to developers to build a lot of these applications, but we think this guy is the limit and I think there's going to be a lot
of things that we don't even realize yet that this technology is going to enable and it's going to be really exciting to see what sort of things people build on top of it. Definitely definitely and providing for the infrastructure for other VR
like other G apps for building a secure ecosystem. It's really important for the underlying technology because like all the information that we see today they are just like yeah you can build something on top of it and you have to secure it yourself and like all the responsibility of
So, this insecurity for every user is the head of the shoulders of the D app itself, but you have to secure the infrastructure and underlying infrastructure is really bound. Yeah, totally. And, you know, one quick thing to have this relates to Neon, of course, is we've joined the Neon
Builders program and the first thing that we're integrating with you guys is something called multi swap which is a multi chain deck aggregator that we can dive into in a little bit here but the end goal is to integrate quantum portal with me on so that it allows developers from outside the neon
ecosystem to deploy applications on top of neon, right? So like it's going to make it easier for networks to attract developers because they're not necessarily having to attract the developers to build strictly within their ecosystem. They can do that attract developers outside of the ecosystem. Maybe like, you know,
Rust devs or piteal devs or move devs right to be able to deploy in Neon's EVM more seamlessly and so that's really the end goal is to integrate Neon with quantum portal once that technology becomes a little bit more mature but we're starting off with with multi-swap
which is going to enable people to seamlessly move liquidity over to the neon much more quickly. Which we can talk about here soon too if we want. Definitely, definitely, definitely awesome. Yeah, sure, actually, let's touch on those features.
Why would someone actually want to use Phirram as opposed to creating their own solution? What are the benefits to it? Yeah, so maybe let's touch on multi-swap here and what we're building initially as being part of Neons
really builders program here and why they would want to use multi swap over let's say you know just any type of bridge. So let's look at like what does it look like for a user to want to move assets from one network to another right now. Currently let's say someone wants to
move liquidity or assets from finance smart chain to neon. That user journey is quite cumbersome at the moment. Let's say they have their tokens on their Metamask, they want to go to PancakeSwap and they want to swap it into an
asset that's bridgeable. So then they swap it into a bridgeable asset. That's one application they're using. Then they find out, okay, what bridges are compatible with BSC and Neon. Okay, so they go find the bridge, then they bridge their tokens over. They just, they hope it shows up on the other end because most bridges are using what's called a mint
in burn function which has been the vector for pretty much every exploit that's ever occurred in D5 over the last two years almost. It's like over two and a half billion dollars worth of exploits have happened via this mint and burn functionality that's inherent in pretty much every bridge. So they go find a bridge.
They've ridged their tokens over, they hope they show up on the other end. And then they're like, okay, my first time playing around on Neon, I got to find out where the liquidity wise for this token that I want to buy, likely one of the projects that is also a part of this early builders program with us. And then they go to CoinMarketCap, they say, okay, it's on this deck.
I'm going to go to this decks now and swap it into the asset that I want. So as you can see, they also got to add the RPC to their Metamask and maybe they even need some tokens to pay for gas, so they got to go to a faucet. There's a lot of things that they have to do in order to just take
take part in the neon ecosystem. So MultiSwap basically does everything that I just described on the back end, but on the front end what the user is experiencing is a sort of 1 inch or a uniswap type experience. You can think of a multi swap as a multi chain 1 inch. So it's a multi chain Dex aggregator. So it allows the swapping
of any asset for any asset on any connected network to any wallet. And the way we're doing this is we're going to that origin chain Dex. We're swapping the token into USDC. Then we're using USDC as the routing token. And then so we're
We're bridging USDC, but since USDC exists natively, or even if RAPT USDC exists on another network or another stablecoin, we can map that stablecoin to another without having to worry about minting or wrapping any tokens of our own.
bridge part of multi swap has no operational control over the token contract. So there's no ability for our bridge to mint or wrap tokens, which like I mentioned earlier is the biggest vector for exploits because what happens when you're wrapping tokens? You're essentially you're having to lock
tokens up on the origin chain network in order to uphold the peg or maintain the peg of the wrap-dass set on the destination network. So it creates these massive honeypots, right? So you can't flood the market with a ton of the same token or there's inflation that
puny pots that are being created upwards of tens of billions of dollars in many cases of multiple tokens. So we're just using one token and because we're not having to maintain the peg of the rap data set because we're not wrapping any assets, because USDC exists natively or at least some stablecoin exist natively that we can map it to.
So that means that there doesn't need to be any, there only needs to be enough liquidity in these bridge pools to support the volume that's being transacted across the bridge. So, you know, we could keep like at most maybe a million in liquidity on these bridge pools, which is a lot less than billions. And so it doesn't really attract any
bad actors to want to come in and say, "I'm going to spend a year trying to figure out how to exploit this massive honey pot." So from an operational security standpoint, and just from a technical security standpoint, we see multi-swap is a much safer solution to moving assets
across networks because we don't implement this mint and burn or lock and mint mechanism. So then after that U.S. D.C. is bridged over to the destination chain, then it's swapped into whatever the desired asset is that the user wants on neon and it's tapping into
to existing Dex liquidity. So that's how we're decentralizing even one step further. We're a Dex aggregator, we're not a Dex ourselves, so we're not actually hosting any of the liquidity ourselves. We're tapping into pre-existing Dex liquidity from pre-existing DeFi platforms on the connected networks.
So this product not only makes it easier for users to move assets much more seamlessly across networks and reduce the layers of friction that exists between young ecosystems like Neon and new users, but it also helps pre-existing projects by way
of volume and encouraging TBL, since we're not the ones posting the liquidity. We're not trying to reinvent the wheel. We're just trying to provide users the best route to have their token swapped from one network to another, in this case neon, of course.
That's multi-swaps main advantage and that's the first thing that we're building on Neon when there's going to be a lot more to come. But we think this is a great way to kick off their relationship with Neon because in the beginning one of the biggest hindrances for a young network to gain adoption is the fact that it's so difficult to
move assets from one network to another. A lot of times people just like, "Ah, this new ecosystem sounds awesome, but I don't want to go through all the hoops that I have to jump through just to test out some, you know, defy platforms or purchase a token that only exists in that ecosystem." And so this is going to make it a lot more
easy and kind of get rid of a lot of the excuses that people have not to participate in new ecosystems. That's great. That's great. That was a really awesome explanation. And I was actually going to your docs and I came across so like how the liquid is being handled so
the bridge pool and it was quite interesting to know that the surplus liquidity that is there on one side of the bridge can be stored in the multi-site space instead of just the bridge pool so that it should not be our honeypot for the hackers. Yeah. So yeah it was actually quite interesting to know that because
Yeah, definitely like people are very skeptical for purchase because it's really prone to attacks due to high liquidity, you know, just filed up on one end of the bridge. So it was really interesting to know. My question was like, it was said that
The token administrator for any network is responsible for maintaining that liquidity. So how often does this function has to be carried out? Is there any protocol for it to determine that the liquidity needs to be regulated now or like how does it work?
So I think there's an important distinction to be made between a bridge and most change swapping protocol. We're not trying to help people move assets from one network to another just so that they can bridge asset A for asset A. On a lot of bridges,
people are taking a token that doesn't exist on another network and they're bridging it over and now they're the first person to hold that token on another network and then they realize when they're wrapped version of the token they get it on the other network they go to try to liquidate it and they're like wait there's no liquidity that exists in the
look at the token contract and they're like, oh, because I'm the only one that holds it. Right. And so then they have to like bridge that token back or wait for enough people to bridge it over eventually so that there's enough liquidity so that they can actually liquidate. And so it's just like this problem of fragmented liquidity that exists because of the
way that we originally designed bridges, which in my view, in Farmsview in general, we just think that bridging was kind of created on a faulty pretense. And so we're trying to reimagine the way that assets are moved across numbers. So when you ask how often does liquidity need to be managed?
We're not responsible for minting any tokens. People should only use multi-swap for swapping into the actual asset that they want. It removes a step for them to bridge an asset over and then hope that there's liquidity for that wrapped version
of the asset to swap into the desired asset. They can just swap directly from the origin chain to that desired asset. They never actually have to hold this wrap version of the token because in most cases that version of the token doesn't even exist. But then, you know, if you're asking about how do we
managed liquidity from the USTC standpoint, that's a different story. So that does need to be managed a little bit, but that's just like making sure that there's enough liquidity on the bridge pool in the USTC. It's single asset liquidity. It's not like the way we imagine liquidity on index where there's a liquidity pool.
of a pair. It's single asset liquidity and like you know you read in the docsturity you can actually remove that liquidity if it gets too high on one network to multi-sixate. Right. Right. And so if it gets too low on that one network then you just remove it from the multi-sixate and you add it back to
the bridge pool. And so that's kind of how we manage the routing token liquidity. But in terms of managing liquidity from like a wrapped token standpoint, that's not even something that we're trying to do.
because we're trying to remove that step altogether for users. Right, makes sense. Okay, so now that we've learned about some of the features transferring tokens in and out and how you
you guys do that. Let's talk about your integration to Neon. As you guys have mentioned, you guys have been building since 2018 and you've built on multiple chains, EVM and non EVM. So the drawing for my experience could you share some insights on the process of integrating
with the owner, how was it? Was it easy to work through it? Yeah, actually, and I'm not just saying this. I've had to kind of be the liaison or the conduit between the developer support programs, developers themselves on these different networks, and all
developers, that's one of the main roles that I play at Ferram. And so I've done this with multiple networks and sometimes it's easy, sometimes it's not, a lot of times it's not. I will say like the communication between the Neon team and our dev team
has been really really good and it's been a very seamless process so far. We actually had such a good feeling about Neon that we started the integration prior to us even being part of the Early Builders program officially just because like you know
We saw you guys heading in the right direction, typically when we are integrating more established networks, we're seeking out grants in order to justify prioritizing these integrations in our backlog because there's so many networks out there. So we took a very different approach with Neon.
by starting prior to even getting whitelist in the early builders program. And that I think is a testament to the team over there with you guys, you guys are really good at making people feel like they belong over there.
and really good at communicating between your guys as dev team, our biz dev team, your biz dev team and our dev team. It's been a very seamless process and there hasn't been any red flags since the onset of this where I've been like, "Man, I don't know, I don't know,
know if communication is going to run dry and you guys are super quick to respond and it made us feel really, really secure with moving forward because we're putting an entire team of our integrations team on this and so it's like if things don't go right, we just waste it a bunch of time
and only to find out that it's not going to work out and that's never even crossed our minds with Neon. So it's been a really, really, really positive experience and just want to thank you guys for running such a tight ship over there. Especially in early stage projects or in early stage network I should say.
a lot of times that kind of stuff takes time to really dial in. But you guys have dialed in that side of things from a very early stage. And I hope that as you guys scale and as you guys onboard more projects, that same amount of attention and
care still holds true because I think that's such an important part of onboarding to builders and onboarding developers to the network. So just keep doing what you guys are doing and you're going to have a very bright future I think. Thank you for the long.
Thank you so much the characters. It was a really real pleasure working with your guys as well. I was working with you guys for a long time when I joined Neon and it was a real pleasure working with the attack team.
because as you said, the wait was from our side, it was from your side as well and there were prompt responses and there were prompt changes and yeah it was a really small integration so yeah it was fun working with the guys. Thanks, Shruti, that's good to hear. Yeah, it's been fun.
Yeah, it's awesome to hear like everything's been working very smoothly and I think we owe it all to Nikki and he's really fast as well on the responses. So, I think we have quite a little bit of an audience like nearly 20 people. It's not much right now, but I think
more people will listen in half the words. But like for the people who will listen, and if they're thinking about like leveraging phirram and building on neon EVM or maybe even another chain, what piece of advice would you have to offer them like to make it easier for them? - You know, I,
I definitely think like just getting a proper channel of communication is probably first and foremost. Like, don't just try to go in and do it on your own. Like I mentioned, Nia's got a great team of people helping you do this, so leverage that. I think that's probably the
The biggest thing that I could recommend is like, you can go in and read docs and, you know, Neon's documentation is also fantastic, which is one of the things that we also look at when we're scoping out whether or not to build on a network. But still, you know, like even
with fantastic documentation and error code messaging and all that good stuff like you still want to have that direct line of communication so you know Neon offers that and so leverage that get a telegram channel, Slack channel whatever the case may be and and put one of
of one or two of you guys as devs or if you're a solo dev make sure that you've got a channel communication with them and they've got a team of people who are like I mentioned really quick to respond and then also leverage the community there's a ton of other really good builders out there that are built
in neon and you can leverage that as well. So my point here is just use the resources that are available and instead of like that's the beautiful thing about open source and Web 3 is like you're not
I'm not on an island all by itself. There's a ton of people out here willing to help because we're just trying to make this space a better place. So yeah, I would just say to leverage those connections and leverage those resources. Definitely, definitely.
built in Web3 and yeah I mean there are some of the progress that makes it that would be really happy and willing to help you in myself like Medians are open please reach out and whatever you're building whatever projects you're building it would be amazing to listen to your ideas to help you move forward
on New York EVM and yeah I mean just keep building okay so now like because like we like we understand that firm has integrated or is in
grading or I think nearly as finished grading with the NABM. So what do you think this will mean for future builders or users coming in? Do you think it'll make the onboarding easier? And what other things will you might
might you integrate inside of Neon in the future from like your stack? Yeah, so I definitely think that it's going to make things easier, especially from a user perspective, just because of everything that you know, it kind of outlined earlier with how this product reduces layers of friction.
for users to join new ecosystems. So it gives them a single interface to move their assets from one network to another rather than having to go through all of these hoops and use three or four different decentralized applications on various networks just to move assets over.
This just gives them one interface. If you're saying, it's too hard to move assets from one network to another now. You don't really have an excuse with multi-swap because it's just so easy. I think from that standpoint, it's really going to help onboard new users.
From a builder standpoint, this product really helps existing Dex's. I know there's a few Dex's in the early builders program who we're going to be talking with and integrating their APIs so that we can actually integrate our
routing engine, which is called fiber, pharom interblock chain express routing engine. And so that's going to be integrated with different dexes on the network so that we can actually tap into pre-existing dex liquidity. So for those builders that are building those dexes, that's going to, you know,
help increase TVL and volume on their platform. So I would say those those are the two stakeholders that will probably be most benefited by this. Of course, me on the network itself, just being able to help attract more liquidity to the network too. And then in terms of like what else we're going to need
bringing in terms of our tech stack, we still have our suite of blockchain as a service solutions as well that can be provided in a B2B fashion to projects building in neon like our state as a service solutions or iron investing solutions. We actually just created a really
really cool product that we haven't even really announced yet that helps DAO's manage stakes liquidity on snapshot. So like you can actually like track where stake tokens exist, which users are staking, how much they're
staking so that it can be counted in like a weighted voting fashion. So that you're not just having to only track tokens that are held in wallet. You can actually track tokens held in a staking contract across different networks. So it's this like multi chain snapshot tool.
that track stake balances across networks for voting purposes, which is really cool too that we can offer to people building in the neon ecosystem as well. So it'll help DAO's too. So there's a lot of stuff that we can bring to neon. Multi-swab just seemed like the most imminent thing because it
allows a more seamless way for users to take part of the ecosystem from the onset. But yeah, I mean, there's a slew of other things. And then of course, eventually, when quantum portal is a little bit more mature, we'll be integrating Neon with quantum portal so that developers outside of the ecosystem can deploy applications on Neon very
seamlessly. So there's a lot to be excited about with this partnership and you know multi swap is just kind of like scratching the surface. Man I love that douse snapshot. Staking snapshot, that was really cool. I think it like it really opens up.
Possibilities for like future builders and what they can build out. Yeah, totally snapshot just actually merged the strategy yesterday So it's pretty cool. We haven't even announced that yet, but maybe I wasn't But hey, we got a little kernel of information for all the pharaoh listeners out there now they have some some
some alpha. But big shout out to our CTO Taha bossy for creating that he is working really hard on that over the last couple weeks because we're creating our Dow. So a lot of times these products kind of sprout up out of necessity for ourselves and then we're going to
to be a really cool tool for other people to use. And so it kind of turns into a product that other folks can leverage. So yeah. And devs are epic big shout out to all of them actually. Yeah, totally. So like well, like
While we're here, let's take some questions from the audience. Guys, if you have any questions from Shirti or Nick, please ask away. Like this is your moment.
Yeah, it looks like no one really wants to ask a question. I think everyone's a little shy. Don't be shy guys. I don't I don't bite. Yeah. Okay, so if we don't have any questions for
Today, then I guess we'll end it off here. Thank you guys so much for tuning in today. You can catch Firm at @FirmNetwork on Twitter and you can catch Neon at neonlabs.org or Neon Foundation. And thank you, Shruti and thank you Nick for tuning in today.
See you guys later. Yeah, thanks so much for having me on today both you guys. This was a lot of fun. I really hope to see, you know, our communities merge a little bit more to like I know a lot of the people in our community are really excited about me on so I'm sure you're seeing some new faces from the firm to me that they join in up over there.
there and we hope to see more of the neon folks in the farm community because it looks like we'll be working together for some time now. So we're looking forward to the rest of this and thanks a bunch for having me again. For sure. Thank you guys. Thank you all for joining and having me.