You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Configuration for how the Signer module should load validator keys. Currently two types of loaders are supported:
133
142
# - File: load keys from a plain text file (unsafe, use only for testing purposes)
134
143
# - ValidatorsDir: load keys from a `keys` and `secrets` file/folder (ERC-2335 style keystores). More details can be found in the docs (https://commit-boost.github.io/commit-boost-client/get_started/configuration/)
135
-
[signer.loader]
144
+
[signer.local.loader]
136
145
# File: path to the keys file
137
146
key_path = "./keys.example.json"
138
147
# ValidatorsDir: format of the keystore (lighthouse, prysm, teku or lodestar)
Copy file name to clipboardExpand all lines: docs/docs/get_started/configuration.md
+21-9Lines changed: 21 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,17 +31,20 @@ Note that in this setup, the signer module will not be started.
31
31
32
32
## Signer module
33
33
34
-
To start the signer module, you need to include its parameters in the config file:
34
+
Commit-Boost supports both local and remote signers. The signer module is responsible for signing the transactions that other modules generates. Please note that only one signer at a time is allowed.
35
+
36
+
### Local signer
37
+
38
+
To start a local signer module, you need to include its parameters in the config file
35
39
36
40
```toml
37
-
[signer]
38
-
[signer.loader]
41
+
[signer.local.loader]
39
42
format = "lighthouse"
40
43
keys_path = "/path/to/keys"
41
44
secrets_path = "/path/to.secrets"
42
45
```
43
46
44
-
We currently support Lighthouse, Prysm, Teku and Lodestar's keystores so it's easier to load the keys. We're working on adding support for additional keystores, including remote signers. These are the expected file structures for each format:
47
+
We currently support Lighthouse, Prysm, Teku and Lodestar's keystores so it's easier to load the keys. We're working on adding support for additional keystores. These are the expected file structures for each format:
45
48
46
49
<details>
47
50
<summary>Lighthouse</summary>
@@ -61,7 +64,7 @@ We currently support Lighthouse, Prysm, Teku and Lodestar's keystores so it's ea
61
64
#### Config:
62
65
```toml
63
66
[signer]
64
-
[signer.loader]
67
+
[signer.local.loader]
65
68
format = "lighthouse"
66
69
keys_path = "keys"
67
70
secrets_path = "secrets"
@@ -84,7 +87,7 @@ We currently support Lighthouse, Prysm, Teku and Lodestar's keystores so it's ea
@@ -107,7 +110,7 @@ We currently support Lighthouse, Prysm, Teku and Lodestar's keystores so it's ea
107
110
#### Config:
108
111
```toml
109
112
[signer]
110
-
[signer.loader]
113
+
[signer.local.loader]
111
114
format = "teku"
112
115
keys_path = "keys"
113
116
secrets_path = "secrets"
@@ -128,8 +131,7 @@ We currently support Lighthouse, Prysm, Teku and Lodestar's keystores so it's ea
128
131
129
132
#### Config:
130
133
```toml
131
-
[signer]
132
-
[signer.loader]
134
+
[signer.local.loader]
133
135
format = "lodestar"
134
136
keys_path = "keys"
135
137
secrets_path = "secrets/password.txt"
@@ -140,6 +142,16 @@ We currently support Lighthouse, Prysm, Teku and Lodestar's keystores so it's ea
140
142
:::
141
143
</details>
142
144
145
+
### Remote signer
146
+
147
+
You might choose to use an external service to sign the transactions. For now, we support Web3Signer but we're working on adding support for additional signers.
148
+
149
+
The parameters needed for the remote signer are:
150
+
151
+
```toml
152
+
[signer.remote]
153
+
url = "https://remote.signer.url"
154
+
```
143
155
144
156
## Custom module
145
157
We currently provide a test module that needs to be built locally. To build the module run:
0 commit comments