Skip to content

Commit 81d122d

Browse files
feat: update Validium doc (#407)
# Description Update the Validium doc, fix outdated configs. ## Linked Issues <!-- If you have any issues this PR is related to, link them here. --> <!-- Check out https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue on how to automate linking a GitHub Issue to a PR. --> ## Additional context --------- Co-authored-by: Sarah Schwartz <[email protected]>
1 parent 480ce61 commit 81d122d

File tree

1 file changed

+42
-40
lines changed

1 file changed

+42
-40
lines changed

content/10.zk-stack/20.running/35.validium.md

Lines changed: 42 additions & 40 deletions
Original file line numberDiff line numberDiff line change
@@ -169,45 +169,47 @@ All the configs can also be set using environment variables instead of `.yaml` f
169169

170170
```yaml
171171
da_client:
172-
avail:
173-
bridge_api_url: https://bridge.somedomain.com
174-
timeout_ms: 10000
175-
full_client:
176-
api_node_url: wss://turing-rpc.avail.so/ws
177-
app_id: 1
178-
max_blocks_to_look_back: 5 (optional)
179-
dispatch_timeout: 180s (optional)
172+
client: Avail
173+
bridge_api_url: https://turing-bridge-api.avail.so
174+
timeout_ms: 20000
175+
avail_client_type: FullClient
176+
api_node_url: wss://turing-rpc.avail.so/ws
177+
app_id: 1
178+
max_blocks_to_look_back: 5 (optional)
179+
dispatch_timeout: 180s (optional)
180180
```
181181

182182
- Gas relay:
183183

184184
```yaml
185185
da_client:
186-
avail:
187-
bridge_api_url: https://bridge.somedomain.com
188-
timeout_ms: 10000
189-
gas_relay:
190-
gas_relay_api_url: https://gas-relay.domain.com
191-
max_retries: 5
186+
client: Avail
187+
bridge_api_url: https://turing-bridge-api.avail.so
188+
timeout_ms: 20000
189+
avail_client_type: GasRelay
190+
gas_relay_api_url: https://staging.turbo-api.availproject.org
191+
max_retries: 15
192192
```
193193

194-
2. Add the following block to the `secrets.yaml`:
194+
2. Add the following block to the `secrets.yaml`:
195195
- Full client
196196

197197
```yaml
198198
da:
199-
avail:
200-
seed_phrase: YOUR_SEED_PHRASE
199+
client: Avail
200+
seed_phrase: YOUR_SEED_PHRASE
201201
```
202202

203203
- Gas relay
204204

205205
```yaml
206206
da:
207-
avail:
208-
gas_relay_api_key: YOUR_API_KEY
207+
client: Avail
208+
gas_relay_api_key: YOUR_API_KEY
209209
```
210210

211+
3. Make sure to fund the account with enough Avail tokens to cover the gas costs of the transactions.
212+
211213
::
212214

213215
::panel{label="How to configure Celestia client?"}
@@ -216,21 +218,23 @@ All the configs can also be set using environment variables instead of `.yaml` f
216218

217219
```yaml
218220
da_client:
219-
celestia:
220-
api_node_url: https://api-node.somedomain.com
221-
namespace: 000000000000000000000000000000000000ca1de12a5e2d5beb9ba9
222-
chain_id: mocha-4
223-
timeout_ms: 30000
221+
client: Celestia
222+
api_node_url: https://api-node.somedomain.com
223+
namespace: 000000000000000000000000000000000000ca1de12a5e2d5beb9ba9
224+
chain_id: mocha-4
225+
timeout_ms: 30000
224226
```
225227

226228
2. Add the following block to the `secrets.yaml`:
227229

228230
```yaml
229231
da:
230-
celestia:
231-
private_key: YOUR_PRIVATE_KEY
232+
client: Celestia
233+
private_key: YOUR_PRIVATE_KEY
232234
```
233235

236+
3. Make sure to fund the account with enough Celestia tokens to cover the gas costs of the transactions.
237+
234238
::
235239

236240
::panel{label="How to configure EigenDA client?"}
@@ -239,28 +243,26 @@ All the configs can also be set using environment variables instead of `.yaml` f
239243

240244
```yaml
241245
da_client:
242-
eigen:
243-
disperser_rpc: https://disperser-holesky.eigenda.xyz:443
244-
settlement_layer_confirmation_depth: 3
245-
eigenda_eth_rpc: https://eth-rpc.somedomain.com # optional
246-
eigenda_svc_manager_address: 0x1111111111111111111111111111111111111111
247-
wait_for_finalization: false
248-
authenticated: false
249-
points_source_url:
250-
g1_url: https://github.com/Layr-Labs/eigenda-proxy/raw/refs/heads/main/resources/g1.point
251-
g2_url: https://github.com/Layr-Labs/eigenda-proxy/raw/refs/heads/main/resources/g2.point.powerOf2
252-
# or, alternatively
253-
# points_source_path: /path/to/points
246+
client: Eigen
247+
disperser_rpc: https://disperser-holesky.eigenda.xyz:443
248+
eigenda_eth_rpc: https://ethereum-holesky-rpc.publicnode.com (only necessary if Holesky disperser is used)
249+
cert_verifier_router_addr: 0xDD735AFFe77A5ED5b21ED47219f95ED841f8Ffbd
250+
operator_state_retriever_addr: 0x003497Dd77E5B73C40e8aCbB562C8bb0410320E7
251+
registry_coordinator_addr: 0x53012C69A189cfA2D9d29eb6F19B32e0A2EA3490
252+
blob_version: 0
254253
```
255254

256255
2. Add the following block to the `secrets.yaml`:
257256

258257
```yaml
259258
da:
260-
eigen:
261-
private_key: YOUR_PRIVATE_KEY
259+
client: Eigen
260+
private_key: YOUR_PRIVATE_KEY
262261
```
263262

263+
3. Deposit the tokens to the Payment Vault on the L1. See the
264+
[EigenDA documentation](https://docs.eigencloud.xyz/products/eigenda/integrations-guides/quick-start/v2/#on-demand-data-dispersal) for more details.
265+
264266
::
265267

266268
::panel{label="Is it possible to transition from Validium to Rollup and vice versa?"}

0 commit comments

Comments
 (0)