Hello. Hello. Um, so this is Akam El Milligi. I'm Miten. We're both developer advocates at Ledger.
Um, typically we're the link between Ledger and the developer community trying to integrate Ledger and we also spend time teaching the ecosystem about current initiatives and why security matters in uh in general. Um, a little bit about Ledger really fast. Uh, Ledger was created in France. It's a French company created in 2014. Uh we have sold over 7 million devices so far.
Um and today we secure over 20% of the world's assets. Uh our devices are secure by design and this is done through the combination of a secure element which is the chip inside the device and a secure display which is immediately on top of this chip. Uh what this means is what you see on your device, what you see on your ledger screen is exactly what's going to happen. Uh our mission is to secure web 3. Uh you may be familiar with our devices already.
Uh who here in this room has a ledger device? Okay, very nice. Almost all of you. Um and we recently announced the Ledger Tax and Flex in the on the right part where it's a touchscreen device. Um it's an e- in screen and uh it brings new use cases and features which are very um it's more practical for the new features and use cases which we will see today.
Um okay who here in this room can tell me what this transaction does? Anybody? Um it does look kind of ruggy. Um, and if you're having a hard time, uh, you are correct because this is what we call blind signing. And, uh, typically it's very hard to understand if it's a legit transaction, if the payload is malicious, maybe it's not even the right contract or function, or maybe you're authorizing something you don't mean to.
Um, blind signing is a lot like signing a blank check. Obviously, you wouldn't sign a blank check, but sometimes you blind sign transactions, which uh is exa essentially the same. Uh in general we say that if uh the transaction is unreadable it's also unpredictable and if it's unpredictable it's not safe to sign. Uh so this brings us to the first track we have uh which is the clear signing track that aims to fix blind signing. So again this is blind signing and so okay we brought a few papers.
We have the tracks on paper as well. Um you can also come and see us at the booth if you have any questions. Uh but essentially um we provide example projects of uh the clear signing tracks. Um but feel free also to you know be creative and do your own projects. Um any tooling that helps with clear signing adoption or clear signing usage uh will be appreciated.
Um and we will see how clear signing works but essentially if you participate in the clear signing initiative and you create a JSON file you can win a ledger flex as well. Um there's also a feedback um you can provide on the whole ERC7730 clear signing experience and this is also part of the bounties. So we have 4K for clear signing with two prices so 2.5K and 1.5K.
Um but yeah so clear signing is the opposite of blind signing and here we have an example flow. So you can see on the first screen we are put in the right conditions. We know we are about to swap tokens. And on the middle screen here, we can see that we are interacting with a 1 in contract. We are about to send a,000 rapmatic and receive 554.
91 USD. Uh we can check if the receiver is correct. Does this match my address? And if all is well, we continue by signing the transaction. So, you know, clear signing is fully transparent.
It's human friendly. It's written in English in natural language. And uh it's empowering because you feel in control as a as a user. Um so how does this work? Uh first of all you might think as a developer okay but we do have the AI why don't we use the AI and actually AI just don't get you far enough.
We can see here that the intent is not very clear exact input single. We have the raw token address which you know you have to verify manually compared to earlier with rapmatic for example. Um the amount also is in base unit which is you know we're not machines so base unit is not very friendly for us and it's very hard to hide parameters. Uh we want to be able to control what's going to be displayed on the device for the end users. Um clear signing in reality is uh divided in three steps.
So we have the creation phase, the validation phase and the integration phase. Uh as I mentioned we have we ask DAP developers such as yourselves to create a JSON file and uh this JSON file will describe your smart contract and provide human readable fields for example for functions and variables. Um to do this we at ledger we also released um addition tools. So it's a very easy to use tool online. There's a QR code on the sheet of paper that you have and uh essentially it takes really less than half an hour to create a JSON file with this tool and this is the track where you can win a ledger effect.
uh once you did your JSON file as a developer you push it to the repository which is public uh it's a ledger repository and uh all the files all the JSON files already done are on this registry so you can go and see uh how one in might have done it how a might have done it and uh the endorsement right now is done by Ledger so there's a security team at ledger who is going to review these JSON files make sure they do describe the smart contract as and that no function or variable is left behind And finally, the integration phase is where all the magic happens. So all of this JSON file and all the metadata is parsed, filtered and formatted to be prepared to display on the device. And uh obviously last step if you have a Ledger device with the secure user interface, you can be sure that's what's displayed on your screen is what you are about to sign. Uh JSON file, I'm sure you're all familiar with it. Um it's human readable, it's lightweight, efficient, it's understandable by machines, by humans.
It's very practical. It's easy to nest data. Uh we have on the on the left an example. So uh for example, the amount in uh was renamed in the context of clear signing amount to send which is more user friendly. Uh the format of the field is token amount which is exactly what we want and uh but the important part as well is on the bottom part we can see a required field and this is exactly what we need to to choose what is displayed on the device.
So here in the required we have the amount in the amount out and the recipient. Um so now we're going to see an example of how a uh might have used our JSON creation tool to create their clear signing JSON file. So it's very simple as I mentioned. Uh the first step is just to enter the a contract address. On the left there's a QR code here if you want to link a direct link to the tool.
Um on the right step two is very basic metadata. So the owner info, legal name, URL. Uh and this will all be displayed on the device as you can see on the on the image on the right. Um and then we start crafting fields. So we chose on the top part the borrow operation.
Uh we chose to give it the name borrow tokens. And uh we are really able to hide fields any unnecessary field we don't want displayed on the device we can hide them. And we also customize the amount field and the interest rate as well. And uh you can see on the right some very nice uh previews on a ledger flex of how the flow will look like for the end users. Uh and then you're done.
Actually you just download the JSON file and you submit it to the same repository I mentioned a minute ago. Um and this is the end result of what it's going to look like on device. You can see we just did a the borrow operation. We can see the interest interest rate mode on the right and the deptor all the information we just clear signed. Um some ideas for the hackathon as well which is not in the piece of paper is to improve this creation tool this JSON creation tool.
So what we did is we opened some issues for you. Uh these are the issues. So essentially Victor Fju is an engineer at Ledger and he opened a few issues you can check out if you want ideas on on how to improve the JSON creation tool itself. Um as I mentioned the registry with all the existing JSON files of the main DAPs out there um you can have a look and see uh how they might have done it and make sure you don't clear sign something that is already clear signed and already inside the registry. Uh as I mentioned, you can win a Ledger Flex by submitting a JSON file, which is very easy and straightforward.
Uh but however, we do have a tool at Ledger that will analyze the quality of your JSON file and give you a score. So if you can come to our booth and uh we will run the your JSON files into this tool and see we can we can work together to make it uh perfect for production. The second track now is hardware integrations. Uh again, this is also on the piece of paper you received. So we have 5,000 here, 3,000 for the first one, 2,000 for the second place.
Um and uh you can leverage uh our new device management kit. Um like for example, you can uh integrate Ledger hardware into your uh DAP. Uh what we also would like you to look at is how to implement the ledger device management kit in all the popular Ethereum connector libraries. So there's a few listed here. like ethers.
js, WagMe, Rainbow Kit, uh all the ones you're probably familiar with already. Uh you can also choose to build an app for Ledger devices. Um so maybe slightly more ambitious but still doable. Uh our new device management kit uh is a very nice way to interact with Ledger devices. Uh maybe some of you are familiar with LedgerJS, which is the legacy set of tools that we had before.
Uh the new device management kit really allows you to discover devices, manage the connection, exchange data. Uh you have a nice state management as well where you can see if the device is on, off, idle and you can call OS commands directly. So a very nice way to interact with Ledger devices and there's a link at the bottom of the page here as well. Uh the final track is about documentation. Uh anything you think uh might help improving the documentation is useful to us.
Uh we have a full team at Ledger working on the documentation specifically making sure it's thorough and and accurate and matches the tech advancements. So we have $1,000 here. Uh there's a few examples here of what we we might expect uh any gaps in documentation uh UX as well. Um if you feel that the code examples need to be more thorough or better explained. Uh so yeah, feel free to just go for it and and destroy our documentation.
Um a few useful links. Again, these QR codes are on the sheet of paper as well. And uh and that's it. Thank you. Come and see us at the booth.
We would love to have you. Thank you.
Anyone has any questions?
Hi.
Hello.
Sorry. Okay. Uh so uh what is the approximate review time of JSON file from your team?
Uh so the tool is pretty much immediate. It takes a minute uh to review.
You will have a score immediately.
Uh yeah very fast.
Okay. Thank you.
Is there any simulation of connecting uh my Ledger wallet because I don't have it with me. So uh how can I play with it? Okay. So, so we do have devices that we can lend and you can also come and see us at the booth at any moment and we can, you know, we can see it together. Um, yeah.
So, we don't have unlimited device to give to every developers but uh we can arrange something if you if you need one.
Thank you.
Any more question?
So, I have a question. Uh clear sing is only for leger flex or nano s plus that work that's work on nano s or only on ledger flex
what does the
okay yeah just to have it on microphone uh clear signing works on all our devices but of course the experience is better with the bigger screen and the the single page with all the information on on the latest devices. Anyone can submit JSON for any contract, not only sound.
Exactly. And that's uh Yeah, exactly.
Okay.
Any DAP, of course, that's not already in the registry.
Thank you. Any more questions?
Thank you very much.
Thank you very much. [Music]
Automatic transcript — names and jargon may be misspelled.