Skip to content
This repository has been archived by the owner on Mar 20, 2024. It is now read-only.

Commit

Permalink
remove links
Browse files Browse the repository at this point in the history
  • Loading branch information
@shrimalmadhur
shrimalmadhur committed Oct 26, 2023
1 parent 5ea912f commit 82a1c9f
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/docs/keys/developers.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ A good choice for a remote signer is [Web3signer](https://docs.web3signer.consen

The AVS can implement a feasible and sufficient method of loading the keys. This is asking for a path to a keystore folder. This keystore needs to follow some structure either the AVS knows how to read, or an AVS [plugin](/docs/category/plugin) knows how to transform to something the AVS knows how to read.

Usually, the plugin idea is the most recommended because the AVS has the freedom to use whatever structure they need or want for the keystore. Also, no constraint is being put on users or key generation tools. This also fits the idea of the [AVS setup wizard tool](/docs/category/avs-setup-wizard) supporting such plugins. Apart from the wizard domain, users could use this plugin (as an AVS command/subcommand) to process the raw keystore if they go for a manual setup.
Usually, the plugin idea is the most recommended because the AVS has the freedom to use whatever structure they need or want for the keystore. Also, no constraint is being put on users or key generation tools.

Plugins could be made to generate the keys directly to a keystore folder the AVS knows how to read. Generation would be made according to user inputs. Third party tools could be used to generate keystores.

Expand All @@ -52,4 +52,4 @@ By keys, we refer to any kind of secret, either in plain text or encrypted.

This keystore structure requires a strict specifications on the file names, folder names, and contents within the keystore. Plugins can help enormously to get the burden of maintaining such structure off the user.

The path to this keystore folder can be provided via an environment variable or argument. Either way, a target for an option in [the profile file](/docs/spec/packaging/profiles) of the packaging proposal for Nodes can be used to allow the AVS setup wizard tool to get his path from the user.
The path to this keystore folder can be provided via an environment variable or argument.

0 comments on commit 82a1c9f

Please sign in to comment.