CommitWatch RSS
Q
← Developer activityStrong match

Qkin-Keystone

Public commit activity attributed with strong match confidence. This page describes observable work, not personal trustworthiness.

38 commits1 monitored projects2 candidates0 high-risk analyses
Project constellation

Where the commits appear

Amber nodes are monitored by CommitWatch. Gray nodes are sampled from authenticated GitHub public commit search and may not represent complete contribution history.

Monitored External sample
Projects connected to Qkin-KeystoneA visual map of monitored and externally discovered repositories.Qdeveloper38Keystone 3 firmware
Monitored evidence

CommitWatch projects

Keystone 3 firmwareKeystone38 commits2 candidates0 high risk
External discovery

Other public projects

No external sample loaded yet.

A verified GitHub handle is needed before external discovery.
Analyzed activity

Recent published watches

Message quality and risk characterize commits, never the person.

Low 25 AI analysisMessage 28 · Opaque
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

fix merge conflict bug

This commit fixes a merge conflict in a firmware file for the Keystone 3 hardware wallet. The change adds a missing memory cleanup function (FreeTrxMemory) and restores a missing user-interface entry for TRX swap transactions. Without the …

Memory cleanup function added (FreeTrxMemory) — possible memory leak mitigationMissing UI view restored (REMAPVIEW_TRX_SWAP) — possible UI/UX regression fixCommit title describes the change as a merge-conflict bug fix, not a security fix
333badc3by Qkin-Keystone+3−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 11 AI analysisMessage 45 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

add expiration for warpped tron instance

This commit adds a new 'expiration' field to a Tron transaction data structure used inside the Keystone hardware wallet firmware. The change only initializes the field to an empty string in a few places and does not, by itself, appear to f…

New struct field added but not validated in the visible diffNo explicit security claim in commit title or messageNo functional code change beyond struct initialization
3f277a90by Qkin-Keystone+3−01 file
No security note in commit
Open full analysis →Source commit ↗
Low 35 AI analysisMessage 45 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

fix TRX swap to asset mapping bug

This commit fixes a bug in how the Keystone 3 hardware wallet classifies certain Tron (TRX) transactions. Previously, only memos starting with '=:' were recognized as swap transactions. Now memos beginning with 'SWAP:' (case-insensitive) a…

Transaction-type classification heuristic expandedSwap-specific approval flow may now trigger for previously mismatched memosNo cryptographic, signature, or parsing hardening visible in diff
82866b9aby Qkin-Keystone+2−11 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 28 · Opaque
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

update code format

This commit only reformats existing source code. It changes line breaks and indentation in a single Rust file so that a long expression and an if-statement are split across multiple lines. No logic, behavior, or security checks were change…

cca2aca6by Qkin-Keystone+4−31 file
No security note in commit
Open full analysis →Source commit ↗
Low 34 AI analysisMessage 38 · Opaque
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

fix TRX swap to asset

This commit changes how a Keystone hardware wallet displays the destination asset for TRON (TRX) swap transactions. It adds a mapping from short/raw asset codes (like 'b' for BTC, 'e' for ETH) to human-readable names, normalizes case, stri…

UI parsing of untrusted swap memo dataNormalization/mapping of asset identifiers shown to user before signingUse of bounded string helpers (strncpy_s, strcpy_s) with local temp buffer
a48b77e6by Qkin-Keystone+66−43 files
No security note in commit
Open full analysis →Source commit ↗
Low 37 AI analysisMessage 28 · Opaque
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

fix code review

This commit moves a memory-freeing operation from one cryptocurrency display structure (Ethereum Swapkit) to another (Tron). It appears to fix a code review finding about a string pointer being freed in the wrong place, which could otherwi…

Memory management change in FFI Rust/C boundaryRelocation of `free_str_ptr!` call between structsPotential double-free or use-after-free if pointer ownership was mismatched
c2fdab1bby Qkin-Keystone+1−12 files
No security note in commit
Open full analysis →Source commit ↗
Informational 14 AI analysisMessage 28 · Opaque
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

fix pr review

This tiny code-quality patch addresses two minor issues found during a pull-request review: one removes an unnecessary `.clone()` call in Tron transaction handling, and the other adds a missing memory-field cleanup for a new Ethereum/Swapk…

Memory-management consistency fix: adds missing `free_str_ptr!` for `raw_value` in `DisplaySwapkitContractData::Free`Code-review cleanup: removes redundant `.clone()` in Tron transaction expiration handling
31e9649fby Qkin-Keystone+2−12 files
No security note in commit
Open full analysis →Source commit ↗
Low 27 AI analysisMessage 45 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

update tron swapkit memo ui

This commit adds a new on-screen display for Tron cryptocurrency swaps that use a memo starting with '=:' (called 'SwapKit' style). It shows the user extra details such as the destination asset, destination address, raw amount, memo, and e…

New UI path triggered by attacker-influenced memo prefix '=:'Memo content is parsed with strchr on ':' and rendered as destination asset/address, creating a UI spoofing surfaceNo visible length/charset validation on memo before display
d063c974by Qkin-Keystone+178−813 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 67 · Adequate
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

test: verify memo in raw_data and fix formatting

This commit only adds a new test assertion to existing Rust test code. It checks that the transaction memo matches the raw_data.data field in a Tron transaction test. There is no change to production code, no bug fix, and no security-relev…

2f90d5ffby qkin+2−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 28 · Opaque
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

update code format

This commit only reformats a single Rust test file by splitting a long assert_eq! line into multiple lines. It does not change any executable code, logic, or security behavior.

dc988b09by qkin+4−11 file
No security note in commit
Open full analysis →Source commit ↗
Informational 11 AI analysisMessage 45 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

fix:add memo for tron swap tx

This commit adds a new test case for parsing TRON swap transactions that include a memo field. It does not change any production code; it only verifies that an existing parser can correctly extract a memo from a specific transaction payloa…

468eff30by qkin+10−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 45 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

update tron parse raw message

This commit only changes the user-facing warning text shown when a TRON raw message cannot be parsed. It is a wording update with no functional or security change.

e749ef3bby Qkin-Keystone+1−11 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 45 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

add sol icon in connect keystone nexus

This commit simply adds the Solana (SOL) coin icon to two lists of icons shown on the 'connect wallet' screen for the Keystone Nexus wallet. It is a cosmetic UI change with no security relevance.

86490bcfby Qkin-Keystone+2−21 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 28 · Opaque
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

add sol nexus support

This commit adds support for two Solana (SOL) public key derivation paths when connecting the Keystone hardware wallet to compatible software wallets via the 'Keystone Connect' feature. It is a routine feature addition and does not contain…

a9d31cb9by Qkin-Keystone+5−12 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 28 · Opaque
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

update rust code format

This commit only reformats Rust source code. It moves a comment onto its own line and adjusts blank lines. No program logic, calculations, or security behavior changed.

a53b1778by Qkin-Keystone+4−31 file
No security note in commit
Open full analysis →Source commit ↗
Low 44 AI analysisMessage 45 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

update review bug and remove useless comments

This commit fixes a logic bug in how Tron transactions are routed based on QR code type. Previously the firmware treated 'TronSignRequest' as if it were a Keystone-style request and vice versa, which could send the wrong data to the wrong …

Inverted conditional routing between TronSignRequest and KeystoneSignRequest in Tron transaction parse/check/sign pathsFloating-point precision fix in token amount formatting (log10 rounding replaced with iterative decimal counting)Removal of a hard-coded Tron standard request test vector from rust_c test commands
bed968eeby Qkin-Keystone+21−254 files
No security note in commit
Open full analysis →Source commit ↗
Low 35 AI analysisMessage 35 · Opaque
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

remove useless dependency

This commit removes unused serialization libraries from the Tron app and, more importantly, changes how a missing wallet derivation path is handled. Previously, a missing path was silently replaced with an empty default. Now the code retur…

Silent fallback on missing derivation path replaced with explicit error returnRemoval of unused serde/serde_json dependencies reduces attack surfaceChange is in Tron signing request validation path
5634d954by Qkin-Keystone+4−53 files
No security note in commit
Open full analysis →Source commit ↗
Low 36 AI analysisMessage 18 · Opaque
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

update review

This commit updates Tron-related code in a hardware wallet firmware. It changes how decimal precision is calculated for token amounts, removes an 'unsupported transaction type' error fallback, and broadens the accepted derivation path pref…

Floating-point arithmetic now used for financial precision calculation (log10 on divider)Catch-all error arm removed from transaction type match, narrowing explicit handlingDerivation path validation broadened to accept additional coin types (194')
4fb3a5e8by Qkin-Keystone+16−272 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 28 · Opaque
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

update image hash

This commit simply updates a stored hash value in a text file used for tracking image assets. There is no code change, no bug fix, and no visible security relevance in the commit itself or the supplied materials.

67c98a5bby Qkin-Keystone+1−11 file
No security note in commit
Open full analysis →Source commit ↗
Informational 11 AI analysisMessage 62 · Adequate
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

chore: revert submodule pointer to match origin/master

This commit only changes a Git submodule pointer (a reference to another repository's version) back to match the upstream master branch. There is no code change visible, no security fix, and no security-relevant behavior described.

32ff9aa1by Qkin-Keystone+1−11 file
No security note in commit
Open full analysis →Source commit ↗
Wrong identity?Names can collide and public author strings can be misleading.Contact commitwatch@karma-x.io →