Create Ecosystem
Create an Ecosystem namespace.
Ecosystem represents the root protocol / namespace layer of the open:// identifier scheme.
All entities resolve under a given Ecosystem.
open-token ecosystem create --help
Synopsis
open-token ecosystem create <Name> <Meta> <Body> <Years>
Arguments
| Argument | Type | Required | Description |
|---|---|---|---|
<Name> | String | Yes | Ecosystem namespace name. This is the root identifier for the protocol namespace. No forward‑slash or dot separators inside ecosystem name. Serves as the root for all child entities. |
<Meta> | String | Yes | Arbitrary metadata JSON string. Stores namespace‑level profile data: namespace description, governance config, avatar, social links, display preferences. Must be single‑line compact JSON. |
<Body> | String | Yes | Arbitrary body content JSON string. Stores namespace‑level resolution and protocol configuration: default routing rules, fallback records, protocol parameters. Must be single‑line compact JSON. |
<Years> | u8 | Yes | Registration duration in full years. Determines Ecosystem namespace expiry timestamp. Subject to on‑chain program minimum value constraint. |
Behaviour
- Creates on‑chain PDA account for the Ecosystem namespace.
- Transaction signer becomes the initial Ecosystem owner.
- Expiry timestamp computed from Openverse
Clock::get().unix_timestamp + years * 365 * 86400. - Validates name character set, byte‑length limits and global uniqueness.
- Raw
Meta/BodyJSON strings are stored on‑chain; deserialization is performed inside the Openverse program. - Deducts Ecosystem registration fee according to on‑chain treasury configuration.
- When Ecosystem expires, all entities under this namespace become logically invalid for resolution, even if individual entity accounts remain active.