Supercharging Blockchain Interoperability with Reactive Network

GM, GM. Welcome to what's going to be another fantastic episode of DevNTell. So if you didn't know, DevNTell is a 30-minute podcast held every week allowing founders, hackers, and anyone in between a stage to showcase their products. And today, I'm ecstatic to welcome Rong Kai, who's the CEO of Reactive Network. If you didn't know, Reactive Network is an EVM-compatible execution layer that allows developers to create dApps using reactive contracts. So if you stick around for today's episode, you'll see Rong give us a deep dive into how Reactive Network is redefining Web3 automation, including exploring event-driven smart contracts, securing AI integration, and the future of decentralized infrastructure. All right, let's get into it. But first, a word from our sponsor.

GM, GM. Welcome to the show, Rong. I'm ecstatic to have you on today. My pleasure. And yeah, thank you so much for taking the time out of your day to come chat with us. I know we have a lot of great content to go over today on Reactive Network. Before we get into that though, would you like to give a brief introduction about yourself for the crowd?

Yeah, definitely. I just realized your background's Mordor. I've got the map of Middle Earth behind me. Yes, Mordor's behind me. Yes. Sorry, I got distracted because the eye staring at me and I was like, oh, wait a minute.

Anyway, yes, thanks for having me and it's a pleasure to be on the show with you and everyone who's watching. Thank you so much. My name is Rong Kai. I am CEO of Reactive Network. And I've been in this industry since 2020. A lot of things have happened. I was in Binance for the first two years, I was doing actually BSC Accelerator Fund and that's how I knew about my current team and from 2021 onwards I joined my team and we initially were doing real-time data and then we were in indexing and then now we found that we did Reactive Network together. So the journey has been quite a thing. I'll probably share more if you're interested, but of course today we're here to talk about tech and I'll share more about Reactive Network as well.

Yeah, yeah, for sure. Yeah, I mean, if you don't mind, I'm always curious how people found themselves in tech and Web3 and the Web3 industry in general.

Yeah. So my story is probably very out of the norm, so to speak. Before 2020, I was a senior police officer in Singapore. So I was in law enforcement for eight years. I was the head of operations of a division, a thousand officers, I was running the entire division police stations, basically major events and all that kind of stuff. I was happy doing that, but of course in 2019 I have a young daughter and my wife told me like you need to kind of re-look at your priorities because I was working easily 70 to 90 hours a week. And so I switched industry, I went into blockchain because I kind of liked what the industry is doing, but I think what for a lot of people who's working in industry, not just buying crypto of course, if you're working in blockchain, I think one of the things that most attract you is the freedom that you get. Most companies are remote, even if you're not remote, you go to the office, it's very like the ethos is there, very decentralized. A lot of freedom in terms of decision making and so on, which sort of attracted me to this industry as well.

And then went to Binance, I was lucky to get an introduction, I went into Binance, I ran the 100 million BSC Accelerator Fund with together with a team. We looked at 500 companies, we invested in 31 when before I left. So that was a very, very good exposure to not just in the investment side of the house, but actually understanding the tech. Because when you talk to them, they tell you they pitch to you and you hear everything they trying to build this, trying to build that, and why is this so important because a blockchain ecosystem needs this, it needs that and so on. So that was really a kind of a foundational crash course that I had in blockchain and the technology and it really helped me in transitioning into my current role. I first joined as COO and then now I'm the CEO since 2023. My company we were doing initially like right at the beginning when I was in Binance, we actually invested in in in my outfit. And we were doing back then a real-time sort of data feed. We pull data off blockchain, we process it and in real-time we send it to you wherever you want. It could be on email, on telegram, or somewhere else. Or you can do something with it, at back end you want to automate certain things. But that was still like pulling it off-chain and coming back on-chain again. And then subsequently we needed historical data, so we became an indexer, but indexing wasn't what we wanted to do. We wanted to do like we want to be really, really good at real-time and we came back in this space and we sort of created Reactive Network. I'll share more about the problem statement and all that on Reactive Network later. I have a very short deck of slides to share with everyone. But very long story short, the impetus was really because we felt that anyone building on-chain decentralized applications, DeFi, whatever it is, you kind of still apply the very old model where you pull data off-chain and come back in again, pull data off-chain and come back in again. It is a very roundabout way of doing things if you look at it from a data standpoint. Anyone who's building on Web2 will just think that it doesn't make sense. And they seem to take things for granted that you'd be like wait a minute, you guys are still not doing this, what what era are you in? Are you still in 1970s? And that was what we felt as well, we're like can we do something about that? And and we created Reactive Network sort of to address that.

Amazing, amazing and yeah, um, that's like you said, quite the unorthodox way of getting yourself into tech, but your experience in the police force as in a leadership role, I mean naturally ramped you up for for what you're doing now, which is amazing to hear. And yeah, like you said, I've I've looked into Reactive Network a bit, it looks like it's solving a real gap that did exist in the blockchain ecosystem where basically you were at the mercy of basically just indexing events to be able to react to things, but it seems this is going more so kind of like a parallel to like SNS, SQS, being able to just react to events, which is pretty cool. But I don't want to spoil anything. I think this is a a good segue if you want to bring up your bring up your slides and we can get into it.

Definitely. Let me share my screen. Here we go. And for folks who are watching us live, if you have any questions for Rong as he's going through his slides or anything that we're going through, please feel free to ask and we'll get that answered for you. All right, stage is yours.

All right, thank you so much. So I wouldn't take too long. This is like a dialogue and I do want to hear from people who's listening in as well and interact with us and feel free to ask questions. So I'll just share really just to explain the technology because after all this is new. We actually created the world's first interoperable execution layer. So it'd be like what's this? What's execution layer? Is it a Layer 1? Is it a Layer 2? It's not. It's not a any layer like that. If you strictly want to put us like a layer, we're kind of like a 0.5, but when you tell people you're a Layer 0.5 they'd be like it doesn't exist, what's this? Yeah, because it's new. So essentially this is a gap that it's not just a opportunity, but it's something that we ourselves feel very strongly. So if you look at the left, the Web2 experience is pretty straightforward. They deploy a code, the code react to changes in tech component state directly and it performs function and it goes to applications. What it essentially mean is that if you're building an application on the internet, on mobile phones, and so on. You deploy a code, you expect the code to react to things happening. If you connect a data set to it, it will see the data changing and it knows what to do based on that. Very straightforward. It's a function that has been like you know if this then that, it's been if you learn coding anywhere it's been around since a long time ago, maybe in the 80s or even before. But the Web3 experience is not. It's interesting, but it's historical. I won't go too deep about why it's like that. I'll just show you like this is the current state. You deploy a code on-chain, so we talk about smart contracts, smart contracts are code that's on-chain. It cannot respond to on-chain events, only states. So it can it will know that a state basically is like block by block. It will know that at this block this is the current state of all the wallets and everything that's happening on it. Your wallet has say 10 ETH right now and the next block your wallet has 9 ETH. Great. What happened to the one ETH in between? It doesn't know. The smart contract, the code itself will not know. And of course blockchain itself they cannot take data or respond across blockchains. They can't cross because blockchains are supposed to be kind of self-contained, sterile system. It must have consensus. That's why it it cannot just take data just like that from other chains organically.

And but business being business they we need to solve this, right? And for the longest time people be like hey this is actually solved right now. We do this, yeah. We take the data off-chain, we standardize it, we feed it to a Web2 based code. The Web2 based code which is on the left will then will just do all this and it will come back to the Web3 node and then it it respond accordingly. A very roundabout way to do this and for most of the time because we need indexing for historical data as well so we kind of like we just latch onto it and and we want to do this this way. But the problem is and you you should talk to a Web2 developer and and some of you who are on the Web2 side you you probably will be nodding your head with me is like yeah. Why are we accepting this? We kind of just accepted it because it has been we've been doing this for close to a decade, but it shouldn't be this way, should the experience be closer to kind of as seamless and possible like Web2. And I think that's something that is a question we ask ourselves like right at the bottom. Can we can we push Web3 a little bit closer to mass adoption by making the the development experience as seamless as possible in Web2. And so we we actually created Reactive Network to do that. So rather than having initiated action that goes to a blockchain A and because there's no cross data and no interaction to cross blockchain B, it could be the same blockchain actually. You could see blockchain A and blockchain A on the left and right, it's still the same, but the the idea is still still remains they don't interact because they don't respond to the data, the events that's happening, they only respond to states.

So rather than do this, we pull everything into external indexer and move with external code right, but it's not just external indexer with external code. There's because you need to pull it off-chain and come back on-chain again behind the scenes there's a lot of other things, data storage, transaction signing, synchronization, etc. Each component has its own point of failure. You need all five to work. Actually it could be six or seven depending on your own tech stack, but this is the more very simplified version of it. And one fails the whole thing fails. And of course there's cost of setup and you need to rely on someone else providing this service to you if you don't want to do it yourself. And what we do is we put it on-chain instead. If you can observe and we can interact a a vast a majority of on-chain use cases will be solved very organically, remains on-chain and you don't have to kind of rely on centralized point of failure.

I think very importantly is that we are not saying that we don't need indexers anymore. There's a lot of use cases where you need like to throw through whatever's happening on-chain, you want to look at the past historical data, you want to look at big data. Yeah, of course indexing is actually very important, we we we did indexing, we know. But for I think a lot of very on-chain reactive, responsive things that's happening, especially with smart contracts. Actually what you see on the right, which is what we wanted to do completely there's autonomous and these reactive actions that's on-chain. Reactive Network actually solves this for all all of these kind of use cases. The value we want to bring is basically this, we want to reach a stage where reactive smart contracts will underpin the complex reactive functions on-chain. Because right now if you are building a Web3 dApp, very often the very first version, the Alpha version, pretty straightforward you come in, you build, you have a lot of things that's off-chain, you have some things that's on-chain and you make sure that the whole thing talks and it interacts and you have a Alpha, you have a MVP and you push it out right and people start interacting with it. Great. And your second iteration, your third iteration, that's where the real problem comes. Because each time you want to iterate you you don't just need to solve one part, back here again, you need to solve all the parts. That cycle takes a longer time, way longer time actually. Maybe if you're building this completely off-chain you're on Android or Apple Store for example if it's a phone application, maybe each version of updates takes you a few days if you're fast, maybe one week, two weeks if you're slow, so on on average. But on Web3 it takes could be months to have the next version. That's that's that's a significant jump in terms of of lag time, development lag time right. Why why is Uniswap on version 4, why are they not yet on version 30? It's because of this. This is it, this is why.

So when we look at the pace of development, this is a major blocker and we want to underpin this complex reactive functions on-chain. So we enable more complex smart contracts, both conditional and reactive, and then we close this interoperability gap for applications. Once it happens, both the user experience and the developer experience will be streamlined and and then we can start powering really powerful things especially intent-centric applications and so on. We can give a certain intentions, we power that reactivity part of it. That's the whole point. And then hopefully it will lead to to mass adoptions. This is my last slide actually. It just explain how it works and I think after that we can we can share more. But very simply this is a very simplified diagram of how it is. Things still happening on on source chains on the left, user initiated action goes to smart contract and you click approval, approval, approval, you know that sort of stuff and it goes to the blockchain and blockchain execute and it creates a event to say that yeah, I've executed it. The reactive smart contracts, if it's built and it's observing across all the states across all the blockchains that we are connected to, you observe all these live events right, you'll retrieve the histories live. It will compute the data and execute the contract logic on on the smart contracts if it sees events because now it can see the event. It sees the event it will and and my event and my own code tells me that if I see this, it means the certain parameters, execute something else on-chain. So rather than do this off-chain now you're doing it on-chain. And then you publish the results and it creates yet another event because it's publishing the the results which is like a prompt on the the destination chain to say that hey, can we do something? And then user gets the result. It it basically bypass the current restrictions on all the blockchains that we have which is the if you are building on Ethereum, Polygon, any of the blockchains, they they're not they're not reactive.

We don't want to create a Layer 1 that is reactive and say that yeah now we are competing with you guys. To me, yes, I mean we can possibly do that, but that leaves out everyone else that are still on all those systems. What we wanted to do actually is why don't we create something that benefits everyone as a whole. And that's why we created a data execution layer, not a Layer 1 or Layer 2. Because we wanted this to benefit everyone regardless of blockchains, regardless of of even the code behind it. At the beginning we are only supporting EVMs, but in fact non-EVMs are probably coming pretty soon. We we were predicting that to be next year, but it might be coming this year and that's something that's extremely exciting for us.

So this is it. This is this is basically what it is. I have one which is really on use cases, but rather than you know go through it one by one, I thought why don't we have a conversation. I don't I wouldn't just show this, I think it distracts us from the various different use cases, but I wanted to have open conversations with you guys think about the possibilities and so on and I can share more on who's building on us right now. Like right now we have more than 20 what we call RVMs, Reactive Virtual Machines. Each RVM is basically one use case, and under it it can have anywhere between one to a dozen different reactive smart contracts on them. So I'll stop sharing and I think we'll come back to the floor.

Yeah, yeah, yeah this is really neat. I just want to double click on the the smart contract bit a bit a bit more. So it seems like at least from your diagram, the reactive smart contracts are kind of like a middleware if you want to have like a Web2 parallel that kind of do something before like in between going from chain to chain. And does is there so does there have to be a particular smart contract on either side that basically accepts whatever the message is from the reactive smart contract to be able to send it along to wherever it's supposed to go or?

Yeah. I mean we basically build it as a sort of a bridge between in it could be the same chain right? It could be Polygon and then back to Polygon for example. But the whole point is to bridge this capability gap. There's a lack of this capability, you build a smart contract there and it's just it's just waiting for instructions. It cannot see all these events that are happening. So we created a middleware is kind of a good approximation to sort of what what we are. But I think right now, this is a problem that exist since the very first days of smart contracts. And how people do it is they put it off and coming on and they said this is like a middleware. If it's put in the middle and it but it put it off and then coming back on again chain to sort of create this loop because the business use cases tell you to do it. You need this to be automated, you can't have a person clicking 24/7 all the time thousands of times a day. So you need a a a machine to do that. And what we did is rather than solve it at a it's basically like an application level where you put it off and on again or the basically the next level below it and put it on and off again. We actually go straight all the way down to the smart contract level. It's like oh so we're down to the code that you write on-chain and we solve it there. By doing so by doing it deeper, it creates basically a data flow that's a lot more organic because code is code. Code is basically humans with an intention, you write it out in code that computers can understand and they'll execute it and do it for you some really complex kind of things that you want to do on-chain. Think of all the kind of as complex as you want the kind of financial transactions you want to do on-chain. That can only be done with a code. And if the code is interacting is very limited at that level, it has to jump through into another tech stack and another code that's on Web2 for example to talk to a Web3 code and they are all written in different languages and that means you're introducing a lot more things. You're introducing a way for the data to get there, you're introducing a way to standardize the data, you're introducing a way to translate the data and so on. And what we do is no you cut all of that, why don't you make it a solution that's native at that level and the code is just to them they're just talking code to code. I'm I'm talking English to you and you completely understand me. I don't need to introduce a lot of in between.

Gotcha, gotcha. And do Solidity developers have to learn anything new or is like are the reactive smart contracts fully EVM compatible?

It's fully EVM compatible and you can just write it in Solidity. That's that's why we we we make it this way. We started with Solidity because I think Web3 at the end of the day yeah there's there's Rust developers and so on, but majority right now is is Solidity. We basically just take the majority as a solution we put it in. I see this having relatively long long longevity even you know maybe Ethereum in in the next five years they're going to move away from from Solidity. That's okay because they are never going to like stop supporting the legacy side of the house right? You can't just cut it and then restart completely from scratch. You need a sort of process to move towards a certain uh uh areas and that's also what we're going to do. We're just going to follow industry. At the end of the day, maybe eventually there will be other Layer 1, Layer 2s they come out and say that they are reactive smart contracts right on at the beginning. Maybe they take our technology and they morph into certain things. That still means that our machine has been achieved and maybe we do it next time. But right now, vast majority of blockchains, probably all of them in fact like if you write the smart contracts they are just at that. I mean there's a historical reason behind it. If you look at it from a non-technical standpoint if you are not technical it's okay you'll understand why it coming from. If you look at it, blockchains were created at the beginning Bitcoin right? It's just no you giving me Bitcoin and I giving someone Bitcoin. It's meant to be that. And then you slap a layer of coding on top of that. This is what happens.

Yeah, exactly. Once things become a little bit more interesting is like then then you open like a whole new can of worms, but it's like it's for the best right? It's like that's how that's how we push innovation. Um, and certainly what you guys are doing here. Just curious like um, are there any added gas costs um if there's a reactive smart contract in between?

Yeah. So so the gas will be paid like because I'm structured as a decentralized, well architecturally I'm a blockchain as well right? So if you have a reactive smart contract on us, the smart contract by observing the events they don't need to pay gas, but it's like the acting. Oh I see something that that is relevant to me and then I act. That that creation that act will will need gas. But right now, I mean it's super cheap. It's like fractions vast small fractions of a cent to react to things. Imagine you're paying for example 500 bucks to a indexer a month to to do the same thing. And then on us maybe in a month you're paying less than a cent sometimes it depends based on use case how how data heavy are you. And even if you're really data heavy I think it's not going to be much. And and that's why and and and even to us it's already energy efficient it's because you are we created a system where they are inherently spotting all the events without needing to pay money. Like you know the reason why indexers need to charge so much money is because they spent a lot of energy and resources and coding power to pull data off and sort it out for you before they even read it. But what we are doing is we leave all this completely on-chain in this native format and our code being native to it are already seeing all of this, I don't need to put extra power actually it just sees the whole thing. So straight away we make that part free. And all it only we only charge for the second part which is oh I see events that's happening and this is relevant to me and therefore I need to do something about it and the reactive smart contracts pays a fee and it'd be like oh okay then who's paying the gas. Yes it's not the human who's paying the gas, the human gives the smart contract a a wallet basically and the smart contract now has its own money. Imagine this this robot that that's smart and it has its own money and it will pay if it needs to act on that.

Makes sense, makes sense. Yeah, this is very, very interesting. I'm curious to hear you mentioned it briefly in your slides, but what what are some interesting use cases you're seeing built with reactive smart contracts?

It's a very good question. So I think right now we we have a few that that we are extremely excited about. For example, World of Rogues, they they're using reactive smart contracts to really fuel the automatic sort of interactions within their their game right. It is a game which instinctively tell you that if you're Web3 game and you're a legitimate Web3 game, a vast portion of your assets and coding based and and all that is off-chain, it's naturally off-chain. But the interaction with Web3 is where that part comes in and how do you automate that with the additional complexity that majority of your your digital assets are actually on Web2, off-chain. And they're coming in to use reactive smart contracts to really resolve this this roundabout. So so to me, I mentioned them right at the beginning is because it's not just using us to solve like Web3 to Web3. You can use us to actually make the the intersection between Web2 and Web3 a lot smoother as well. Because if you constantly have to jump between Web3 to Web2 and jump back again jump jump out in, out, in, out, in. It is a lot more inefficient where comparatively maybe you're just Web3 to Web3 and only at the final point you come back to Web2 and then that's it and then so it reduce the amount of back and forth that you need to do.

Another one that that we are really excited about is Smart Trust. They're using us to basically automate the they're doing basically a remote contract escrow service, escrow service. So what it means is that if you are a remote worker or contract worker it is relatively common to hear about someone being scammed out of like a employment contract. You do some digital work for someone who's based in a completely different continent than where you are and it say that oh sometimes you sign the contract, very often it's written as like governed by the law of wherever the employer is. Or maybe you're the employer and you put yourself it's okay maybe you're Canadian and you say governed by the laws of Canada, province of British Columbia. And then this guy is is based in Venezuela and he didn't do the work. And yeah you can go to the court to try to do something about it, but the guy's in Venezuela. How are you going to get him? And so on. Most often is employer to employee, but sometimes it's the other way around. And they have actually tried to use it to kind of solve escrow kind of functions where maybe the transaction the money if you do this work, I will pay you three thousand dollars. And I lock it or I do something about it and it's in a trustless environment. And I can disagree and you disagree, you say you've done the work and I'm the employer I say no I I disagree. And then who's going to arbitrate between this, right? They've created a service that uses Web3 to sort of solve this in a trustless manner. And sort of to have a neutral party to to kind of I wouldn't say take sides, but sort of to assess the situation and then objectively say that the work is done or no the work is not yet done and so on. And then when you lock it up is it just going to rot? If if it's like fifty thousand dollars or a hundred thousand dollars? Not many companies are willing to lock that money up. And they created a system where where this is resolved. I'm not going to go too deep into it, if anyone's interested you can look up Smart Trust. Smart without with just one single T in the middle. So it's a Smart Trust combined into one word. Go and take a look, it's very, very interesting how how they want to use it to resolve. And they're using reactive smart contracts to really bridge that automation between the things that's on-chain to on-chain right? Because there's a certain amount of funds locked in the trustless environment, who's going to automatically release it and so on. Very amazing kind of use cases. And there's more of course, but we we recently are going to start funding a DeFi use case as well and we previously we have another one that came from our hackathon and we fully we actually funded him to turn it into a like a actual working product that's on-chain. It's called Reactor and it basically helps you do stop orders across all the kind of DeFi that you have. There's a lot more as well, actually they they have like liquidity protection and so on that they they want to put it in. So the whole idea then is use it and you are it's no-code like if you're a typical user you don't need to know coding, that's the that's the best. You go in you be like I want to do stop orders. Some places have, some places do not have. And some sometimes you want liquidity protection and that to me is is critical. And how do you do that? Use a reactive smart contract and it deploys for you, set the conditions, if things happen the smart contracts can detect and it will help you do whatever you need it to do.

Wow, yeah, those are some amazing use cases and there it seems like there's a whole ocean of opportunity to build a bunch more. Um, for the developers that are watching us here today, what what would you recommend is the best way for them to start playing around with and and learning Reactive Network?

Um, I think the best way to to really start looking at if you're a developer obviously, look at our documentation. Because our documentation didn't don't just have like a typical set of rules, we actually have an education section. Like an education section assumes you're a developer actually, you're like you know Solidity, these are the basics, you know what we are talking about, and then we teach you how to start from from zero to one. And to me that is one of the things that when we were building this, it was still doing testnet, I I make it a very strong point to my developer team like you guys need to not just have the docs, you guys need to have the textbook to the docs. Like and and the education system and sorry the education segment is also not just textbook to the docs, the education segment is actually like the teacher teaching the students. This is how you do it. Because I wanted people to to lower the the entry barrier as much as possible, come in and learn. And so to me that is probably the best start. And whether you're technical or not technical, I think the best way to really see this effect for yourself is check out Reactor. We will actually have more publications about it next week, I think. But right now it is already live, it is working, I think it's reactor.in like reactor in and go and take a look. I do need to double check if I got it wrong, but I think it's reactor.in. And oh no, it's not reactor.in, but I'll I'll share the link with you separately.

Yeah, yeah for sure for sure. And I I love I love that you guys are taking a lot of care in your docs because a big meme in the blockchain Web3 industry is that docs are usually quite skimpy. So the fact that you guys are putting in the detail and the work into that is is fantastic to hear. And um, are there any grant opportunities um for builders who might be um interested in pursuing a longer-term project in the space?

Yes, I'm glad you asked. We have a Dev Fund. It is of course denominated in Reactive, in REACT our token, our coin. But we actually when we created this we set aside like a huge fund that is meant to incentivize developers building using Reactive Network. And the best part of it is that it is a grant, which means I'm not taking any equity, any so if you want to create a token I'm not going to take your token, I'm not going to take anything from you. All I need you to do is prove that you have your milestones, you are building towards it, you are building using Reactive Network. You have a great use case, you have a great like you mean to really contribute to Web3, we give you that grant. And as you meet each side of the of the milestones we we pay out according to that. So I think it's extremely attractive to especially developers, really you're either starting or you're already in the midst of building something. Like please take a look at it, we have a Dev Fund. You can you can see the Dev Fund on our website as well. By the way jumping back to earlier I was talking about the Reactor. I I've sent it separately to Narb, but it's actually thereactor.in. So you can you can check it out. Thereactor as one word and .in. You can check out that place. I think we we we're working with the developers working on it to to revamp it a little bit more and I believe the developer is actually trying to put like AI to to really make things a lot more spicier over there as well. So I I think it's going to be completed next week. I'm sort of like doing a pre pre marketing so to speak, hey take a look at that and it's for someone else project, it's like a developer that that we previously fund them and we continue to to make things better because we feel that this is actually a very good entry point not just for developers but also for non-developers because it's completely no-code you just click and then it deploys for you.

Awesome, yeah, and we we love the alpha on the show. Um, and is is there anything else um that you might be able to share around the road roadmap um of Reactive Network?

Yeah. So for those who are not familiar with us, we launched three, well actually now it's about four months ago, in March. We launched in March and we basically in that time I think network now is completely stable, it's good, we've started we were connected to we during that four months we connected to Hyperlane and then Hyperlane you know they have that six dozens I think about six dozens different networks that they they are on. And of course through us and through them you you can actually react as destination chains to all of that as well. But on our own we are also continuously connecting to new network and that's something that is extremely exciting for us. Like very just this week we announced that we have integrated Hyperliquid. There's going to be more. I think what we are focusing right now are really the chains that have the most potential for a developer. Like I want to be there because you know why why is it? And if you as a developer you want to be on whatever chain, we will make sure we will support that. And we are looking at some of the major non-EVM chains as well, and very likely they should be coming soon actually, that's something that my CTO Danny, he he didn't give me very good vibes for some of this. Obviously we don't promise anything because with development you guys know as well sometimes things can can come your way and then things are delayed. But right now I think we have a brilliant team and things are going faster than I expected, which is always a good sign.

100%, always is, you you always want to be ahead of the game there. Um, but yeah, looking forward to um basically seeing people start building um cool cool stuff with Reactive Network. And yeah, as Rong mentioned, if anyone's watching here today and is curious to take a project a little bit further than just a weekend hack, they do have grant a they do have grant program available so definitely reach out. And I guess um on that on that part, um if people do want to reach out or have questions, what's the best way for them um to get that help?

Yes. I think the best way is reach out to us on our social media. We on Telegram for example, we we have both the general public one, but we also have a developer Telegram group which I do realize I haven't sent to Narb yet, I'll send to him and then he he can share with everyone. So on Telegram, the developer one is probably well the if you're a developer that's probably where you want to start from. I think other than the developer funding and you know like you just want to try out our documentation, Reactor, go and play around. We have a upcoming competition, it's not a hackathon, it's a competition because we don't want to just attract you know things on testnet. We want to attract actually you're already building something, your your project, it could be one person that's okay but you're already building it. And along the way of building your dApp, you will face the same problems that that I've just described earlier. And straight away I'll be like I'm going to mesh the two together. If just nice you're in this stage of your development, you're looking for a solution, I have a competition and if you build using reactive smart contract and it solves your problem and we see how well your reactive smart contracts with a S like you can have many of them do, actually you stand to win a prize. That's our competition's it's going to become it's going to come in the next couple of weeks we'll announce it actually pretty quickly as well. So that's something for developers to look forward to as well.

Right on, right on. Yeah, looking forward to seeing all the cool stuff get built out of that as well. With that, we'll let you go here, Rong. I know we went a little over time, but really enjoyed the conversation here today and thank you again for taking the time out of your day to chat with us. Likewise, thank you for having me and I'm always very happy to share about what we're doing. It's very exciting to me as especially I myself I'm not a developer right? I I was a police officer, I mean I studied chemical engineering but never coding into this level. And I think what we've built are are something that even me as a non developer are I'm very excited about because this is a core problem in the entire ecosystem. And I think that's something that if you're a developer and you're interested, you should you should take a look, try it out, highly encourage you to come and try it out and and see how this will will change the way you build. Well said and yeah, we'll have all the resources for you to to do just that um in the description below. So definitely maybe take your weekend hack this week to learn some Reactive Network smart contract development. But with that, I just want to wish everybody a very happy Friday, happy weekend wherever you may be and we'll catch you back here on DevNTell next week. Right on, have a good one. Thank you so much. My pleasure. Bye. Bye.