Executing the Trustless Manifesto: Colibri Inside Ethereum’s Wallet SDK Kohaku

Transcript

So hello even too many people but let's start anyway and discuss this very very important topic. First question for you. Do you believe that etherum is a trustless system? ist designed. Yes, I will say it is a trust systeming. Did you oder do know the trustless manifesto from Ethereum?

talk about was released last year and it talks about how the system should be so I don't want to talk about the whole manifest time it but let's at least look at some of the points so one part of the manifest says that we should have trusted systems so that we don't have to rely on intermed accation verify information system able to verify information by myself

fact check system we have now really a trust No, it's not most of our applications 90% 99% maybe even more trusting RBCs. Means we have a trustless system like Ethereum which by default by the core protocol is trustless but we are accessing the system over centralized gateways. Centralized gateways to decentalized system. Not the best thing what we should do. And the other thing is when we are using wallets for

instance, did you ever sign a transaction which you did not understand? I did maybe you you to so is also something which needs to be improv because we need to use to understand what we are signing otherwise blind signing and we know the results from last year. So how are wallets working today? So let's talk about wallet X Y Z. You can put any name from any wallet you are using into this today.

So they are taking information from NRPC. So balances locks events which collecting transactions building a transaction for def protocol information collected using OBC. So and that means we have all information in our wallet but we trust that the OBC deliver the right data. So that means if we are really thinking about this we have this decentized world but we are still

working completely on trusted data. It's not so that we say RBC bad. Of course it would be nice if device could run but we know not possible. So, but even if RBCs are bridge technology, we need to see how we can improve this so that we can have trust access to data even if using RPCs. Ja, the system is trustless the applications we are building on top of the system not.

So, but we don't need to stay on this point and when we read or listen to what Wal is always saying, he says we need to become trustless in all our applications. So, we don't need to wait for the next five or 10 years until all the CK EVMs and all me finished. reminder regarding some events happening in the last days.

chain attack only days ag very important library in javascript was attacked which was able to ja to mislead information so that we could not trust information we receive in our applications. Last year we had several of supply chain attacks and when we think okay using RPCs is quite okay because it works everyone is doing this we should have in mind that attacks are coming again and again and there is a risk when we take data which we cannot prove and that's

why trust manifesto says we need to be verifying any information in our device, in our client, in our application right when we are using this. So don't trust always verify. This is our topic and and we need to come to the point that this is the new normal. So now some words to the actually topic I want to talk about. So the Kohago wallet I don't know are you familiar with Kohago wallet then I give some short information. ist initiative von the von the Etum foundation. SDK and also wallet extension which is focused

on privacy in the main reason. So and there are a lot of integrations of privacy protocols but it also defines shows how the interaction from a wallet with the blockchain should be how we should interact with protocols how we should prepare our transactions before we are sending them. So that's why trustless information is a very essential part in the privacy wallet. cannot build privacy on trusted data.

We need to first have trustless data and then we need to build the privacy on top of it. So why does Koaru needed? First we have a lot of information we are reading from the blockchain reading balances reading information contracts are preparing transactions even using privacy protocol first need to collect a lot of information and information needs to be verified.

privacy build privacy state need listen to a lot of events so that you can recover state and then do the transaction and signing already mentioned when I prepare a transaction then I should be able to verify that transaction stateless statel cent wallet foundation all things done very efficiently so we will talk about stateless clients now so that you can

understand what col stateless as a stateless client is how it can be used and how it can help information get information never to trust information delivered in the correct way before any information used verify so that we have not the original workflow ask get information and execute information

constru possible verify verifi will send my transaction execute what doing so what is stateless client stateless client is a client which is not dependent of the pppe network that means this client is not synchronizing device fetches data verifying information so that we can have the full

verification we have the same security as we have in in a light client or even in note but CL very small stat into any application could application mobile application even IoT device small IoT chip smart watch could be enough for statlesseless clients fill this gap we have now we have the gap that we can run a client or even light which is also

still synchronizing or we are usingc status client is in between so how is done so we have two types of proofs we get data we get an execution proof for the execution layer and we get consensus proof for the consensus layer execution layer get information get account balance and get the proof that this balance belongs to the information in the state or we get transaction

received and we block information belong together what we don't know point information real blockchain could fake block need another proof which is the consensus proof consensus proof shows block is really part of the canonical chain and ist done for Ethereum by starting trust checkpoint and then have all the validator committee transitions proven so that we

come in this chain up to the current block so that we know the signatures we have are the right signatures of the current validator committee this could be a little bit expensive because if my trusted checkpoint checkpoint mon old chain of transitions why we are putting transitions in one proof so we have

connected proof oder recursive proof from the checkpoint to the current block in one single proof makes very efficiently. I mention it before in our client we have the chance oder we need to verified information approaches generofs first can do it locally that means the client itself fetches all information creates the proofs and then can verify that the information is correct this works it's nice because we are not dependent on any other infrastructure but it is quite slow service

trust trust together trust fetch abc fetch proof service together we can validate our data and the end is rpc verified rpc data so that we can verify this will be the future of RC services that deliver data and also proof so that we can get data but not need to trust RBCs anymore regarding the simulation of transactions

depending simulation maybe checks good maybe external services used to do simulation but the much better way is to simulate transaction directly in the device directly in our in in our application and it means get EVM evaluated presenter

understand what information easy way people know what signing also become standard for any wallet blind signing as did in the past must in future need interacting more complex protocols we need even more to understand what is our transaction all things available in the coago wallet so you can test it not something for the future it is now available can be used

is a test implementation verifi check it out use the stk check wall extension or use colibri directly so that you can have all features also in in your applications. What is next? So we have now integrated colibri to have a stateless access to trustless data in the application. The next step will be that we add also privacy methods on top of this protocol level. Of course, privacy is important thing.

a lot in conference about privacy protocols are not the only way only place need privacy so for instance if prepare real gun transaction private privacy protocol but to prepare you already talk a lot about what you are intending to do to yourc providerc knows before sending transactions what planning to Ction protocol of the information already shows what going to do need kind of read privacy

lot of very complex methods. We are presenting method which is called pragmatic approach for privacy. I will present it in some weeks in [schnauben] first in PR. in Berlin will talk more about privacy approach will integrated in protocol and also working on the transaction security layer so that not only simulate the transaction but also using local AI methods to explain it and to check it for critical paths for critical things so that the user gets an information

which is really helping find out information but why doing because trustless information need to be the normal must stop using trusted information in any of our applications not in wallet not in deps not in any other applications building on blockchain trust verify always possible life now you can use it and it does not change at all application very simple

approach to replace call and col is managing all other things thank you Thank you very much. That was a great talk, great presentation really nice. Yeah, I just probably one quick question. So the wallet itself is stateless, right? You don't store anything on the client whatever device it's using.

So the all the data is on chain right or where does it real store? So the actual questions how does it will be will it be scalable or not? Yes. So die the system itself doesn't change anything on what you are doing right now. Normally now you get the information RBC and RBC is providing information from the blockchain and the only thing what we are doing is adding a proof to this information.

means in device application add the client and the client fetches not only information but also the proof the only thing and from the bench did also a lot of benchmarks so it is very very small amount of time you add on top of normal l agency in the millisecond region user will not really feel it but the benefit of it.

Thank you. Okay. Thank you much. If you have any more questions, welcome. Try out CBR. applications. Komm. เ