@thepowereco/cli NPM

@thepowereco/cli

the power cli

Usage

$ npm install -g @thepowereco/cli
$ tpe COMMAND
running command...
$ tpe (--version)
@thepowereco/cli/1.12.19 linux-x64 node-v18.20.5
$ tpe --help [COMMAND]
USAGE
  $ tpe COMMAND
...

Commands

`tpe acc get-balance`

Get the balance of a wallet address

USAGE
  $ tpe acc get-balance [-a <value> | -k <value>] [-c <value>] [-b <value>] [-p <value>] [-e]

FLAGS
  -a, --address=<value>         Wallet address
  -b, --bootstrapChain=<value>  [default: 1025] Bootstrap chain ID
  -c, --chain=<value>           Chain ID
  -e, --isEth                   Use an ethereum address
  -k, --keyFilePath=<value>     Path to the key file
  -p, --password=<value>        Password for the key file (env: KEY_FILE_PASSWORD)

DESCRIPTION
  Get the balance of a wallet address

EXAMPLES
  $ tpe acc get-balance --address AA100000001677748249

  $ tpe acc get-balance -a AA100000001677748249

  $ tpe acc get-balance --address AA100000001677748249 --bootstrapChain 1025

  $ tpe acc get-balance --keyFilePath ./path/to/keyfile.pem --password mypassword

See code: dist/esm/src/commands/acc/get-balance.js

`tpe acc register`

USAGE
  $ tpe acc register [-c <value> | -n devnet|testnet|appchain] [-f <value> | -x] [-h <value>] [-p <value>] [-r
    <value>] [-s <value>] [-e] [-d <value>]

FLAGS
  -c, --chain=<value>     Specify the chain
  -d, --hdPath=<value>    [default: m/44'/60'/0'] HD path for the account
  -e, --isEth             Register an Ethereum account
  -f, --filePath=<value>  Path to save the exported file
  -h, --hint=<value>      Hint for the account password
  -n, --network=<option>  Specify the network
                          <options: devnet|testnet|appchain>
  -p, --password=<value>  Password for the account
  -r, --referrer=<value>  Referrer for the account
  -s, --seed=<value>      Seed for the account
  -x, --noSave            Do not save the exported file

DESCRIPTION
  Register a new account on the specified blockchain or network

EXAMPLES
  $ tpe acc register --chain 1 --password mypassword --filePath /path/to/save
  Register a new account on a specified chain with a password and save the data to a specified file path.

  $ tpe acc register --network devnet --referrer myreferrer
  Register a new account on the devnet network with a specified referrer.

  $ tpe acc register
  Interactively register a new account by selecting the network and chain.

  $ tpe acc register --chain 1 --no-save
  Register a new account on a specified chain without saving the data to a file.

See code: dist/esm/src/commands/acc/register.js

`tpe acc send-sk`

Send SK tokens to a specified address

USAGE
  $ tpe acc send-sk -a <value> -k <value> -t <value> [-b <value>] [-m <value>] [-p <value>] [-e <value>] [-d
    <value>] [-g <value>] [-v <value>] [-c <value>] [-h]

FLAGS
  -a, --amount=<value>          (required) Amount to send
  -b, --bootstrapChain=<value>  [default: 1025] Default chain ID
  -c, --chain=<value>           Chain ID
  -d, --decimals=<value>        [default: 9] Decimals of the token
  -e, --token=<value>           [default: SK] Token to send
  -g, --gasToken=<value>        Token used to pay for gas
  -h, --isEth                   Use an ethereum address
  -k, --keyFilePath=<value>     (required) Path to the key file
  -m, --message=<value>         Message to include
  -p, --password=<value>        Password for the key file (env: KEY_FILE_PASSWORD)
  -t, --to=<value>              (required) Recipient address
  -v, --gasValue=<value>        Gas value for deployment

DESCRIPTION
  Send SK tokens to a specified address

EXAMPLES
  $ tpe acc send-sk --amount 100 --to AA100000001677748249 --keyFilePath ./path/to/keyfile.pem --password mypassword

  $ tpe acc send-sk -a 100 -t AA100000001677748249 -k ./path/to/keyfile.pem -p mypassword

  $ tpe acc send-sk --amount 100 --to AA100000001677748249 --keyFilePath ./path/to/keyfile.pem

See code: dist/esm/src/commands/acc/send-sk.js

`tpe autocomplete [SHELL]`

Display autocomplete installation instructions.

USAGE
  $ tpe autocomplete [SHELL] [-r]

ARGUMENTS
  SHELL  (zsh|bash|powershell) Shell type

FLAGS
  -r, --refresh-cache  Refresh cache (ignores displaying instructions)

DESCRIPTION
  Display autocomplete installation instructions.

EXAMPLES
  $ tpe autocomplete

  $ tpe autocomplete bash

  $ tpe autocomplete zsh

  $ tpe autocomplete powershell

  $ tpe autocomplete --refresh-cache

See code: @oclif/plugin-autocomplete

`tpe container actions`

Perform various container actions

USAGE
  $ tpe container actions -m <value> -i <value> -f <value> [-p <value>] [-s <value>] [-a <value>] [-b <value>] [-n
    <value>]

FLAGS
  -a, --ordersScAddress=<value>       [default: AA100000005033174401] Orders smart contract address
  -b, --providersScAddress=<value>    [default: AA100000005033174348] Provider smart contract address
  -f, --containerKeyFilePath=<value>  (required) Path to the container key file
  -i, --containerId=<value>           (required) Container ID
  -m, --method=<value>                (required) Method to call on the container
  -n, --chain=<value>                 Chain ID
  -p, --params=<value>                Parameters for the method
  -s, --containerPassword=<value>     Password for the container key file (env: CONTAINER_KEY_FILE_PASSWORD)

DESCRIPTION
  Perform various container actions

EXAMPLES
  $ tpe container actions -m "container_start" -i 1 -p 1 -f ./path/to/keyfile.pem -s mypassword

  $ tpe container actions -m "container_stop" -i 1 -p 1 -f ./path/to/keyfile.pem -s mypassword

  $ tpe container actions -m "container_destroy" -i 1 -p 1 -f ./path/to/keyfile.pem -s mypassword

  $ tpe container actions -m "container_handover" -i 1 -p 1 -f ./path/to/keyfile.pem -s mypassword

  $ tpe container actions -m "container_getPort" -i 1 -p "1 web 5000" -f ./path/to/keyfile.pem -s mypassword

  $ tpe container actions -m "container_getLogs" -i 1 -p 1 -f ./path/to/keyfile.pem -s mypassword

See code: dist/esm/src/commands/container/actions.js

`tpe container create`

Create a new container with a given name and key pair

USAGE
  $ tpe container create -k <value> -n <value> [-p <value>] [-f <value>] [-s <value>] [-a <value>] [-r <value>] [-c
    <value>] [-e]

FLAGS
  -a, --ordersScAddress=<value>       [default: AA100000005033174401] Orders smart contract address
  -c, --chain=<value>                 Chain ID
  -e, --isEth                         Use an ethereum address
  -f, --containerKeyFilePath=<value>  Path to the container key file
  -k, --keyFilePath=<value>           (required) Path to the key file
  -n, --containerName=<value>         (required) Name of the container
  -p, --password=<value>              Password for the key file (env: KEY_FILE_PASSWORD)
  -r, --sponsorAddress=<value>        Address of the sponsor
  -s, --containerPassword=<value>     Password for the container key file (env: CONTAINER_KEY_FILE_PASSWORD)

DESCRIPTION
  Create a new container with a given name and key pair

EXAMPLES
  $ tpe container create -k ./key.pem -p mypassword -n "NewContainer" -s containerpassword

  $ tpe container create -k ./key.pem --password mypassword --containerName "NewContainer" --containerPassword containerpassword

See code: dist/esm/src/commands/container/create.js

`tpe container list`

List containers owned by a user

USAGE
  $ tpe container list [-k <value>] [-p <value>] [-a <value>] [-c <value>] [-e]

FLAGS
  -a, --ordersScAddress=<value>  [default: AA100000005033174401] Orders smart contract address
  -c, --chain=<value>            Chain ID
  -e, --isEth                    Use an ethereum address
  -k, --keyFilePath=<value>      Path to the key file
  -p, --password=<value>         Password for the key file (env: KEY_FILE_PASSWORD)

DESCRIPTION
  List containers owned by a user

EXAMPLES
  $ tpe container list -k ./key.pem -p mypassword

  $ tpe container list -k ./key.pem --password mypassword

See code: dist/esm/src/commands/container/list.js

`tpe container update`

Update container details

USAGE
  $ tpe container update -k <value> -i <value> -n <value> -f <value> [-p <value>] [-s <value>] [-a <value>] [-r
    <value>] [-e]

FLAGS
  -a, --ordersScAddress=<value>       [default: AA100000005033174401] Orders smart contract address
  -e, --isEth                         Use an ethereum address
  -f, --containerKeyFilePath=<value>  (required) Path to the container key file
  -i, --containerId=<value>           (required) Id of the container
  -k, --keyFilePath=<value>           (required) Path to the key file
  -n, --containerName=<value>         (required) Name of the container
  -p, --password=<value>              Password for the key file (env: KEY_FILE_PASSWORD)
  -r, --sponsorAddress=<value>        Address of the sponsor
  -s, --containerPassword=<value>     Password for the container key file (env: CONTAINER_KEY_FILE_PASSWORD)

DESCRIPTION
  Update container details

EXAMPLES
  $ tpe container update -k ./key.pem -p mypassword -i 123 -n "New Container Name" -f ./containerKey.pem -s containerpassword

  $ tpe container update -k ./key.pem --password mypassword --containerId 123 
      --containerName "New Container Name" --containerKeyFilePath ./containerKey.pem --containerPassword containerpassword

See code: dist/esm/src/commands/container/update.js

`tpe container upload`

Upload files to a container

USAGE
  $ tpe container upload -k <value> -i <value> -f <value> -t <value> [-p <value>] [-s <value>] [-c] [-a <value>] [-b
    <value>] [-n <value>] [-g <value>] [-e]

FLAGS
  -a, --ordersScAddress=<value>       [default: AA100000005033174401] Orders smart contract address
  -b, --providerScAddress=<value>     [default: AA100000005033174348] Provider smart contract address
  -c, --chooseProvider                Choose provider
  -e, --isEth                         Use an ethereum address
  -f, --containerKeyFilePath=<value>  (required) Path to the container key file
  -g, --ignoreUploadList=<value>      Ignore upload list (e.g. "[.git,node_modules,logs]")
  -i, --containerId=<value>           (required) Container ID
  -k, --keyFilePath=<value>           (required) Path to the key file
  -n, --chain=<value>                 Chain ID
  -p, --password=<value>              Password for the key file (env: KEY_FILE_PASSWORD)
  -s, --containerPassword=<value>     Password for the container key file (env: CONTAINER_KEY_FILE_PASSWORD)
  -t, --filesPath=<value>             (required) Path to the files

DESCRIPTION
  Upload files to a container

EXAMPLES
  $ tpe container upload --containerId 123 --containerKeyFilePath ./key.pem --containerPassword mypassword --filesPath ./files

  $ tpe container upload -i 123 -f ./key.pem -s mypassword -t ./files

  $ tpe container upload --containerId 123 --containerKeyFilePath ./key.pem --containerPassword mypassword --filesPath ./files --chooseProvider

  $ tpe container upload -i 123 -f ./key.pem -s mypassword -t ./files --ignoreUploadList "[.git,node_modules,logs]"

  $ tpe container upload --containerId 456 --containerKeyFilePath ./key.pem --containerPassword ethpassword --filesPath ./upload --isEth

  $ tpe container upload -i 789 -f ./container-key.pem -s "securepassword" -t ./files --ordersScAddress 0xOrder123 --providerScAddress 0xProvider456

  $ tpe container upload --containerId 321 --containerKeyFilePath ./key.pem --containerPassword mypassword --filesPath ./data --chain 5

See code: dist/esm/src/commands/container/upload.js

`tpe contract deploy`

Deploy a smart contract to the blockchain

USAGE
  $ tpe contract deploy -k <value> [-j <value> | -a <value> | -b <value>] [-t <value>] [-v <value>] [-i <value>] [-p
    <value>] [-l] [-c <value>]

FLAGS
  -a, --abiPath=<value>      Path to the ABI file
  -b, --binPath=<value>      Path to the binary file
  -c, --chain=<value>        Chain ID
  -i, --initParams=<value>   Initialization parameters
  -j, --jsonPath=<value>     Path to the JSON file
  -k, --keyFilePath=<value>  (required) Path to the key file
  -l, --inPlace
  -p, --password=<value>     Password for the key file (env: KEY_FILE_PASSWORD)
  -t, --gasToken=<value>     [default: SK] Token used to pay for gas
  -v, --gasValue=<value>     [default: 2000000000000000000] Gas value for deployment

DESCRIPTION
  Deploy a smart contract to the blockchain

EXAMPLES
  $ tpe contract deploy --abiPath ./path/to/abi.json --binPath ./path/to/bin --keyFilePath ./path/to/keyfile.pem --password mypassword

  $ tpe contract deploy -a ./path/to/abi.json -b ./path/to/bin -k ./path/to/keyfile.pem -p mypassword --gasToken SK --gasValue 2000000000000000000

  $ tpe contract deploy --abiPath ./path/to/abi.json --binPath ./path/to/bin --keyFilePath ./path/to/keyfile.pem --initParams "param1 param2"

See code: dist/esm/src/commands/contract/deploy.js

`tpe contract get`

Call a method on a deployed smart contract

USAGE
  $ tpe contract get -a <value> -d <value> -m <value> [-p <value>]

FLAGS
  -a, --abiPath=<value>  (required) Path to the ABI file
  -d, --address=<value>  (required) Smart contract address
  -m, --method=<value>   (required) Method name to call
  -p, --params=<value>   Parameters for the method

DESCRIPTION
  Call a method on a deployed smart contract

EXAMPLES
  $ tpe contract get --abiPath ./path/to/abi.json --address AA100000001677748249 --method getBalance --params "0x456 1 2 [1,2] {a: 1, b: 2} 1n"

  $ tpe contract get -a ./path/to/abi.json -d AA100000001677748249 -m getBalance -p "0x456 1 2 [1,2] {a: 1, b: 2} 1n"

  $ tpe contract get --abiPath ./path/to/abi.json --address AA100000001677748249 --method getInfo

See code: dist/esm/src/commands/contract/get.js

`tpe contract set`

Execute a method on a specified smart contract

USAGE
  $ tpe contract set -a <value> -d <value> -k <value> -m <value> [-r <value>] [-n <value>] [-p <value>] [-s
    <value>] [-c <value>] [-e]

FLAGS
  -a, --abiPath=<value>         (required) Path to the ABI file
  -c, --chain=<value>           Chain ID
  -d, --address=<value>         (required) Smart contract address
  -e, --isEth                   Use an ethereum address
  -k, --keyFilePath=<value>     (required) Path to the key file
  -m, --method=<value>          (required) Method name to call
  -n, --amount=<value>          Amount of tokens to send
  -p, --password=<value>        Password for the key file (env: KEY_FILE_PASSWORD)
  -r, --params=<value>          Parameters for the method
  -s, --sponsorAddress=<value>  Address of the sponsor

DESCRIPTION
  Execute a method on a specified smart contract

EXAMPLES
  $ tpe contract set --abiPath ./path/to/abi.json 
      --address AA100000001677748249 --keyFilePath ./path/to/keyfile.pem --method set --params value1 --password mypassword

  $ tpe contract set -a ./path/to/abi.json -d AA100000001677748249 -k ./path/to/keyfile.pem -m set -r "value1 value2" -p mypassword

  $ tpe contract set --abiPath ./path/to/abi.json 
      --address AA100000001677748249 --keyFilePath ./path/to/keyfile.pem --method setData --params "0x456 1 2 [1,2] {a: 1, b: 2} 1n"

See code: dist/esm/src/commands/contract/set.js

`tpe help [COMMAND]`

Display help for tpe.

USAGE
  $ tpe help [COMMAND...] [-n]

ARGUMENTS
  COMMAND...  Command to show help for.

FLAGS
  -n, --nested-commands  Include all nested commands in the output.

DESCRIPTION
  Display help for tpe.

See code: @oclif/plugin-help

`tpe plugins`

List installed plugins.

USAGE
  $ tpe plugins [--json] [--core]

FLAGS
  --core  Show core plugins.

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  List installed plugins.

EXAMPLES
  $ tpe plugins

See code: @oclif/plugin-plugins

`tpe plugins add PLUGIN`

Installs a plugin into tpe.

USAGE
  $ tpe plugins add PLUGIN... [--json] [-f] [-h] [-s | -v]

ARGUMENTS
  PLUGIN...  Plugin to install.

FLAGS
  -f, --force    Force npm to fetch remote resources even if a local copy exists on disk.
  -h, --help     Show CLI help.
  -s, --silent   Silences npm output.
  -v, --verbose  Show verbose npm output.

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Installs a plugin into tpe.

  Uses npm to install plugins.

  Installation of a user-installed plugin will override a core plugin.

  Use the TPE_NPM_LOG_LEVEL environment variable to set the npm loglevel.
  Use the TPE_NPM_REGISTRY environment variable to set the npm registry.

ALIASES
  $ tpe plugins add

EXAMPLES
  Install a plugin from npm registry.

    $ tpe plugins add myplugin

  Install a plugin from a github url.

    $ tpe plugins add https://github.com/someuser/someplugin

  Install a plugin from a github slug.

    $ tpe plugins add someuser/someplugin

`tpe plugins:inspect PLUGIN...`

Displays installation properties of a plugin.

USAGE
  $ tpe plugins inspect PLUGIN...

ARGUMENTS
  PLUGIN...  [default: .] Plugin to inspect.

FLAGS
  -h, --help     Show CLI help.
  -v, --verbose

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Displays installation properties of a plugin.

EXAMPLES
  $ tpe plugins inspect myplugin

See code: @oclif/plugin-plugins

`tpe plugins install PLUGIN`

Installs a plugin into tpe.

USAGE
  $ tpe plugins install PLUGIN... [--json] [-f] [-h] [-s | -v]

ARGUMENTS
  PLUGIN...  Plugin to install.

FLAGS
  -f, --force    Force npm to fetch remote resources even if a local copy exists on disk.
  -h, --help     Show CLI help.
  -s, --silent   Silences npm output.
  -v, --verbose  Show verbose npm output.

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Installs a plugin into tpe.

  Uses npm to install plugins.

  Installation of a user-installed plugin will override a core plugin.

  Use the TPE_NPM_LOG_LEVEL environment variable to set the npm loglevel.
  Use the TPE_NPM_REGISTRY environment variable to set the npm registry.

ALIASES
  $ tpe plugins add

EXAMPLES
  Install a plugin from npm registry.

    $ tpe plugins install myplugin

  Install a plugin from a github url.

    $ tpe plugins install https://github.com/someuser/someplugin

  Install a plugin from a github slug.

    $ tpe plugins install someuser/someplugin

See code: @oclif/plugin-plugins

`tpe plugins link PATH`

Links a plugin into the CLI for development.

USAGE
  $ tpe plugins link PATH [-h] [--install] [-v]

ARGUMENTS
  PATH  [default: .] path to plugin

FLAGS
  -h, --help          Show CLI help.
  -v, --verbose
      --[no-]install  Install dependencies after linking the plugin.

DESCRIPTION
  Links a plugin into the CLI for development.

  Installation of a linked plugin will override a user-installed or core plugin.

  e.g. If you have a user-installed or core plugin that has a 'hello' command, installing a linked plugin with a 'hello'
  command will override the user-installed or core plugin implementation. This is useful for development work.


EXAMPLES
  $ tpe plugins link myplugin

See code: @oclif/plugin-plugins

`tpe plugins remove [PLUGIN]`

Removes a plugin from the CLI.

USAGE
  $ tpe plugins remove [PLUGIN...] [-h] [-v]

ARGUMENTS
  PLUGIN...  plugin to uninstall

FLAGS
  -h, --help     Show CLI help.
  -v, --verbose

DESCRIPTION
  Removes a plugin from the CLI.

ALIASES
  $ tpe plugins unlink
  $ tpe plugins remove

EXAMPLES
  $ tpe plugins remove myplugin

`tpe plugins reset`

Remove all user-installed and linked plugins.

USAGE
  $ tpe plugins reset [--hard] [--reinstall]

FLAGS
  --hard       Delete node_modules and package manager related files in addition to uninstalling plugins.
  --reinstall  Reinstall all plugins after uninstalling.

See code: @oclif/plugin-plugins

`tpe plugins uninstall [PLUGIN]`

Removes a plugin from the CLI.

USAGE
  $ tpe plugins uninstall [PLUGIN...] [-h] [-v]

ARGUMENTS
  PLUGIN...  plugin to uninstall

FLAGS
  -h, --help     Show CLI help.
  -v, --verbose

DESCRIPTION
  Removes a plugin from the CLI.

ALIASES
  $ tpe plugins unlink
  $ tpe plugins remove

EXAMPLES
  $ tpe plugins uninstall myplugin

See code: @oclif/plugin-plugins

`tpe plugins unlink [PLUGIN]`

Removes a plugin from the CLI.

USAGE
  $ tpe plugins unlink [PLUGIN...] [-h] [-v]

ARGUMENTS
  PLUGIN...  plugin to uninstall

FLAGS
  -h, --help     Show CLI help.
  -v, --verbose

DESCRIPTION
  Removes a plugin from the CLI.

ALIASES
  $ tpe plugins unlink
  $ tpe plugins remove

EXAMPLES
  $ tpe plugins unlink myplugin

`tpe plugins update`

Update installed plugins.

USAGE
  $ tpe plugins update [-h] [-v]

FLAGS
  -h, --help     Show CLI help.
  -v, --verbose

DESCRIPTION
  Update installed plugins.

See code: @oclif/plugin-plugins

`tpe provider create`

Create a new provider with a given name and key pair

USAGE
  $ tpe provider create -k <value> -n <value> [-p <value>] [-a <value>] [-r <value>] [-c <value>] [-e]

FLAGS
  -a, --providersScAddress=<value>  [default: AA100000005033174348] Provider smart contract address
  -c, --chain=<value>               Chain ID
  -e, --isEth                       Use an ethereum address
  -k, --keyFilePath=<value>         (required) Path to the key file
  -n, --providerName=<value>        (required) Name of the provider
  -p, --password=<value>            Password for the key file (env: KEY_FILE_PASSWORD)
  -r, --sponsorAddress=<value>      Address of the sponsor

DESCRIPTION
  Create a new provider with a given name and key pair

EXAMPLES
  $ tpe provider create -k ./key.pem -p mypassword -n "NewProvider" -s containerpassword

  $ tpe provider create -k ./key.pem --password mypassword --containerName "NewProvider" --containerPassword containerpassword

See code: dist/esm/src/commands/provider/create.js

`tpe provider list`

List all providers or filter by key file or address

USAGE
  $ tpe provider list [-k <value> | -r <value>] [-p <value>] [-a <value>] [-o <value>] [-c <value>] [-e]

FLAGS
  -a, --providersScAddress=<value>  [default: AA100000005033174348] Providers smart contract address
  -c, --chain=<value>               Chain ID
  -e, --isEth                       Use an ethereum address
  -k, --keyFilePath=<value>         Path to the key file (used for filtering by owner)
  -o, --ordersScAddress=<value>     [default: AA100000005033174401] Orders smart contract address
  -p, --password=<value>            Password for the key file (env: KEY_FILE_PASSWORD)
  -r, --address=<value>             Filter by address

DESCRIPTION
  List all providers or filter by key file or address

EXAMPLES
  $ tpe provider list -k ./key.pem -p mypassword

  $ tpe provider list --address 0x123...abc

See code: dist/esm/src/commands/provider/list.js

`tpe provider set-url`

Set or update the URL for a specific provider using the provider ID. Requires a key file for authentication.

USAGE
  $ tpe provider set-url -k <value> -i <value> -u <value> [-p <value>] [-a <value>] [-r <value>] [-c <value>] [-e]

FLAGS
  -a, --ordersScAddress=<value>  [default: AA100000005033174401] Orders smart contract address
  -c, --chain=<value>            Chain ID
  -e, --isEth                    Use an ethereum address
  -i, --providerId=<value>       (required) Id of the provider
  -k, --keyFilePath=<value>      (required) Path to the key file
  -p, --password=<value>         Password for the key file (env: KEY_FILE_PASSWORD)
  -r, --sponsorAddress=<value>   Address of the sponsor
  -u, --providerUrl=<value>      (required) Url of the provider

DESCRIPTION
  Set or update the URL for a specific provider using the provider ID. Requires a key file for authentication.

EXAMPLES
  $ tpe provider set-url -k ./key.pem -p mypassword -i 123 -u "https://provider.example.com"

  $ tpe provider set-url --keyFilePath ./key.pem --password mypassword --providerId 123 --providerUrl "https://provider.example.com"

  $ tpe provider set-url -k ./key.pem -i 123 -u "https://provider.example.com" --sponsorAddress 0xSponsorAddress

See code: dist/esm/src/commands/provider/set-url.js

`tpe storage tasklist`

Shows the list of all tasks for the current account

USAGE
  $ tpe storage tasklist [-b <value>] [-c <value>] [-a <value>] [-n <value>]

FLAGS
  -a, --storageScAddress=<value>  [default: AA100000001677723663] Storage smart contract address
  -b, --bootstrapChain=<value>    [default: 1025] Default chain ID
  -c, --configPath=<value>        [default: ./tp-cli.json] Config to read
  -n, --chain=<value>             Chain ID

DESCRIPTION
  Shows the list of all tasks for the current account

EXAMPLES
  $ tpe storage tasklist

  $ tpe storage tasklist ./tp-cli.json

See code: dist/esm/src/commands/storage/tasklist.js

`tpe storage upload`

Upload application files to the storage

USAGE
  $ tpe storage upload [-b <value>] [-c <value>] [-a <value>] [-p <value>] [-s <value>] [-n <value>] [-e]

FLAGS
  -a, --storageScAddress=<value>  [default: AA100000001677723663] Storage smart contract address
  -b, --bootstrapChain=<value>    [default: 1025] Default chain ID for bootstrap
  -c, --configPath=<value>        [default: ./tp-cli.json] Config to read
  -e, --isEth                     Use an ethereum address
  -n, --chain=<value>             Chain ID
  -p, --password=<value>          Password for the key file (env: KEY_FILE_PASSWORD)
  -s, --sponsorAddress=<value>    Address of the sponsor

DESCRIPTION
  Upload application files to the storage

EXAMPLES
  $ tpe storage upload ./tp-cli.json

See code: dist/esm/src/commands/storage/upload.js

`tpe update [CHANNEL]`

update the tpe CLI

USAGE
  $ tpe update [CHANNEL] [--force |  | [-a | -v <value> | -i]] [-b ]

FLAGS
  -a, --available        See available versions.
  -b, --verbose          Show more details about the available versions.
  -i, --interactive      Interactively select version to install. This is ignored if a channel is provided.
  -v, --version=<value>  Install a specific version.
      --force            Force a re-download of the requested version.

DESCRIPTION
  update the tpe CLI

EXAMPLES
  Update to the stable channel:

    $ tpe update stable

  Update to a specific version:

    $ tpe update --version 1.0.0

  Interactively select version:

    $ tpe update --interactive

  See available versions:

    $ tpe update --available

See code: @oclif/plugin-update

oclif

@oclif/color @oclif/core @oclif/plugin-autocomplete @oclif/plugin-help @oclif/plugin-not-found @oclif/plugin-plugins @oclif/plugin-update @thepowereco/tssdk axios cli-table3 enquirer json-colorizer jsonwebtoken listr2 viem

@everything-registry/sub-chunk-913 @zalastax/nolb-_thep

7 months ago

7 months ago

7 months ago

7 months ago