sign
The sign
command provides sub-commands that helps you sign git objects (e.g. tag and commit) and generate a push token which a MakeOS node will need to authenticate your push requests.
The command, when called without a subcommand will attempt to sign the current branch's latest commit and generate a corresponding push token.
To see a list of sub-commands, run kit sign -h
Global Options
The command includes global options that can be set for all sub-commands.
-f, --fee
- Set the number of coins to pay as a transaction processing fee. If unset, the value ofuser.fee
config option of the current repository will be used.-n, --nonce
- Set the next nonce of the signing account. This is the number of transactions sent by the signing account + 1. If unset, the value ofuser.nonce
config option of the current repository will be used.-v, --value
- (Optional) Set the number of coins to be transferred from the signing account. If unset, the value ofuser.value
config option of the current repository will be used.-r, --remote
- Provide the remote name where the push token will be added to.-x, --reset
- Clear previous request tokens from the.git/config
before creating a new one.
Remote API Server
--remote.address
- The address of the Git & RPC remote server.
RPC
For methods that require connecting to a running node, Kit will attempt to connect via RPC by default. These are the options to control the connection:
--rpc.user
- The username to send to the RPC server for authentication.--rpc.password
- The password to send to the RPC server for authentication.--rpc.https
- Enables SSL connection to the RPC server.
Signing
-u, --signing-key
- The address or index of a key that will be used to sign the transaction. If unset, the value ofuser.signingKey
config option of the current repository will be used.-p, --signing-key-pass
- The passphrase that will be used to unlock the signing key. If unset, the value ofuser.passphrase
config option of the current repository will be used.
Last updated