Skip to main content
Version: v4

Join an ecosystem

This is the other side of the tree: your corporation applies to issue or verify an ecosystem's credential. The ecosystem (or one of its grantors) validates the application from its Pending Tasks; for an open role the participant exists at once.

Prerequisites​

  • A corporation acting in the frontend, with an operator authorization covering the participant messages. See Create a corporation.
  • The DID of the service that will hold the accreditation: your Verifiable Service's agent, already deployed.
  • The account of that agent, if it will act for the accreditation itself (the VS operator, below).
  • Enough VNA for the validation fees the validator charges, the trust deposit, and the network fee. The wizard shows them before you sign.

Find the ecosystem​

Discover & Join lists every ecosystem on the network with its controller, its active schemas and its figures. Search by name or DID, sort, hide the ecosystems you own or already take part in, and open the governance framework with EGF before you commit. Each schema card shows its onboarding modes and validity periods.

Discover & Join listing an ecosystem with its credential schemaDiscover & Join listing an ecosystem with its credential schemaClick anywhere or press Esc to close

Join opens the wizard for that ecosystem.

The join wizard​

Review the ecosystemReview the ecosystemClick anywhere or press Esc to close

Who controls the ecosystem, its DID and trust state, and its figures. Continue when you are on the right one.

Step 1 of 6

The agent's delegation​

Advanced: VS operator delegation lets your Verifiable Service's agent act for this accreditation without an operator of the corporation in the loop: the VS operator account (the agent's account), the messages it may run for this participant, an optional spend limit per period, and whether the corporation pays the agent's network fees, with a budget. It is frozen at creation: changing it later means revoking the participant and creating it again. Leave it empty if your operators sign for the participant from the frontend.

Use the agent's own account

The VS operator must not be an account that already holds an operator authorization of your corporation; the chain refuses the pair. Give the agent its own account.

Sign​

The confirmation dialog shows the onboarding transaction, the network fee, the validation fees escrowed for the validator and the trust deposit, before the wallet asks you to sign.

The confirmation dialog of an onboarding process startThe confirmation dialog of an onboarding process startClick anywhere or press Esc to close

After you submit​

  • For a role that needs validation, your participant is created with its onboarding process pending approbation. The validator sees it in its Pending Tasks, and its agent and yours run the evidence conversation. See Validate applicants.
  • While it is pending, Cancel Request on your participant card cancels it and returns the escrowed fees.
  • Once validated, the participant is active until its end date. Renew Onboarding Process before the end starts a renewal with the same validator.
  • For an open role, the participant is effective from its start; no validation is needed.
The participant card of an active issuer, seen by its own corporationThe participant card of an active issuer, seen by its own corporationClick anywhere or press Esc to close

Verify​

curl -s 'https://idx.testnet.verana.network/v4/participant/list?schema_id=<schema id>&did=<service did>' | jq '.participants[] | {id, role, op_state, vs_operator, effective_from, effective_until}'

Next​