Skip to content

Commit a113e60

Browse files
committed
Address review comments
1 parent f30e91b commit a113e60

File tree

1 file changed

+5
-7
lines changed

1 file changed

+5
-7
lines changed

source/mainnet/net/guides/company-identities.rst

Lines changed: 5 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,7 @@ After obtaining the ``id-object.json`` identity object from the identity provide
6565

6666
.. dropdown:: Format of the key files
6767

68-
Both initial account keys and subsequent account keys are stored in JSON files. The unencrypted data is a JSON record with a number of fields. For sending transactions the fields that are relevant are:
68+
Both initial account keys and subsequent account keys are stored in JSON files. The unencrypted data is a JSON record with a number of fields. This is the same format as exported by the other Concordium wallets (except Desktop Wallet). For sending transactions the fields that are relevant are:
6969

7070
- ``accountKeys`` contains the account keys. It has the following format:
7171

@@ -116,11 +116,9 @@ However, if the ``account-keys.json`` file is not encrypted it can be imported i
116116

117117
.. code-block:: console
118118
119-
concordium-client config account import account-keys.json --format=genesis --name my-account
119+
concordium-client config account import account-keys.json --name my-account
120120
121-
where the ``--name`` option is optional, and if given, will name the account according to the given value ("my-account" in the example above).
122-
123-
If the account-keys.json file is encrypted then it must first be decrypted. This can be done with the :ref:`utils tool<downloads-auxiliary-tools>`.
121+
``--name`` is mandatory and will name the account according to the given value ("my-account" in the example above).
124122

125123
The initial account keys cannot be directly imported into ``concordium-client``.
126124

@@ -139,7 +137,7 @@ If the identity object used to create credentials is lost, it can be recovered f
139137

140138
#. Enter your seedphrase in the Enter seedphrase field. And click **Find identities**.
141139

142-
#. You see a list of accounts associated with the seedphrase. It is possible to save the account keys that can be ussed to interact with the account on the chain. Indices that are to the left of the account address are pointing to the identity index, being the first value and the account index being the second value (0,0). In the Identities to recover drop-down, select the identity you want to recover. There will always be one additional index on the list for selection to be sure that request can be generated for more than one identity. This is mainly useful in cases where first identity object was lost or unused to create accounts. Click **Generate recovery request**. The command outputs the ``recovery-request.json`` file. The request should be sent to the identity provider through a trusted channel. Store the auxiliary output securely. When the request has been verified successfully, you will receive an email with an identity object . Store this file securely as you need it to create accounts on the chain.
140+
#. You see a list of accounts associated with the seedphrase. It is possible to save the account keys that can be ussed to interact with the account on the chain. Indices that are to the left of the account address are pointing to the identity index, being the first value and the account index being the second value (0,0). In the Identities to recover drop-down, select the identity you want to recover. There will always be one additional index on the list for selection to be sure that request can be generated for more than one identity. This is mainly useful in cases where first identity object was lost or unused to create accounts. Click **Generate recovery request**. The command outputs the ``recovery-request.json`` file. The request should be sent to the identity provider through a trusted channel. When the request has been verified successfully, you will receive an email with an identity object. Store this file securely as you need it to create accounts on the chain.
143141

144142
.. image:: ../images/company-id-recover.png
145143
:alt: company id tool screen showing identities related to seedphrase and option to select
@@ -148,4 +146,4 @@ If the identity object used to create credentials is lost, it can be recovered f
148146

149147
- For Testnet requests: Send the file to [email protected] with the subject line "Recover company identity".
150148

151-
When the recovery request has been verified successfully, you will receive an email with the identity object file named ``id-object.json`` that you lost. Store this file securely as you need it to create accounts and regenerate account keys.
149+
When the recovery request has been verified successfully, you will receive an email with the identity object file named ``id-object.json`` that you lost. Store this file securely as you need it to create accounts.

0 commit comments

Comments
 (0)