Investigate extraction of TACo protocol data

[cygnusv]

On the early days of TDec/TACo, we envisioned the protocol to be structured in such a way that coordination and state was kept separate. To this regard, we wanted coordination to be implemented via smart contracts, and state to be provided by a data availability layer. For complexity reasons, we decided in the end to use Polygon for both, but given current state of things, it may be useful to investigate how to extract protocol state. This is useful for several reasons:

• Protocol optimization:
  • Design/decide client-side transcript retrieval (caching etc.) #70
  • Check for consistency of public key and aggregation transcripts #186
  • Cheaply verify transcript aggregate correctness using trustless (e.g. on-chain) arbiter ferveo#97
• Supporting protocol verifiability:
  • Who cares - and when do they care - about transcript validation? nucypher#3078
  • https://github.com/nucypher/sprints/issues/40
• Protocol state redundancy:
  • We already have external validation that this may be a requirement for some adopters.
• Protocol portability:
  • Implicitly hinted in https://github.com/nucypher/sprints/issues/119

The goal of this issue is to design the process and tooling to:

• Identify all relevant protocol state sources (e.g., Coordinator, TACoChildApplication, Subscriptions, AllowLists, etc)
• Define versionable protocol objects that can be used to represent state
• Extract living protocol state into serializable protocol objects
• Identify potential storage and/or data availability layers that could be used to store protocol objects (e.g. IPFS, DA layers, a TACo sidechain/L2?)