Skip to main content

Update Meta

Update the meta field payload stored within an Ecosystem namespace. Meta stores arbitrary JSON‑formatted metadata string, typically used for high‑level profile tags, display attributes, application‑specific configuration payload. Only the current Ecosystem owner is permitted to execute this instruction.

open-token ecosystem update-meta --help

Synopsis

open-token ecosystem update-meta <Name> <Meta>

Arguments​

ArgumentTypeRequiredDescription
<Name>StringYesTarget Ecosystem namespace name. No dot characters. Must reference an existing non‑expired on‑chain ecosystem account.
<Meta>JSON‑StringYesRaw JSON string payload. Subject to on‑chain program maximum byte‑length limit. Program saves the string as‑is; JSON schema validation is responsibility of off‑chain clients.

Behaviour​

  • Transaction signer must match stored Ecosystem owner public key; returns OwnerMismatch on authorization failure.
  • Validates target ecosystem exists and is not expired (NameExpired).
  • Overwrites the on‑chain meta field with the supplied raw JSON string.
  • Does not touch owner, renter, expiry timestamps, sale‑offer, rent‑offer, body field.
  • Active usership lease (if present) remains completely unaffected; renter usership rights stay intact.
  • On‑chain program does not interpret JSON content; parsing and business logic happen on client side.

Constraints & Validation Rules​

  1. OwnerMismatch: Transaction signer is not the Ecosystem owner.
  2. NameExpired: Ecosystem ownership registration expired; cannot update metadata.
  3. NameTooLong / NameEmpty: Invalid ecosystem name input.
  4. MetaTooLong: Supplied JSON string exceeds program‑defined maximum byte‑length limit.

Note: On‑chain program does not reject malformed JSON. Caller must ensure valid JSON serialization.

Usage Example​

Set ecosystem open meta with shell‑escaped JSON string:

open-token ecosystem update-meta open "{\"name\":\"Open Namespace\",\"tags\":\"public\",\"version\":\"1.0.0\"}"