Elements

This commit corrects the help text for the decodepsbt RPC command. It changes the documented return type from an array of input indexes to a simple true/false flag, matching what the code actually returns. There is no code behavior change and no security impact.

This commit updates the embedded secp256k1-zkp cryptographic library inside the Elements project to the latest master from BlockstreamResearch. It is a large, routine dependency refresh touching build scripts, CI configuration, and many source files. The commit itself does not describe any specific security bug fix, and the visible changes are mostly build/CI modernization plus upstream synchronization. Because it is a wholesale submodule-style update, it could silently include upstream security fixes, but the provided diff does not identify any particular vulnerability or CVE.

This commit is a large maintenance patch for the Elements blockchain project. It mainly fixes build and test problems introduced by a recent upstream Bitcoin merge: compiler warnings became errors, fuzz tests used the wrong transaction format, Windows/MSVC builds failed, and some functional tests assumed too much disk space. The only directly user-visible runtime change is replacing a risky fixed-size on-stack array in transaction blinding code with a heap-allocated vector, which removes a potential stack-overflow/crash path when handling very large transactions. Most other changes are build-system, CI, or test-only adjustments.

This commit is a massive merge of upstream Bitcoin Core changes into the Elements repository. It adds or replaces thousands of files covering the build system, CI configuration, documentation, tests, and source code. There is no specific security fix or vulnerability patch visible in the supplied materials; it appears to be a routine upstream synchronization.

This commit fixes a mismatch in how a Merkle block proof is unpacked inside a 'pegin' (a transaction that moves coins from a parent blockchain into this Elements sidechain). The proof was being read as if it might contain witness data, but it is always written without witness data. This mismatch could cause the proof to fail to decode in some situations, which could break peg-in validation or processing.

This is a large subtree update that imports a newer version of the Simplicity library into the Elements project. The visible changes add Bitcoin-specific jets (pre-built functions), transaction environment handling, and build files. There is no direct evidence in the commit message or diff that this fixes a known security vulnerability; it reads as a feature and maintenance update. However, any change to cryptographic/transaction code deserves careful review because bugs here could affect how transaction scripts are validated.

This commit only adds a new documentation file explaining how developers can update the Simplicity C code subtree in the Elements repository. It contains no code changes, no configuration changes, and no executable logic. There is no security-relevant change to the software itself.

This commit changes a single line in the project's Windows CI configuration. It pins the version of 'jom'—a build tool used during automated Windows builds—to a specific release (1.1.2) instead of always downloading the latest version. There is no direct evidence in the commit or supplied references that this fixes a security vulnerability. It appears to be a build reliability or reproducibility change.

This commit simply adds a new GPG public key file used to verify official release signatures. It is a routine trust/key-management addition with no code changes and no direct security vulnerability.