Hello everyone and welcome to this exclusive space with Shenztake and Aurora. I'm still waiting for my two speakers. I see Eugene as join. I will invite him to speak right now.
We are still waiting for the almighty Alexa Franco was joining soon. Obviously today we will discuss this integration from Shenzhen or Hello Eugene.
Just talk about the stack of three adoption on a Google Cloud event in Singapore.
Okay, I see your likes that's showing and you have invited him to talk.
Okay, hey, hey, hello everybody.
Okay, so we on. So I hope everyone is enthusiastic for this year maybe because we got some pretty interesting stuff to discuss. I would like from to start with the basics and to start with our guests today.
BUG in the founder and CEO of Shainestack, BUG in could you introduce yourself? Absolutely. So my name is Eugene. I'm a head, I'm a CEO and founder of Shainestack. So Shainestack is a leading
company providing a developer's easy access to Web3 infrastructure. So my background is in engineering, cybersecurity, I've been building it on a global scale for more than 13 years. Very excited to be here today.
Thank you Eugene, pleasure to have you too. Alex, could you introduce yourself?
Hello everybody, Alex and the CEO of Aurora Labs. This is the company that is the key developer of the Aurora Protocol. We are building a solution.
a protocol for the EVM compatibility for the near-block chain. So EVM-capable smart contracts and applications are able to run on a more performant and future-proof network.
Thank you, Alex Eugene. My first question was what is chain stack could you like resume globally? Everything that chain stack does and introduce it to our audience Right, so so in chain stack we empower web 3 builders globally
So we provide them services that allow them to abstract the way all the complexity of building on different blockchain protocols, Aurora included. So we basically provide no APIs, date APIs, data indexing, decentralized storage solutions,
So basically everything that people for building in Web 3 need to be successful and to be focusing on what's important and not on the infrastructure pieces, right? So we have companies of all sizes from startup to enterprises, some of the notable customers
are very familiar to the community here. I'm sure like one inch and that greater coin get co layers zero chaining. Why are these some of our our our customers who we help with the infrastructure?
Thank you Eugene. I would like to introduce you to the spirit of the company maybe. Well, I was partially doing this before, but just to continue. So we're all itself viewed from the standpoint of the user as a
and the EVM-compatible network. In fact, it is a smart contract that is running on the both New York Oracle. And because of this, we are having multiple additional things that are available on Aurora in comparison with just the Babon EVM-compatibility. First of all,
I think that was launched already one and a half years ago. This is the rainbow bridge currently at number three among the largest bridges in the world. Note hack, fully trustless and permissionless and working as a Swiss clock usually referred to as the
best user experience in the world. Besides that, in our stack, the solution that simplifies the user on board into the blockchain because of the unique feature of the Aurora blockchain, which is a Oracle level method transactions, again, pretty technical thing. But what it allows
what it allows to do is the additional level of abstraction or additional level of separation of responsibility. So we are able to separate user authentication from the authentication
of the user actions, I mean transactions, right, signing the transactions from the actual payment to the protocol. So the payment can be done off chain, can be done absolutely separately and so on, which means that for what the user is to be onboarded to Laura, it takes just one minute of
in Aurora Plus and the user gets 50 free transactions per month and users get over to start transactions in Aurora, they do not need to pass KYC, they do not need to work with the changes and things like that. Our goal among our
goal among all of the EVM compatible networks. It is not only the kind of scaling of the EVM blockchain or kind of extending the Ethereum economy outside of Ethereum blockchain, but the main thing there is focusing on the users, focusing on
on the user experience, making sure that people from Web2 are able to onboard easily, and our solution, the Aurora blockchain, is actually able to compete with something that is provided by Web2 companies.
Thank you very much Alex, very complete and sorry very appreciated. I would like to go back to Eugene and Osh always changed stack different compared to other services or his competitors what are what should be looking to
the most in chainstack. Sure. So first of all, first of all, I want to say heads up and put us to Alex and our team and I want to appreciate their thoughts on how they are different because some of the things that Alex mentioned and the team is building is really genius. It's like
The bridge is I love the stories when I'm reading about that dams the pack the bridge that was prevented by the bridge or our or a plus which gives like hustle free Yes, let's experience for users. I think this really Very very cool advancement in the space versus
what other protocols are doing. So for us, we're also not a typical infrastructure provider. So we are focused mostly on the high load depths and not like beginner users. However, our UI is very, very friendly and
even some of our competitors, they say that we have the best UI in the space. We have a lot of advanced options for all the chains with support, including like full archive data, HTTP websocket, grab code APIs. Different authentication options not limited by the key authentication for the know.
We have globally distributed infrastructure with the six different hosting providers, nine regions available globally. So let's say when you hit the nodes, let's say from Singapore that is hosted in Singapore and ChainStack, you have 16X performance.
better speed than hitting like in pure alchemy because they're mostly positive in us for instance. So we provide advanced options for our services. We don't provide just like scalable, elastic APIs. We also provide like dedicated nodes with unlimited requests for power users and they can customize it in the way they want, including
and resource customization, all different options for the node software. We completely possess reliability speeds, so we want to provide the best experience possible for our users, where we are outstanding customer support, which is 27 against the global if all of the same team. And last but not least, we accept crypto for
services which is very important since any other services in this space even though they provide access to web stream for structurally except on the crypto only credit card payment so we are very proud that we pioneered this space and basically you can pay like even in dodgecoin for change the KPIs.
Thank you very much. Thank you very much. It was very nice. Thank you. Alex, I think you answered partially to my future question, but I was about to ask, oh, is already front compared to other networks, but I think you eat the spot already a little bit. But what's the
difference on the infrastructure or services for devs? Like, yeah, focus on the differences, I would say. From the devs side, for the people who are developing
decentralized applications, Aurora is extremely similar to Ethereum blockchain. So for them, all of the tools that are working with Ethereum or did a nature they are used, like SDKs, IDs, different approaches, all of these are available.
hard-haired, truffle, wallets are working with Aurora because Aurora has Web3 compatible interface. So from that standpoint, everything is good. There are services indeed. There are services, I need to admit, that there are services, some services that are provided by third parties,
are not integrated with Aurora. These services are mainly some kind of closed source things and we are not able to influence these companies that are providing these services. In terms of the generic open source infrastructure, anything
that is working with the theorem is going to absolutely similarly work with Aurora. The difference is in the chain ID. So this is the place where you deploy your smart contracts and where your product leads the launch. And just the endpoint for
for the RPC. So for this end point, we have our own end points that is available for everybody. And we also have partners like Chainstack and people are able to use the end points that they provide. There is no difference because these are just the nodes in the same network.
So that's, this is a great thing. In terms of the benefits for depth overall, right, not for the developers, not the depth, but for depth overall, there is an important thing, an important intervention would be the speed of transactions and in general the
So at the moment Aurora blockchain is capable of delivering something like X10 in terms of the performance or the amount of transactions that can be processed in comparison with Ethereum. The raw plans how to scale it even on a single Aurora main.
And there are additional plans. Here is the alpha. How to scale it beyond a single Aurora instance. So these solutions are in active development and even more and more people would be able to work
on Aurora ecosystem. This approach for scalability is extremely in line with the thesis of the near blockchain which is used for us as a settlement layer because near is a truly scalable chart
blockchain that is available and there is an introduction for already multiple years. So this is the only blockchain that is truly scalable and works in production. So from that standpoint we would believe that the people who are going to or developers or DAPS who are going to
and who are going to launch on Aurora, they will never ever see the problems with this capability independently of the amount of users that they are going to have in the future. And also an additional thing that is kind of a little bit orthogonal to this, this is the speed
transaction or the transaction finality. So this thing we are inheriting completely from the near blockchain and because the blocks are generated in near with a pace of one block per second and in order to reach the finality so when the transaction is fully finished and it can
not be rolled back, it requires just two blocks. So in the matter of two seconds, user transaction is both executed, verified and finalized and cannot be rolled back. Which means that for the DAP developers, they are able to create a very
responsive front ends, very user friendly experiences when they don't need to allow for stuck transactions that usually happen in Ethereum because of the guess that prices going up and down and things like that.
So you just create a front end where the user experience is extremely smooth. Yes, you need to allow for user waiting for some action so it is not instant, but it happens within two seconds. And two seconds is much better than, you know, minute that
that usually people are allowing for working with Ethereum. So in general, the application is much more kind of simpler and easier to digest by the user. And this is one of the things that make a lot more different.
Thank you very much Alex, I think it was a very complete answer. I think we all got a very good global picture here and I would like to move on from what I could call the presentation of the project.
and on the other more detailed questions. And Eugene, the next one is for you. What are the programs of managing blockchain infrastructure we told an RPC provider?
Right, so I want to continue on what Alex has mentioned, the simplicity of experience, for instance, for our own and the speed of development as well as the familiarity of transactions, speed of transactions. So it all comes at cost, obviously, right?
But this cost is now not on the users' shoulders, but on the node of Rata shoulders. So for instance if you run, and if you know this, it's relatively simple to run today. It was very messy so far.
of sort that any user can run at home, there is a lot of tools to run it. Now it's getting slightly more complicated with like separation of different layers, like the consensus layer, the official layer. Now it's getting back to some sort of complicated state. But the thing is that for average user, for even
like a dev developer company, it's still like additional expertise that is required for any kind of blockchain node. Aurora not being like different here since it's built on here it has some sort of dependency on here so for
For instance, if you want to run like archive, for example, you need to run an archive mirror, because they are very tightly coupled. It's getting more and more complicated when protocols innovate.
all this complexity within the protocol within the node software other than exposing it to the user layer. So it's getting more and more complicated with the newer protocol so it's getting even more complicated when the apps are going multi-chain. So imagine you run like operating
nodes on one chain and then you want to scale on like four other checks. What does it mean? You need to rank four other nodes and they are all different in terms of preparation, in terms of the release cycles of the node filter, in terms of the timelines.
that I given to you as an audit operator, to patch your node, etc. There are hundreds of different considerations mostly with regards to DevOps and SRE related to operating all these nodes and the complex thing will. So this is some of the
examples of challenges when you basically, when you want to or a hero node, right, and not use a public RPC, which also has its own limitations or like a professional API provider like Chainsack.
Thank you Eugene. Alex from your point of view here, what are also the pain like Eugene was a bit speaking about that like you do I would say what are the pain points here what do you see as pain points on that side as well from from an
And it will provide a point of view. Well, I'm second and everything that that you can be saying. We figured out that providing an access to the blockchain is an extra, especially in a scalable manner.
is an extremely, extremely hard thing to do. So, Eugene was telling that the pin times or the latency times is in case you are from Singapore is 15 times lower than for an Alchemy. That's absolutely great.
here. The thing is that in general, from my point of view, the challenge for companies like Chainstack and also for Aurora because we are partly covering some pieces of what Chainstack is providing because we need to have a public RPC to
Now, this is only tiny, small, tiny, tiny thing that we need to develop. But even within this thing, we already know that unfortunately, unfortunately, the way how the blockchain standards are developed at the moment,
I'm talking particularly about Web 3 RPC. It is developed as a research project. It is not developed for serious production use. One tiny example here,
And this is the big challenge for everyone. The Web3 or Web3GS or Web3 standards is a pool-based RPC, right? So you always need to
get to the server and ask, "Hey, what about the transactions that are coming to me? What is the gas price? Can you tell me?" You cannot subscribe to events. You cannot get push notifications from the RPC because it's not the part of the
standard. And because of this, it creates an excessive and enormous load on the RPC. And this is how things in Web2 are not working already for decades. So I do believe
believe that the biggest one of the biggest challenge here is that what it causes is for companies like Chainstack or our department who is taking care of the infrastructure, lots of headache because it creates an excessive load on the RPC servers.
And this type of problem is not the only problem there, right? There are tons of them. And that's the core issue of this is that the blockchain tech, unfortunately right now, is not designed properly. We need to develop new standards in order to simplify
things, to use our resources, computational resources wisely as a vertical, and in order for us to get closer to the web to competition that is out there. The only competitors that I'm thinking of
for Aurora or for in general blockchain these things are these are not different networks these are web2 companies that are able to build centralized solution and somehow we need to figure out how we can compete with them in a decentralized world
Thank you Alex. This last sentence is like a late motif for the blockchain industry I think. I would like to go back to Eugene and maybe disclose a little bit about the benefits of running nodes on your own in general.
Absolutely. First of all, I would like to second what Alex said about the research projects I have been always thinking about this and it's a little bit finer that like multi-billion dollar industry today in Web series actually built in reality, built on the software
are mostly influenced by enthusiasts quite long time ago. We see, I think, the second wave of more serious development joining in this space. We have some examples here, for instance, one of the notes of her that is much more performant
and that is being adopted by some protocols like Erie von For instance. It has been built with the performance in mind rather than like the KLA's HACTS, cool blockchain clients and see how the works can build a network out of it. So in terms of running your own notes, there are plenty of benefits on a
And that's very in line with the ethos of their system. But basically you have like self-custard of your keys and you have self-service nodes that you host yourself. So the benefits are similar to what you do when you don't use cloud providers, for instance.
you run like your own servers, you're pretty on data centers. There's a lot of ups and downs here. If we're talking about benefits, obviously it's more controlled environment, right? So you control what's going on, exactly what you run on your own servers. You have direct access
to it so related, for instance, or performance wise, it could be much better than using some clouds services that are running somewhere else and maybe some other continents. You also can scale this.
deployment as much as you want if you have enough resources we can just like basically log into your own machine and like run more stuff there if you want so it's more controlled environment it's more according to the ethos of the ecosystem that basically everybody should own their own keys
everybody should own the old node should run their own computational device for the network, right? Unfortunately, this approach is only the advantage of running your old node because the list of disadvantages is way, way longer, eventually because again,
The software was not built to run it in an easy fashion. So the software was built by enthusiasts to basically to show conceptually that this is possible. So that's why operating stuff in blockchain is pretty clear.
interacting with blockchain nodes is pretty rough experience. So that's why there's new wave of data APIs now being built, including like abstractions for developers, because it's the nodes themselves. They were also not built with the development in mind. They were built with operators in mind. So all the APIs that
Blockchain nodes provide a very very technical and sometimes not convenient so Like some people are very surprised when they realize that but for instance, it's very hard to get Let's say wallet balances from the node. It's just impossible due to like the architecture of MDM methods first, right? Of course like newer
protocols and learn on the mistakes of the past or on the imperfections of the past and some protocols like near itself for instance is having a lot more like improved notes of her and like APIs and so on and so forth but still yeah as Alex said also there's a lot of
like legacy so-called from initial attempts to build blockchain infrastructure. So yeah, unfortunately the list of disadvantages to run your node usually beats the advantages which are basically two major ones that I mentioned in the beginning.
Maybe in general we just need to get cove the project for creating a new kind of more robust approach for the RPC for example that will allow to decrease the
decrease the load on the RPCs. And maybe in case we will be able to make it a little better then it will be easier at least for everyone to operate notes including ourselves.
Yeah, and the next question was a bit for the people who have already built on Aurora, those some project built on Aurora run their own nodes. And do you encourage them to do so or do you consider it's not like the position of an network provider to do so?
What's your take on this Alex? Well, I always look at this as the more notes we have, the more visible the blockchain is, the more this agreement, the more potential this agreement we would be able to see in case something sketch is happening.
any additional node that is run separately by the project, so themselves managing the node, or maybe they are buying the node in the cloud from the node provider. Any of this movement is improving the security of the network.
and it's helping the software, or it's helping to deliver the pieces of the blockchain. So, yeah. In case you're able, and in case you're at the level when you're not already a small company, a small startup of three to five people, when you
you're just not able to pay attention to this piece but you already found your product market fit, you already have your first users, first revenues flowing in the company and you're already at the stage when you can think more strategically
on the things that you're doing, then probably the first thing that you would understand is that you must take care of the stack that you're working on. You must be sure that everything that your business is based on is not going
into fail and here contributing in the security of the blockchain that you're using is an extremely important thing. So yeah, once you get to this point and encourage everyone, not to forget about contribution to the security of the layer one that you're using.
Thank you very much Alex. I would like to remind everyone who's listening right now that they can ask the question either below one of the oral tweets we did for the space or in the space and we will try to answer them at the end of the discussion. I would like to continue with something that you already
I will touch a little bit Eugene and I will group two questions in it. What are some problems you can meet while learning your own node and all Kenshin stack help to solve those problems? Oh my god this topic I can probably elaborate for a day or two alone so we can
maybe have a spin-off AMA for, let's try to have it shorter. Like we can talk about problems running your own blockchain infrastructure for a long time. So, challenges start with the most boring ones, but you might not even think about, for instance, the fact that
the blockchain is always growing is very important so it's depend only database if we oversimplified so you have data added all the time to the blockchain so for instance if you have like a one terabyte disk when you run your own node and then suddenly the node grows above one terabyte you need to do something about it
So you either need to go to Amazon.com and order a new disk and then set it up and then I set up some sort of raid etc. So this is like super boring stuff right so apart from the super boring like hardware related stuff when basically requirements for the node can change like dramatically from the from the disk side
is perspective from requirements for CPU and RAM when the node starts processing more transactions, for instance, and then you need to upgrade it to. There are less obvious things that eventually if you run a node for a longer time and you use it in production, which is important because technically speaking, if you run a node,
Just for yourself, like for your own users personally just to connect your wallet to it, then you don't care very much about like its reliability, its performance, its speed, right? But when you actually run a depth on top of it and you have a significant amount of users and as Alex mentioned you gain some product market speed and you actually need to sustain
the growth of your app and you have hundreds of new users, thousands of new users coming to your deck. Then there is also devops, like SRE challenges that you might meet because you need to scale up the nodes according to the traffic. Ideally you want to have some sort of auto scaling.
For the APIs because they do at one moment of time you can have like five simultaneous users on using a depth at other moment you can have 5000 and hence your infrastructure should be able to handle all the spikes and all these ups and downs for the traffic right so this up you were like Infrastructure related challenges which you
see in the web to space as well, right? Apart from that, there are also blockchain and software specific challenges, for instance, your node can suddenly go out of scene for thousands of reasons. And then when your users of your dapplin' central transactions, they might not propagate and they will start complaining or
They might be like some security upgrade of the chain that you don't know about because you focus on different things and you forget to upgrade the node and then it goes to like some like fork network then again your users are frustrated because they try to do something about to depth and they see information that is not up to date
or when they stop sending transactions they don't propagate. So let's say for some networks we see like some irregular network upgrades and no software upgrades sometimes they like ship five upgrades per week for their no software and they are all critically
So we as a professional in all the operations we obviously handle all these upgrades because that's our job and that's our business. But for average, let's say, a developer or like that company or anybody who
is consuming blockchain data, this is something unexpected, right? So they don't want to like spend all of their resources on like upgrading all software like day after day. And yeah, here are like several categories of challenges, right? So starting from simple hardware challenges that you just
need to deal with because it's an append only database and it constantly grows, ending up with very peculiarly specific blockchain software challenges that only exist in Web3. Eugen, can I loop in here? So you're a provider of the node?
So, which means that you are supporting quite a lot of different networks. Moreover, you can give to us and to everyone who is listening to this a unbiased point of view on this. Like people cannot say that you are supporting one ecosystem.
system and not supporting the other ecosystem. And for some of them, if I'm saying that Aurora is great, it makes, like, it is a biased view. You cannot really trust it because like, okay, obviously I'm working in this ecosystem and going to shoot out of it. But maybe you can give to us, and obviously the first part of
the first type of problems that you mentioned, they are kind of generic problems. While the second ones are about the each particular ecosystem. So maybe you can just name the ecosystems, yeah, and again, please do it and buy it independently on the fact that you're working with Aurora. Can you tell us
If it is okay, what are the ecosystems that are more convenient? It is the most convenient for you to work with and on the contrary, the most that are extremely bad to work with in terms of your business.
question and the first time I heard this was actually a near-con in Lisbon and I was talking to some near-engineers who are friends and they were saying, "Okay, why don't you as an old provider of 18 networks like write some sort of workforce about, okay, what's good, what's good?" Yeah, that would be absolutely great because this is going to be
an unbiased view. Yeah it's a great question. So honestly speaking TLDR there is no single ecosystem that has absolutely no problem. So every ecosystem like no matter how developed it is it has its own like moments of
So for instance, even Ethereum, let's take it here as a baseline. So again, as I mentioned, it's quite straightforward to date run in Ethereum node. But let's say when the merge from proof of work to proof of stake happened a few months ago, the first network to merge was Robstance.
That's a that's a test network for Ethereum and the communication of this change of this merge on the test net was so bad that there were plenty of people who didn't even realize that You actually now after this merge happens you need to run two blockchain clad one four
consensus layer and one for execution layer. And there were a lot of aha moments for people when they basically were running just execution content, which was the only one required before. And then the network just literally stopped on their notes and it stopped updating. And then after some time of end reading,
in depth information in the internet they are like "Oh shit, now I need to run a consensus client too" because now all the like block related operations are happening elsewhere. So now I need to run like two binaries and I need to connect them to each other. I need to have some kind of GWT token fast between them because it's
the authentication should be there at 1 or so forth. So even Ethereum, which is like the oldest ecosystem, it has its own like the problem, right? So I can share a few things about Aurora 2. So one of the things that we are working on with Aurora 2, for instance, is the way they communicate changes for Node-April.
So as best practice, like some other change, they are doing a great job here. And for instance, whenever there is a network upgrade or there's a new software version, they push it somewhere in RSS or telegram, public group or in some other means of communication.
of this change. So this is generally best practice. I highly advised to do the same for our team which is very useful for all the operators to give the latest information about the upgrades and like what to do, what not to do, how to upgrade and so on. So this is something that is currently missing for instance but we are since we worked with so many
systems, we are trying to obviously improve all the existing that we work with to have some sort of unified experience at least having some sort of baseline like information about upgrades and all this kind of stuff, right? Another thing is for instance like right transactions for a
that is currently a little bit challenging because of the architecture of Aurora being pretty complicated. So now what we have to do for instance to send transactions to the chain, we have to like send the right transactions to the relay which is being hosted by Aurora team.
for instance, which is also a little bit suboptimal because we want to have, let's say self-contained deployment of a node that will be able to read and write data from the blockchain, right? Ideally, but due to the complexity of the protocol and like tightly connected architecture with the near protocol,
This is something that is challenging today because this is a piece of centralization to some extent here. So if I may say Aurora, post-it-relayer goes down, it's very hard to send transactions to the chain. So I can talk about this forever. I can talk about the outrageous
hardware requirements in Solanec, a system for instance, and never growing like capacity, a demand for like Solane nodes, which is literally impossible to operate if you want to run your own node. You cannot run it on the laptop for sure. It's very, very hard to find hardware for Solanec.
for instance on the market so if you are like an enthusiast who wants to run your salon and all would like to you it's very very complicated and some protocols they don't learn on the mistakes and there are some peculiar protocols like ICP internet computer and at some point I looked up how to run a
node on ICP and the funny thing there, like advancing in a direction where basically you need to have a custom build hardware to run an ICP node which is even worse than like having a rare configuration of hardware for instance required for Solan and
So again, this is just some random examples of different ecosystems. And again, there is no ideal ecosystem that has no problems except for maybe Bitcoin. And the Bitcoin node has been extremely stable, but the point is that the software itself is very, very simple. So there is no smart contract language.
So it's basically like YouTube so based, I've looked at it and it can basically just like transfer assets. So and it's pretty reliable. So we ran Bitcoin nodes for almost three years and they have been extremely stable and they upgrade cycles very convenient. So yeah, fun.
the fact that the Bitcoin is very, very stable, but due to the very limited functionality of the node mostly. So whenever functionality is richer, whenever there is higher speed of transactions, whenever there is more complexity, you constantly have different sorts of problems in every ecosystem.
Eugen, thanks very much for your feedback. Thanks for the feedback for Aurora. We are going to work on the making better the communications around the thing. And with regard to the writing the transactions, yeah, we know about this issue.
We are working on an update to the public node REPL. We are actually rewriting it from scratch, making sure that it is going to be fully consistent with what we are able to provide on our own API.
Thanks for this and yeah, great that Bitcoin developers know what they are doing and I'm absolutely second in you. I've just read yesterday an article on CoinDesk about how great was the management of the merch shop
upgrade by Paul Brody from EY. So I completely disagree with it because obviously for us the maintainers of the rainbow bridge it was extremely important to understand what is the change and what are the changes that are happening in the
in the consensus layer, because Rainbow is working on top of the light clients. It was extremely poorly executed. In terms of the management and of the upgrade, I would wish to
would be I think they focused mostly on communication for the stakers because this is what is perceived to be important right because these people are securing a network so I think that the migration from like mining to staking was relatively well
communicated and explained but it looks like they completely forgot about node operators at least in early testnet upgrades I think for the main net it was already more or less clear thanks to the testnet upgrades but I totally agree it was quite poorly communicated in general
back to you Alexis. Yep, I just wanted to say that you were speaking about how we can, or real, real, excuse me, reliable Bitcoin is, but for the first time ever, I saw a few days ago that it stopped producing blocks for one hour, so it happens even to the
best let's say well it is probably realistic right so the fact that Bitcoin was not producing a block within one hour well sometimes it happens it is not because it stopped it was because just miners were not able to find the block that's it and yeah people
Typically, it should be found within 10 minutes. That's the way how the network is working. But in case there is a decrease of hash rate and it's just an unlucky day that people sometimes cannot find the blocks for one hour.
So it is just pretty stable. It was just not producing a block within an hour. And probabilistically, it can happen. Probabilistically, it can happen. With an extremely tiny
with an extremely tiny probability Bitcoin might not even find a block within one year, right? But yeah, but it is so, so low that with the highest chances it's not going to happen.
but don't give nightmares to Rodion, Alex, and everyone wants to sleep all right. Yeah, just forget about the last two minutes. I just wanted to maybe have one last question with a bit less technical
more general. Both projects are supporting a Web3 and Builders community in general. Let's start with Chainstack, your guest today. What does Chainstack do to support Web3 and Builders community?
in general. Right, so we try to be very very practical here and there's an infrastructure provider which is key to success for every builder in the space. We try to provide the best infrastructure, the most reliable, the fastest infrastructure and which
is very, very important for the builders in this space, the most affordable infrastructure. So we obviously are commercial company ourselves, right? So we are making money on the infrastructure, however, we understand and endorse the efforts of builders in this space. So that's why we develop our
pricing model in a way that is very very affordable to use. So for instance like our developer plan which is completely free and there is no string attached is very generous in terms of like what it provides in terms of like protocols it gives access to so in fact you can use like
all 18 protocols to support today on a developer plan, on Chainsack. And the features that are advanced are also very, very affordable compared to other providers like all the infuers and all the alkenes in the space. So we want to help builders in the space to have
have a affordable access to all the chains and have very, very democratized access to this. Because I think major value proposition for me personally, as I see it, for blockchain in general, is democratized access to things. And things can be collectibles, things can be
We want to retain the status of democratization of access and hence our pricing model for all the infrastructure that we do. We constantly think about how to make it really affordable and how not to make people spend like $10,000 per month.
per month on RPC, which is ridiculous. So that's why we have this model of, let's say, dedicated nodes that is very, very close to efficient for power users that send billions of requests per month. So in other providers, for instance, they would pay tens of thousands of dollars because they charge
for API call and in our case it's way more affordable because they basically can use their dedicated node in a way they want and send as many requests as they want. Apart from that we obviously do all sorts of like ecosystem activities so we support different hackathons
We run boot camps with various protocols as well. What we try to do also, which is quite unique, is we try to be very, very precise in our documentation and we try to deal the amazing documentation as
precise as possible. So if you go to docs.chinstead.com or if you go to our blog, which is most of the technical blog, you will see tons of information which is basically revealing some hidden subjects in space. Let's say how do I access Manpool and what are the methods of accessing it and how do
like pan-interjections and so on, like how to use GraphQL APIs with your EDM nodes, etc. So there's tons of information that we produce and our developer experience team produces. So we take the accommodation very, very seriously because it's also a piece that is very immature in the web space as
we see it because we as a founding team we came from a web2 space and we got used to amazing documentation for certain products and pieces of software that we used. So we want to bring the same maturity of the documentation in the space because this is clearly lacking in many many cases and we try to build the best documentation
that is helping developers. So we mostly try to be very practical, so we try to give the best services we can for the best price we can with the best documentation for our services as well as the related ecosystem pieces and software around it, including just like generalize documentation for protocols for us.
Thank you Eugene. When you said about documentation and etc. I agree that's one of the things that still to develop in general. We were speaking for example like maybe one month ago with the CEO of Brave, Brenda Nigh who created Java
And it happens last year, I was doing a bit of JavaScript. I'm a total newbie because I'm a marketing head. And it's crazy to see how easy we find things to deploy on JavaScript. And in crypto, it's way harder in general. So I totally agree documentation is a big deal for the future.
Alex, on the other side, are you supporting WebTree and Builders community? Do you have programs to develop new developers coming up to the network, etc? Anything that any action that Aurora is doing in this way? Yeah, in general.
pretty similar to what you generally was so was telling. We do not have any products that where people are actually paying for them. Rainbow breaches completely free for everyone. We really believe that the rainbow breaches is a
probably good and the public good needs to be good. So it needs to not to take any fees on this. Aurora, the usage of the Aurora Smart Contract is absolutely free. There are no force push for the users to own Aurora token,
which is the governance token of the Aurora protocol. So, naturally users are paying ETH for the execution of the transactions and with the services like Aurora Plus users are actually able to get three transactions on top of Aurora. Again, just free
making the public goods good. Then besides that there are also grants program that are available for small teams. Our our D belief is that grants are not working good. They are creating
and miscellaneous and unfortunately many people are misusing this and there are even companies in the space that have their business model that is focused around getting the grants which is obviously not the thing that we would like to have for our vertical.
So we are given small grants up to 50k to small teams who are willing to try out some of their concepts. And for the teams who are bigger than that and that are willing to get more money, we encourage them to actually do the fundraise and we are helping with
But with this, we have this special program for everyone who is running inside the forward ecosystem. We're helping them to connect with VCs. We're finding their pitch. We're providing some feedback on the market conditions, on everything that they have, on the product market feed, on the token economy and things like that.
Yeah, and obviously we also participate in handcats on some different things around it. Besides that, we have an additional, again, small grant program that is around people who are not coding, right, because
Blockchain community is not only developers, it's also enthusiasts that are fascinated by the technology. So we also would like to give something to them. So in case you are a creator, your production content, you're spreading the knowledge about the blockchain in one way or another.
You are able to apply for a so-called community grant program for Aurora. You can go to Aurora forum.oror.dev and see the information about it. I see on the people who are listening to this space
that there are some of the winners of this community grants. So that's great. And yeah, so everyone would be able to find help inside of the Aurora ecosystem. And obviously we are focusing on this part of the WebThru.
Thank you Alex. Indeed, I also see the community grant winner here. Thank you. Of course, thanks to the community pages for all they do for our, we really appreciate the work. And yeah, there is a program for that if you create good
content and TQ can create good content. Really invite you to go on forum.or.devan. Yeah. Just show out your ID and see if we can help you on that way. That was my last question. Now I have gone through comments and I don't
see any questions. So we got four minutes left. What I propose is maybe Alexa or Eugene got a question for each other. And I propose that you ask the question if you have one and if you don't have one we can stop here.
Yeah, I have a very conceptual question for Alex since you guys are building on top of a near-each system like what's the end game for Aurora within the near-each system which is having their own blockchain and
And the communities, I understand that EVM is apparently a way to easy access for existing EVM based chain developers, including Ethereum, to onboard
on the near ecosystem, but I'm just curious, what's the long-term plan? Where do you see our role in five years? Is it still operating as EVM-based chain, or do you want to, in some way, merge with near-blockchain, so I'm really curious about that.
Thanks for the question. It is really deep and quite important to understand. So our point of view on this is the following. We do believe that Nier is an extremely good settlement player, right? And a good
analogy for it is like TCP/AP protocol or the internet in general. So there are some services that are running on near. This is near is the way how people can communicate and figure out what is the truth and what is not. There are some services that are running on top of near.
that are extremely important, for example, for internet these services are type of DNS. So these things are there. And we see that Aurora, and we see actually that EVM is one of these services. It is the public good for the near protocol.
And this is something like a brand that developed JavaScript for the internet. So yeah, EVM is the JavaScript for this.
This is probably good. It's not like we are monetizing the EVM itself. But we're thinking of us and of the Aurora ecosystem as of decentralized Google of the near. If near is the internet, then Aurora is a decentralized Google that is running
on top of it. We are just maintaining and we are contributing to the public goods like EVM and breach, right? But besides that, we are focusing on the infrastructure around the Internet. So take a look here. Things that we are developing with Aurora Plus,
This is literally a browser and a search engine that are combined together because we are given an access through Aurora Plus to the whole New York system, not only to the EVM, but actually because of the ability to do calls outside of the EVM.
This thin is the access to the end users to be able to transact or in general on your blockchain. It's kind of similar to browser. Besides that, in the Aurora Plus, we are showing some additional information about the governments
And also the applications that are running currently inside of Aurora, but we are planning to extend this to kind of more surge capabilities, right, to find the place inside of the NIR ecosystem. Besides that, we are also working towards this scale
ability solutions that I was throwing some alphas around. And you can think of this as of Google Cloud. So Google also provides the servers that are supporting the internet or supporting the applications that are trying to run in the internet.
Something similar to this is what we are building right here right now. There are some thoughts around the AI applications and things like that. So I would say that Aurora is a, that near is a settlement layer, Aurora is a decentralized
Google on top of this settlement/internet layer and that's our outlook in the future. I love it and I think that you said multiple times besides that but I want to end it up with the fact that you are settling down
on near it's bringing the near valuation and the value of ecosystem also up. So I think it's very cool, like close circle, right? Basically you increase the value of the near ecosystem by adding more services and pop up near. So I really love it. Thank you very much.
Yeah, absolutely. It was a pleasure speaking to you. We need to do it more often. Let's do a recurring email about Infra and all the stuff around it. It was really great talking to you guys.
Thanks to the speakers, Alex and Eugene, I think this EMA was quality. Thanks a lot. And thanks for everyone participating and listening to this EMA and everyone's support, TIGCHIN stack and Aura, day by day. If you are not already subscribed to the Aura Twitter channel or the CHIN stack channel,
you come from originally, I invite you to do so support us to projects. You are the ones that are making it real. Thank you everyone for participating in this EMA and we catch you soon on our respective social medias. Thank you everyone. Thank you, LFG guys. Bye.