Starting a test parallel network with amendments pre enabled

• With ledger_entry, you can see which amendments are active, and which currently have majority (Majorities).
• One obvious symptom of expected amendments not being enabled is if new accounts are given a starting sequence number of 1.
  • With the DeletableAccounts amendment, new accounts should start with a sequence number equal to the current ledger sequence number.
• When resetting a network (i.e. clearing the ledger state), use --start to make sure amendments are enabled from the start.
  • This is preferable to using the standard 2-week waiting period, which is a long delay.
  • #4386 New genesis ledgers should always start with amendments enabled
• If it is a test network that the community is aware of, it is best to communicate on Discord both before and after the reset.

rippled --start --net --silent --conf /etc/opt/ripple/rippled.cfg

# Run rippled in foreground:
rippled --start --net --conf /etc/opt/ripple/rippled.cfg

# Stop rippled in foreground, make sure the rippled process is killed. Then start with systemd

• Once the network is going, restarting rippled without --start should be fine.
• Running it with -a could get the amendments enabled from the start. But just using --start should be enough.

Background context on Amendments

In the rippled.cfg config file, the [amendments] stanza was introduced for servers to list the amendments they want to support. Originally (2015-2016), this meant you are "voting" for it. Amendments are requests/instructions to enable features. Amendments are a way to coordinate when features enable (so that all nodes enable a feature at the same time), but on the other hand, the [features] stanza does not impact amendments; instead, it forces (or assumes) certain features to be enabled.