Lava Network fixes data fragmentation in crypto w/Omer Mishael

9 Apr 2024 · 4:01

Sebastien Couture talks with Omer Mishael on The Interop about Lava Network's approach to data fragmentation across blockchains. In this short clip, Mishael describes the problem of scattered, inconsistent data access for developers building cross-chain applications and how Lava's infrastructure aims to unify access to that data across networks.

Speakers

Topics

Transcript

as uh the ecosystem moves to a layer 2 rollup model and we have thousands of applications leveraging underlying security underlying data layers uh data availability lays um how will lava help support the growth of the ecosystem looking at the three existing modular Stacks you could see that the access for developers is kind of missing from the paradigm and lava aims to be that fourth layer of developer access and how we do that is we're going to aim to fix fragmentation so let's say we have a clipse building an svm machine on

top of a Celestia data availability layer and ethereum uh sment and then suddenly how do developers access that so do they need to now ask some centralized provider uh to to support it and then having you know up and coming ecosystems they need a way to convince uh um that it's worth it that it's financial and waiting for them to add it or even worse let's say di mention you know uh having 10,000 up chains uh popping up it would be so easy to set up an up chain but if it's very difficult to develop on it because the rule set of the up chain is not readily available for applications to process then that

could actually be the ball neck for scaling up and with a future with a paradigm where lava simplifies that lava supports these app chains very quickly and easily the modular specs the beauty of it is that they can inherit existing Solutions so let's say you created uh an svm you don't need to create a new spec you just say hey this is an svm let me inherit from an svm spec Define the new ver ifications that you need for your own solution being it for example a different chain ID even it could be the only difference uh in terms of you know data access uh and then providers can uh

serve it so the thing is specs are so flexible in the way that what you can bring into your existing solution without having a lot of work that uh it scales very well with new chains so for example bar chain had their test net very successful successful initially and they had RPC problems uh and Gil our CTO told me hey can we support bar chain and immediately and it took me 1 hour to deploy it on our test net and it took me longer you know to get people that have the binary to actually join it so the lava stack actually supported super fast and that's how easy it is to add existing Solutions uh and lava was built

to support all of those Solutions supporting so many different AP API interfaces being a grpc rest URI tender Min Json RPC websocket you name it graphql queries um all of those are abstracted by our clients meaning that you can you know just patch in your API set you define you know the the rule set of the apis stuff like the compute units that you're offering for each API so settlement is fair in terms of uh compensation and incentives to the load that you're performing uh um and then that's it you're ready to go you attract your providers if you have a faithful community that are already running it so they can access immediately developers

if you want to do an IPC Endeavor or you want you know developers are profitable enough to pay for it um they have the flexibility to do [Music] so