ACADEMY / From zero to privacy in Bitcoin.
P26 · Desk and Cuvex

Verify a policy and receive confirmation

Preparation: Give everyone the same complete policy. Use the correct firmware profile and a device without competing operations.

  1. Start Verify Policies in the supported context. Original requires explicit selection of the installed profile. BIT negotiates capabilities under its specification.
  2. Deliver the request by NFC/Mirror or USB-C according to the model.
  3. Review the policy fields on the device. You may use Mirror to compare selected pairs in any order.
  4. Complete device confirmation and return the response through the appropriate transport.
  5. In Desk, validate the response for this request. A visual OK from the comparator cannot replace that step.

Result: The response is correlated and applies to this review. The catalog does not remotely attest firmware, and the device is not presented as a persistent policy store. On FIRMWARE_CAPABILITY_REQUIRED, first check the Desk version and model/build combination.