Cascade internally has three different versions of a zone: an unsigned version, a signed version, and a published version. At the moment, none of these are persisted; upon a restart, Cascade has to fetch an unsigned zone and sign it immediately. This can cause a number of issues; zone loading failure could block Cascade and zones might be resigned unnecessarily.
We need to decide when and how zones get persisted and where necessary implement saving and restoring.
Cascade internally has three different versions of a zone: an unsigned version, a signed version, and a published version. At the moment, none of these are persisted; upon a restart, Cascade has to fetch an unsigned zone and sign it immediately. This can cause a number of issues; zone loading failure could block Cascade and zones might be resigned unnecessarily.
We need to decide when and how zones get persisted and where necessary implement saving and restoring.