-
-
Notifications
You must be signed in to change notification settings - Fork 629
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tezos: add baking support #114
base: main
Are you sure you want to change the base?
Conversation
Currently working on a better way to display the signed operations. Considering worklfow.startdefault() as suggested in trezor/trezor-core#473 |
I created a new "baking" homescreen for the baking mode. With this approach we can display information of the last signed operation during the baking mode. We store the last level and the operation type in storage so in case of a restart, we can display the last signed operation when starting baking mode. |
refactor staking -> baking, delegator -> baker remove watermarks and tags, force set in trezor remove unused baking field tezos: add staking support fix control staking refactor names delegator -> baker, staking -> baking, add baking banner Changed workding in screens rework message blocking logic - remove all unused message handlers mode now stored in runtime memory, code adjusted accordingly reorganize writers remove redundant check of watermark bytes writing directly to the hasher with HashWriter force set the magic_byte/watermark and tag use directly helpers.validate_full_path rework baking check, remove debug prints fix typo - removed space remove unused dialog requested changes made add option to not show signed baker operation on display Add tezos staking support refactor staking -> baking, delegator -> baker Add start/stop baking to trezorctl remove baking field - send blank TezosControlStaking message remove unused trezorctl calls and modify tests restore test file core/tezos: add new default workflow for displaying signed opertions core/tezos: screen - handle first ever baking op with the device core/tezos: fix the overlapping TEZOS BAKING bar core/tezos: cleanup Add block/endorsement level validation - double baking/endorsement prevention
Hi there, thank you for your PR. I just wanted to give you a quick update from our side. We are interested in adding this to our firmware but we just don't have enough capacity to review it right now. We would be more than happy to take a closer look at it later, when our capacity frees up a little, likely during the course of 2021. Thank you for your understanding. |
this is great news, we will update code to reflect latest 007 protocol update, thanks |
Ads signing for baking and endorsement operation.
Resubmitting PR from trezor/trezor-core#473 and trezor/trezor-common#267