While adding new storage is straightforward, the event log can appear in multiple locations naturally. Abandoning a storage (e.g., migration elsewhere) is not elaborated in the spec.
Should an intentionally abandoned event log include a final event removing it from storage endpoints to signal no further updates? In that case, resolvers/verifiers would use the last defined list of endpoints to find the current version ...
While adding new storage is straightforward, the event log can appear in multiple locations naturally. Abandoning a storage (e.g., migration elsewhere) is not elaborated in the spec.
Should an intentionally abandoned event log include a final event removing it from storage endpoints to signal no further updates? In that case, resolvers/verifiers would use the last defined list of endpoints to find the current version ...