-
It’s currently complete to test the clear singing on device using the current https://app.devicesdk.ledger-test.com/signer/ethereum, it’s unclear how to test on device with just a transaction field as the current workshop example only cover EIP-712 message singing, I tried to build the etherjs v6 transaction object locally but I couldn’t trigger the transaction on device, the webpage loaded without any response
- About this I’m really missing a clear step by step guide with some transaction example, from a simple send to a lido deposit transaction for example (as the clearsigning is already ready)
-
The current PR is confirmed and “green” on the github CI but additional approval are required on the CAL review the contract informations in https://app.devicesdk.ledger-test.com/signer/ethereum
- Because of this when testing it the device will not be able to fetch the contract name, and intuitively, I want to overwrite this in the formatting by passing a displayName in my deployment object
- How can this process be made more permisionless ?
-
The current EIP-7730 should be updated to simplify the management of registry containing multiple deployment. For example protocols like Kiln or Yearn, have many deployments (from 10 to 100s), they will need a simple way to update this list overtime
- Currently the token parsing is only allowing to use the first
contract.deployments.[0]..
- With this model, for 10 vaults, the partners will need to create 10 files in the registry
"params": {
"tokenPath": "$.context.contract.deployments.[0].address"
}
