You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, this repo is extremely important for the security of Keystone users.
Last PR merged was in January, last release of contracts zip in Sept 2024.
Why is that, how can this change? I'd like to be able to upgrade the set of contracts now and then, or any time I'm proposed to blind sign.
I'd like to see a flow how I can add contracts simply, using sourcify, etherscan, or any other tool out there.
The text was updated successfully, but these errors were encountered:
I agree with @Tbaut. The Bybit fiasco just showed us the importance (again) of being able to clearly understand what we are signing on our HW wallet. I was relieved to see that Keystone has the ABI decoding feature but the docs here and the README of this repo show some conflicting instructions. Either way, my wallet was unable to parse the encoded data and I am stuck with blind signing now. Please make it easier/clearer for advanced users who want to upload custom contract ABIs for transaction decoding.
Hello, this repo is extremely important for the security of Keystone users.
Last PR merged was in January, last release of contracts zip in Sept 2024.
Why is that, how can this change? I'd like to be able to upgrade the set of contracts now and then, or any time I'm proposed to blind sign.
I'd like to see a flow how I can add contracts simply, using sourcify, etherscan, or any other tool out there.
The text was updated successfully, but these errors were encountered: