Not sure why the python constant is named differently than the constant in the C++ source code.
Especially, if we use this in context of MAX+1 (https://github.com/bitcoin/bitcoin/pull/25575#discussion_r918569813) the rename makes sense, in my eyes.
Not sure why the python constant is named differently than the constant in the C++ source code.
Especially, if we use this in context of MAX+1 (https://github.com/bitcoin/bitcoin/pull/25575#discussion_r918569813) the rename makes sense, in my eyes.
Concept ACK
Note that the test rpc_psbt.py
actually also defines MAX_BIP125_RBF_SEQUENCE
, i.e. I’d propose the following additional patch after the scripted-diff:
0diff --git a/test/functional/rpc_psbt.py b/test/functional/rpc_psbt.py
1index d2a888fd3..264b2ac32 100755
2--- a/test/functional/rpc_psbt.py
3+++ b/test/functional/rpc_psbt.py
4@@ -11,8 +11,9 @@ from itertools import product
5 from test_framework.descriptors import descsum_create
6 from test_framework.key import ECKey, H_POINT
7 from test_framework.messages import (
8- ser_compact_size,
9+ MAX_BIP125_RBF_SEQUENCE,
10 WITNESS_SCALE_FACTOR,
11+ ser_compact_size,
12 )
13 from test_framework.test_framework import BitcoinTestFramework
14 from test_framework.util import (
15@@ -27,7 +28,6 @@ from test_framework.wallet_util import bytes_to_wif
16 import json
17 import os
18
19-MAX_BIP125_RBF_SEQUENCE = 0xfffffffd
20
21 # Create one-input, one-output, no-fee transaction:
22 class PSBTTest(BitcoinTestFramework):
-BEGIN VERIFY SCRIPT-
sed -i 's:BIP125_SEQUENCE_NUMBER:MAX_BIP125_RBF_SEQUENCE:g' $(git grep -l BIP125_SEQUENCE_NUMBER ./test)
-END VERIFY SCRIPT-
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
Reviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.