Skip to main content

cluster-anchoring

Usage: pmc cluster-anchoring [OPTIONS] COMMAND [ARGS]...

  Interactions with cluster anchoring chain configuration

╭─ Options ───────────────────────────────────────────────────────────────────╮
│  -h, --help  Show this message and exit                                     │
╰─────────────────────────────────────────────────────────────────────────────╯
╭─ Commands ──────────────────────────────────────────────────────────────────╮
│  update  Propose new cluster anchoring configuration                        │
│  get     Get cluster anchoring configuration                                │
╰─────────────────────────────────────────────────────────────────────────────╯

The blockchain command (pmc cluster-anchoring) consists of sub-commands to interact with Cluster Anchoring Chain configuration.

cluster-anchoring update​

Usage: pmc cluster-anchoring update [OPTIONS]

  Propose new cluster anchoring configuration

╭─ Configuration Properties ──────────────────────────────────────────────────╮
│  -cfg, --config=CONFIG    Alternate path for client configuration file      │
│  -s, --settings=SETTINGS  Alternate path for project settings file          │
│  --lookup-brid            Ignore any 'brid' property in configuration file, │
│                           always perform lookup                             │
│  --lookup-nodes / --no-lookup-nodes                                         │
│                           Lookup system cluster signer nodes for sending    │
│                           transactions to (default: yes)                    │
│  --network=TEXT           Target network to make requests to (if chromia.yml│
│                           is configured)                                    │
│  --secret=PATH            Path to secret file (pubkey/privkey)              │
│  --key-id=KEY_ID          Key ID of the keypair to use                      │
╰─────────────────────────────────────────────────────────────────────────────╯
╭─ Options ───────────────────────────────────────────────────────────────────╮
│* -ac, --anchoring-config=PATH  Configuration file for cluster anchoring     │
│                                chain (GtvML (*.xml) or Gtv (*.gtv))         │
│  -h, --help                    Show this message and exit                   │
╰─────────────────────────────────────────────────────────────────────────────╯

The update command (pmc cluster-anchoring update) proposes a new cluster anchoring configuration.

cluster-anchoring get​

Usage: pmc cluster-anchoring get [OPTIONS]

  Get cluster anchoring configuration

╭─ Configuration Properties ──────────────────────────────────────────────────╮
│  -cfg, --config=CONFIG    Alternate path for client configuration file      │
│  -s, --settings=SETTINGS  Alternate path for project settings file          │
│  --lookup-brid            Ignore any 'brid' property in configuration file, │
│                           always perform lookup                             │
│  --lookup-nodes / --no-lookup-nodes                                         │
│                           Lookup system cluster signer nodes for sending    │
│                           transactions to (default: yes)                    │
│  --network=TEXT           Target network to make requests to (if chromia.yml│
│                           is configured)                                    │
╰─────────────────────────────────────────────────────────────────────────────╯
╭─ Options ───────────────────────────────────────────────────────────────────╮
│  --save=PATH  where to save configuration, format will be determined by file│
│               extension: .xml or .gtv                                       │
│  -h, --help   Show this message and exit                                    │
╰─────────────────────────────────────────────────────────────────────────────╯

The get command (pmc cluster-anchoring get) receives the anchoring configuration of a given cluster. The configuration can be saved to a desired path.