panacead --help
.panacead
commands, including usage examples.panacea
panacead keys add
panacea17kmacx3czkdnhtfueqzzxk9xqzapj453f23m5a
panaceavaloper
panaceavaloper17kmacx3czkdnhtfueqzzxk9xqzapj453wg3mgr
panaceapub
panacead keys add
panaceapub1addwnpepqwk3j2j3knuyah89skh8wtn5kr4qx32nhql6hzjadzmre2xlfmvxgy39ln8
panaceavalconspub
panacead init
.panacead tendermint show-validator
panaceavalconspub1zcjduepqktkqqsl9rchj77v9vg0crc87grp9h2u5ggpdtvcq74kxlr29lgwsa3dr66
sk, pk
respectively) to be able to receive funds, send txs, bond tx, etc.<account_name>
:CheckTx
, where gasPrices >= minGasPrices
. Note, your transaction must supply fees that are greater than or equal to minimum fee which the validator requires.gasPrice
in the mempool, so providing higher fees or gas prices may yield higher tx priority.account <account_panacea> does not exist.
This can also happen if you fund the account before your node has fully synced with the chain. These are both normal.:::to_address
is a key matching the format: panacea1y3mhszahwatjc3023datq46a0u2fv337tes4n9
<amount>
accepts the format <value|coin_name> -> ex) 10000000umed
. :::--gas
flag. If you pass --gas=auto
, the gas supply will be automatically estimated before executing the transaction. Gas estimate might be inaccurate as state changes could occur in between the end of the simulation and the actual execution of a transaction, thus an adjustment is applied on top of the original estimate in order to ensure the transaction is broadcasted successfully. The adjustment can be controlled via the --gas-adjustment
flag, whose default value is 1.0. :::--height
flag:--dry-run
flag to the command line:--generate-only
to the list of the command line arguments:events
, which are added on every transaction.Event
type and take the form of: {eventType}.{attributeKey}={attributeValue}
. Events can also be combined to query for a more specific result using the &
symbol.event
is the following:events
:page
and limit
:Type()
function of the relevant message.tags
on each module by looking at the /tags directory of each module. :::panaceavalconspub
address (public key) can be used to create a new validator by staking tokens. You can find your validator public key by:umed
than you have!pubkey
: A public key associated with the Tendermint private key (which was generated by panacead init
). The public key can be resolved by panacead tendermint show-validator
in the node that you want to make as a validator. For details about various key types, please see this guide.moniker
: A validator nickname that will be displayed publiclydetails
: A detail description of the validatoridentity
: The identity
can be used as to verify identity with systems like Keybase or UPort. When using with Keybase identity
should be populated with a 16-digit string that is generated with a keybase.io account.commission-rate
: An initial commission rate on block rewards and fees charged to delegatorscommission-max-rate
: A maximum commission rate which this validator can charge. This cannot be changed after the create-validator
transaction is processed.commission-max-change-rate
: A maximum daily increase of the validator commission. This cannot be changed after the create-validator
transaction is processed. This is used to measure % point change over the commision-rate
. E.g. 1% to 2% is a 100% rate increase, but only 1% point.min-self-delegation
: A strictly positive integer in umed
that represents the minimum amount of self-delegated voting power your validator must always have. If the validator's self-delegated stake falls below this limit, their entire staking pool will unbond.amount
: An amount of your self-delegation1med
(1000000umed
). In other words, validators cannot be in the active set, if their total stake (= self-bonded stake + delegators stake) is under 1med
.--moniker
defaults to the machine name) if the field has never been set or remain the same if it has been set in the past.--from
option specifies which validator you are editing.--commission-rate
value must adhere to the following invariants:commission-max-rate
commission-max-change-rate
which is maximum % point change rate per day. In other words, a validator can only change its commission once per day and within commission-max-change-rate
bounds.umed
to a validator. These delegators can receive part of the validator's fee revenue.<validator>
is the operator address of the validator to which you intend to delegate. If you are running a local testnet, you can find this with:[name]
is the name of the key you specified when you initialized panacead
.--height
flag.--height
flag.--height
flag.Pool
defines the dynamic parameters of the current state. You can query them with the following command:pool
command you will get the values for:p1
, p2
, and p3
, each of which is held by a distinct party, the user holding p1
would require to import both p2
and p3
in order to generate the multisig account public key:p1p2p3
has been stored, and its address will be used as signer of multisig transactions:--show-multisig
flag:unsignedTx.json
contains the unsigned transaction encoded in JSON. p1
can now sign the transaction with its own private key:p1
transmits both unsignedTx.json
and p1signature.json
to p2
or p3
, which in turn will generate their respective signature:p1p2p3
is a 2-of-3 multisig key, therefore one additional signature is sufficient. Any the key holders can now generate the multisig transaction by combining the required signature files:Bash
and Zsh
can be generated through the completion
command, which is available for both panacead
.Bash
completion scripts run the following command:Zsh
completion scripts run the following command:.bashrc
or .bash_profile
to enable Bash autocompletion:panacead query aol list-topics <owner_panacea>
[name]
is the name of the key you specified when you initialized panacead
.chain-id
and from
. That is, it generates a Secp256k1 key-pair and derive a DID and a DID Document. The DID Document is stored in Panacea.~/did_keystore
directory.<did-doc-path>
. To prove that you are the DID owner, you must pass a <key-id>
that is one of verificationMethod
s in the DID Document. Also, that command will prompt you to enter a passphrase of that key if the key-pair is stored in your keystore: ~/did_keystore
. The key-pair will be used to make a signature so that Panacea can verify that you are the DID owner.<key-id>
must be specified and the corresponding key-pair should be used to make a signature so that Panacea can verify that you are the DID owner.-
followed by random 3 letters will be appended to the provided symbol to avoid uniqueness constraint. Those 3 letters are the first three letters of the Tx hash of the issue
transaction. The generated symbol will be returned as a Tx response.amount
must be specified with the micro-denomination that contains the 3-letter suffix (without -
).