elements-23.2.1

This release includes the following changes:

• Brings Elements up to date with Bitcoin Core version 23.2. To see the Bitcoin 23.2 release notes please click here.
• Adds support for arm64 macos native builds.
• Fixes a problem in the getnewaddress rpc: getnewaddress will now return an unblinded bech32 address even when -blindedaddresses=1 in config (PR #1246, issue #1245).
• In contrast to Bitcoin, Elements is not changing the default wallet format from legacy to descriptors, this is because many things (like peg-ins and peg-outs) still work only on legacy wallets.

elements-22.1.1

What's Changed

• Improve elements memory usage by @gwillen in #1190
• Correct help for getsidechaininfo RPC by @philippem in #1203
• Obscure mainchain rpc fields in the logs, just like the local ones by @psgreco in #1206
• Allow deploying regtest networks with p2wsh peg-ins by @psgreco in #1209
• Improvements to pr review script by @gwillen in #1118
• Fix underflow when blocks are ahead of headers by @psgreco in #1212
• Fix linter (trailing whitespace) by @psgreco in #1214
• Correct testproposedblock help by @jhfrontz in #1216
• Elements-qt: Avoid mixing assets when using all the available balance by @andreabonel in #1222
• Elements-qt: Use available balance from the currently selected asset by @andreabonel in #1223
• RPC: Avoid assert by keeping a flag to identify trimmed dynafed blocks by @psgreco in #1225

Full Changelog: elements-22.1...elements-22.1.1

N.B.: With this release, we added a signed version of the osx dmg, this hash is not reproducible.

Elements 22.1

This release includes the following changes:

• Brings Elements up to date with Bitcoin Core version 22.1. To see the Bitcoin 22.1 release notes please click here.
• rpc: decodepsbt: fix check for blind_reissuance_amount_proof output by @jgriffiths in #1182
• fix pset swap example by @wintercooled in #1192
• Add include_explicit to walletcreatefundedpsbt by @achow101 in #1186
• Add native support for liquidtestnet by @psgreco in #1167
• Add missing field 'signblock_challenge' back to getblock by @andreabonel in #1194
• Have testproposedblock return RPC_VERIFY_ALREADY_IN_CHAIN by @stevenroose in #928

Full Changelog: elements-22.0.2...elements-22.1

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).

elements-0.21.0.3

What's Changed

• Fix elements naming in gitian builds in #1128
• backport to 0.21: change getnewblockhex to take multiple commitments in #1183

Full Changelog: elements-0.21.0.2...elements-0.21.0.3

Elements v0.21.0.2

Changelog:

• raise max P2P message size to account for larger elements dynafed headers
• remove block from in-flight list when a duplicate is received through RPC

elements-0.21.0.1

Changelog:

• fix for header sync performance
• fix for createrawtransaction RPC: make pegin-related fields optional
• add evbparams to manipulate BIP9 deployments, similar to Bitcoin Core's vbparams
• make dynafed signalling opt-out instead of opt-in
• improve logging

Elements 0.21.0

Changelog:

• Bring Elements up to date with Bitcoin Core 0.21
• Design and implement new PSET protocol

elements-0.18.1.12

Changelog:

• Support supplying contract hash to issueasset RPC
• Fix description of -chain parameter
• Add liquidv1test chainparams
• Add logging for dynafed activation and transitions
• Undo default signalling behavior for dynafed unless enabled

elements-0.18.1.11

Changelog for v0.18.1.11:

• Specify the dynafed epoch length for liquidv1.

Changelog for v0.18.1.10

• Add SIGHASH_RANGEPROOF support
• Add two missing dynafed fields to getblockchaininfo
• Support changing mainnet dynafed activation
• Only verify proposed dynafed parameters if they differ from current