Elements

This commit fixes mistakes in the text descriptions and type labels shown by several command-line/RPC commands. Most changes are cosmetic documentation corrections, such as fixing typos, marking fields as optional, and correcting error messages. The only functional change is a small update to the `combineblocksigs` command so its optional `witnessScript` argument behaves as documented for both old-style and dynamic-federation blocks, plus a regression test for that behavior. There is no direct security vulnerability being patched.

This commit adds a code-style linter to the project's continuous integration (CI) pipeline and makes two small supporting changes: it tells the shell linter to ignore a specific quoting warning in build scripts, and it adds a parameter to a test helper function with a note explaining it is used by a currently disabled test. There is no security-relevant code change here.

This commit is a routine cleanup titled 'Fix: linter errors'. It removes trailing whitespace, fixes typos in comments and strings, corrects indentation, removes unused include directives, and deletes a large number of stale test files under test/bitcoin_functional/functional. There is no functional code change that affects how the software behaves or processes untrusted data.

This commit only fixes mistakes in the text documentation and examples shown to users of the software's remote procedure call (RPC) interface. It changes descriptions of data types, corrects command names in examples, fixes a typo in a backtick, and updates help text to match what the code actually does. There are no code behavior changes, so it cannot be exploited or cause security problems on its own.

This commit re-enables a functional test for a feature called 'trim headers' and makes a small wallet change so that anyone-can-spend outputs (OP_TRUE) are recognized as wallet funds on custom Elements chains when a special configuration flag is set. The main purpose appears to be test maintenance, not fixing an active security vulnerability. The wallet change could affect how funds are classified, but only in a specific, non-default configuration.

This commit only updates the text descriptions and type annotations shown in RPC help/man pages. It does not change any executable code, validation logic, wallet behavior, or network handling. The changes make documentation more accurate (for example, correcting field names like 'fee reason' to 'fee_reason', marking optional fields, and adding missing Elements-specific fields), but they cannot be exploited or cause security problems.

This commit changes how several RPC commands detect missing optional arguments. Instead of checking how many arguments were supplied, the code now treats an explicit JSON 'null' as 'not provided.' This lets callers pass null as a placeholder for optional parameters, matching normal Bitcoin/Elements RPC conventions. It is a usability and consistency fix, not a security patch.

This commit changes how Elements' mempool handles transaction replacements. It disables 'full-RBF' (where any transaction can be replaced by a higher-fee version even without signaling) and requires explicit BIP125 opt-in signaling for replacements. It also adds a regression test for CVE-2021-31876, confirming that a transaction cannot be replaced just because one of its unconfirmed parents signaled replaceability. This is a defensive policy change to protect merchants and users who rely on first-seen mempool behavior from unexpected transaction replacements.

This commit corrects a documentation-only error in the help text for the 'decodepsbt' RPC command. The two fields 'inputs_modifiable' and 'outputs_modifiable' were incorrectly listed as numeric (NUM) types when they are actually boolean (BOOL) values. No code behavior changes, so there is no security impact.

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 makes four small fixes in the Elements sidechain codebase. Two changes remove incorrect assumptions in block-signature size checks. One tightens the peg-in witness format check from 'at least 5 items' to 'exactly 6 items'. One adds explicit-type checks before counting burned pegged-asset outputs as a subsidy. And one prevents a wallet RPC call from crashing when asked to blind a transaction that has no outputs. The changes look like routine bug fixes rather than a single coordinated security patch, and no exploit is directly demonstrated.

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 only updates the text shown by the help command for several RPC (remote procedure call) interfaces. It corrects descriptions, marks some fields as optional, and documents newer parameters such as asset labels, peg-in inputs, and blinded transaction fields. There are no code logic changes that affect how the software processes commands or secures funds.

This commit simply renames the project's unit-test executable from 'test_bitcoin' to 'test_elements' across build scripts, CI, coverage tooling, and documentation. It is a branding/consistency change with no effect on the software users run or on security.

This commit is a documentation-only cleanup of the built-in help text for many RPC (remote procedure call) commands in the Elements node software. It corrects typos, marks fields as optional where they are not always returned, adds missing fields that the code already returns, and updates examples. There are no code logic changes, no bug fixes in executable behavior, and no security-relevant changes.

This commit fixes the Windows/MinGW build process for the Elements project. It renames leftover 'bitcoin' installer filenames to 'elements', corrects a path used by the installer graphics, and adjusts which internal libraries are linked and in what order so the software compiles successfully on Windows. There is no indication this changes runtime behavior or fixes a security vulnerability.

This commit is a work-in-progress patch to the project's continuous-integration (CI) build scripts and one CMake build file. It swaps some shell equality tests from '==' to '=', changes a conditional to a case statement, switches the CI build from autotools to CMake for certain configurations, adds macOS-only compiler warning suppressions, and changes how wallet-tool binaries are linked. None of these changes are security fixes for shipped product code; they are build-system and CI maintenance changes.

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 adds a single log message that records whether a network feature called ELIP 203 is active when the node starts. It does not change any rules, permissions, or behavior; it only prints a status line for operators to read.

This commit only changes wording in user-facing messages and comments, replacing 'pegin' with 'peg-in' for grammar consistency. It does not alter any code logic, network behavior, or security checks.

This commit adds a new 'pegin subsidy' feature to the Elements sidechain. When users move small amounts of Bitcoin into the sidechain (a 'pegin'), the sidechain now sometimes adds an extra output that pays the network operators (the functionaries) a fee to cover the cost of later moving those coins back to Bitcoin. The change also adds a helper that reads how many signatures a federation script requires, and exposes new information in several RPC commands. There is no explicit security bug in the diff, but the new subsidy logic touches consensus-relevant money flows and relies on external fee data, so it deserves careful review.

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.