Projects
![]()
No projects found
Investors
New
DAO Treasuries
DATs
Lend / Borrow APRs
Chains
Categories
Spaces
How @injective is Reshaping the Future of Finance
Recorded: March 20, 2025 Duration: 0:45:23Space Recording
Short Summary
Injective Protocol Launches with Innovative Features and Strategic Partnerships to Revolutionize Decentralized Finance. The discussion highlights Injective's focus on fast transactions, zero gas fees, and shared liquidity, positioning it as a key player in the evolving landscape of decentralized finance.
Full Transcription
All right, so we are live.
So hi, everyone.
Welcome back to another stream where today we
will be talking about the Injective protocol.
And with us today, we have Shuhan from Injective.
And he is a dev rel engineer at Injective.
And Shuhan will take us through what Injective is
and what are the key differentiators of the Injective chain.
So I'll pass it on to you, Chuhan, where, you know, if you want to greet the audience,
ask them questions or give a brief introduction about yourself, then teach everyone of us about
Injective. So over to you, Chuhan. Thank you, Sahil. Thank you.
So, hi everyone.
My name is Chuhan.
I'm from Injective, now working as Gabriel there.
And I believe most of you have heard Injective before,
but probably not know exactly why Injective is so unique
and what's the very, you know, the most powerful feature that Injective Blockchain can offer to you.
So during this presentation, I will help you to understand better about Injective Blockchain.
And also we're going to dive into the modularity and the multi-VM and why all those features can shape and define evolution in the future.
Before we start, I want to give another special thanks to QuickNote.
QuickNote is a very good infrastructure partner for us.
At the end of this presentation, I think I will give a few minutes quick live demo to show you how you can easily set up the endpoints
with QuickNode infrastructure
and do a quick interact with the injective network through it.
Okay, let's start our presentation.
So what is Injective?
We always give one sentence to answer this question.
Injective is a blockchain built for finance.
But what's the meaning behind of this is,
for now, we think finance is still under the majority
of finance or the mainstream finance is still under a centralized system.
But we all believe there is a trend for the next generation finance.
It's going to be more decentralized and people can actually control their assets and actually
managing the assets
by themselves. They can save their profits. They can trade with freedom. I think this is a very
good definition for next generation of finance. So how the next generation of finance required for a blockchain. I have some, you know, I have some,
I have conclude few points I wanna share with you.
So I think first, this blockchain need to have
very high speed and should be scalable, highly scalable,
because, you know, you just imagine in the real world
when you type your credit card, you want to pay for a coffee.
A lot of the millions of people are doing the same thing. So this system has to have the ability to
process your transaction along with the millions of another transaction together,
parallel, or finishing instantly. Otherwise, I won't feel good if I want to pay my coffee
and wait for 10 minutes until my transaction has been confirmed on the blockchain. That
would be a very inconvenient way for the daily or real-case use.
Second, I think this blockchain or system need a tailored financial tools.
I mean, it's some customized or specialized financial tools that the users or the developers
can easily find on this ecosystem.
So that there's no need for rebuild from zero, there's no need for extra developing resources wasting to
rebuild every real. And I think third, it's also very important since it's interoperability.
Because finance, we're chasing for the efficiency, we're chasing for the
capitalized efficiency. If the blockchain or the existence is too isolated from the others, which means you
cannot leverage the entire liquidity from the entire blockchain industry.
But with a high interoperability, you can actually leverage the other ecosystem's
liquidity or their advantage so that the entire ecosystem can be better and more stronger.
And the next one is, I think this blockchain needs to become very cost-efficient.
That's also very natural thinking.
Like if I want to buy a coffee through this blockchain, I don't want to
charge me more than the price of the coffee.
More specific saying, I hope this cost
won't cost me extra
fees for buying the coffee.
And also, I think the next few points are also very natural.
Since we are the next generation of finance,
we need to have decentralization, we need to have transparency.
And also, I think the last very important part is
this blockchain needs to have a resistance to the manipulation.
For example, like MEV, you know, if we really want to build some blockchain for finance,
it definitely needs to be anti-MEV. Otherwise, a lot of value has to be attracted by the,
a lot of value has to be attracted by the no matter it's validator or indexer or some
malicious node.
So I think the anti-MEV feature is also very important for blockchain who wants to be the
foundation of next generation finance.
Okay, let's dive into Injective,
then see how Injective's features support
all of those points that I mentioned above.
First, Injective have very fast transaction time.
So you can imagine this injected blockchain can confirm
and send it to your transaction and process it,
execute it under one second.
So it's really fast compared to the other blockchain
like Ethereum or Bitcoin, very slow.
Normally in Ethereum ecosystem, your transaction
needs to wait a few minutes until it's confirmed, received by the
validators and then submitted to the EVM to be processed. Also, in order to make it become unchangeable, you will need to wait more than 32 or 64 approaches
until, this is a mechanism under Ethereum 2.0.
So you need to wait more time.
Normally it's gonna take you 20 to 30 minutes
to achieve like almost,
make your transaction almost unchangeable. takes you 20 to 30 minutes to achieve like almost,
make your transaction almost unchangeable.
So this is not, I think it's not so good,
but the injective is just very fast confirmed.
Next feature, injective actually offers
zero gas fees feature.
So like I mentioned before, you don't need to, if you want to buy a coffee
to inject it, you don't need to pay extra fees to process these transactions. So this is very nice.
So Chuhan, like on traditional blockchains or other blockchains like Ethereum or its L2s,
the miners or validators who actually keep the network running,
who secure the network, who confirms transactions,
produces blocks, they are incentivized by gas fees, right?
So how does zero gas fees work on Injective?
Yes, yes.
So I wanna say this in some of the DApps
in Injective ecosystem, actually the user interacts with the DApps, it's zero gas fee, they don't need to pay anything.
But if a user wants to send a transaction to injective network, which is like, you know,
execute a smart contract or just upload their code into the network,
they have to pay a very little amount of gas fee.
Like a 0.0000001 dollars, something like that.
So it's almost like just zero.
And I think you are also building like, just like zero.
So I'll conclude this like practical zero,
but not theoretical or technical zero.
And so it's very negligible.
So you can say that it's like close to zero.
Yes, yes, yes, yes, exactly.
Okay, I understand.
Yeah, that makes sense.
So next we have smarter smart contracts. This is maybe not easy to
understand but here's another word to expand this. Because Injective is
supporting Wasm, which I think Wasm is very very better language to
define smart contract because it has highly modular design
if you ever writing smart contracts through WOSM
and also it's running resources are really low.
So actually it's very cost efficiency
if you're running WOSM smart contract.
So I would like to conclude
that it's smarter smart contract meaning.
Also, another very important feature is the order book that Injective offers for the users.
This is a native order book feature that users can directly use and can feel the power behind it. I will go over a little bit about this later, but
I think this is one thing very important for how Injective can become the
the next foundation for the
next generation finance.
Oh yes, definitely because for this particular use case or order book, I think it's very
I for this particular use case or order book, I think it's very interesting and beneficial
that injective is offering order book out of the box natively because on other chains,
usually order books or these finance order books are maintained by third parties or third
party protocols not offered by the chain team itself.
So this is very interesting to see that Injective comes
with the native order book support.
But how does that work out?
Like does that comes natively supported
or is there a native decentralized order book
already maintained or people can create their order books?
How does that look like?
Yes, yes.
So in Injective, we have a lot of customized and powerful
and easy to use modules that are developed by our engineer team.
So the audible feature is also contained by the Exchange module.
It allows users directly interact with Exchange module
and to create audible system by themselves.
So no need, if you are a developer,
no need to construct an order book by yourself.
Also, this order book is an MEV,
so no need to worry when you're using this,
when you use this order book system,
your EAPs or if you place a deal or place a trading on that,
you will suffer by MEV, it won't. So it's very easy and very powerful tool for everybody to use it.
Understood. Yeah, I mean, it's very powerful having a native order book where you do not have to worry about using a protocol and the order book native order book which is backed by the protocol itself created by the protocol itself is very powerful. utilize or leverage the power of Tendermint consensus.
So it is very, also another very good
and very powerful consensus algorithm
that we use in our blockchain.
So by leveraging its power,
we can achieve over 25k TPS.
to 25k TPS. So this, I think this surpass most of the current existing blockchain. Just imagine some
of the parallel EVM chain, they only can, you know, can have the number about TPS around 10K,
but with 10 remit consensus,
we can easily surpass 25K.
So this is super powerful.
And with that, you can just imagine
why we can have very fast transaction time,
and also why the entire block stays
can be confirmed in very short amount of time.
This is also another important feature
that the decentralized finance ecosystem requires.
The next very good feature is we have shared liquidity,
which maybe not easy to understand,
but I will also give an example to explain this.
So in the objective ecosystem, the different DApps can also be, can also benefit by the
share liquidity features.
Just imagine there's two DApps like Helix or another one maybe Mito.
These are all our ecosystem projects.
So if somebody, a user, wants to buy 100 INJ on Helix,
but the liquidity provider just placed a sale order for 100 INJ on my note. The shared order book will automatically match
these two order or transaction together,
even though they are from the original
from different applications.
So just here that you can feel the power of it,
because in this ecosystem,
all of the DApps
are naturally connected because they have the shared liquidity.
So this also can, I think, increase the capital efficiencies
by this feature.
Got it.
And this just speaks about the native order book support,
right, like the power of the native order book support, like the power of the native order book support
where anyone can match their orders with any other person,
regardless of what app they are using.
So yeah, I mean, it's very powerful, I think,
because nobody has to worry about segmented or side load
or fragmented liquidity.
It's there for everyone to use.
Yes, exactly.
Just imagine if you were a developer,
you want to build your own, maybe exchange,
maybe another like define the apps.
But if you think order books power,
you can also join the share liquidity family.
So you don't need to worry too much
about your liquidity provider because the entire system
person
Yeah, that's why some sort of
like
In a way you can say that the entire ecosystem or the entire chain itself acts as a very big
Widespread exchange in a way like not exactly but in a way because it has a shared order book
so that anyone's order can be matched with a seller,
anyone can buy from a seller and orders can be matched.
Yes, yes, yes.
I think this is also very important for those small
or start up projects because they don't have that many resources small or you know start startup
projects because they don't have that many resources to find
Find the liquidity providers
Okay, the last one I think the very good features is we have a lot of
Plug-and-play and powerful modules. I will
Introduce you some of the modules in next page. I already
mentioned order book module and its power. It can share liquidity.
Thanks for the order book, the share liquidity feature can be
implemented. We have binary options module which can support more market derivatives options for people.
We have Oracle module, like we have a built-in Oracle module so that in Injectives,
it's super good power to link RWA real-world assets into Injective because a powerful oracle, a good price feed oracle can always give you
a link connection between the real world and the blockchain.
So with this power, Injective can actually do a lot of RWA assets, like maybe in future we can do can see sports maybe better or any other like
rwa just coming to injective ecosystem we have bridge module this is also very powerful
we have peggy it's it's deployed on ethereum so it's a the key key component to connect us with Ethereum ecosystem. It allows users to seamlessly transfer
their assets on Ethereum to Injective. So this also increases our interoperability.
We have smart contracts module.
We have Smartcom Trans module. Yeah, we have option.
Yeah, we have option modules.
Sorry, I would like to interrupt you with a question.
I have one question.
So just like order book,
are oracles and bridge modules available natively
where I as a user can just come to Injective
and use the oracle and bridge module
to for the oracle module create my own real world feeds
and for Bridge, just bridge my funds
or these modules help me to create my own Oracles
or own Bridge, how does that work out?
Yes, actually, like the title said,
it's plug and play modules.
So we have injected SDK, it's exposed some of the modules interface to users, to developers.
You can easily invoke those exposed interface and interacting with those modules.
So if you want to build just like order book module, If you want to build some,
reach the apps or you just want to,
or in your own Dapps,
you just want to breach something.
You don't need to searching for another solution
or you're writing a bridge by yourself.
You just play with the injective SDK,
with the bridge module and then everything's fine.
Understood, understood.
So a follow up question on that.
So as you mentioned that all of these modules
can be used in a plugin play format
or can be used via the injective SDK.
So let's say that I as a developer,
like develop a new module,
let's say a swap module or a dex module, just for an example.
So will that be, or can that be made available via the SDK
in future and used by other users via the SDK?
Or how does that look like?
Are these modules open source and can be made by users
as well or just by the team?
Yes, I think since we have a governance module, so if in future users, developers,
they really do create a very good modules that are very special, have special power. For example, maybe they have like AI trading modules,
something like that.
Maybe they can just submit a proposal to apply,
to apply to make them module become one of the
native module of injective SDK.
It's totally possible if the proposal passed.
And so from what I'm hearing,
there's a module for everything.
Like there's a governance module as well.
Yes, yes.
Okay, so we have finished this part.
And in the next part,
I wanna explain on the technique wheel to everyone why we need multi-VM environment.
As the picture saying that we want to have native EVM, we want to have SVM, we want to have Wasm support in Injective.
Why it's so important? So as a builder, you know I'm a developer relationship,
so I have contact with many, many builders. So there's, it looks as there's many options for
them to build in Web3 World, but actually if you categorize, it's falling into like these four
pillars. Most of them will choose Ethereum or Ethereum Lirutus.
Most of them will go to develop in some customer Lirutus.
Some of them will go to another VMs like HVM,
like Movin or just Watson.
Some of them will develop into a AppChain.
But there's one fact, the reality is, EVM currently is dominant in
crypto, especially in developer side. We can say there's so many Ethereum,
Symmed, Hackathons, Hackathouse, a lot of people, even myself,
when I first get in touch with Web3, I'm learning, the language I'm learning is Solidity.
So I know how to write part contract in Solidity.
That's a reality.
So, but we also know there's a lot of limitations
But we also know there's a lot of limitations of the EVM, of the solidity.
of the EVM, of the Solidity.
Included but not only restricted stack based architecture and also only 24kb contract byte size.
And also the performance is not that good.
Compared to 25k TPS chain I think Ethereum
itself the main chain right now it's a bit a little bit slower and it's I know
the Ethereum foundation they're trying to upgrading the blockchain they
they introduced a lot of upgrades by the past.
Also, they introduced the idea of layer 2.
But I think it gives some upgrade, gives some optimization, but not good enough.
Especially when we are under the topic, under the theme of the blockchain for next generation finance, I think EVM,
Ethereum and those there too are still behind the high performance requirement from the
topic.
So this is all of the drawbacks that we already know.
I know they keep upgrading, but still I think if we're looking for another option,
another ecosystem, this might be a better way
to achieve our goal.
And SVM also have some drawbacks.
For example, SVM runtime mandates explicit state access
declaration and concurrent design.
Also it has limited compute budget sometimes you will see it. And also I believe for people who
experience or who tried pump the farm before sometimes especially when there's
There's meme season, I guess, just a few months ago,
when I tried to chase meme tokens through pumped file,
especially when the busy period,
the transaction just stopped there.
I don't know whether it's processed or not,
just stopped there, and also I cannot resubmit or something.
So there is also some challenges with SVM.
So the conclusion is all of this framework
have some trade-offs.
For Ethereum, it's a little bit slow,
and it's not very good scalability.
For customer, there too, the lack of infrastructure too,
because maybe they have their own design, own consensus.
So it's all made by themselves.
The infrastructure is not that good.
And for like SVM, it's has its own challenges for APChain.
Also, it's just made for themselves.
It's not have like very global standard
like developer tools for supporting developers.
But we can leverage,
we can combine EVM contract, smart contract
with the advantage from injective ecosystem
through a multi-VM module that injective gonna have.
Right now, what does this mean?
It means you can develop your Dapps through EVM contract
and it can also access all of the modules in injective.
Just imagine how good it is.
For example, if I create a Uniswap,
or I just copy paste Uniswap code
and deploy an injective EVM module,
that means you have EVM DApps
which lives on injective blockchain,
and it can join the share liquidity feature.
We can, you know,
enjoying the benefits from the injectives, very good, uh,
interoperability and also the, all the other benefits from there.
Just imagine how good it is.
Your unit swap can benefit from 25 K TPS consistent.
No need to,
your user will not need to worry about low latency and
also the very high gas fee because Injective has almost zero gas fee for your user.
So to have a multi VM support in Injective is a win-win situation for both developers
and our chain.
For developers, they don't need to... I know Rust is very good.
I know Rust is a very strong language.
But in fact, if you're coming from a certain ecosystem,
you only know Solidity.
To learning a new language and to learning new tools to develop your project,
it's always time consuming.
But when we injective ourself, native support EVM,
this not gonna be an issue again.
And also you can, at the meanwhile,
you can benefit from both very good features
from injective itself.
Here's one of the approach that we probably can,
we gonna have, like how you can leverage the features from injective
or how you can leverage the advantage
of the injective modules that we will have some pre-compiled,
EVM pre-compiled when you're smart contract encounter
those pre-compiled command or codes,
it will go communicate with no matter what's on contract
or the other injected module like order book or exchange or bank module.
You can just enjoy all the benefits through it.
So, John, if a developer wanted to deploy a contract, will it be in rest or solidity?
Or from what I'm seeing right now, it should be in solidity and then it gets compiled into
Wasm and then they get executed? Or how does that look like from a developer's point of view?
No, it's not compiled to Wasm. You still have your Solidity contract. You don't need to change a bit.
It's just when your contract process in injective EVM module, it will be decode as opcodes.
You know that. During this level, developers will not know. Only the virtual machine itself knows.
And when the virtual machine reads through
those lines by lines of codes,
when they encounter a very special one,
it will know, immediately know, okay,
this one means this smart contract,
this DApps wants to communicate with other module.
So it will send a message to the other modules
and other modules will give some feedback back or change the state so that it can, so your EVM
contract or your EVM project can actually invoke the other injecting modules by that.
between modules by that.
Understood.
But since it also supports VOSUM module,
so I can also write contracts in REST, right?
Or it still has to be in Solidity?
You can just write Solidity.
It can interact with VOSUM module,
which means you can write solidity contract.
For example, I have a counter in solidity contract
and I have another contract writing Watson.
That says when the solidity contract,
which the counter, which the 100, I do something.
You can do something like that, you see?
So, which means your, your EVM,
your solidity contract can actually interact with Watson contract
But this does not mean you have to
Transfer the night. It's just and have the connection make the connection between these two
Understood yeah, but that makes sense and that's clear now
Yes, yes, I think maybe this can make some developers or hackers. I mean,
the hacksaw hackers have some very great idea or really playful idea in future.
Just link these two languages together. And it doesn't. Yes, so okay, I think I already covered this part,
but I wanna end it again.
You can just leverage all of the native injective benefits
from your Solidity contract or your EVM project
the contract or your EVM project if you deploy an injective EVM.
if you deploy an injective EVM.
And also you can benefit from injectives interoperability.
So that means your Dapps can benefit from all of the ecosystem because just like I mentioned before,
mentioned before, we have the IBC to connect and also the bridge module connect with a lot of
different ecosystems. So users' assets can easily be transferred into Injective.
That's the capital efficiency can increase also a lot.
So John, would you like to reiterate what IBC is? IBC is a
Cosmos SDKs tool which allows the blockchain to connect with different
other blockchain or interact with different other blockchain. It's like an
interface thing. So if you, anyone can implement the
IPC for certain blockchain so that they can, these two can do some interactions.
Understood. Yeah. Thanks for explaining that.
Okay. Technical features for injecting EVM. Yes, we have all those, a lot of these features are
just inherited from injective itself, right? And also we want to make this injective EVM
as, you know, as similar as EVM it is. I think 100 is our goal. So ERC4337, account obstruction also going to be supported by our EVM.
Nice. So account obstruction like ERC4337 is going to be, is available natively as well?
Yes, it's going to be available. So if you want to build up your AA wallet future,
and deploy our injective, it's also going to be supported.
Nice, yeah.
That's another very powerful thing
to have natively available.
Yes.
OK, let's go into our final part.
I want to do a QuickNote integration demo right now,
maybe take a few minutes,
because I think QuickNote offers very good
infrastructure experience for a developer
who wants to deploy their own endpoint
and have their dedicated endpoint by themselves.
So if you go to your QuickNote account, log into the dashboard, you click
quick endpoints, there will be a lot of choice. If you just search injective, there will be
injective pops out. Let me just change my share screen to my web browser.
So, Shuhan, have you used the injective endpoints
from QuickNote yet?
How has your experience been so far?
I haven't used it before, yeah, once.
And I just want to do it again to show how easy
and how quick you can just set up your own QuickNote
test note for now.
Yeah, let me reshare my screen with my QuickNote page.
And for everyone who is watching, if you have any questions about injective for Johan, drop
them in the comment section below and Johan will be happy to answer them.
So let me pull up his screen again.
Yeah. Let me click Create Endpoint.
Just like I said, there is an interactive.
I click Continue.
There's an interactive testnet node that I can deploy.
Boom. Yep. Okay, since I already create the free one before, so this is not an option for now, but you can see the price level, so you can choose whatever you want.
I just create a free one.
It costs you nothing.
Let's go back to after you click this I just create a free one. It's cost you nothing. Let's go back to, after you click this,
your endpoint is just live.
It's super easy.
And we can be done in just a minute.
Let me just click that.
And for everyone who's watching,
like you can just create a endpoint for free.
And like on the free account, the only thing is that you will only be able to create one endpoint and that account will be free forever.
You do not need to worry about paying anything. Of course, that will be a little bit rate limited, in the sense that you will only be able to send certain amount or certain number of requests
per second and you will only have certain amount of credits in your account.
But still it will work if you just want to test out a new network, if you want to check
out a new network, that's the way to go.
If you are just exploring the network, that's the way to go.
You do not need to pay anything.
It will be free forever.
Back to you, Chuan.
Yes.
So let's go back to the one that I just created before,
this live stream.
You can see we have everything synapse is active,
and we have HTTP provider.
So let's do a check if this actually work.
if this actually work.
Sorry, but I need to change my
service plan to my terminal page.
Yes.
Yeah, that's fine, John.
Yeah, the last one.
Won't be long time. Okay. So yeah. Can anybody see my, uh,
everybody see my terminal? Yes, we can see your terminal. Okay.
So I will expand this command. It's, it It looks scary but actually it's not scary.
Okay, so it means I'm running injective which is a command tool
from the injective team. It allows you to interact with injective blockchain,
submit transaction or interact with module. It's all powerful in one tool.
So you can install it in Injective documentation page.
There is a full tutorial to teach you how to use it.
I'm using a Dockerized Injective
because it only supports times,
I mean Linux system,
but my Mac because it's old version,
so it's not M1 chip, so it's not supported.
I will instead use tokenized one to run in the injective.
And also what I'm doing is after this injective command,
it's curi bank balance following with my wallet address.
I think it's very straightforward.
It's just injective curi bank is a module that I mentioned before and
the things to comment that I want to
the thing I want to query is balance and following with my audio address and the chain ID is injective
888 is testnet ID and node I just replace it to the QuickNode one.
You can see it.
I just create it.
So let's say it will return.
And Juan, after the stream,
make sure to delete that API,
like that API token and create a new one.
You can do that from your QuickNode dashboard. Okay, sure, sure, sure. Okay, I just released some private info to everybody. I will delete it.
It's not gonna be used anymore. Okay, so you can see I have a lot of people
balance under my injective address, so it actually works.
That is the little demo for you guys
to show how easy, how convenient you can setting up
your own quick note endpoint
for your development with injective.
And can I, yes, can I go back to my PBT?
There's one last slide I want to show.
Sure, sure.
Please, please go ahead, Chuan.
Yeah, so as everyone saw, Chuan just showed us
how you can interact with the Injective blockchain
using Quick Note Endpoint and injective command line tool injective.
using QuickNode endpoint
and Injective command line tool, Injective.
Yeah, that's the command that just used already expanded.
And I want to thank everybody. Thank all the audience who come to this live stream. Thank
Note again. The QR code attached is our developer Telegram group.
You are so welcome to join, scan the QR code
and join our Telegram group.
If you have any technical question,
you can just post there.
We are gonna help you and give you
technical support anytime.
And in Jagatthi, this year we also host many hackathons.
And also there's one hackathon just over.
It's AYA hackathon just over it's a hackathon
we co-host with DoraHacks and we have a prize pool about 100k USD
so please subscribe with our Twitter official Twitter account and
looking forward to see you guys again in this year's big conference or another event with Injective.
Yeah, 100%. Thank you so much, John, for explaining us what Injective is and how developers can
leverage different modules and native things which comes out of the box with Injective,
with Injective, which on any other chain,
which on any other chain people will have to use 10 different apps to do that.
people will have to use 10 different apps to do that.
So for everyone who's watching us,
if you have any questions for Chuhan related to Injective
or how to get started with Injective,
feel free to drop them in the comment section below.
And I will highly recommend all of you
to join the Injective Builders or developers chat
by scanning the QR code,
which is being displayed on the screen so that if you have any questions later on as well you can simply ask those questions in that
chat and get support from the Injective team. So, Shuhan looks like you did a really really great
job at explaining everything about Injective,
and people do not have any questions related to it.
So, I think we can conclude over here,
and for people who are watching this
as a normal YouTube video,
after this has been uploaded on our YouTube channel,
if you have any questions during that time,
again, you can drop them in the comment section below
and we will make sure to get them answered
by Chuhan or Injective team.
And during that time also,
you can just scan this QR code
and ask any questions in the Injective developer
or Builder's chat.
So thank you everyone who joined us
and who has stayed with us for this long.
And we will see you in the next stream.
Thank you so much, Johan, for joining us
and taking us through what Injective is
and how people can get started with Injective.
Thank you, Sahil. Thank you so much.
Thank you, everyone.
Thanks, everyone.
