Delivering Amazon-like App Experiences
ProtoLayers Talks · December 2024 · 20:13
Prabal Banerjee of Avail explains how blockchain can deliver Amazon-like app experiences by combining speed, scalability and user-centric design. The talk connects the data availability layer and modular rollup stacks to what users actually feel in an application, such as quick confirmations and low costs without giving up decentralization.
Speakers
Topics
From ProtoLayers Talks, hosted by ProtoLayers.
Transcript
please join me welcoming P Pabo banery from Evel Pao we will discuss how cross and interoperability can deliver seamless am onine user experience in web 3 so the stage is yours hey everyone uh I know today this is the last presentation right so I wouldn't want to keep you guys uh here for too long I'll try to wrap this up as short as possible but at the same time want you guys to go out feeling that there is some new paradigm that is getting built and this is not just getting built by us that is so many partners in the blockchain ecosystem who is looking towards the same vision we
are trying to make our contribution in that part the title of the talk is essentially how we can have an Amazon like experience in a cross chain world now what does it mean to have first Amazon like experience and what is the status quo in the cross world is what we need to look at first one thing that I think is non-debatable at this point in time is how the status quo is fragmented you have your assets lying a across multiple different chains you want you have enough funds to do an action but you cannot do it because of the lack of funds on that particular chain or on that particular asset class and in this
kind of a world the user experience is completely suffering right and that is has been a big big point in the narrative play that has been going on where monolithic chains are taking over in terms of user experiences and and rightly so because as a user I don't want to care about which chain I'm using what is this security primitive and so on and so forth I just care about the best-in class experience we don't need to reaffirm our Point here but this is screenshots from L2 beat and such you can see there are like 50s of l2s that is there listed and many many more growing and we contributing to that Bridges there are many many types of bridges all having
different types of security guarantees and security assumptions and multisig and poas and whatnot and we don't have a very good feeling of how exactly the security model is changing behind like beneath the feet of the user when they are doing cross chain applications let's talk about bridges a bit this is one style of bridging but this is the most prevalent style of bridging that you will see today you let's say you have two chains optimism and arbitrum uh and you can change this to any two different l2s you basically lock your funds on one chain go to the other chain prove to that other guy that I really locked my asset on this chain
based on the on the Primitive that this guy is convinced of your statement they will mint corresponding assets this is only one part of the bridging suppose you have done your action here and you want to bridge it back you essentially burn this and then again convince this guy that you have essentially burned all your assets on this one this is a typical experience across l2s across chains but let's talk about a bit of web two experiences you are going to Amazon Amazon is just think of any other Marketplace that you
have let's say they are trying to give you the best-in-class experience but also the best-in-class product in terms of what a Marketplace can provide so here is your best Marketplace think of anything more often than not they only specialize on being a Marketplace they don't handle payments Amazon handles payments in some jurisdictions but roughly speaking generic nature of marketplaces is that they do not handle payments but you cannot buy a product without being doing payment right can you buy any product on any Marketplace without paying for it which means that payment is an essential part of that product which it is not building but it is doing so with something like a PayPal
or a strip or a payment aggregator now you see that these payment aggregators and you know all the familiar names on the space they are doing an amazing job just doing one thing which is aggregating payments they are the middleman where you don't need to worry about what your credit card or debit card or what kind of card it is it takes care to transfer depending on what kind of card do you have so it can connect to a Visa or a Mastercard or an AMX or something which is very popular in your jurisdiction but this is the guy which actually does the payment mind you that they do not hold funds Visa doesn't hold funds for you right your bank holds the fun fund your card has an account
balance and so on and so forth then how come something like a Visa is able to accept the payment on behalf of you this is because they actually make a call to the bank API this is the familiar pattern this is a promise result pattern that you see across the entire web2 stack none of the web2 services today work without a promise and a resolution of Promise so you make all asynchronous calls all cross web to when you actually think about it the the call back here is that Visa gets the affirmation from the bank the bank says that yes enough uh funds are there or they can settle it
with the user the Visa gives that assertion to PayPal PayPal gives the assertion to Amazon and all of this happens in a seamless manner you do not have to worry about whether you know you started with a Visa card or something Amazon doesn't care and it doesn't need to give this is the experience that I'm talking about when I say Amazon link now let's think of an Ideal World a Ideal World where you do not know anything about blockchains you do not know anything about chains what should ideally happen is you need to have very specialized chains which are very good at doing something that is because if you think of the product level stack the architectural stack you can make only
tradeoffs when you have specificity like instead of generosity generosity makes things bloated right and specificity is when what brings more and more you know user level experiences to the end user and that is very clear right today think of ethereum ethereum did a mindboggling thing of bringing General like computation inside blockchains they made General computation possible and no wonder that they are the evm is not the most optimal in terms of price in transaction you cannot do both things you cannot have tuning completeness as well as you know gas no no gas limits that's just not possible that is just beyond theory of
computation basic colleg is what what have taught us today but l2s took it a not up they took things to let's say a centralized sequencer which gives you some level of guarantees but at the same time now you can get user level experiences where an arbitrum can offer a 250 millisecond block time this is only possible because they are going for specificity in terms of how the architecture looks like that same level of specificity needs to go into the Virtual Machine level where you can think of one chain being very very specific to just handling nfts it's the best 721 chain that you have ever looked at it has all the basic Primitives and the pre- compiles needed to make ERC 721 as performant as possible and think of
another one which is a payment chain so think of any rc20 like token but it is The Ledger of your Choice which only tackles fible tokens in this kind of a world what you would want is a trade needs to be placed on this nft chain this is your Amazon whereas your payment needs to be done on the payment chain this is your PayPal or Visa or whatever equivalent this is what handles your payment this is where you keep your funds this is your hot wallet I'm not talking about a cold wallet let's say this is your hot wallet and this is the user level application which you are trying to do in this kind of a world what we need to have is you need to give a cryptographic
guarantee to the NF chain that the payment has been done that's how e-commerce scales and that's how we need to scale blockchains think of the times when there's a huge Sur surge in demand because there's a sale let's say there's a Black Friday sale or your typical you know local Festival sale here in that time the marketplace scales the payments don't payments know the kind of TPS that they can provide depending on which bank the bank doesn't scale up its resources just because there is a sale happening is the marketplaces which scale because the payments they take the similar Cadence enough jargon and enough
thoughts uh let's talk about how do we do it this is where a Nexus comes in we are trying to look at a world where you know you can seamless interact between two different chains and this we think is a precursor to how chain abstraction Works chain abstraction tries to abstract out and that is definitely definitely needed no doubt about it we are thinking of this as more like a primitive which enables abstracting of chains what does it do basically it is a permissionless verification Hub what it does is it takes multiple rollup States it computes the proof and Aggregates
them together and then provides a single aggregated proof back to all the other custom chains think of it like I do not need to verify one chain with the other I will talk a little bit about that probably here you can see today this is what what the interrupt today looks like you have four different chains you have hundreds of different connections all the different connections are of different security Primitives you have a validator set driven you have a light client driven you have a proof of authority you have a te all of these wrapped tokens are very different they are not the same the guarantees are not the same and that's why you need to create all the different kinds of you know user level interactions that you
need to do today you need to go to a bridge agregator to be able to bridge your funds you do not go to Bridges even today and what does it mean it means that when you have one aggregated proof and zero knowledge proofs gives you this enormous benefit where you can basically comp compress computations together you do not need to verify individually chains you just have to verify one aggregate proof this aggregate proofs verifies that all the straight transition functions across all the different chains worked actually correctly that what was defined in the state transition function itself so evm chains they already have evm if you just agree that there are no new pre- compiles and such added then that is a
specific type of execution engine and that means that all different execution engines are actually having the St same state transition function which we can verify just tell me when it's five minutes but like what do you actually need to verify your rup that is extremely important because you can tell me like why you why a needs to do all of this why cannot I do it with any other play that is there in the market and one thing which is very very core to our philosophy is that of security right so so we were thinking from the bottom up that what is the security of a rollup what gives the rollup its security so there are two main components one is
data availability and the second is execution a rollup which cannot prove it execution is not even a rollup right because then it's a pessimistic solvent chain construction when it talk about a rollup it has to have verifiable execution and that today typically is done through two methods one is fraud proof the one we known as optimistic chains and the other is validate proofs or ZK rollups so these are the two main types of L2 Stacks that you see today that is all fine but if you do not have the transactional data or the state Delta you cannot reconstruct which means that depending on what is your uh execution proof you can either get stuck or you can get completely corrupted in
an optimistic chain if the data is not available no one can actually act as a watcht you can completely get censored of the data which means that an attester can attest to arbitrary statements which makes makes it completely insecure in Z rollups it's much better you cannot get live you cannot get safety failures because it's a ZK rollup the soundness of the ZK proof allows that but you can get stuck in in terms of you know you know that you have funds you know that the computation was done correctly which is that no fund was compromised but you just can't exit that's that's what enables like having data published for any user to do is have arbitrary exits
and that is one of the core thesis of why rollups are secure this is what we are envisioning we are envisioning that different rollups all just talk to Nexus and the Nexus acts as the source of Truth for for all these chains to each other when I say source of truth I do not mean that Nexus has again a different security primitive when I mean is how can I make this the most trust minimized construction that we can so this is what we are thinking we are thinking that there is this Nexus middleware which takes the State updates from all the different chains and then provides one single aggregated proof back to all the other chains which means that if I want
to know the state of chain a I just need to verify one aggregate State not only a I get P to Z for free I may or may not use it that's on me because you have to make chains Sovereign right I cannot impose interoperability that is just you know breaching their sovereignity but at the same time there is no harm there is no level of extra computation that they are paying because the aggregate proof is just the same that's what constant size aggregate proofs are giving you today okay sounds great but what's the bottom leg why hasn't everyone done this already why haven't we done it already and showing a working demo this is purely because all the different rollup
Stacks use different kinds of proofs today the proof side is also very very fragmented if you see um a polygon ZK VM has a different proof system than a ZK sync which has a different proof system than a start net which has a different proof system than a scroll where do I go how can I make these rollup proofs all the same and this is where the adapters come into the picture we are trying to provide a homogeneous interface is across heterogeneous proof systems this one is the trickiest bit because now you do not need to you need not need to worry about others curves and what is most optimal whether someone is working on a 32-bit field or a 64bit field or a 56-bit field whether integers are native
to that construction or not you do not need to worry about that because all you need to worry about is can I have a single verifier encoded as an adaptor which in turn makes all of this click together in the end this is what we want to look like we want to it to look like this that the it should look like much like the airplane ticket booking system or the Amazon experience that you have today you want to buy an nft yes you go and reserve the nft first you do not need to reserve it yourself the wallet takes care of it it reserves the nft it then asks for NEX Nexus for a proof of payment inclusion
where the user makes the payment the payment inclusion goes to Nexus and it can be proved that the payment was done what's better is you can also prove that the payment was not done what cryptography gives you is both sides you can prove if it's a sound and complete kind of a environment then you can not only prove that you had included a payment or you have done it done it or you can also show a timeout today most of the payments that you do not actually go through are actually timed out right now after you time out how do you show that within the certain period of time you actually did not pay out that is why you can here give a payment of like a proof of inclusion but you can also give a proof of non-inclusion those are the
powers of cryptography which will make it look like this where you have both execution and data separate there are n number of modular chains all building with different types of stacks and there are many many other Stacks which we have not talked about today all of them posting proofs to Nexus and the most basic thing is you can run a light client your wallet can run a light client your Raspberry Pi your Smartwatch can run a light client in order to verify Nexus which means that you can also verify that all these different chains actually did did their task correctly think of the enormous level of user experience Improvement and the user guarantee Improvement that you can give
today either you ping an RPC which is a centralized service and you realize that whatever account balance that they give to you is correct or you run a complete full note none of which are possible in user level devices when you go into a light client mode when you have the power of verifiability through validity proofs and data avity sampling they two together make it all possible to run inside a light plant you neither need to download the entire data that's data sampling nor do you need to rerun all the computer ation that's what validity proofs skes to talk take it all back this was the Amazon like experience that's what it looked like hopefully this is what we
can bring here where there's an open se you can go and check out and this is not not far away right many many of the existing top-of-the-line daps are starting to becoming their own app chains so I'm not talking over a world which has never been seen before it has already been promised people are going to build their own application specific once you reach a significant level of scale you have to provide your users with better guarantees and that can only be provided with application Level rollups once you have application Level rollups then this kind of experience has to be there otherwise as synchronous communication cannot work out all of this inside the same chain cannot scale up and if there is no real trust
minimization guarantee between then you will face the cosmos L conundrum where there are individual usually they are all secure they are also connected but they don't talk to each other that's it thank you happy to answer questions thank you very much proo from thank you M for sharing the insight and uh it is still around feel free to you know connect and discuss with him as well and this is a final session for this Buddhist St went and that wraps up our Pro layers conference so thank you so much everyone for being with us today and our sponsor as well for making this possible and have a good um trip and enjoy call as much as you can before the
W up of De conservant so have a good trip thank you very much k