feat(near): NEAR Protocol native support#245
Open
BitHighlander wants to merge 1 commit into
Open
Conversation
…+sign) - messages-near.proto MessageTypes 1600-1603 (via device-protocol feature/near-proto) - near.c: Ed25519 key derivation (SLIP-0010 coin type 397), hex implicit address, SHA256+Ed25519 signing - fsm_msg_near.h: NearGetAddress + NearSignTx handlers wired into FSM - messagemap.def, fsm.h, fsm.c: registration + forward decls - lib/transport/CMakeLists.txt: nanopb compile step for messages-near.proto - coins.def: NEAR entry (ed25519, decimals=24, BIP44 0x8000018D) - coins.c: isNear() added to isAccountBased()
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
m/44'/397'/0', SLIP-0010 hardened)NearGetAddressandNearSignTxFSM handlers with on-device confirmation screenEd25519(SHA256(borsh_serialized_tx))— host Borsh-serializes, firmware signsmessagemap.def,coins.def(coin type 397, 24 decimals), transport CMakeLists nanopb compile stepraw_txbytes +receiver_id/action_displaystrings for confirmation displayFiles changed
lib/firmware/near.cinclude/keepkey/firmware/near.hlib/firmware/fsm_msg_near.hlib/firmware/fsm.cinclude/keepkey/firmware/fsm.hlib/firmware/messagemap.deflib/firmware/CMakeLists.txtlib/transport/CMakeLists.txtinclude/keepkey/transport/messages-near.optionsinclude/keepkey/firmware/coins.defProto dependency
messages-near.protowithNearGetAddress/NearAddress/NearSignTx/NearSignedTxat MessageType 1600–1603 is onfeature/near-protoin device-protocol — that should land first so the nanopb step resolves at build time.Test plan
NearGetAddressatm/44'/397'/0'returns 64-char lowercase hex pubkeyNearSignTxshowsreceiver_id+action_displayon OLED before signingActionCancelledfailureed25519_sign_open