Skip to main content
Version: v4 (next)

Update an Ecosystem

MOD-ES-MSG-2

Post a message that rotates an Ecosystem's DID. In spec v4 this is the only field update-ecosystem changes.

Prerequisites

This is a delegable transaction executed on behalf of a Corporation. Before running it you need:

  1. A Corporation (policy_address) that controls the ecosystem — see Create a Corporation.
  2. The policy funded with uvna for fees.
  3. An operator granted authorization for /verana.ec.v1.MsgUpdateEcosystem via Grant Operator Authorization.

Sign with --from <operator> and pass the corporation's policy_address as the [corporation] argument.

Message Parameters

NameDescriptionMandatory
corporationpolicy_address of the Corporation that controls the ecosystemyes
idID of the ecosystem to updateyes
didNew Decentralized Identifier (DID) — must follow DID-CORE syntaxyes
info

The ecosystem must be controlled by the signing corporation (ecosystem.corporation_id must match). Rotating the DID to a value already held by an ecosystem controlled by a different Corporation is forbidden (MOD-ES-MSG-2-2-1).

Post the Message

Usage

veranad tx ec update-ecosystem [corporation] [id] [did] \
--from <operator> --chain-id <chain-id> --keyring-backend test --fees <amount> --gas auto --node $NODE_RPC

Example

veranad tx ec update-ecosystem $CORPORATION 1 did:example:18c0de8b382b27289488be5aaabae72e \
--from $OPERATOR --chain-id $CHAIN_ID --keyring-backend test --fees 750000uvna --gas auto --node $NODE_RPC

Example response

code: 0
events:
- type: message
attributes:
- key: action
value: /verana.ec.v1.MsgUpdateEcosystem
- key: module
value: ec
- type: update_ecosystem
attributes:
- key: ecosystem_id
value: "1"
- key: corporation_id
value: "2"
- key: did
value: did:example:18c0de8b382b27289488be5aaabae72e
gas_used: "67973"
txhash: 2E38D26BDA0527FDAEB53649CC14934EE13D90A5E8DFFF294F52821680460B8E