Elements

This commit hardens how Elements handles 'peg-in' transactions—transfers of assets from a parent blockchain into a sidechain. It adds size checks for witness data fields and wraps decoding in error handling so malformed inputs are rejected cleanly. It also fixes a place where the code could read past the end of an array when setting up a Partially Signed Transaction (PSBT). The changes are defensive: they prevent crashes or undefined behavior from bad transaction data, but they do not by themselves create new asset theft or remote-code-execution paths.

This commit fixes a crash bug in the Elements blockchain wallet software. When creating a confidential (blinded) transaction, the code could hit an internal 'assert' and abort the program if it tried to generate a rangeproof for a zero-amount output sent to a normal spendable address. The patch turns those hard crashes into ordinary error returns, and adds an explicit early check that rejects zero-value spendable outputs before blinding. It also adds tests proving the boundary between valid and invalid cases. The change is defensive and improves robustness, but it is a partial patch: it does not add the same explicit zero-amount guard to the older BlindTransaction path, only to the newer PSBT blinding path.

This commit removes a single trailing space at the end of a comment line in a Python test file. It is a cosmetic linting cleanup with no functional change to the software and no security relevance.

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 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 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 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 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 is a straightforward build hygiene change. It moves a Simplicity library header include out of a widely-used header file and into the single source file that actually needs it, replacing the direct include with forward declarations. This reduces compile-time dependencies for other parts of the project and makes future build system changes easier. There is no functional change to how transactions or scripts are validated.

This commit fixes a typo in two build helper scripts. The scripts were pointing to an outdated or incorrect Git repository URL for the Guix package manager (https://codeberg.org/guix.git instead of https://codeberg.org/guix/guix.git). This is a routine maintenance fix with no security implications.

This commit fixes a missing validation check in the Elements sidechain. When creating or reissuing custom assets, the code already checked that the main asset amount was within the 21-million-coin money range, but it forgot to perform the same check on the optional 'reissuance token' amount. A user could therefore issue or carry a reissuance token whose nominal supply exceeded the normal limit. The patch adds that missing range check and includes tests showing that nodes with stricter policy now reject such out-of-range reissuance-token issuances from their memory pool.

This commit simply changes the web address from which the Guix build system downloads its own source code during reproducible builds. It switches from the GNU project's Savannah server to Codeberg, a non-profit code hosting platform. There is no security vulnerability or malicious change visible in the diff.

This commit fixes a trivial typo in a documentation file. The phrase 'pops a pops a' was corrected to 'pops a'. There is no code change and no security impact.

This commit moves a network rule about unblinded asset issuances above 21 million units from a global node setting into per-chain parameters. Before the change, the default was to accept unlimited issuances globally. After the change, the default is to reject such issuances unless a chain explicitly opts in. This is a policy/consensus-adjacent change that could affect which transactions nodes accept, but it is not presented as a security fix and does not by itself create a new exploit.

This commit fixes a bug in the Elements sidechain where creating or reissuing more than 21 million units of a non-bitcoin asset was incorrectly rejected when the issuance was unblinded (publicly visible amounts). The change makes the 21-million limit apply only to the network's main pegged asset (like bitcoin), not to other custom assets, and adds a configurable policy switch so node operators can choose whether to relay/mine such large unblinded issuances. Previously, unblinded issuances over 21 million could fail validation even though they are allowed by consensus rules for non-policy assets.