Marek

@arya, this PR needs a manual conflict resolution.

Yes, we still have this bug. I got a few of the errors while running an unsynced instance locally: ``` 2024-03-13T13:23:23.783618Z WARN {zebrad="58bfe97" net="Main"}:sync:try_to_sync:try_to_sync_once{extra_hashes={}}: zebrad::components::sync: error downloading and verifying block...

> we might want to replace the panic with an error and proper shutdown. The only problem I see is that we still won't be able to run Zebra with...

I guess we deal with something similar when we enable metrics with the `prometheus` feature, but Prometheus is not available. Zebra can handle that without panicking.

> Zebra can handle that without panicking. Or stopping. I just checked that, and it just continues running.

I don't think so because writing would fail or panic. I added this note to the description: > Note that this is not a security issue since attempting to write...

I, as a random Zebra user, am interested in having this functionality. I could run Zebra at home on a private IP, redirect its traffic through a $5 VPS (which...

I based my estimate on the scope in the description above: > ## Scope > This issue is related to research the necessary steps, infrastructure and artifacts as well as...

Is the scope of this ticket limited to only adding a `v6` enum variant to the `Transaction` enum without adding any further logic?

There's a discussion about the new design in #8271.