[#931] Kill support for TORUs, minimal sr1 address support, tz4 address support
I contemplated making a separate MR for each of these, but all of them touch the same code, so merging after the fact would end up being quite annoying.
Morley reference tests may occasionally fail in ticketer-2.tz
here, this is fixed in !1331 (merged).
Description
Problem: TORUs will be forbidden on the mainnet since Mumbai, and never gained traction during their short lifespan.
Solution: We could properly deprecate them, but the amount of work
required to do that doesn't seem justified. Thus, completely remove
support for TORUs. tx_rollup_l2_address
is still recognized by the
parser and the deserializer, but both report an error when they see it.
Same for txr1
addresses, parsers report errors when they see them.
Problem: Mumbai adds a new type of address, sr1
.
Solution: Add minimal support.
Problem: tz4 addresses are now on mainnet starting with Mumbai, using BLS12-381 cryptography.
Solution: Add support.
There are a few caveats with these:
- they can't be used as delegates
- operation signatures, unlike other signature types, are tagged
+ minor chores.
Related issue(s)
Resolves #931 (closed), #930 (closed), #927 (closed)
✅ Checklist for your Merge Request
Related changes (conditional)
-
Tests (see short guidelines)
-
If I added new functionality, I added tests covering it. -
If I fixed a bug, I added a regression test to prevent the bug from silently reappearing again.
-
-
Documentation
Stylistic guide (mandatory)
-
My commits comply with the following policy. -
My code complies with the style guide.