When EVM "Mini-DApps" Go Gasless...Web3 UX Reimagined!

Transcript

GM everybody. Um this is Neil from Kayat. So today I would like to talk about an an amazing UX features that is actually you know bringing the web3 UX to the next level in our industry. So um first of all as a as a context um Kaya is a EVM chain. So we have been the exclusive messengers layer one for both line messengers and cacao talk and we have been embracing the focus on you know mobile first mobile only super app because that's you know that is based on the messengers and we are also embracing 250 millions uh users monthly active users uh you

know thanks to the messengers uh for both messengers combined together and as a EVM layer one we are very much looking into a high throughput put EVM chain that is really focusing on the UX and maybe I would say um improving the uh UX problems that we have compared with different EVM chains or maybe from the T foundation where everybody you know has been basing on when you were building your layer one Ethereum. So uh our mission is very clear uh for our ecosystem. We are very much focusing on on boarding the 250 millions uh users from the messengers that is from the web 2. We are laser focused to bring them from the web two to the web 3 and also uh allowing builders to scale uh you

know with you know turnkey crypto fiat payment so many uh features that they will be able to use and so many use cases that they will reveal and actually uh on board uh more liquidity and more I would say volumes right to our layer 1 for kay for the context um we are EVM layer 1 as usual When I say yuzu, I mean uh Kai is actually coming from a merger between the cacao blockchain called Clayton and also uh the finer which is the line blockchain from last year. So uh Kay actually inherited the layer 1 from Clayton which was you know built more than 5 years ago and that's why the network has been very stable and

producing over 2.6 6 billions transactions already over the five years and also more than uh 190 millions right like that for the blocks that we have ever produced uh during the course of um almost 5 years and if you really look into um the test stack of it we are fully EVM compatible so I would say equivalence so we support any of the EVM 2's logics EIP you know fast and reliable low gas and this is the reason why bring us to this to this talk is all about the gas abstraction. So f first we do have a fee allocations and you know from this year we're looking into user can pay gas uh with other tokens for example the US on kay. So the one second

finality is what we are also embracing which is the like kind of immediate finality. So what you see is what being finalized already. So this is quite standard for AVM layer one. Now guess what I mean when we get to the bottom of it like um maybe since the inceptions of um Ethereum yellow paper back in 2015. So we know that we need gas fee uh is required to execute transactions on the network especially that is exclusively you need the native gas token by default to do that. with the gas we can compensate the validators uh to uphold the network security and functionality and at the same time is actually looking

into if that will be encryptions happen for example that leading to the network congestions so we're looking into it that could be a deterrent uh for the network um to I would say uh in response to anything DOS attack and gasp is really here to making sure we remains both operational and secure for for the layer one network. Now getting into a bit deeper right when we think about UX problems related to gas straightforward when when any devs architect you have a layer one or say like EVM layer one straight away they will say you know what I'm going to put a very low gas like peppercorn gas like really really minimum that maybe one of

the hundred of what Ethereum is causing right now so as today Clayton or Kaya have been doing that already so no test cause uh sorry lower transaction post on users which means that uh you know the users will be very happy for that. Now onto the gas payment uh in native gas token by default. I want to have a quick sort of hands from the audience like do you have any experience that you want to send a transactions but you don't have a native gas tokens then you don't know what to do with it. Uh some sort of hands like some people don't show up probably they get a g um big backs of paying for the gas. I don't know but anyway it's just a little bit meme wreck that just in order to have the transactions on any of the EVM you need

to have the native gas token to do so this experience that um which is a fragmented UX uh which add complexity uh and uh and friction I would say that um which is still the most pressing US problem as of today when we are you know operating our layer one and growing our layer one. So then it leads to okay so if you don't have this um if you don't want to have this problem you were trying to solve it there there's so many example that people looking at the gas abstraction and with the gas abstraction the key point right here is to abstracting away the complexity of the gas fee for the transaction to be processed in any layer one and it has

been going up and going further onto the industry trend already that is you becomes a standard in the industry right now. So first we we were thinking about oh it's nice to have that I could use token other than the native gas token to pay for the gas but now they're more like looking into oh this must be a core UX and vault core UX um you know requirement right now for everybody excuse me so user now expect gas abstractions as a standard uh in our industry right now now within the EVM ecosystem or from the Ethereum there has been a lot going on when it comes to gas abstractions. So I think back in 2023 before the um the FCC 202 I think that

was the time that announced accountion by fitalik. So 4337 came in what happens that it enables smart contract you know to build account did that abstract away the complexity of gas management from the user. basically start seeing you know pay master you start seeing you'll be able to use other ERC20 tokens to settle transactions on Ethereum or any other EVM chain and then we are looking into oh uh 2771 we have the secure native matter transaction what does it does so you have a trusted uh forwarders right there for you in the smart contract standard the whole thing is contract level implementations that is relying on the relayers for the relayers to pay for the gas on behalf of

the users which is very similar to fee delegations so on and so forth you have the permit functions enable gases token approval gases token approval yes so with all these it simplifies how users interact with the decentralized application and for kay what would be our strategy and features about gas abstraction so we are thinking in the same way that we okay so first of all u kayak could be an obst to settle the gas fee but there should be more tokens in our ecosystem that could do the same thing as a gas fee payment. So uh as a coin to support the gas fee payment. So we are thinking about has been implement

our own unit GA you know architectures while others are still relying on a quite I would say relayers or centralized service provider like a third party pay master and we are here to looking into exploring and which is already implemented already trustless uh guestless transaction model on the protocol level which is b onto the proc level that is uh with the trustless mindset other than a contract level implementation. Now with that we are very happy um from a grumpy man becomes a happy man right now like um you know um the guy on the left is very confident that uh he got or she got more options right now to set to the transactions on

Kaya but from the UI perspective what does it what is it going to be looking like for the user so basically if you have zero kaya and you want to go ahead with the kay transactions what's going to happen is that they're going to be a popup right They're asking you do you want to use other coins right like that that is support the gas transaction that will be able to using as a gas token for this transaction that you're going to send out if you really put it on the wallet application as an example. So basically uh most of the tokens on the car ecosystem if they do support the guest support if they do support the guest's transactions that will be obviously a check right there from the SDK to see whether these tokens support

it. If that support automatically that will be one of the option if um the user does not have any kay obviously you only have an options like that uh which is the alternate coins other than kay and we also come across some kind of I wouldn't say misunderstanding but you know guesses um could be really confusing sometimes for uh you know um you know um web two native or web three native users right there they might be thinking about and then memes right here oh guest list nice so it's a free I don't have to pay for any gas. Um I just being upfront right here is uh you just pay the gas in another way uh but via the gases transactions that we have on the protocol level. Now we get to the the uh the main part of how Kaya enable

gas abstractions right now. So the key point is based on the one of our improvement proposal from our ecosystem the 247. So that is based on the gaslessness transactions. So the mechanism basically again that is uh you have the gases transactions while user can swap white listed fungeible token on kaya um into the kayak without processing any kaya to pay for the gas. So basically the transaction flow for the guest's transaction will be more like the block proposer which is you know in our language the validators the consensus you know they temporarily lands the required gas fee in kay to the user uh for the token swap when the

token swap happens the user use the borrow like the borrow kay to execute a swap transactions so GA token returns to be kay and set to the gas rather for the kay transactions And the user will repay the borrow kaya from the k received via the swap and with the remaining kaya they will just go on for whatever you know transaction they would like to go for for example in this case game related transaction. So that tokens will be paid for that uh on that now the 247 does come with some conditions. So when the users has no kaya balance uh but they hold some kind of GA supported tokens on the KA ecosystem then the wallet use a gases transactions and

allowing the gas fee to be settled with a GA support tokens and if the user has no kay the gases transaction must be enforced. If the user had some kay so they have some options to pick um you know which token that they will be using uh to settle um the transactions. Now for the 247 how does it work actually is first of all the proposer will be injecting um the land like the land transactions uh onto the trans I mean on the pipeline on the transaction pool first and then uh there will be approved transaction swap transaction or the game transactions based on the example that I just provide and then on top of it the land transaction will land

over the kay required for the uh transaction sender to pay for the gas on kayak for that transaction that they're going to send. But we need to always have a mindset of I wouldn't say mindset but there always something happened like what about one of the transaction does not go on and maybe one of them got revert and that was why our amazing TA team from Kay contribute to think about or maybe it's time for us to have a transaction bundle um standard which is which which come up with another 245 which is KP 245 that we think of. So what happen is imagine uh you know for the gases transaction perspective land

transaction approved transactions swap and game etc there becomes a bundle of the transactions that they have and if there's any transaction within this bundle you know fail or reverted the whole guest transaction would not be um going on. So what happen is the block must be uh you know produced and then there will be no more guest transaction included in that block. So that is a little bit example for the transaction bundle that you could see the land transactions being signed by the proposer which is the valid datas in this case and you also have the approved transactions swap transactions and the game transactions uh game transactions actually uh going out from the users signed by the users and this is how

they're going to swap the guest in the kayak token and that's how they're going to use the swap functions the swap transactions like that to get um kayak token to pay for the guest for their own transactions with the borrow amount from the um file datas. Now on protocol level it seems working but then fine but then how are we going to get that onto the dab level or even minabs level that's the key point right so yeah so whenever you have some protocol features like that you'll be relying on the SDK and all this kind of API and features that you will have and then dabs you will just interacting with the fe uh with the SDK uh API right there directly so um so gas abstractions

actually function provide in the Kai SDK to generate and send the guest transactions. So it just supports uh everything about 247 as conform and the conditional uh guest mode as I mentioned already when the user has no kayak the guest transaction must be enforced. If they do have some client they will have an options and there are few more which is uh not too major I would say but uh that is just some you know uh checking on whether a guest like a GA token whether they are GA support token so that they will be some candidates for uh the miniaps uh as well for the transactions uh to support the guest abstractions.

Now this is a uh strategic visions that we talk about right here. Um with this GA uh guest abstractions uh that is actually future proving for miniabs uh ecosystem on kaya. Uh we could integrate uh GA now ensure a long-term compatibility uh with the growing miniabs ecosystem that we are having and it will become the foundations and standard for the minabs as well. Um you know I would say from now on because we have just launched the features right there and we are looking to have it in the main very soon and the future gas token possibility that could be more choices uh in our ecosystem that more options I would say that will be supporting more

um GA support tokens uh that we could see in our ecosystem so that users will be having more flexibilities about um you know type of the backs that they have um to you know go for the Kai transactions in a second. So yeah, so it's not really a trade over but I would say um yeah, so we have the Kai gas abstractions open business. Uh we do have different I would say campaign right there. Actually it's not gas free but we're trying to make it to sponsor the gas payment for them. So as we could see more uh USDT right that um could be used uh during the gas uh abstractions that we have. So we see more transaction about gas appraction that will be using

USDT. So that would be also one of the major use cases for our native stable coins as well. And for users they have the gas pay transaction confirm everything ready as it is as if they just pay in the kaya token. And actually back in 202 um very similar to uh the wheel layer implementations that we have on the matter transactions actually back in 202 we already have the concept of feed allegations. um deployed already. So basically we have a transaction type or fee delegated transaction and we also have a a role key that is for the fee payer and to make it happen for a user u sorry the services is actually paying the gas fee on behalf of the users.

Now we get to the summary very quickly. Um, by the way, if you're really interested in looking into the whole um, you know, KIP that we have about gases transactions or transaction bundles that you like to see, you just click the link to have a look and and really when we look into that um, you know, uh, limiting the limiting to have the native gas token payment for the guests that we have is really u, you know, contribute uh, I would say attribute to these um, fragmented um, you know, web3 UX that we are having. And most importantly um you know uh by including the gaps abstractions we can uh abstracting the complexity of gas fee and transaction with the native gas payment on kaya and most importantly with our introductions

of the gas abstractions methodologies right here we are looking uh into the gas transactions to um enable it but it is very important that this is trustless network native features which you don't need to really require. for any half fork to achieve that later on if you were to on board to have more GA features and at the same time this allow users to cover the gas with more than just native gas token like USDT. So no kayak no problem whenever you like to send in any kayak transactions in the way. Now I will go very quickly about some ecosystem initiatives. Um so basically for kayak we are miniabs ecosystem um you know uh messengers

layer one we're having a lot of opportunities for our amazing developers right here to build a mini dabs and get the uh distribution channel which is very effective to the 250 million million monthly active user from the messengers and we have onboard so far already millions users via the miniabs merely so uh out of the thousand project pool. We have on board 83 project. We and we are looking for 300 uh projects by the end of of this year and a month ago we do launch we did launch our native stable coin implementations on kaya uh with tether. So we have the native USDT and what is going to happen is we embracing

stable coin summer. We need more use cases that will be taking uh the mini devs as a distribution channel. So what is going to happen uh this stable coin summer hackathon will be focusing on professional builders with I mean at least with a team of project and if you are amazing builders building some project already on other ecosystem and you're looking to build a mini devs right here on kaya uh to make use of the distribution channel open arm and feel free to join this hackathon and there will be a over millions uh price pool that we have already confirmed which will be announced in the upcoming few weeks.

Now with that um Kaya is Asia super app chain and mobile first gateway to web3 and most importantly with the stable coin we hope to be the gateway of stable coin in Asia as well and which is what we have been trying to push. If you're interested you want to see more and you want to get to connect more about kaya feel free to go uh hop on to one of the links right here to get more informations about it. With that that will be everything that I'm trying to cover today. Thank you very much and thank you very much for having KA at FCC. Thank you. [Music]