Blockstream Jade

This commit is a straightforward code cleanup: it moves several on-screen confirmation function declarations from individual source files into a shared header file. There is no change to what the code actually does, no bug fix, and no security-related behavior change.

This commit is a straightforward code cleanup: it moves type and function declarations that were scattered across several files into a single new header file called sign_utils.h. There is no change to what the code actually does, only to how the source files are organized. It does not fix or introduce any security issue.

This commit simply moves an existing Bitcoin transaction fee confirmation function from one source file to another. The code logic is copied verbatim with no functional changes, so it does not fix, introduce, or change any security behavior.

This commit simply renames a local variable from `liquid_fees` to `explicit_fee` inside the transaction-signing code. The change is purely cosmetic and does not alter any logic, calculations, or security behavior. It is described by the author as making the code consistent with PSBT signing code elsewhere.

This commit refactors how the Blockstream Jade hardware wallet checks transaction fees when signing a PSBT. Previously, the fee was calculated and validated inside the PSBT-specific code. Now it uses a shared validation routine that is also used for regular transaction signing. The goal is consistency: the same duplicate-fee and fee-validation checks apply regardless of whether the user is signing a raw transaction or a PSBT. The commit removes several local fee checks (such as rejecting blinded fee outputs or unexpected fee asset IDs) and relies on the shared function instead. This is a code-quality and consistency improvement, not a clear-cut security fix, but it touches security-critical fee logic.

This commit is a simple code cleanup: it renames several internal helper functions from names starting with 'rpc_get_' to names starting with 'params_' so they match the naming style used elsewhere in the project. It also makes two helpers 'static' (private to their file) and fixes a typo in a comment. There is no change to behavior, no bug fix, and no security impact.

This commit reorganizes how Blockstream Jade validates transaction data before signing. It moves several Liquid-network checks earlier in the process and adds new rules: a transaction output with no recipient script (typically a network fee) must now be unblinded, non-zero, use the network's official policy asset, and there can only be one such fee output. The change also prevents a transaction from being silently treated as a different network type (Bitcoin vs. Liquid). These are defensive hardening measures rather than a fix for a confirmed active attack.

This commit changes the Blockstream Jade hardware wallet firmware so it can now sign Liquid/Elements PSET transactions instead of rejecting them. It also adds a check that the PSBT type matches the selected network (Bitcoin vs. Liquid). A new FIXME comment asks whether Bitcoin signing should only accept 'non-witness utxo' data, and descriptor-based wallet signing is disabled for Elements. The change is a feature addition with some defensive tightening, not a clear vulnerability fix, but it touches security-critical signing code.

This commit enables the Jade hardware wallet to sign Liquid network transactions using the existing sign_psbt command. Previously, this command was rejected for Liquid. The change mainly removes that rejection, skips Bitcoin-only fee math on Liquid, and updates test fixtures. It is a feature-enablement patch rather than a clear security fix, and the commit message says full tests will follow later.

This commit adds user confirmation screens for Liquid (Elements) transactions in the Blockstream Jade hardware wallet. Previously, Liquid PSBT signing likely did not show the user the outputs and fee before signing, or used Bitcoin-only confirmation logic that did not properly handle Liquid assets. The change makes the device ask the user to confirm what is being spent and what fee is being paid before producing a signature. This is a security-hardening improvement rather than an obvious vulnerability fix, but the absence of such confirmation could have allowed malicious software to trick a user into signing an unwanted Liquid transaction.

This commit changes how the Blockstream Jade hardware wallet examines transaction outputs before signing a Liquid (Elements-based) PSBT. It now inspects outputs for confidential/unblinded asset and value data, detects scriptless fee outputs, validates that fee outputs use the correct policy asset, and rejects blinded fee outputs. Previously, the code only tried to identify 'change' outputs on Bitcoin-like transactions. The change appears to be a security hardening/fix for Liquid transactions, but the commit message does not explicitly call it a security fix.

This commit changes how Blockstream Jade hardware wallets parse PSET (a variant of Bitcoin's PSBT format used on the Liquid sidechain). Previously, parsing PSET data could crash the device because verifying confidential transaction proofs needs about 54 KB of temporary memory—more than the normal task stack provides. The fix runs PSET parsing in a temporary task with a larger 54 KB stack, while ordinary PSBT parsing stays unchanged. The commit also adds explicit recognition of the PSET magic bytes, whereas before Jade only checked for PSBT magic bytes and noted that PSET was not yet supported.