Explain the design rationale and domain concepts behind the Ledger Device Management Kit (DMK) API, including Clear Signing, Secure Channel, Ledger OS (BOLOS), Device Actions vs Commands, sessions, transports, derivation paths, and Genuine Check. Use when a developer asks 'what is X?' about a DMK concept, 'why does X work this way?' about an API design decision, or 'what's the difference between X and Y?' for DMK components.
93
—
Does it follow best practices?
Impact
100%
1.12xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Multi-chain derivation path constants
No m/ prefix - Ethereum
100%
100%
No m/ prefix - other chains
100%
100%
Correct Ethereum path
100%
100%
Correct Bitcoin Native SegWit path
0%
100%
Correct Solana path
100%
100%
Correct Cosmos path
100%
100%
Paths are constants
100%
100%
Silent error explained
70%
100%
No user input for paths
100%
100%
Format rule documented
100%
100%
ETH signer setup with Clear Signing and browser transport
context-module installed
100%
100%
context-module imported/used
0%
100%
checkOnDevice true
100%
100%
originToken optional
100%
100%
originToken upgrade path
100%
100%
Signer kit for signing
100%
100%
Signer kit for address
100%
100%
WebHID Chromium requirement
100%
100%
HTTPS/localhost requirement
100%
100%
User gesture requirement
100%
100%
Device Actions vs Commands selection and session lifecycle
GenuineCheck uses DeviceAction
100%
100%
ListInstalledApps uses DeviceAction
100%
100%
InstallApp uses DeviceAction
100%
100%
Firmware uses sendCommand
80%
100%
No reconnect with old sessionId
66%
100%
Design notes: DeviceAction rationale
100%
100%
Design notes: sendCommand rationale
75%
100%
App name catalog matching
100%
100%
Secure channel internet requirement
100%
100%
Disconnect session handling
90%
100%
c9739bb
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.