diff --git a/pages/docs/device-app/develop.mdx b/pages/docs/device-app/develop.mdx index 70135720..c518c178 100644 --- a/pages/docs/device-app/develop.mdx +++ b/pages/docs/device-app/develop.mdx @@ -36,13 +36,10 @@ explanations. /> +
-
-
+
+
- -
- -
diff --git a/pages/docs/device-app/develop/tutorials/plugin.mdx b/pages/docs/device-app/develop/tutorials/plugin.mdx index ac1fe0b7..01ae8e03 100644 --- a/pages/docs/device-app/develop/tutorials/plugin.mdx +++ b/pages/docs/device-app/develop/tutorials/plugin.mdx @@ -17,13 +17,13 @@ Let’s start with a high-level overview of what a plugin is, how it interacts w If you’ve already interacted with any smart contract using a Ledger Device, then you’ve already seen this screen: -![Blind Signing](/blind-signing.png) +![Blind Signing](/plugin/blind-signing.png) This is a UX disaster. The user has no guarantee of interacting with the right smart contract, nor of signing the correct data. The only user action is literally to blind-sign the transaction. Display information is specific to each smart contract: so when swapping on a decentralised exchange, you probably want to see information such as “Swapping X ETH for Y DAI”. When depositing DAI on Aave, you need to see the amount in DAI. So, the information is specific to the smart contract. -![Plugin](/plugin.png) +![Plugin](/plugin/plugin.png) Modifying the Ethereum App would not do because its size would quickly go out of control. Instead, the solution lies in a small and versatile parser of smart contract data, which works hand-in-hand with the Ethereum App and decides what to display for the best user experience. diff --git a/pages/docs/sections.mdx b/pages/docs/sections.mdx index 9d347e99..234b521e 100644 --- a/pages/docs/sections.mdx +++ b/pages/docs/sections.mdx @@ -12,7 +12,7 @@ import { Card, Cards } from 'nextra/components' image arrow title="EVMs plugins for Clear Signing" - href="/docs/plugin"> + href="/docs/device-app/introduction/plugins"> <>![Cryptoassets Library](/defi-cover.jpg)