Skip to main content

multi-signature

Usage: chr multi-signature [OPTIONS] COMMAND [ARGS]...

  Handle transactions with need of multiple signers

╭─ Options ───────────────────────────────────────────────────────────────────╮
│  -h, --help  Show this message and exit                                     │
╰─────────────────────────────────────────────────────────────────────────────╯
╭─ Commands ──────────────────────────────────────────────────────────────────╮
│  create  Creates a new transaction for multi signature and signs it with    │
│          your key                                                           │
│  sign    Sign a existing transaction with your key                          │
│  send    Send a fully signed transaction                                    │
│  view    View a existing transaction                                        │
╰─────────────────────────────────────────────────────────────────────────────╯

You can use the multi-signature command (chr multi-signature) for handling transactions that need multiple signers.

multi-signature create​

Usage: chr multi-signature create [<options>] <opname> [<args>]...

  Creates a new transaction for multi signature and signs it with your key

Configuration Properties:
  -cfg, --config=<config>    Alternate path for client configuration file
  -s, --settings=<settings>  Alternate path for project settings file

Node:

  Target a test node

  -brid, --blockchain-rid=<text>  Target Blockchain RID
  --cid=<int>                     Target Blockchain IID
  --api-url=<text>                Target api url

Deployment:

  Use a configured deployment

  -d, --network=<text>      Specify which deployment target to use
  -bc, --blockchain=<text>  Name of blockchain in deployment configuration

FT compatible dapps options:
  --ft-auth               Adds ft4.ft_auth operation for FT-compatible dapps
  --ft-account-id=<text>  Explicitly specify which account to use
  -id, --auth-descriptor-id=<text>
                          Explicitly specify which auth descriptor id to use

Options:
  --secret=<path>        Path to secret file (pubkey/privkey)
  --signers-file=<path>  Path to file containing public keys of signers
                         (pubkey1=x,pubkey2=y,...)
  --target=<path>        Path where file should be saved
  -h, --help             Show this message and exit

Arguments:
  <opname>  name of the operation to execute.
  <args>    arguments to pass to the operation. (integer: 123) (big_integer:
            1234L) (string: foo, "bar") (bytearray: will be encoded using the
            rell notation x"<myByteArray>" and will initially be interpreted as
            a hex-string.) (array: [foo,123]) (dict:
            ["key1":value1,"key2":value2])

The create command chr multi-signature create allows you to create a new transaction for multi signature and signs it with your key.

multi-signature sign​

Usage: chr multi-signature sign [<options>]

  Sign a existing transaction with your key

Configuration Properties:
  -cfg, --config=<config>  Alternate path for client configuration file

Options:
  -f, --file=<path>   Path to file of transaction
  --secret=<path>     Path to secret file (pubkey/privkey)
  --target=<path>     Path where file should be saved
  --file-name=<text>  Override default name of output file
  -h, --help          Show this message and exit

The sign command chr multi-signature sign allows you to sign a existing transaction with your key.

multi-signature send​

Usage: chr multi-signature send [<options>]

  Send a fully signed transaction

Configuration Properties:
  -cfg, --config=<config>    Alternate path for client configuration file
  -s, --settings=<settings>  Alternate path for project settings file

Node:

  Target a test node

  -brid, --blockchain-rid=<text>  Target Blockchain RID
  --cid=<int>                     Target Blockchain IID
  --api-url=<text>                Target api url

Deployment:

  Use a configured deployment

  -d, --network=<text>      Specify which deployment target to use
  -bc, --blockchain=<text>  Name of blockchain in deployment configuration

Options:
  --secret=<path>           Path to secret file (pubkey/privkey)
  -a, --await / --no-await  Wait for transaction to be included in a block
  -f, --file=<path>         Path to file of transaction
  -h, --help                Show this message and exit

The send command chr multi-signature send allows you to send a fully signed transaction.

multi-signature view​

Usage: chr multi-signature view [<options>]

  View a existing transaction

Options:
  -f, --file=<path>  Path to file of transaction
  -h, --help         Show this message and exit

The view command chr multi-signature view allows you to view a existing transaction.