What changed, and why it matters
This tiny change reassigns numeric values to two internal labels used for Monero's range proof types. Instead of the labels automatically getting consecutive numbers (0, 1), they are now explicitly set to 0 and 3. The commit message says it 'reverts' an earlier change that had assigned them consecutive values. This is likely a backward-compatibility or serialization fix, because stored data or network messages may already expect the value 3 for the newer bulletproof range proof. On its own the patch does not look like an active exploit, but a mismatch in these numeric values could in theory cause two versions of the software to disagree about transaction data, which can be a security concern in a cryptocurrency.
Treat this as a consensus-compatibility fix rather than a vulnerability patch. Review the preceding commit that introduced the consecutive enum values to confirm whether it caused an actual incompatibility, and verify that all serialization paths (binary archive, JSON, wire protocol) now use the restored values consistently. Run integration tests that exercise bulletproof range proofs across mixed node versions.
Security signals we found
Enum value change with potential serialization/consensus implications
Revert of a prior enum numbering change
No explicit security explanation in commit message
Single-line change in a core RingCT type header
Evidence from the diff
The patch modifies the RangeProofType enum in src/ringct/rctTypes.h. Previously the enumerator values were implicitly RangeProofBorromean = 0 and RangeProofPaddedBulletproof = 1. The change explicitly sets RangeProofBorromean = 0 and RangeProofPaddedBulletproof = 3. The commit title frames this as reverting an earlier commit that made the values consecutive. This affects any code that serializes, deserializes, or switches on this enum. If a prior release already used value 3 for RangeProofPaddedBulletproof, the intermediate change to 1 would have created a consensus/serialization incompatibility. The current patch restores the original numbering, presumably to maintain compatibility with existing chain data or wire format.
Changed components
src/ringct/rctTypes.hRangeProofType enumRingCT transaction serialization/deserializationMonero consensus-critical range-proof handlingInspect captured patch +1 / −1
### src/ringct/rctTypes.h
@@ -305,7 +305,7 @@ namespace rct {
RCTTypeCLSAG = 5,
RCTTypeBulletproofPlus = 6,
};
- enum RangeProofType { RangeProofBorromean, RangeProofPaddedBulletproof };
+ enum RangeProofType { RangeProofBorromean = 0, RangeProofPaddedBulletproof = 3};
struct RCTConfig {
RangeProofType range_proof_type;
int bp_version;Why this scored 43/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.