elements-22.0.2

This release includes the following changes:

• Brings Elements up to date with Bitcoin Core version 22.0. To see the Bitcoin 22.0 release notes please click here.
• Multiple improvements to PSET (Partially-Signed Elements Transactions):
  • Updates to the PSET specification (PR #1122).
  • Multiple fixes to the PSET implementation (PR #1121, PR #1145, issue #1065).
  • New parsepsbt RPC for testing (PR #1121).
  • Changes PSET to not blind asset issuances by default (PR #1150).
  • Adds fields for explicit input value and assets, and their proofs. Also adds a flag to indicate whether an issuance should be blinded (PR 1157, PR #1165).
• Multiple fixes/improvements to how dynafed parameters are returned in RPC output (PRs #1108, #1111, #1114, issues #1102, #1109).
• The dumpblindingkey RPC now accepts non-confidential addresses, if there is a corresponding blinding key (PR #1131).
• Fixes a crash in the wallet when handling unusual outputs with blinded assets but unblinded values (PR #1134, issue #1105).
• Fixes a corner case when receiving a block from a peer races with getting the same block from submitblock, wrongly banning the peer (PR #1085, issue #1084).
• Fixes a problem in Windows where Elements would be installed in Bitcoin’s folder instead of its own (PR #869).
  (Note: Since Elements 22.0 will be installed in the right location, cleanup of the left over files in Program Files\Bitcoin may be required.)
• Minor fixes in elements-qt (PR #1146, PR #1154).
• Adds documentation about the format used to serialize Elements transactions (PR #1148).
• The getnewblockhex RPC accepts an array of commitments instead of a single commitment (PR #1155).

Changes since v22.0:

• Avoids clearing out all the blinding data when dropping change (PR #1172).
• Preserves blinding key when parsing taproot address (PR #1184, issue #1181).
• Looks for the default cookie path to connect to the local bitcoind (PR #1173, issue #1120).