Improve plugins visibility, update README (#162)
* Add link to paraswap in plugin doc * Update readme with new dev portal and paraswap plugin link
This commit is contained in:
@@ -10,6 +10,8 @@ Specification version 1.0 - 24th of September 2020
|
||||
|
||||
This specification describes the plugin interface used to display a specific UI on device for Ethereum smart contracts.
|
||||
|
||||
Feel free to checkout the ParaSwap plugin to see an actual implementation. Link: https://github.com/LedgerHQ/app-ethereum/blob/named-external-plugins/doc/ethapp_plugins.asc .
|
||||
|
||||
## Flow overview
|
||||
|
||||
When signing an Ethereum transaction containing data, the Ethereum application looks for a plugin using .either a selector list or the contract address.
|
||||
@@ -279,7 +281,7 @@ The following return codes are expected, any other will abort the signing proces
|
||||
|
||||
When setting a pointer from the plugin space, make sure to use an address that will be accessible from the Ethereum application (typically in the plugin RAM context, *not* on the plugin stack)
|
||||
|
||||
Do not use data types that need to be aligned (such as uint32_t) in the plugin context
|
||||
Do not use data types that need to be aligned (such as uint32_t) in the plugin context.
|
||||
|
||||
## TODOs
|
||||
|
||||
|
||||
Reference in New Issue
Block a user