# Gasly - Shared Gas Tanks for Digital Payments - Channel: [ETHCluj Meetup](https://streameth.org/ethcluj-meetup) - Date: 2025-10-07 - Duration: 1:05:31 - Watch: https://streameth.org/watch/yt-hhRxJzb9umQ - YouTube: https://www.youtube.com/watch?v=hhRxJzb9umQ ## Description In this session Flaviu Dan and George Popescu present their project Gasly - a next-generation platform that simplifies digital payments by centralizing gas fee management. Instead of requiring every wallet to hold native gas tokens, Gasly introduces Gas Tanks shared accounts that cover transaction fees for families, businesses, and developers. With Gasly, teams can fund a single tank and seamlessly use stablecoins across multiple wallets and applications, without worrying about maintaining gas balances everywhere. This makes digital payments easier, safer, and more scalable. https://www.meetup.com/ethcluj/events/311001058 ## Transcript Welcome to our first think tank session in a long while. We had many technical presentation meetups this year but this is the first uh think tank session. Uh and we are expecting to have more online and inerson think tanks until the end of the year. The idea behind Ethereum think tanks is that we have projects or ideas uh being presented by the founders and then the attendees can ask questions, give suggestions and constructive feedback so that the founders can potentially use the feedback to take the idea of the project to the next step. And um the feedback can come from technical point of view or business point of view or user experience, philosophical, anything that attendees want to point out or suggest. And today we have two speakers, Flavio and Georgia. Welcome guys. Um both working on their project called Gest. And uh Gastly proposes a solution to manage gas fees for groups of uh individual wallets like for families, companies, and other types of uh groups or organizations. So um let's get started. Who wants to go first? >> Uh hey, I'm going to go first. Pleased to meet you. I'm George. Uh I'm going to share my screen just to >> show you a bit about Gazzley and uh >> Sure. I forgot to pre-share the session, but anyway, I think everyone got the idea. We'll also leave the meetup link in the YouTube video in the description so you can access the event from there. Perfect. Uh, good. So before starting talking about Gastly, how many times did you had the problem that uh you you wanted to send some tokens from a from a wallet and you didn't had gas into that wallet and you had to ask for a friend to send you some gas. Uh this is what we a problem that we have usually into into our group and based on these issues we had in mind to to build Gastly. Gastly which solves this this problem because uh you won't have to to ask for gas anymore because Gastly is managing uh managing this. So basically Gastly is a shared wallet for your entire team or your entire family depends on on the needs that you've got. But you don't have to to to send gas to multiple wallets. you have a single wallet where you are keeping the gas and others can that you're inviting to to to join that that wallet um you can use the gas from it. So yeah, if you're a team you you're going to stop wasting time asking for I don't know those that are superiors to send you some gas if you're a developer. uh and this is solving also on the on the company's side of some some issues. Uh but let's go a bit into the Gastly. So, uh this is a landing page that we've got for Gastly and those are are the networks that we are supporting. Basically, we are supporting networks that are uh that have volume today and are used by by many people. And currently Gatly is is focused on on stable coins. So you're going to be able to send stable coins using Gazzley. Uh the connection on the platform that we've built is it's a web tree connection. You're connecting with your wallet. I'm not going to use Metam Mask. I'm going to use the Coinbase wallet. So, and you you got this simple interface. We didn't want it to to make it complicated or um or hard to be understand to be understanded by others. So, that's why we tried to build it as simple as possible. So, the first thing that we are going to do is to create a new tank, a new gas tank. I already have one, but I'm going to create a new one just just uh to show you how simple is to create a gas tank. Gas tank is that shared wallet that I I've told you about. U I'm going to name it George George George George George George um one good and yeah now I I can uh invite members into into the tank. So what G what Gazzly does is you are filling this tank with with some some to with some gas and you won't have to need to to to have gas on your wallet if you are a member in this gas tank. So for example I can I can invite uh I can invite someone into my into my tank. Just give me a sec. Uh add member. And I'm adding a member also. I can I can modify the name uh of the member. I I can see this one already has a name because I suppose he already did the it's a member of Gazzley platform. And if you're you're already a member, your label is is going to get to the tankers as well. And also I can I can manage I can make him admin and he can manage the tank as well. He can add other members uh to the tank. So right now what um what members can do can send stable coins without having gas. uh all that I'm showing you right now here it's an uh it's just a client we have an API that has documentation and a third parties can implement Gastly that they using using our API that also has have a documentation uh and you basically can integrate Gastly into your own platform in order to use and to replace this interface. This interface is just to show you it works. But Gastly can be integrated in decentralized applications for payments, can be integrated in in different other third party applications. And the difference between having a smart contract that manage gas and the way Gazzi works because Gazzly, yeah, it's a managed account. Uh uh so it's it's a noral behind Gazzly. is not a smart contract here. And the difference is you're not going to have to deploy contracts on each individual uh individual blockchain because you have a simple wallet address that it's relaying your transactions that relaying the transactions that you are doing. So you don't have to we are not deploying smart contracts for each uh uh blockchain. You're going to you're just having uh a single address that that it's working with those blockchains. So I'm going to I'm going to send Flav view one [Music] to to Avalanche. The single thing that I have to do is to sign the transaction. And this is not what I usually happens on demos and I don't know. Uh, okay. That's weird. I did the test before, but I'm not sure. Ah, it makes a lot of sense cuz I don't have I did I didn't added any gas on on the on the on on any on any networks. I'm going to go back to to to my my previous uh gas tank that has some balances. Apologies for this. And I'm going to I'm going to send. So yeah, I in order to put some gas in this, you just have to you just have to um to go to the balances and hit top up and you're scanning the car and send send the gas. But on this this particular tank, I I already have some uh some gas and I I can do what failed on the previous one. Uh so I'm going to do this exactly the same thing and this time it's going to work because I have I already have uh have some gas and also I have some I have balance on the the wallet um and that is the transaction have been uh have been executed and transactions I already can see the transaction confirmed also I can see the name of the member and after that the address also I have I have a very easy way to copy the address to clipboard but yeah the transactions have been executed by the gas tank but if you're looking to the net transfers it's from me from my wallet the wallet I that I've got connected to Flavia's wallet so if you don't have gas into your wallets and I suppose all of us have multiple wallets and Some of them you you you don't have casks and that's a simple a simple solution that you can you can have because you're just connecting to for example if you're using uh MetaMask you have that built-in browser that you can put Gazzly car.clars.app app into MetaMask. You're connecting to to Gestly. You're creating a tank, adding your wallets into Gastly into that tank and you can easily fill that wallet with some gas and all the wallets that you have are going to use gas from there. And you can send everything to a single wallet or do your thing with the tokens that you've got without having the necessity to send gas. that's to to each individual wallet. And if we are talking about sending on Ethereum and sending on all the wallets that you've got, you're also saving some some funds, not only time when you're using uh using gas. Good. So, you're able to manage to manage members. You're able to manage permissions of the members and also you have a his a complete history of the transactions that that uh that you did. with link to explorers uh with some filters that allows you to to to filter for multiple multiple users. Uh from this particular wallet only I did transfers. So yeah, you also have the balances where you can see balances per each individual chain history. And this is the refill history. This is going to get uh uh populated when you're you're refilling the gas tanks. and a simple simple summary which doesn't tell you any more things but important thing if you're a developer you also have this um API docs that allows you to to build your own gazzly that is going to use the API and you're not uh you don't have to use the interface that we built just as a proof of concept you can you can build your app or the app based on uh and use asly as a as a service. Um yeah, mainly a single thing that I have to mention about uh the number you you can you can right now that we are limiting to three gas per per user gas tanks and also 64 members per per tank. Yeah. uh for more things and the real use cases. I'm going to let Flavio to to continue. Thank you, George. Uh hello everyone. I'm Flavio and together with George and Eddie, we are focusing on enable enabling digital payments using stable coins. And basically we build gas first first for for us to implement in our applications. And since we build it, we can um uh have it as a service to anyone who wants to use it. Um, I will uh share my screen and show you that uh since um Georgia add it added my wallet to his u do you see my screen? >> Yes, >> it's it's on uh Okay. Yes. >> Yes. So, I have an wallet that I use for my personal uh stuff. Let's see. This is the address that um um Georgia already added in into town one. And right now we I am accessing the same interface with my uh personal wallet. Time waiting. So I already did two groups family uh Flavio families and Flavio personal because I have multiple wallets for myself but I also got um the membership of uh Tank one tank one that George already made and you can see beside Tank one there's a little um drawing that uh suggest that I'm solely a member and on on my groups I'm the owner. Let's see failed. What has failed? Let's see if I got the uh one or whatever. Um >> uh I send on on a different wallet. Uh I'm going to >> I don't I don't have that wallet on this laptop right now, but it's okay. Then I I can uh just um skip and I got the tank uh limit uh reach for this presentation. I um I set up demo account, demo um version that implies a restaurant that has multiple wallets and multiple uh users and don't uh the restaurant doesn't need only uh the only thing that the restaurant needs is a gas uh guestly account. Let me show you for this presentation. So this is my demo restaurant which has multiple wallets. the main wallet with an address terminals with the POSOS's uh for uh receiving payments by the waiters or the bar or the reception. Uh one wallet for making payments when a supplier comes to the restaurant and uh and uh brings some merchandise. Another wallet uh that uh it's used by the people uh the person responsible with the purchases. Another wallet that can be linked to let's call it legacy card debit card. There are a couple of uh companies that provide uh debit cards for companies like cipher wallet or wirex business and the payroll wallet nowadays. And maybe in the future um employees could can be paid in stable coins more precisely. So basically for a business a small business or a regular business or corporation or whatever they can start their their own payment system let's call it using stablecoin and now machine. So in my case, let's connect to Gastly. So for the for a small business uh Gazley is the right choice uh for not uh providing um gas on every particular um particular wallet or uh and the owner of the business or whatever only makes only needs to make the the group and add all the wallets to that group. Signature rejected. Great. So, my group is called restaurant. I have only one group. I don't need more. Uh I already added the members. Here are the all the members. And I already filled up the avalanche. um uh gas tank to make a transaction. Prior to this demo, I already did. And now I can show you how can I bring myself to main. I will stop sharing for a for a minute so you can see my camera. So other apps that we are building right now and uh these are also beta stage and they uh we are waiting for approval from Apple store and Google store are called uh posses and um pay I don't think you can see right now but on Android you can already install Euro CPOS and I will demonstrate you for businesses how easy it is to provide the option to receive payments in stable coins. So, uh right now is the first time I u open the app is not set up for the POS. I only need the address. So in this case I will go with Andre Barmanet and I will just scan the wallet you see. So right now I don't have any addresses added. I just add address scan my wallet address because for receiving payments is not really um required seed phrase or um so I added my my so right now in this end I'm holding the POS terminal of of the bar of the Andre employee And let's say in this end I am a client who just ordered the cocktail at the bar and Andre needs to provide me with a payment request. Let's say on avalanche the background uh goes to red and one cocktail this time needs 2 34 like this. And the client scans with in this case Euro CPOS. And we have all the information uh filled up the network, the token, and the amount. And I just click confirm. And right now I'm coming back to my screen. So you can see it's still processing because we are on a beta beta RPC server. Here is the screen share payment successful. I'm seeing the other side share. Fine. And let's go back to the restaurant and see. Wait, look. Uh so the terminal of uh one of the terminals and this is one one big advantage of the uh blockchain solutions or the blockchain network is that you can create as many terminals uh you need. You don't have to pay for each one. And another thing that I like when when a customer pays an amount regularly with the current payment systems when you pay a 100 the merchant or the business or the restaurant in in the best case scenario receives 99 with the tokens with stable coins in and blockchain when you pay 100 the merchant or the business receives the full amount 100. So in this case the client paid 2.34 and the business received two uh 234. Now the employee does not does not need to have the seat phrase. It doesn't need to be a wallet by itself. it only needs to be uh sub account. In this case on the terminal I have multiple sub accounts. So at the end of the day I can see every terminal uh whatever amount it received and during the night and I can say we will implement a solution to centralize all the uh payments received into the main account so that the main account the next day can move funds to the payment uh wallets. Going back to Gastly. Uh the members now I'm the owner, the main account. I will log out for the moment. I will and I will log in with the wallet of the terminal POS that received the amount and I will move the whole amount to the main account. And this can be done by um um by the accountant, the financial manager or the person responsible with the payments. The employee doesn't need doesn't have to do anything. Good. So bas basically in my um my wallet which is um for the bar I don't have any gas but with um with the gly I can move fs that I received here are the maximum founds and I can send to the main account which I have right here. Copy. I guess it's the same. Yes, sign and send for the moment. But we can um automize also this sending signing and you will see here that the so success and in the balance sheet we now have um less avalanche but on my wallet on the terminal wallet. I didn't have gas at all at all. It's just so I can see that on the main account I received and I can see my history. This this is the test that I did earlier and this is the test that I did now. So basically we want to have a full range of apps that will um allow any business, any group, any organization to enable digital payments without the need of a bank or an intermed intermediary. And I guess we are on a good track. That's it from me, Alex. Cool. Awesome, guys. >> Yes. >> Nice. Nice. So, so lots of working here and uh interesting that I see um uh your um so so there are emerging use cases, things that things that you from the product perspective uh make sense. Now uh what are your plans further from here? Meaning what concrete steps do you want to to go and then I'll I'll just let everyone else who has other questions. So what's what what's your go to market now? What what do you do since like after this meetup or since tomorrow? So first of all, the first thing that we're going to do with Gastly is to integrate in our services in our other products as as uh Flavio showed you. Uh the we are we are working on um on the P on the pay app and that paid pay app will have a first integration of Gazzley just to allow those that are want to to use Gazzly as a service into into their pay pay apps just for also for for the use case that Flavio just showed you. Um so we are currently in the building phase. Um we are going to launch also these these products but I'm not sure if Flagby wants to to market them since they are um for example Gazi it's just a bit of what we are building just a small part of what we we are building right now. So we don't have yet any plans for go to market since we are in the building. >> Okay. >> So it's more like exploring for now or something like that. >> Okay. Cool. Fair enough. Uh right now we are waiting for approval from Google uh store and app store for the other stable coins that we we build separate apps apps uh like uh USDTPOS, USDT pay and USDCPOS and USDC pay. So >> so so you have created uh sorry for interrupting uh you have created separate applications for each stable coin. >> Yes. >> Why why did you do that? is that limitation from the perspective of the app store that because I know that there are some weird conditions that Apple requires. So um our goal is to make simple apps for everyday use >> and this approach got pass into a little bit of reviews from Apple because uh these apps are considered clones and we didn't got approved and got a little bit delayed and I guess we will solve solve that problem but uh we will have in the end for uh pay uh side an unified app it will be called defi pay and it will recognize a lot of QRS maybe we will implement NFC and so on and depending on the QR code that the merchant provides or prefers the app will um change to that network and that token another ser Another service that we also are building for us after this presentation and we will uh continue with that it's called swap. uh it will uh provide the instant swap services for uh micro payments and if the if the user has funds in one network and the merchant request into another network uh during the payment process uh we will swap the the token to the desired network without further interaction from um from the user. So basically uh my idea was to to uh localize apps let's say Euro C. Uh I guess it will mainly be used in Europe instead USDC and USDT it will be used um international. >> Okay cool. Um other questions in the room. Okay. Similar. >> Yeah. Um just a thought. So from what I've understood there are role based permissions on on Gestly. Uh so I guess it's withdrawals are also kept right. So I guess my question would be around what prevents abuse? This is addressing also I understood this is addressing mostly like small businesses right or generally businesses at this point. Uh yeah just one question at a time first of all like what prevents abuse and then we can move forward through it. Uh I will answer abuse. So uh in the first stage we thought uh we let unlimited uh members and unlimited u uh tanks but after thinking we decided to limit the number of the the number of the tanks and the number of the members. Basically in real life you will only need one tank for for u that's my my my opinion >> I I can I can complete a little bit of you and sorry so the idea is not just created for businesses but also for personal use the idea is how many of you have $1.5 something in maybe 10 20 30 wallets because you need one time to use that wallet for a test or one time you receive some uh some things there or you need to do a payment that you did not want to do it from your main account. So you send it via an uh checks to to that and so on. So first of all you are creating we are creating here a solution for personal use. You just have the the gasly and you have a number of wallet that you will assign. So in this way the abuse is you are abusing yourself in this situation if you are doing like this. The second things for for small businesses and mediumsize because we are uh capping this at 64 members. So 64 members is also uh to say a midsize uh business especially in Romania. Um it's like you as an admin you are you have the ability to control the the gas tank. So you will see exactly and you will need to make some calculation for the number of transaction that you are estimated to have during that month because also in the next version of Gastly we'll have an um um and also using other other systems from the entire ecosystem. uh the possibility to put like some stable coins $100, $200 and after that to change this and to refuel the the gas tank. So uh from the abuse things I I don't think we have this this problem because this system is created as solving solving a problem for from the users and especially when we are talking about businesses usually you are doing for your employees or this kind of this kind of situation it's like using uh master um bank account and with sub accounts that you are doing now in the in the thread file of all the things. >> Okay, >> makes sense. Yeah, George, you wanted to say something? >> Yes, of course. Cuz um to be honest, I like I like your idea and what you just said. uh but yeah since there are a lot of use cases uh I suppose that can be a setting per tank to have a a minimum amount of transactions that the user or gas that user can use that resets on a specific time so yeah that's that's uh that's a thing that we we can do >> makes sense >> can I want to complete Yeah. >> So um uh couple of things uh we are debating now whether uh to make this uh uh code public. So any company which maybe doesn't trust us can uh implement Gastly on their own. This is one point. Uh the other point so uh large corporations can always uh uh create more more wallets and split Gastly into more wallets and each w make a wallet for a department let's say. So there is no limitation here. Uh you cannot abuse uh u the service be because you need to be a member of some group to abuse something. The only abuse right now is the the the gas price on Ethereum which is way high. >> That would have been my next question. Yeah. >> Uh so uh we are also planning so uh this type of tank that we we use for demo is self-managed. So uh a smart guy in in the company uh will do the job and fill up the tank. But we also plan an auto manage um uh type of uh tank or group which in which the customer will provide USDT and we will deduct from that uh USDT depending on the networks used to fill up the the the empty tanks. Uh basically it's a decision beside a group of or a decision that belong belongs to the owner who who decides whether allows a users a user to to use the the common tank or the share tank or not. Or since anyone can make three groups, maybe for Ethereum we'll make a different group and that's it. or uh ban ethereum >> or or you could uh or you could uh if you want to open source it you could I don't know create some kind of plug-in system where if someone can implement an automation or let's say decision making uh automated decision maker that can say okay maybe in some cases you don't want to uh the gas fees are too high and you want to restrict at that moment and you basically can automate made the >> so plugin and um implement >> in our uh in our apps. We plan to uh we plan to u prioritize the gas uh depending on the desire of the user. So the user can use his own gas and only if the doesn't have the gas in the wallet then uses the gas on the on the share tank. So maybe for Ethereum they will use their I don't know there are many possibilities and uh we debate it a lot whether to use the funds to automatically uh fill up the tanks or upon request. So right now we only have self-manage. The owner decides basically anyone can fill the tank right now. It's a public address. Anyone who sends funds uh can fill up the tank. Uh >> so if if a gas tank uh runs out, the transaction fails. >> Yep. >> Okay. >> Yeah. Like like in the first demo. >> All right. >> The scope. >> Did you implement any notification for users or is it in scope? Okay. Just no question. And also uh I I remember you were saying that there's about 64 users per tank sorry like members per tank right uh do you envision that this might you know impediment like be be a little bit of a problematic thing in terms of scalability or is it just you know you build on the first one and then you know move forward uh to add more if if needed. So let's say for premium users or premium clients they can edit this u this uh this uh setting just a number for to prevent so I don't think you need to be member in two different groups with a single wallet maybe with one wallet in one group and the other wallet in in another group uh We're very uh how do I say it? Um customizable. It's the in fact it's the user's choice what to do with multiple tanks, multiple wallets, multiple groups. >> I see if you're building this programmatically as not as we have the interface right now. you basically can manage on your side uh the wallet management and you can create multiple wallets that are creating multiple gas tanks. So uh there's not a problem on that one and also we are using a queue. So since if for example you're doing multiple transactions we that are using the same gas tanks that's why we we it's a good idea to reduce the number of the users that are that are in a tank because if you're doing multiple transactions from using the same gas tank that is going to enter in a queue and some of the transactions are going to be executed with a longer time wait time. So it's a good approach from my point of view the fact that we reduced the number and also it's not a problem on the scalability because if you're using the APIs that we have got you can create multiple tanks that are man managing uh different gas tanks and you're associating a gas tank and a ma uh an address that it's a owner of the tank on your site as a integrator of the service. So we plan to add more stable coins and maybe on the premium part on uh on the p the side the customer can add custom tokens. So right now to to to protect ourself and the user from abuse or from fishing or scams. We will allow only well-known uh tokens which are official contracts like USDC, USDT, Euro C and the time as the time goes by we will add more and more stable coins from our point of view but the customer can can add uh own tokens. >> Yeah, it makes sense. I guess then it's just going to be a question of your auditing process for stable coins that uh are accepted on on Guessie. Thank you so much. I I won't take too much of the time. I see that we have questions in the chat as well. Maybe other people here want to ask questions. Go ahead guys. >> So, uh there's a question on the chat. Uh people often lose their wallets uh being by being hacked. Do you have any limitation how much someone can consume from that time? Not uh not at the moment. But uh we definitely want to u let's call it force uh each tank to have multiple admins. So when when a group of wall a tank a share tank um uh over each a limit let's say three members I guess uh it will need to be two two admins. So in the case the owner loses the wallet or some something happens the second admin takes over removes that removes the remove that admin and uh things can go on. the second one. >> Sorry, just do is it going to be also like shared admin like multi-IG type of uh No. Okay. >> No, not yet. Uh we we stay away from from contracts. Uh contracts can be tricky. uh simple users don't read anything what they uh click on. That's why u we we stay away from contracts and I happy with the solution George George has found uh without contracts. I'm a fan of transfer and the peer-to-peer networks and so on. So uh I don't see the need for a contract in in this case. And this is answering the following question. How is possible? Uh what single deploy on a single chain to have to work on many others? So yeah, we are not using contracts. We are using EVM ad wallet address EVM address. So uh the wallet address of the tank the the tank is actually external loan address. EO aa so it's a norm a regular wallet address the regular wallet that is working with >> I have a question here uh Georgia because so it seems that there are multiple even I had the same kind of got a bit confused because we were used that to the fact that um we have been using um metat transactions before and this is not met transactions basically right >> and it has also a fallback for on method transactions >> but it works uh differently because you cannot theoretically uh via that old method get a signature from an address and push it yourself >> correct because you're going to need >> the name in the name of on behalf of that signer >> and my question is what EIP exactly do you use. Can you mention that because maybe that's some upgrade that we missed and we do not know about. >> It's EIP 309 and EIP 2612 >> three uh 30 009 >> mentioned on the send page. Yeah, if if you are going to open the send page, you're going to see the EIP it's transfer with authorization one of them. >> Okay. >> And uh the permit it as a fallback. >> Okay. Okay. >> And yeah, and the USD USD doesn't support transfer with authorization. That's why we we have the fallback. Uh, regarding the regular meta transaction, which which is the simplest way to do it, there's a single problem there because you're going to have to approve to to to sign that approval on on the on the wallet. And that approval requires gas. >> Mhm. >> So, you won't be able to you won't be able to send the transaction. >> Chicken and the egg problem. >> Okay. You got it. Got it. So, so you have to do an approve. Uh, okay. Okay. >> So, in order to to execute a meta transaction, you have to do that allowance to the token contract. If you're not doing you're allowing the spender to spend to spend tokens from from you. So, that requires gas to be >> Yes. >> Okay. Cool. Um so let's move to the fourth question from Catalin. Then what is the business model? So basically he's asking the same thing. Uh meaning >> or not necessarily. >> Let's say let's let's assume that he's asking how you guys will make money or fund this. Did did you think about it? Do you have any ideas? some swaps. >> Yeah. So, we want money for from this particular service. >> Uh since we are going to make it is probably to make it uh make it also public. >> Uh it's just a service that we is not is not actually a service. It's a solution. >> Mhm. >> So, we are not going to sell it. We're going to use it together. So that's that's the point of the product. >> Okay, cool. Great. >> But we are going to use it on different other products that uh are going to also have uh payment are going to be like >> are going to have a business model. >> Yes. Our target are digital payments using stable coins. And to reach that target, we need tools or services to enable our apps to work flawlessly or to make them them simple for the everyday user. My goal is to be able to pay with euro at an One of the problems that I as onchain as a blockchain user is that besides the fact that you have multiple wallets, you also have use multiple networks, right? So in your case in case of guess Gestly maybe I missed this. Do I need to fund individual networks or can I just uh or actually I think you did not get to that point but are you thinking about funding one tank on one network and at the same time um maybe allowing groups of wers to spend gas from other networks. So for the self-managed tank share tank uh every network needs individual refilling but for the auto manage that uh type tank which is not ready yet we will use an uh found provided by the owner of the tank and we will fill the tank as needed automatic. Let's say we are still debating on the Ethereum U budget. >> Yeah. But in that P posos example or in that use case where you receive payments from um different um >> yes and then all you have all the money in one wallet actually no you don't spend gas by receiving funds so that's that wouldn't be a problem. >> Okay. Anyway, >> it's difficult because you you the way you presented the project and you developed the project so far, it takes you to think about multiple 100 solutions in different places. And uh the thing is that it would probably be more clear when you have some some concrete customer that has a concrete need and you address just that need and that would be would make it more clear exactly where it goes because at the uh at the moment it can be a general solution right so you present different use cases on top of it. So uh right now our our solution are self custody solution. >> Yep. Uh but but fun fact, the POSOS only requests an Ethereum address or or EVM or ERC format address that can be also from an exchange where where the company or the user has account and uh the merchant or the business when uh when using C5 provider for the wallet Right? Uh then it doesn't matter the network that uh it provides. He can receive it on each network. In the end uh the found will be on on >> one form instead uh with uh with the D5 approach. uh founds are separate by se separated by the network and I have some ideas in this uh area also at let's say at the midnight or some or some uh grown job uh we can unify the the funds into a single network. So this is a this is this is a small disadvantage but for Euro for for example for Europe which is barely known in the crypto space Euro C will be enough and Euro is from base uh which also provides a network with affordable fees the base network and I guess and Avalanche also is affordable And I guess in Europe payments will be made on base uh being the same let's say provider or creator or supplier. >> Uh we have a question from Stefan. Stefan go ahead. Unmute. >> Yes. >> Yeah. >> Unmute yourself. >> It was that click. Uh, can you hear me now? Yes. >> Yes. >> Okay. Great. Uh, so it's nice to have you all here. I'm don't have quite a question. I have more an idea regard uh that I think uh I'm not sure if the the EVM uh chain supports it but let's say that I'm a a restaurant manager and I would like for my customers to to to not to pay the gas fees. Let's say I'm on Ethereum. I will support them which they are a little bit high. But what I am thinking if you guys can do if let's say like uh five different customers send a payment to merge it into L1 transaction. So uh that can um I don't know lower the gas fees. I'm not sure if the EVM chain supports that but I think that would be an idea in order to reduce the gas cost. Not sure if I've explained it correctly. >> Yeah, understand what you mean. Um so as a manager it doesn't uh I don't want the money to to arrive instantly. Okay, I can wait for five transaction and get the money one day later. It's no problem for me but to avoid the the high gas fees. It's just an idea if it get it can be packed it can perhaps uh lower the gas costs. So that was my idea not quite the question. >> Uh this problem arises only on the Ethereum network the the other networks had have really quite low fees. So uh comparing to the regular payment systems, right? When you pay €100 and the restaurant gets only 99, it's 1%. It's a lot. with this uh with this technology the blockchain itself only the Ethereum today and two weeks ago were were a problem and we cannot fix we cannot fix for the sender >> yes but to take it further uh I I could intervene and probably complete the Stefan's question so maybe you can use some l tool like optimism or um arbitrum or base but in your use case in your restaurant use case. So a customer comes, he wants to pay, he or she wants to pay and basically you include that their address in your group address. Basically you subsidize the gas fees, right? And you uh subsidize the gas fees from an cheaper network like from arbitrum, right? or base and you all the payments that the customers do uh are processed on base and then the batch payment in the end basically just means uh making a few transactions to Ethereum when you get to higher amount accumulated amount that would be an example but anyway L2 and EVM L2 is just as because people still keep like hundreds of thousands of dollars if not millions in one address on base and they don't worry too much about it. So maybe this is an operation that you would do a lot um more um let's say not that frequently to move it to other networks. So you don't have to necessarily support all the networks from Ethereum ecosystem. Right now, please >> I think for for the use case of the restaurant, we should optimize everything for the networks that have lower fee because also the user knows because already he is paying everywhere and I'm not paying with my Ethereum wallet when I go to the restroom because uh also now when you are going to the restaurant and you pay with your credit card you know how much money you have you know how much fee you'll you will pay on on that credit card so I think it's also from the customer part of the things uh that they will use the network with the lowest gas fees because uh now if I see that the gas fee is $200 on on Ethereum maybe I do a swap maybe somewhere in a checks and after that or change something and and do a other transaction that is is with a lower lower feed. So we we should also educate a little bit the the customers in in this direction because the entire ecosystem that flavio view uh brings up is to make the life of the user very simple and to use stable coins as uh the new method of payment because has like uh is very fast is very cheap and so on. So the entire ecosystem is built on the UXUI very friendly uh framework. So the the normal users to to have the possibility to pay fast and with the lowest fees as as possible. This is the idea and also dividing these parts in a C USD and so on. Also we are dividing the regions because like in uh Europe USDT is not very popular now especially with the Mica um uh regulation but USDT is very popular in the Asia part USDC is more popular in America, Europe and and so on. So we are we are trying to to divide the things and to uh educate the users to use the USDC payments USDT and also other types of stable stable coin. Cool. Okay guys, so um any other questions or discussions, suggestions? Do you want to wrap up? I think we can wrap up, but uh from my personal perspective, I'd love to see where this goes. And uh yeah, I understand that now you're having the app submitted uh to the app store for review. curious to see how that works for you guys. I know they're most of the time quite exigent on this side of things. So, uh yeah, best of luck. Come back to us with the good news. >> We will when we'll have the the apps uh on the on the stores, we will come back and present them. >> Cool. Okay then. Thank you. And um >> with Gastly integrated. >> Yes. And with Gastly integrated and all the problems solved. >> Yes. >> Cool. Cool. Nice. >> Okay guys, again thank you very much for coming and presenting. And uh yes. So whenever you want to showcase any more features that you are going to develop just uh drop us a message and uh we'll do another session and um yeah. Okay. Okay. And for the for the rest, we'll have our next think tank in two weeks from now. And um we'll announce it on our channels, Telegram, LinkedIn, and uh and Dex. So, see you in two weeks. Bye-bye. Bye. >> Bye. Bye. Bye. Thank you.