A mobile-based light-client solution by hsyodyssey | Devcon SEA
Devcon·Tue, Oct 7, 2025, 12:00 AM
After PoS Merge, there was a bit of a lag in Light-client related work. In response, we developed a mobile-based Light-client to help more devices natively join the Ethernet network. Speaker(s): hsyodyssey Skill level: Intermediate Track: Core Protocol Keywords: Core Protocol, Light Clients, Tooling, DePIN, Mobile, client, mobile-based, light Follow us: https://twitter.com/efdevcon, https://twitter.com/ethereum, https://warpcast.com/devcon Learn more about devcon: https://www.devcon.org/ Learn more about ethereum: https://ethereum.org/ Visit the https://archive.devcon.org/ to gain access to the entire library of Devcon talks with the ease of filtering, playlists, personalized suggestions, decentralized access on Swarm, IPFS and more. Devcon is the Ethereum conference for developers, researchers, thinkers, and makers. Devcon SEA was held in Bangkok, Thailand on Nov 12 - Nov 15, 2024. Devcon is organized and presented by the Ethereum Foundation. To find out more, please visit https://ethereum.foundation/
Transcript
[Music] and so glad to be here and today I would like to share about our current work named Mobi a mobile based like client I'm s hun and partner of the ABC Labs so ABC is not just a ventur capital we are always make our hand dirty before we make the investment so that's part of the investment strategy so this work is powered by ABC and cisc CC is another company which are doing really good job on ZK Hardware acceleration they will help us to build more efficient stateless light client so so the entire blockchain Community is founded on One Core principle don't trust verify this principle served as a foundation payLo for the architecture of the blockchain networks so after the POS so the etherum officially po the light client works but fortunately several third party teams are initial their own implementations such as NBAs based on name and lar based on the tab scrap and Hiers based on the rust so however none of the L CL Solutions con natively run on the most ubiquitous devices the mobile phone right and so our goal is quite simple we we are working on to offer and our to e room Community a alternative a light client can run any mobile devices so the motivation so why this is is technically feasible so as 2024 the performance of edge devices uh has advanced significantly we are already seeing some developers running local RM on your mobiles and running light clients on the mobiles only require a periodically network communication and some storage so therefore running a eim light client on the mobile is entirely feasible so how to make it happen so our goal is is not build something new and uh we want to build SDK for the native running L kind for the mobile for the mobile platform especially for the Androids so the whole we don't want to build something uh already happened so the the whole architecture is about based on their very efficient Library called Hiers created by xxd and Hiers is based on R and what we are doing here is to make a cing WP and to make it as a library for the Android so our secondary goal is after achieving the compatible with the E midnight and is to make a h function like to offer light client services for E all e layer tools if they provided light CL protocol and so because their time is limited and we'll share some experience to make it happen so as we know the heers is code based rtin in the rest so they're containing a significant amount of their synchronized thre and but Android is on the hand on that hand is a build right build on the cing and which running on the gvm so the rust do not have their garbage collection mechanisms whereas the gvm has the GC so this happen a lot of times that results in the synchronized threat has been incorrectly garbage collected by the gvm so it's really painful and more moreover Android you have some unique permission protection mechanisms includes the where various permission Crosser arrows when when directly invoking involve some Hiers code base and uh eventually we have some long additions so apart from the basic functionality we have further expectation for the mobile light client including but not limited to the to the following two directions the first one is functionality the core function of the light client is verification right but however given the sto storage performance of the modern devices we aim to build something called light Cent PL so beyond the simple verification we intended to add some storage compability for example users could selectively store some State and histor data of their s and then you can they can uh carry them locally and additionally we want to build some rpcs functionality for use for other use l client knowes this it's kind of the portal Network and another part is the entertainment or make it more smart as we mentioned so in addition to the light client so mobile devices now have the ability to run local RM inference so for for example Android private local Gemini inference apis and we want to explore where we can combine the local node and local M together to conduct some uh something uh interesting and so here is a demo and I bring my phone here but due to their time liation if you got interesting I can show you after after this talk and another demo is called local RM and I bring the Lama 3 three billion to the to to to to the phones and I can show it after the talk so that's all and about myself I'm partner of the VC labs and fin year PhD at and my us about their database SS thank you thank you uh s uh do we have questions for our friend amazing speaker here okay he there thank you this is great that you're working on like clients in the the ecosystem yeah um how long does it take for the client to be connected to the network and then how quick can you for example do an eth call and validate that if you build a mobile application on top and and how secure is it at the end maybe you can talk to that so actually is there ISM protocol provided a a native function called G proof and you can use this G proof to verify the data from the other client so the heers basically the heers work that you can verify any data from untrusted rpcs in a local way because the protocol cannot be changed so that's really how to guarantee the security yeah no I um I understand that I've I'm in the same v as you but if you do an eth call right which you want to do you want to do method call you don't know if the VM that is on the remote side is executing correctly so do you have a local VM or like how do you solve that problem wait I think the L client do not have the local VM they just the use their just use their get proof to verify their correctness of their mot tree yeah but with the get proof you can only prove the storage not the result of a call yes yes oh that part is that want to you to to to introduce their AI agent part like we use RM to detect whether the core is malicious or not to help because the light actually the functionality of the light is very limited so far so we want to extend something new that's was this Mission yeah next question um okay so since you are working on mobile right there's another constraint which is power so like um have like how's the power consumption on phones running on us you mean the the like battery life like how oh did you optimize for it or so actually we are working on a benchmark like how many um CS Bas can call on current mobile devices yeah okay um a followup to the previous question about how e call Works um I so the way how it works is you have a local evm inside helos they used the red evm revm yeah and it uh uses e get proof to fetch the code yes you can get the code from the state tree yes puts it in and whenever the evm needs some storage that um it doesn't have available locally it is another E get proof like it's a lot of round trips there is a lot of latency um there are some uh efforts on the way to improve that to make it more compact but if because the Revan runs locally it means that you can trust the local execution and later on if you have seen yesterday's talk from Justin breake with like the redacted title um in the future once we have CK snarks that prove the execution and the server can also do that and we don't need the local um guys thank you so much uh we'll continue this conversation meet backstage and
Automatic transcript — names and jargon may be misspelled.