We were investigating the switch from signet to regtest in the test
environment, and I misidentified the solution as being an ordering, or
numbering issue in the enum. Turns out we were using an altogether
different enum in the first place, and that was causing the
issue. Nevertheless, lining these up the same way should prevent
accidental breakage if we end up using the numeric encoding somewhere.
We were investigating the switch from signet to regtest in the test environment, and I misidentified the solution as being an ordering, or numbering issue in the
enum. Turns out we were using an altogether different enum in the first place, and that was causing the issue. Nevertheless, lining these up the same way should prevent accidental breakage if we end up using the numeric encoding somewhere.Fixes #434