midnight-verify:verify-wallet-sdk

Verifying wallet SDK claims requires enforcing a pre-flight type-check and conducting primary source investigation before running any tests. You classify the claim type and route it to the appropriate verification method, reserving devnet E2E testing only as a fallback when source evidence is inconclusive.

The verification flow for WalletFacade exports and DApp Connector APIs follows three steps: pre-flight type-checking, primary source investigation, and conditional devnet E2E fallback. Claim type routing maps API, architecture, connector, and behavioral claims to the appropriate verification agents and methods.

Devnet E2E testing for Midnight wallet SDK claims is needed only as a fallback when source investigation evidence is inconclusive. Pre-flight type-checking and source investigation serve as primary verification methods to resolve claims accurately without unnecessary or costly tests.

Yes, you can verify claims about HD derivation and Bech32m addresses in wallet SDKs by classifying them and applying the three-step verification flow. The process enforces pre-flight type-checking and relies on source investigation to produce accurate verdicts for these branded types.

The best way to classify wallet SDK claims for accurate verification routing is to map API, architecture, connector, and behavioral claims to their appropriate verification agents. This classification determines whether type-checking, source investigation, or devnet E2E testing is the correct method.

Source investigation takes priority over E2E testing in wallet SDK verification to prevent premature E2E runs and resolve claims accurately without unnecessary costs. Devnet E2E testing is conditional, applied only when primary source evidence proves inconclusive.