[Task] Provide on-chain availability for revocation, schemas and trust-list etc.

[eike-hass]

Description

Figure out on-chain availability for use-case that need storage exceeding what a single output can store (likely in the <100kb range)

Motivation

On-chain availability for commonly used data like credential revocation information, credential (or other) schemas or list of trusted entities profit from DLT capabilities like high-availability, guarantee of latest state, auditability and advanced enforced access control (e.g. multi-sig).
On the other hand ledger space is precious, so we have to be sure we really want to occupy the ledger with this kind of information and evaluate if our current control mechanism (storage deposit) is sufficient.

Additionally we need to align our needs with other efforts like DPP or Tokenization data and design a common scheme for referencing and storing or anchoring data on-chain.

Resources

Internal design document: https://docs.google.com/document/d/149GurmiyJG3fREWLJffyUHszyZI8bJeldWIcRJaB2M8

To-do list

• Arrive at a common design with other teams/initiatives
• Figure out where (in which repository/project) to implement the solution
• Deliver the solution

Change checklist

Add an x to the boxes that are relevant to your changes, and delete any items that are not.

• The feature or fix is implemented in Rust and across all bindings whereas possible.
• The feature or fix has sufficient testing coverage
• All tests and examples build and run locally as expected
• Every piece of code has been document according to the documentation guidelines.
• If conceptual documentation (mdbook) and examples highlighting the feature exist, they are properly updated.
• If the feature is not currently documented, a documentation task Issue has been opened to address this.