Ethereum Without Trusted RPCs: Stateless and Trustless Clients by Steffen Kux

Transcript

Guten Today I'm here to talk about trustless clients and why we should have Ethereum and other blockchains without trusted OBCs. mentioned in several presentations and publications that we really need trustless infrastructure in Etherum. This is also valid for all other blockchains. So what what is meaning when he talks about trust infrastructures? So who is building an application wants to have a centraled part in the applications?

I think everyone want to have decentralized applications and trustless access to blockchain. How is it in real life? architectures fulles synchronizing blockchain all the state information available maybe all information archive node even information only have the last states but they have a lot of information need a lot of b of storage secure and trustless use client to get informationely in

sy we have some changes also part of the network but only synchronize the block header information and if need more information they get it from other full notes so don't have that much information but have a lot of synchronization effort anyways but are trustless in the applications using fulles almost n remote RBC endp infrastructure elements I call it a bridge technology because make it very

simple and easy to get data from blockchain but in fact the centralized gateways to a decentralized in chart about 97% even more applications are using trusted information from centralized RBC endpints so what is a real stateless client first clients they do not have to sync any data not part of the PCP network but the ability Cation

information somewh else en them to prove information proofs to do first we call it the execution proof they have to prove that information they received belongs to a specific block and need a consensus proof which means to pro that block which is referenced is a real block of the blockchain and if the block is valid and the information belongs to the block the application which is using this information for sure knows this is correct information no trust to any party is needed so what needs to be proved a lot

of differents in execution layer. So this is reference on Ethereum in other blockchains it might be little bit different but works in the same way. So we can have information about the state about count balances and so on. proofs for logs proof for the transactions and also we can have proofs for execution of smart contracts and all information we get from the execution client EP 1186 we have all these proof already included in almost all clients and can

use to approve that this members blockensof so proof of work etherum it was not possible to have such consensus proof because we have any signatures available to prove that block was correct created it was possible to do it in cryptoeconomic but now we have validators [Musik] step valit committee

change correct of course a longer chain of proofs but we can connect proofs proof stat type of client in small footprint remote but verification information trustless Colibre

the almost international world for Hummingbird stateless client which implements exactly what I described now so we have the ability to verify all the information coming from the blockchain proof system which connects all consensus proofs to one simple proof No state synchronization storage der small store execute even very small IoT device I can execute in every mobile web application without any additional

resource requirement very small point which makes stateless clients very important applications. So application uses data multiple chains layer tools layer ones if you want to have information you need a client for each and every of chains and stateless client you can have in one client because you don't need to synchronize with change.

developers bindings almost all existing and used languages of course available for ed also available for web applications and for mobile development so what use cases there where we need stateless IoT devices IoT devices small don't talk computer raspberry talk of really small devices like microcontrollers how installed in many of smart home and other smart devices so devices normally have to

trust der cloud solution that the information they receive devices validate information management can be done on chain and cli verify that information is correct I mention already three applications in which are in web applications here normally remote clients are used other clients are not possible but stat I can embed mobile

applications mobile normally more resources small device but here we have the problem that synchronizing data is need a lot of band which is not affordable for an application because to be in sync information use verify so let me give a short summary right

now zero we have implemented cotocolling is use in the next months will ja present official version used productive so in the next phases we will allow to use it in IoT devices present SDK so that it can be easily used the real vision verification

blockchain special standard in future implementations every decide not just trust provider but use information that can verify all the information by So if you want to ja look inside the protocol and how it can be used or can be adapted link to the white paper also git repository. If you have any questions find me and wir discuss it in more detail. Thank you very much.

[Applaus]