Skip to main content
Version: v4

The ecosystem builder's path

An ecosystem is a governance decision before it is a registry entry. This page gives the order of operations and the homework; the guides that follow do each step in the frontend.

Before the frontend​

  • Write the governance framework. Mission, the credentials you govern, who may join in which role and on what evidence, fees, obligations, what gets a participant revoked or slashed, how disputes are handled. The Verana Council publishes templates; the ECS ecosystem's framework is a worked example. Publish it at a stable URL; you will register its digest.
  • Design the schemas. For each credential: the claims as a JSON schema, the onboarding mode per role, validity periods, the pricing asset. Changing a schema later means a new schema, so decide carefully; changing validity periods is allowed.
  • Decide the tree. Will you validate every issuer yourself, or accredit grantors who do it in their region or sector? Will holders have entries (so issuers can revoke) or stay permissionless?
  • Decide the money. Free, or validation fees, or pay per issuance and verification. Priced in the native coin for now in the frontend.

In the frontend, in order​

  1. Create a corporation, then operators and proposals.
  2. Deploy the ecosystem anchor: a VS Agent whose DID will be the ecosystem's DID. Make it a trusted Verifiable Service like any other.
  3. Create the ecosystem with that DID and your governance framework.
  4. Define credential schemas. The anchor publishes their schema credentials automatically.
  5. Create root participants and grantors.
  6. Announce, and validate applicants as they come.
  7. Design the fee model and watch the tree.

Where to look while you build​

The frontend's Ecosystems page lists what your corporation controls; each ecosystem page shows its schemas and participant trees; Pending tasks shows what waits for you. The trust graph shows your ecosystem as the public sees it.