feat: NEAR Protocol native support (Ed25519, implicit account, blind-sign)#248
Open
BitHighlander wants to merge 1 commit into
Open
feat: NEAR Protocol native support (Ed25519, implicit account, blind-sign)#248BitHighlander wants to merge 1 commit into
BitHighlander wants to merge 1 commit into
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
First-pass NEAR Protocol support on the device: derive a NEAR implicit account and sign NEAR transactions.
m/44'/397'/0'), decimals 24NearTransactionand shipsraw_tx; firmware signsEd25519(SHA256(raw_tx))and returns the 64-byte signature. Device displays host-suppliedreceiver_id+action_displayfor confirmation.near.c/.h,fsm_msg_near.h,messages-near.options; wired intofsm.c,fsm.h,messagemap.def,coins.def/coins.c(isNear()→ account-based),CMakeLists.txt.Dependency
Bumps
deps/device-protocolto the NEAR-proto commit. Merge BitHighlander/device-protocol#32 first (or this submodule pin lands ahead of master).Notes
raw_txmatches the displayedaction_display. Per-action parsing / clear-signing is a follow-up. This already supports any NEAR action (transfer, FunctionCall, CreateAccount/AddKey — i.e. name registration) since the host builds the payload.Test plan
messages-near.proto)NearGetAddressreturns hex implicit account for a known seedNearSignTxover a Borsh payload; verify signature against the returned pubkey