From 96736937223bc345aac8290b00f3eab4dfaa57c5 Mon Sep 17 00:00:00 2001 From: Simon Noetzlin Date: Mon, 29 Jan 2024 11:36:28 +0100 Subject: [PATCH] update key assingment doc --- docs/docs/features/key-assignment.md | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/docs/docs/features/key-assignment.md b/docs/docs/features/key-assignment.md index 7ac7d02f48..ab432ff847 100644 --- a/docs/docs/features/key-assignment.md +++ b/docs/docs/features/key-assignment.md @@ -17,7 +17,7 @@ Key assignment is handled only by the provider chain - the consumer chains are n ## Rules -- a key can be assigned before the consumer addition proposal passes on the provider +- a key can be assigned as soon as the consumer addition proposal passes on the provider - validator A cannot assign consumer key K to consumer chain X if there is already a validator B (B!=A) using K on the provider - validator A cannot assign consumer key K to consumer chain X if there is already a validator B using K on X - a new validator on the provider cannot use a consensus key K if K is already used by any validator on any consumer chain @@ -80,3 +80,13 @@ To change your key, simply repeat all of the steps listed above. Take note that ## Removing a key To remove a key, simply switch it back to the consensus key you have assigned on the provider chain by following steps in the `Adding a key` section and using your provider consensus key. + +## Querying proposed consumer chains + +To query the pending consumer addition proposals, you can use the following command on the provider: + +```bash +gaiad query provider list-proposed-consumer-chains +``` + +This query is valuable for staying informed about when keys can be assigned to newly proposed consumer chains.