Supercharging Blockchain Interoperability with Reactive Network

Transcript

Introduction

GMGM. Welcome to what's going to be another fantastic episode of Devantel. So, if you didn't know, Devantel is a 30-minute podcast held every week allowing founders, hackers, and anyone in between a uh a stage to showcase their products. And today, I'm ecstatic to welcome Ron 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 DAPs using reactive contracts. So, if you stick around for today's episode, you'll see Ron give us a deep dive into how reactive network is redefining web 3 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. Today's episode

Sponsor Message

of Devontel is brought to you by our friends at Arbitum. Arbitum is a technology suite designed to scale Ethereum. You can use arbitum chains to do all the things you do on Ethereum, but your transactions will be cheaper and faster. With over 3.8 million ETH saved, 1.69 million active wallets, and over 1.7 billion total transactions, why would you want to settle for any less? Get started today by exploring Arbitum's comprehensive docs and tutorials linked in the description below to help you get started launching your next DAP today.

Now, on to today's show. [Music] GMGM, welcome to the show, Rang. I'm ecstatic to have you on today. Thank you so much, N. Uh, thank you for having me. My pleasure. And, uh, yeah, thank you so much for taking the time out of your day to to come chat with us. Uh, I know we have a lot of great content to go over today, uh, on uh, on Reactive Network. Um, before we get into that though, um, would you like to give a brief introduction about yourself?

Guest Introduction: Rong Kai, CEO of Reactive Network

Yeah, definitely. Uh, I just realized your background's Moro and it's this flipper, but that's ah, you got I got the map Middle Earth. Right on. Yes, middle behind me. Yes. Excellent. So, sorry I got distracted because the the the the eye is staring at me and I was like, "Oh, wait a minute." Uh, anyway, yes. Uh, uh, thanks for having me and it's pleasure to uh, be on the show with you and and everyone who's who's watching. Uh, thank you so much. Uh my name is uh Ron Kai. Uh I am CEO of reactive network and I've been in this this industry since 2020. A lot of things has happened. I was in Binance uh for uh first two years. I was doing actually BSC accelerator fund and this

is how I I knew about uh my current team and and uh uh from 2021 onwards I joined my team and uh we initially were doing uh real time data and then we were in index sync and then now we we founded it and we we did uh reactive network together. So the journey has been quite a while quite a thing. I'll probably share more if if if you're interested, but of course uh today we're here to talk about tech and I'll share more about tech as well. Yeah. Yeah, for sure. Uh yeah, I mean uh if you don't mind, I'm always curious how people found themselves in tech and and web 3 and the web 3 industry in general.

Rong Kai's Journey into Web3

Yeah. Uh so my my story is probably very um out of the norm, so to speak. Um before 2020 I was senior police officer in Singapore. So uh I was I was in in in law enforcement for eight years. Uh I was the head operations of the division a thousand officers. Uh I was running the the entire div police stations ops basically uh major events and all that kind of stuff. Um I was happy doing that. Uh uh but of course I uh in 2019 uh I have a young daughter and my wife told me like you need to kind of uh reook at your priorities because I was

working easily 70 to 90 hours a week and and so uh I I switched industry I went into blockchain uh because uh I I kind of like what the industry is doing but I think what for a lot of people who's working in industry not just buying crypto of If you're working in blockchain, I think one of the things that most attract you is the freedom that you get. Uh most companies are remote. Even if you're not remote, you go to office is is very like the ethos is there very decentralized. A lot of freedom and into decision making and so on which sort of affected me to this industry as well. Um and I went into Binance. Uh I was lucky to to get an introduction. I went to Binance. Uh uh I ran the 100 million BSC accelerator fund

with uh together with a team. Um we look at 500 companies. we invested in 31 when uh 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 when you talk to them they they tell you they pitch to you and you you you hear everything that oh I'm trying to build this I'm trying to build that and why is this so important because a blockchain ecosystem leads this it needs that and so on. So um that was really a kind of a foundational crash course that I had uh in blockchain uh and the technology and it really helped me in transitioning into my current role. Uh I first joined as COO and then now I'm the CEO since 2023. Um uh my company we we

were doing uh initially like right at the beginning uh when I was in Binance we actually invested in in in in my outfit uh and we was uh doing back then a real time uh sort of data feed. Uh we 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 or somewhere else. uh or you can do something with it a back end you want to automate certain things but that 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 that that wasn't indexing wasn't what we wanted to do uh we wanted to do like we want to be really really good at real time and we came back into this space

and we sort of created uh reactive network uh I will share more about the problem statement and all that on reactive network later uh I have I have a very short uh deck of slides to share with everyone but Very long story short, uh the impetus was really because uh we felt that anyone building onchain uh decentralized applications uh D5 whatever it is uh you kind of uh still apply the very old model where pull data off chain and come back in again pull data off chain coming in again it's a very roundabout way of doing things if you look at it from a data standpoint anyone who's bidding on web two will will just think that it doesn't make sense uh and and they seem to take things for granted that you be like wait a minute you guys are you not doing

Deep Dive into Reactive Network

this? What what era are you? Are you still in 1970s? And and that was what we felt as well. We like can we do something about that? And and we created React Network uh sort of to to address that. Amazing. Amazing. And yeah, um that's uh like you said, uh quite the unorthodox way of uh getting yourself into tech, but um your um experience uh in the police force um as in a leadership role, I mean naturally um ramped you up for for what you're doing now. Uh which is amazing to hear. Uh and yeah, uh like you said, I I've I looked into Reactive Network a bit. Um it looks like it's it's solving a real gap that did exist in the blockchain ecosystem where

basically you were at the mercy of um basically just indexing events um to be able to react to things. But it seems um this is going more so um kind of like a parallel to like SNS, SQS um being able to just react to events u which is pretty cool. Uh but I don't want to spoil anything. Um I think this is a a good segue if you want to bring up your um bring up your slides and we can get into it. Definitely. Let me share my screen. Um here we go.

And uh for folks who are watching us live, if you have any questions for R as he's going through um his slides or anything we're going through, u please feel free to ask and we'll get that answered for you. All right, stage is yours. All right, thanks so much. So I won't take too long. U this is uh like a dialogue and then I do want to hear from um people who's listening in as well and and kind of interact with us uh and and feel free to ask questions. So I'll just share uh really just explain the technology because after all this is new. We actually created um the world's first interoperable execution layer. Uh so you be like what's this? What's execution layer? Is it is it layer one?

Reactive Smart Contracts Explained

Is it layer two? It's not it's not a any layer like that. Um uh if you strictly want to put us like a layer with kind of like a 0.5 but when you tell people you're a layer 0.5 they'll be like it doesn't exist. What's this? Yeah, because it's new. U so essentially this is a gap that uh it's not just opportunity but it's something that we ourselves feel very strongly. Um so if you look at the left uh the web to experience uh it's pretty straightforward. So they deploy a code the code react to changes uh in a tech component state directly and it performs function and goes to application. What essentially mean is that if you're building an application on the internet uh on mobile phones and and so on. Um you deploy a code you expect the code to

react to things happening. Uh if you connect a data set to it, it will see the data changing and it knows what to do based on that. Um very straightforward. It's a function that has been like you know if this then that has been if you learn coding anywhere it's been around since a long time ago maybe the 80s or even before. Um but the web3 experience is not it's it's interesting uh but it's historical. Uh I wouldn't go too deep about why it's like that. Uh I'll just show you like this is current state. Um you deploy a code onchain. So we talk about smart contracts. Smart contracts are codes that's onchain. Um it cannot respond to onchain events. uh only states. So it can it it will know that uh 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 E right now and the next block your wallet has nine E. Great. What happened to the one if in between? It doesn't know. Uh the the smart contract the code itself will not know. Uh and of course blockchain itself they cannot take data or respond across uh blockchains. they they can't cross because blockchains are supposed to be kind of self-contained a sterile system. Uh it must have consensus. That's why it cannot just take data just like that from other chains organically. Um uh but business being business they we need to solve this right uh and for the

longest time people be like hey this actually solved right now we do this yeah we take data offchain we standardize it we feed it to a web two base code the web two base code which is on the left will then we just do all this and it will come back to the web three node and then it it respond accordingly. a very roundabout way to do this and and for most of the time uh because we need indexing for historical data as well. So we kind of we just latch on to it and we want to do this this way. But the problem is uh and you you should talk to a web two developer and some of you who are on the web two side you you probably will be nodding ahead with me. It's 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 um it shouldn't be this way. Should the experience be closer to kind of as seamless and impossible like web two? Uh, and I think that's something that is a question we ask ourselves like right at the bottom. Can we can we push web 3 a little bit closer to mass adoption uh by making the the the development experience as seamless possible in web two? And so we we we actually created uh reactive platform to do that. So rather than uh having initiated action that goes to blockchain A and because there's no cross data and no interaction to cross blockchain B it could be the same blockchain actually uh you could see blockchain A and blockchain A on the left and right is still the same uh but

the the the idea is still still still remains they don't interact because uh they don't respond to the data the the events that's happening they only respond to states. So rather do this uh we we pull everything to external indexer with external code right but it's not just external indexer with external code here there's because you need to put it offchain and come back on chain again behind the scenes there's a lot of other things data storage transaction signing synchronizations etc each component has its own point of failure uh you need all five to work actually it could be six or seven depending on your own text setup but this is the more very simplified version of it and one fails the whole thing fails

uh and of course it'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 itself u and what we do is we put it onchain instead uh if you can observe and you can interact uh a vast a majority of onchain use cases will be solved very organically remains onchain and you don't have to kind of rely on a centralized point of failure uh I think uh very importantly We we are not saying that we don't need indexes anymore. There's a lot of use cases where you need like to throw through whatever's happening uh onchain. You want to look at 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 uh but for I think a lot of very onchain reactive responsive uh things that that's happening especially with uh smart contracts. uh actually what you see on the right which is uh uh what we wanted to do completely that's autonomous and it's reactive actions that's onchain uh reactive network actually solves this for all all all of the use cases um the value we want to bring is basically this uh we want to reach a stage where reactive smart contracts will underpin the complex reactive functions onchain because right now if you're building a web 3 uh dep um very

often the very first version, the alpha version, pretty pretty straightforward. You come in, you build, you have a lot of things that's offchain, you have some things that's onchain, and you make sure that the whole thing uh talks and and it interacts and you have alpha, you have a a uh uh MVP and you push it out, right? And and people start interacting with it. Great. And your second iteration and 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. it that cycle takes a longer time, way longer time actually. Maybe if you're building this completely offchain, your own uh Android or Apple Store for example, if it's application m 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 web 3 it takes could be months to have the next version. That's that's that's a significant jump in in terms of of lag time development lag time right uh why why is unisoft on version 4 why are they not yet on version 30 it's it's because of this this is it this is why uh so when 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 uh both conditional and reactive and then we close this interoperability gap app for

applications. Uh once it happens uh both the user experience and the developer experience will be streamlined and and then we can start powering really powerful things especially intenscentric applications uh and so on. We're going to give a certain intentions uh we we power that reactivity part of it. That's the whole point and then hopefully will lead to to mass adoptions. Um this is my last slide actually. uh it just explained how it works and I think after that we can we can share more but very simply this is a very simplified uh diagram how it is uh things still happening on on on the source chains on the left uh user initiated action it goes to smart contract and you click

approval approve approve you know that sort of stuff and it goes to the blockchain and blockchain execute and it creates an event to say that yeah I've executed it um the reactive smart contracts uh 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. Um, you'll compute the data and execute the contract logic on on the the smart contracts. If it sees the events because now it can see the event. It sees the event, it will and and my events and my my own code tells me that if I see this, it meets the certain parameters, execute something else onchain. So rather than do this offchain, now you're doing it onchain.

Uh, and then you publish the results. uh it creates yet another event because it's publishing the the results which is like a prompt on uh the the destination chain to say that hey can we do something and the user gets the result it it basically bypass the current uh restrictions on all the blockchains that we have which is the if you're building on Ethereum uh polygon any of the blockchains they they're not they're not reactive uh we don't want to create a layer one that is reactive and say that yeah now we competing with you guys. To me, uh yes, we can possibly do that, but that lives out everyone else that are still on all those uh systems. What we wanted to do actually, why don't we

create something that benefits everyone uh as a whole. And that's why we created a data execution layer, not a layer one or layer two, because we wanted this to benefit everyone regardless of blockchains, regardless of of uh even the code behind it. Uh we of course at the beginning we are only supporting EVMs but in fact none EVMs are probably coming pretty soon. We we we were predicting that to be next year but uh 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. Uh 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. Uh I don't I wouldn't show

Q&A and Interactive Discussion

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 uh what we call RVMs uh reactive virtual machines each RVM is basically one use case uh and under it can have anywhere between one to a dozen different reactive smart contracts on them so uh I'll stop sharing and uh I think we'll come back to the floor. Yeah. Yeah. Uh yeah, this is really neat. Um just want to double click on the um the smart contract bit um a bit more. So it seems like um at least from your diagram um the reactive smart contracts um are kind of like a

middleware um if you want to have like a web two parallel um that kind of do something um before um like in between going from chain to chain and uh does is there uh so does there have to be a um a particular smart contract on either side? um 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 I mean um we basically build it as a sort of a bridge between uh it could be the same chain right it could be polygon and then back to polygon for example um but the whole point is to

bridge this uh capability uh 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 all these events happening. So we created uh a middleware is kind of a good approximation to sort of what what we are but I think right now um this is a problem that exists 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 they put in the middle and it but they put it off and it come back on again uh change to 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 machine to

do that. And what we did is rather than solve it at a uh it's basically like an application level uh 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 smart contract level. It's like oh so we're down to the code that you write onchain and we solve it there by doing so by doing it deeper uh it creates uh basically a data flow that's a lot more organic because uh code is 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. Uh 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 the code and if the code is interacting uh is very limited at that level it has to jump through into another text stack and another code that's on web two for example to talk to a web three code and they're all written in different languages and that means you're introducing a lot more things. You're introducing a 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 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 um do develop do um solidity developers have to um learn anything new or is like are are the reactive smart contracts fully um EVM um 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. uh we started with solidity because I think web 3 at the end of the day yeah there's there's Rust developers and so on but

Solidity and EVM Compatibility

majority right now is is uh solidity basically just take the majority as a solution we put it in uh I I see this having relatively long longevity even you know maybe uh uh Ethereum in in the next five years they're going to move away from from solidity that's okay because they they're never going to like stop supporting the legacy side of the else, right? You can't just cut it and then restart completely from scratch. You need a sort of process to move towards certain uh 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 uh there will be other layer one, layer two that come out and say that they are reactive smart contracts right from at the beginning. Maybe they take our technology and they move into certain things that that still means that our mission has been achieved and maybe we do it next time. But right now uh vast majority of uh blockchains probably all of them in fact like if you write the smart contracts they are just at at that I mean there's a historical reason behind it if you look at it uh from a nontechnical standpoint you're not technical it's okay you you'll understand where I'm coming from if you look at it blockchains were created at the beginning bitcoin right it's just uh now you giving me bitcoin and I giving someone else bitcoin it's meant to be

that and then you slap a layer of coding on 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 why we push innovation. Um and certainly what you guys are doing here. Uh just curious like um are there any added gas costs um if there's a reactive smart contract in between? Yeah. So, so the guest will be paid like because I'm I'm structured as a decentralized uh well architecturally I'm I'm blockchaining as well right so if you have a reactive smart contract on us the smart contract by observing the

Gas Costs and Efficiency

events they don't need to pay guest but it's like the acting oh I see something that that that is relevant to me and then I act that that creation the act will will will need gas uh but right now I mean it's super cheap it's uh like fractions vast small fractions of a scent to react to things. Imagine you you're paying for example 500 bucks to an 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 uh based on use case how data heavy are you and even you have really data heavy I think it's not going to be much and and that's why and and and and even to us it's already energy efficient

is because you are we created a system where uh they are inherently sporting all the events without needing to pay money. Like you know the reason why indexers need to charge so much money is because they spend 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're 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 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 relevant to me and therefore I need to do something

about it and the reactive smart contracts pays a fee and you be like 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 wallet basically and the smart contract now has its own money. Imagine this this robot that that's smart and he has his own money and he will pay if he needs to act on it. Makes sense. Makes sense. Uh yeah, this is very very interesting. I I'm curious to hear uh you mentioned it uh briefly um in your slides, but um what are what are some interesting use cases um you're seeing built with reactive smart contracts?

Innovative Use Cases for Reactive Smart Contracts

Uh it's a very good question. So I think right now we we have a few that that we're extremely excited about. Uh for example uh worlds uh uh they they're using smart contracts to really fuel the automatic sort of interactions uh within their their game, right? It's a game uh which instinctive tell you that uh if you're web three game and you are a legit web three game a vast portion of your uh assets uh and uh coding base and and all that is offchain. is naturally offchain but the interaction with web three is where uh that part comes in and how do you automate that uh with the

additional complexity that majority of your your digital assets are actually on web two offchain and they're coming in to use reactive smart contracts to really resolve this this this roundabout uh so so to me uh I I mentioned them right at the beginning is because it's not just using uh us to solve like web three web three You can use us to actually make the the intersection between web two and web three a lot smoother as well because uh if you constantly have to jump between web three to web two and jump back again jump out in out in out uh it is a lot more uh inefficient where comparatively maybe you're just web three to web three and only at a final point you come back

to web two then that's it and then and then so it reduce the amount of back and forth that you need to do. Uh another one that that we are really excited about uh is smart trust. Uh they're using us to basically automate the they're doing basically a remote contract escro service escro service. So what what it means is that uh uh if you are a remote worker or contract worker uh it's relatively common to hear about someone being scanned out of like employment contract. you you you do some digital work for someone who's based in a completely different continent than where you are and you say that oh sometimes you sign the contract very often is 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 uh British Columbia and then this guy is is based in Venezuela and he 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. Uh uh most often is uh employee to employer, but sometimes it's the other way around. And they have actually trying to use it to kind of uh soft escrow kind of uh functions where maybe the the transaction like the money if you do this work I will pay you $3,000 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 arbitrage arbitrate between this, right? Uh they they've created a service that uses web three to sort of sort this in a trustless manner and sort of have a neutral party to to kind of I wouldn't say take sites 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? Uh if if if if it's like $50,000 or $100,000, not many companies are willing to lock that money up. And

they created a system where where is is resolved. I'm not going to go too deep into it. Uh if anyone's interested, you can look out smart trust uh smart without uh with just one single T in the middle. So it's a smart trust combined into one word. Go and take a look. is very very interesting how how they want wanted to use it to resolve and they're using reactive smart contracts to really bridge that automation between the things that's onchain to onchain right because there's a re there's a there's a certain amount of funds uh uh locked in a trustless environment uh who's going to automatically release it and so on very amazing uh kind of use cases and and there's more of course but uh we we recently are going to start funding uh a

D5 I use case as well. Uh and uh we previously we have that another one that came from our hackathon and we we fully we actually funded him to turn it into uh uh like actual working uh product that's onchain. Uh it's called reactor and it basically helps you stop orders across all kind of defi that you have. There's a lot more as well actually. they they they have like liquidity protection and so on and that that that that they they want to put it in. So the whole idea then is use it and you it's no code like if you're a typical user you don't need to know coding that's that's the best you go in you be like I'm going to do stop waters some places have some places do not have uh and some sometimes you want liquidity protection

and that that to me is is is critical and how do you do that use 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 what you need it to do. Wow. Yeah. Uh those have been amazing use cases and then it seems like there's a whole ocean of opportunity to to build a bunch more. Um for the developers that are watching us uh here today, what would you recommend is the best way for them to start playing around with and and learning reactive network.

Developer Resources and Documentation

Um I think the best way to to really start looking at if you're a developer obviously uh look at our documentations because our documentation did don't just have like a typical set of rules. We actually have an education section like uh and the education section assumes you're a developer actually you're like you know solidity this the basics uh you know what we're talking about and then we teach you how to start from from zero to one and and to me that that is one of the things that uh when we were building this even still doing test net I I 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 and the education system. So education section is also not just textbook to the docs. The education uh segment is actually like the teacher teaching the students. This is how you do it because I wanted people to to lower the entry barrier as much as possible. come in and and learn. And so to me, that is probably the best stuff. And uh whether you're technical or not technical, I think the best way to really see this effect for yourself is to check out Reactor. Uh we will actually have more uh publications about it next week, I think. Uh but right now it's is already live is is is working. Uh I think it's reacttor.in, like reacttor in uh and go

and take a look. Uh I I do need to double check if uh if I got it wrong, but I think it's reactor in and Oh, no. It's it's not reactor in, but I I'll share I'll share the link with you separately. Yeah. Yeah, for sure. For sure. And uh I I love I love that you guys are taking um a lot of care in your docs because a big um meme in the blockchain web3 industry is that docs are usually quite uh skimpy. Um, so the fact that um you guys are putting in the detail and the work into that is is fantastic to hear.

Grant Opportunities for Developers

Um, and uh are there any um grant opportunities uh for builders who might be um interested in um pursuing a longerterm project in the space? Yes, I'm glad you asked. Uh we have a death fund. Uh it is of course denominated in in reactive uh uh in react our our token our coin uh but uh we actually when we created this we set aside like huge fund uh that is meant to to uh incentivize uh 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 you 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 pro that you have your milestones, you're building towards it, you're building using reactive uh network, you have a great use case, you have a great uh like uh you you you mean to really contribute to web three, we give you that grant and and as 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 uh especially developers really uh you're either starting or you're already in the midst of building something like please take a look at it. Uh we have a deaf fund you can you can see the defund on our website as well. Uh by the way jumping back to earlier I was talking about the reactor uh uh I've said it

separately to not but uh it's actually the reactor.in so you can you can check it out. The reactor is one word and uh you can check out that that place. Uh I think we we could uh we we're working with uh the developers working on it uh to to to revamp it uh a little bit more and I believe uh the developers actually trying to put it AI to to really make things a lot more spicier over there as well. So I uh I think it's going to be completed next week. I'm sort of like doing a a pre uh pre-arketing so to speak. Hey, take a look at that. And and it's for someone else project. It's like uh uh as is a developer that that that we previously funded and we continue uh

to to to make this better uh 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 this show. Uh and is there anything else um that you might be able to share around the road uh road map uh of reactive network? Yeah. So, uh, uh, for those who are not familiar with us, we we launched three, uh, well, actually that was about four months ago in March. Uh, we launch in March. Um, and we basically in that time I think network now is completely stable. It's good. We've uh

Roadmap and Future Integrations

started uh we were connected to uh we we during that that four months we connected to hyperlane and hyperlane you know they have that six thou uh four five six I think about six dozens uh different networks that they they on and of course through us uh and through them you you you can actually uh react as destination chains to all of that as well but on our own we are also continuously uh connecting to new uh network and and that's something that is extremely exciting for us. Uh like very just this week we announced that we have uh integrated uh hyperlquid.

Uh there's going to be more. Uh I think what we are focusing right now are really the uh chains that have the most potential for a developer like I want to be there because you know what what what why is it and if you are as a developer you want to be on whatever chain we will make sure we will support that uh and we are looking at some of the major non EVM chains as well and very likely this should be coming soon actually that's something that uh my CTO Danny he he he been giving me very good advice about 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, uh, right now I think we have a brilliant

team and, uh, 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 uh looking forward to um basically seeing people start building um cool cool stuff with reactive network and uh yeah as as Rang mentioned um if anyone's watching here today and is curious to take a project a little bit further than just a weekend hack um they do have grant um uh they do have a grant program available so definitely um 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. Um I think uh the best way is to reach out to us on our social media. Uh we we on Telegram for example, we we have both the general public one, but we also have a developer uh uh telegram group which uh I do realize I haven't sent to yet. I'll send to him and then he can he can share with everyone. So on Telegram, the developer one is probably well the the uh if you're a developer that's probably where you want to start from. Um I think uh the uh other than the developer funding uh uh and you know like you just want to try out all documentations reactor go

and play around uh we have an upcoming competition uh it's not a hackathon it's a competition uh because we don't want to just attract uh you know things on test net when I attract actually you're already building something your your your project it could be one person that's okay but you're already building it. Uh and along the way of building your your debt, uh you will face the same problems that that I've just described earlier and straight away I'll be like I'm going to match the two together. If just nice you're in this stage of your development, you're looking for a solution. uh I have a competition and if you build using reactive smart contract uh and it solves your problem and we see how well your

reactive smart contracts with the s like you can have many of them uh do actually stand to win a prize that's our competition is going to is going to become is 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 to seeing all the cool stuff uh get built out of that as well uh with that uh I we'll we'll let you go here, Rang. I know we went a little over time, but uh really enjoyed uh the conversation here today and uh thank you again for taking the time out of your day to 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 uh to me as especially uh I myself I'm not a developer, right? I was a police officer. I mean I I studied chemical engineering but never coding into this level. And I think uh what we've built uh is something that even me as a non uh developer 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 uh you should you should take a look try it out. I highly encourage you to come and try it out uh and and and see how this will will change the way you build.

Well said and uh yeah we'll have all the resources for you to to do just that. um in the description below. So definitely uh maybe take your weekend hack uh this week uh to learn some reactive network smart contract development. Um but with that, I just want to wish everybody a very happy Friday, happy weekend wherever you may be and uh we'll catch you back here on Devantel next week. All right, have a good one. Thank you so much. Cheers. My pleasure. Bye. Bye.