You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 NetworkIDwhich is required if network_id > 1024 and so those transactions are not closed.
network_id: 1030 => 3:04pm-4:50pm - amendments not enabled
network_id: 1234 => waited more than 12 hrs wait - amendments not enabled
Steps to Reproduce
Update rippled.cfg with network_id to a value greater than 1024
[network_id]
1030
Set amendment_majority_time to 30 mins to accelerate amendment voting
[amendment_majority_time]
30 minutes
Make sure to remove [features] stanza
Bring up a private network (2 validators are enough to reproduce this issue)
Once the network is up, vote to enable an amendment (for example: Checks) /opt/ripple/bin/rippled --conf /opt/ripple/etc/rippled.cfg feature Checks accept
Wait for 30-45 mins (for the next flag ledger to cross)
Verify with command: rippled feature | grep -A5 -B3 Checks
Expected Result
Amendment should be enabled for Checks with this response
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.htmlFixXRPLF#4736
---------
Co-authored-by: RichardAH <richard.holland@starstone.co.nz>
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: