Hello everyone, congratulations, good afternoon, and thank you for coming to the Ledger workshop. I'm Ethan Waldron, I'm responsible for developer relations at Ledger, as well as product, and I'm here with Oscar Shack, who is also a product who is also a product manager at Ledger. We will talk a little about what we do in the world of agents at Ledger and present the directions of our hackathon. Who here in the room is already familiar with Ledger? Very good.
A little. OK. So, Ledger is a French company founded in France in 2014. We create hardware devices that help protect your cryptocurrencies. We have already sold over 8 million of these devices, and today we protect about 20% of the world's crypto assets.
Interestingly, Ledger devices are secure by design, and this is achieved through the combination of a so- called secure element—a chip inside the device— inside the device— and a secure display that sits directly above that chip. Yes, for the past 12 years we have focused on user and developer experience. You may be familiar with our product line. We have Ledger Wallet—a companion app for Ledger devices to manage your funds and Ledger experience. Additionally, we have Clear Signing—a convenient way for users to interact with the device when signing transactions so they understand what they are signing.
We also have a Wallet Provider that helps DApps integrate Ledger into their login or signing processes. So yes, over the last 12 years we have been very focused on user and developer experience. And it's interesting developer experience. And it's interesting that we're now entering a new era, as we all know, the era of agents, and we're also very well prepared to become a reliable infrastructure for this new world of agents. Yes, I'll let Oscar tell you a little bit .
Yes, of course, thank you. So, to get a little deeper into the details of why we want to solve the problem for agents. I think, as we all know, agents are really useful if they can actually do something. For example, to sign transactions or act on your behalf. The problem is that they are more vulnerable to hacker attacks, for example, through prompt injections.
But this is not the only attack vector that can lead to loss of funds or theft of your credentials. Agents can also hallucinate, which can lead to loss of funds. So Ledger can offer you a way to check exactly what an agent is going to do before they do it. And you can view it on the Ledger trusted display, just like you sign crypto transactions today, and it also allows you to store your credentials and private keys securely right on your device. The agent cannot act or move assets independently.
First, it must get your approval on the hardware device. So, over the past few weeks, we've launched three main pillars, essentially CLIs, that allow you to interact with your Ledger device directly through your favorite agent. So you can simply ask for a code: “I want to use the Ledger wallet CLI,” and then connect the wallet, check balances, accounts, and initiate transactions that you confirm on your device. It's the same experience, but optimized through your agent. The second your agent.
The second is DMK skills, which are more geared towards developers like you. You can train an agent to use your device and integrate it into your own application or workflow. This will greatly simplify integration. Previously, Ledger integration took days, if not weeks. Today, with these skills, it takes five minutes.
Just give him those skills. Tell him that you want to sign these actions using Ledger devices. And he will do it for you. I'll demonstrate this in a moment. Finally, there are applications that we run within the Ledger stack for agents Ledger stack for agents that allow you to protect your credentials through a security key application.
This allows you to use Fido2 to securely log in to websites. This also limits agents' access to these websites. There is also another application called Open PGP that allows you to encrypt secrets, such as agent secrets. This is what we launched. We want you all to try this at work.
And before we go any further in the demonstration, I can quickly show you something. I created this dummy site where agents can offer transactions for your Ledger device. There is no integration with Ledger at this time, right? So I can try to sign a transaction on Ledger, but currently no signing or integration with the device is happening. This is just a mockup, but I'll just ask Claude to integrate with DMK's skills and see what he does.
So let's now integrate into a fictitious website. Let's see how long it takes. So, this will help solve many tasks, including integrating with the device, controlling the opening and closing of applications, and retrieving addresses from the device. It supports Bitcoin, Ethereum, Solana, and it seems Cosmos as well . And there's the security key app I just mentioned I just mentioned , with FIDO2 credentials and login .
While this is working, I'll probably have to confirm something. I can show you how the wallet CLI works. Essentially, this allows you to ask things like: "How many BTC do I have on my Ledger?" Excuse me, my device is locked device is locked , but I will unlock it , but I will unlock it . As you can see, it will use the Ledger wallet CLI to find my accounts.
It connects to my device directly. Here you can see that it asks to confirm opening the application on the device. So I'll just click " just click " open." Ahem. OK.
And now it finds the accounts on my device and their associated balances. Meanwhile, another agent integrates a set of device management tools into the application. We structured the skills file according to the documentation for the device management toolkit, and also added some implementation examples from the past. We have optimized this to ensure the best integration path with Ledger is used. In addition, there is all the business logic there that we didn't necessarily include in the documentation.
Using skills not only simplifies the integration process, but also ensures that the information is relevant. Here, please. He answered me. As you can see, I don't have much BTC, but it found all my test accounts on the Bitcoin network. Now I'll ask about Ethereum.
OK. Which, if I were on the Solana network, hopefully it wouldn't take too long. Boom. It will also ask me to open the ETH app, which I will confirm on the device. This is...
Okay. As you can see, it sees that I have multiple Ethereum accounts. So, he gets the balances. That's all. He sees different accounts and different tokens.
I have 30 USDC, another USDC, and 3 USDT. These are my test funds. The CLI allows you to do more complex things. For example, find out how much gas commission I spent last month. Let's say four months.
Ahem. It seems that the DMK integration has also been completed. So, I think it took about four or five minutes, which I think is pretty good. Um, okay. Boom.
So, she'll pull up the transaction history here, um, to check my allocation. Tech. OK. Yes, I want to accept. Okay, that's what I spent on gas commission.
So you can imagine if you have a lot of accounts and you do a lot of transactions, it's pretty handy if you want to review the amount of gas fees. And now I'll just finish with one final operation. So, okay, I want 70% ETH and 30%BTC. I offer deals on my device. Um, and the logic is the same every time, right?
So, there are many read operations that are possible when your device is connected and you have opened an app, etc. But every time funds are moved, um, you need to confirm it on your device, and you'll see this information on it: the amounts, the address they're being sent to, etc. So, let's go. I allow this. He will find the best course.
I'll just open here to pick out the details. As you can see, we've taught the CLI, essentially, to know where to look, to know which accounts are tied to which addresses. Ahem. So it does the hard work for the user. You just, um, ask him in plain language what exactly you want him to do.
Okay want him to do. Okay , he knows I'm actually close to that 70/30%, which is nice to that 70/30%, which is nice , but he's going to offer me one final trade to get to that point. I hope the amount is large enough. OK. Good.
Let 's do something. Good. Let's do 80/20. The exchange was too small then. I think it's test money.
So, I think he'll list the rate for providers here. I'll look at the time. We still have 10 minutes. This is normal, right? Good.
T. Okay. We do 80/20. He is going to sell BTC and buy ETH. Um, while he's doing it , I can show you here.
Um, so now this should work in real time with DMK. If I update, yes, it is now integrated with DMK. So, the mock transactions that I just showed you are essentially. Now, um, if you click " you click " connect" here, it will already find the device connected to the Flex. I click connect.
Um, he recognizes my address. As you can see, everything is pretty smooth. So, I'm going to intentionally lock the device and show you the device and show you that it actually knows that my device is locked, which is much better than what we had before. It really knows the state of the device and can quite smoothly display actions that the user can perform. So, here it asks me to unlock the device.
I'm going to unlock it. Probably with your password. Boom. Unlocked. He is currently processing the transaction.
And I'll show you this transaction. This is a clear sign. Transaction verification is also running in the background . It simulates transaction security. It is reported here that the check did not reveal any threats, which is reassuring.
And if I want to perform this operation, the device shows all the details of the transaction. So, Uniswap. I am going to send this amount and receive this amount. Also shows commissions. If I need more details, I can click on the little X buttons.
This time I will decline the transaction. But you get the point, right? I created a demo app. Integrated it in a few minutes it in a few minutes . And you can essentially integrate a lot of workflows with the Ledger device like this Ledger device like this .
And while we're at it, let's see if I can now execute a swap. Okay execute a swap. Okay . Okay. Let's try option two.
I'm going to sell all my BTC. OK. Let's hope Ethereum goes up after this. Well, let's go. Boom.
Yes. We perform a swap. From Near Intents. Shows that this is the best offer. This is quite convenient.
Of course. I will make this swap. Well, let's see swap. Well, let's see . This might work.
I use a slow commission strategy. I don't know if this will help, but I see we have four minutes. So I guess we can continue the presentation while that's being done. Yes. Okay, great.
Let's do this. Boom. These are a few things we have launched. They allow you to interact with your Ledger devices. They make it very easy to integrate Ledger devices into your own applications.
And, as I said, there are other applications you can work with, can work with, like Open PGP and Security Key. Yes. And that brings us to our hackathon. This year we chose one direction. This is, in fact, Gentic X Ledger.
We have allocated $10,000 in prize money for five awards. Um, and essentially, the main idea is to create AI products that use Ledger as a layer of trust. So, this could be any project where device-level security is important and central to your product. Um, we have a few examples here. Here are some examples where human participation is important in workflows, such as performing risky actions when you want a human to be involved and confirm them on a physical device.
Um, some use cases involve identification—either your own or your agent's identification. Um, these are just examples, but it's, you know, to give you an idea. We also have credential management, and the important authentication management, which can be done using Ledger devices. And I'm sure you're familiar with X42, but we can have agents that pay for API that pay for API tools and services where Ledger acts as a trusted element, as well as any policy-based costs. So, for example, after a certain amount, you have policies where you require mandatory Ledger participation.
This is also an important point. So these are just examples. We are open to anything you can suggest can suggest , we just see that integration with Ledger is becoming easier and easier, and we have eliminated any difficulties with this integration. So you can focus on the use cases themselves . Um, and we have a QR code here.
We have a page on the developer portal, Ledger documentation, this QR code will take you there, it has track details, examples, and all the necessary links to the relevant sections so you don't have to search for them. Um, but there's one important thing, sorry, I'll go back because I see some of you are scanning it. Um, we really appreciate feedback on our documentation. I mentioned that developer experience is very important to us. So if you can write a short paragraph or page about what your experience was with integrating our tools, it would be a great help to us and future developers.
This is also on the page you just scanned. And thank you very much. It was us thank you very much. It was us . Yes.
Have questions or comments? Yes. Device. What is this? Yes, you have an emulator on your computer have an emulator on your computer that you can use too, but we will provide you with the devices when you need them.
Uh, dancers. Yes. My question. OK. Yes, we have several.
Yes. Sorry, I didn't catch what exactly? Do we borrow physical devices? Yes. Yes.
So, we have a few on the stand. If you just come down to us come down to us , we're where the Ledger stand is. We actually borrow some for the weekend. Uh, yes. Yes.
So we have a few specifically for that. Yes. Is there any difference between an emulator and...Uh, okay, let me continue. There are several points.
I think an emulator helps to some extent, but if you want to have more realistic interactions—for example interactions—for example , checking whether an app is open or closed, or, say, you want to debug what happens when a device is disconnected—then it's better to have a real device. But it's still quite useful, and if we have a regular device to borrow, we have plenty of them at the stand, so we can easily provide it to you. Yes. What if this is a high-frequency use case? Can the transaction be allowed?
Yes. This, by the way, is one of the items, the last one on the list that you see here. I think it would be extremely interesting to see use cases where you can let your agent trade or perform actions for you autonomously. If you can create something like that, that would be really interesting. Politicians, for example, you could only...
Yes. Yes. Certainly. So, this would be an idea using Stack and the capabilities that Ethereum offers. I think there are ways to imagine this.
OK. Thank you all. Thank you very much.
Automatic transcript — names and jargon may be misspelled.