-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Amendments not enabled on networks with network_id greater than 1024 (Version: 2.0.0-b1) #4736
Comments
sophiax851
pushed a commit
to sophiax851/rippled
that referenced
this issue
Jun 12, 2024
The Network ID logic should not be applied to pseudo-transactions. This allows amendments to enable on a network with an ID > 1024. Context: - NetworkID: XRPLF#4370 - Pseudo-transactions: https://xrpl.org/pseudo-transaction-types.html Fix XRPLF#4736 --------- Co-authored-by: RichardAH <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue Description
Enabling amendments on network with network_id upto 1024 works fine, but on network with id greater than 1024, amendments are not enabled. Probably this is because the transaction doing the voting is not including the
NetworkID
which is required if network_id > 1024 and so those transactions are not closed.On networks with network_id <= 1024
On networks with network_id > 1024
Steps to Reproduce
network_id
to a value greater than 1024amendment_majority_time
to 30 mins to accelerate amendment voting[features]
stanza/opt/ripple/bin/rippled --conf /opt/ripple/etc/rippled.cfg feature Checks accept
rippled feature | grep -A5 -B3 Checks
Expected Result
Amendment should be enabled for
Checks
with this responseActual Result
But on network with network_id > 1024, amendment is not enabled after 45 mins too
Command:
rippled feature | grep -A5 -B3 Checks
Environment
Any local network with network_id > 1024
Supporting Files
The text was updated successfully, but these errors were encountered: