Control Planes

What is a control plane?

Control Planes are a primary way for consumers to interact with a LearnCard. A Control Plane provides an abstraction for a higher-order wallet object to initiate complex workflows while being agnostic to the means of accomplishing the workflow.

Control Planes:

  • Align plugins based on primary action categories: Identity, Signing, Verification, Storage, Caching, and Communication.

  • Specify interfaces for conforming plugins to implement.

  • Provide execution environments that support more complex workflows.

  • Allows for utilizing multiple plugins to support a particular request.

  • Streamline functionality for high-quality UX requirements, such as caching and querying capabilities.

  • Incentivizes plugin convergence, rather than divergence.

  • Enables plugin discovery, both internal and external.

For Example: when a user stores a credential, they may have a preference over where the credential is stored. Leveraging Controls Planes, a consumer of LearnCard may query for available storage options (IPFS, LocalStorage, DWN, Device Storage, etc.), ask the user which option they would like to use, and then initiate the storage workflow for the user's selection from a generic store function.

To help better understand what Control Planes are, it may be easiest for you to take a look at the available Control Planes within LearnCard:


You may have noticed, but not all Control Planes have been released yet! We are hard at work implementing the remaining Control Planes on our roadmap 🛠

Last updated