@@ -357,6 +357,128 @@ aligned get-user-amount-of-queued-proofs \
357357` ` `
358358
359359
360+ ---
361+
362+ # ## **lock-funds**
363+
364+ # ### Description:
365+
366+ Locks funds in the batcher. Locked balances can be used for proof verification payments but cannot be withdrawn until they are unlocked and the lock period expires.
367+
368+ # ### Command:
369+
370+ ` lock-funds [OPTIONS]`
371+
372+ # ### Options:
373+
374+ - ` --keystore_path < path_to_local_keystore> ` : Path to the local keystore.
375+ - ` --private_key < private_key> ` : User' s wallet private key.
376+ - `--rpc_url <RPC_provider_url>`: User' s Ethereum RPC provider connection address.
377+ - Default: ` http://localhost:8545`
378+ - Mainnet: ` https://ethereum-rpc.publicnode.com`
379+ - Holesky: ` https://ethereum-holesky-rpc.publicnode.com`
380+ - Hoodi: ` https://ethereum-hoodi-rpc.publicnode.com`
381+ - Also, you can use your own Ethereum RPC providers.
382+ - One of the following, to specify which Network to interact with:
383+ - ` --network < working_network_name> ` : Network name to interact with.
384+ - Default: ` devnet`
385+ - Possible values: ` devnet` , ` holesky` , ` mainnet` , ` hoodi`
386+ - For a custom Network, you must specify the following parameters:
387+ - ` --aligned_service_manager < aligned_service_manager_contract_address> `
388+ - ` --batcher_payment_service < batcher_payment_service_contract_address> `
389+ - ` --batcher_url < batcher_websocket_url> `
390+
391+ # ### Example:
392+
393+ ` ` ` bash
394+ aligned lock-funds \
395+ --network holesky \
396+ --rpc_url https://ethereum-holesky-rpc.publicnode.com \
397+ --keystore_path < KEYSTORE_PATH>
398+ ` ` `
399+
400+ ---
401+
402+ # ## **unlock-funds**
403+
404+ # ### Description:
405+
406+ Unlocks funds from the batcher. After calling this command, users must wait for the lock period before they can withdraw their funds using ` withdraw-funds` .
407+
408+ # ### Command:
409+
410+ ` unlock-funds [OPTIONS]`
411+
412+ # ### Options:
413+
414+ - ` --keystore_path < path_to_local_keystore> ` : Path to the local keystore.
415+ - ` --private_key < private_key> ` : User' s wallet private key.
416+ - `--rpc_url <RPC_provider_url>`: User' s Ethereum RPC provider connection address.
417+ - Default: ` http://localhost:8545`
418+ - Mainnet: ` https://ethereum-rpc.publicnode.com`
419+ - Holesky: ` https://ethereum-holesky-rpc.publicnode.com`
420+ - Hoodi: ` https://ethereum-hoodi-rpc.publicnode.com`
421+ - Also, you can use your own Ethereum RPC providers.
422+ - One of the following, to specify which Network to interact with:
423+ - ` --network < working_network_name> ` : Network name to interact with.
424+ - Default: ` devnet`
425+ - Possible values: ` devnet` , ` holesky` , ` mainnet` , ` hoodi`
426+ - For a custom Network, you must specify the following parameters:
427+ - ` --aligned_service_manager < aligned_service_manager_contract_address> `
428+ - ` --batcher_payment_service < batcher_payment_service_contract_address> `
429+ - ` --batcher_url < batcher_websocket_url> `
430+
431+ # ### Example:
432+
433+ ` ` ` bash
434+ aligned unlock-funds \
435+ --network holesky \
436+ --rpc_url https://ethereum-holesky-rpc.publicnode.com \
437+ --keystore_path < KEYSTORE_PATH>
438+ ` ` `
439+
440+ ---
441+
442+ # ## **withdraw-funds**
443+
444+ # ### Description:
445+
446+ Withdraws a specified amount from the user' s balance in the batcher. This command can only be used after the balance has been unlocked using `unlock-funds` and the lock period has expired.
447+
448+ #### Command:
449+
450+ `withdraw-funds [OPTIONS] --amount <amount_to_withdraw>`
451+
452+ #### Options:
453+
454+ - `--keystore_path <path_to_local_keystore>`: Path to the local keystore.
455+ - `--private_key <private_key>`: User' s wallet private key.
456+ - ` --rpc_url < RPC_provider_url> ` : User' s Ethereum RPC provider connection address.
457+ - Default: `http://localhost:8545`
458+ - Mainnet: `https://ethereum-rpc.publicnode.com`
459+ - Holesky: `https://ethereum-holesky-rpc.publicnode.com`
460+ - Hoodi: `https://ethereum-hoodi-rpc.publicnode.com`
461+ - Also, you can use your own Ethereum RPC providers.
462+ - `--amount <amount (ether)>`: Amount of Ether to withdraw.
463+ - One of the following, to specify which Network to interact with:
464+ - `--network <working_network_name>`: Network name to interact with.
465+ - Default: `devnet`
466+ - Possible values: `devnet`, `holesky`, `mainnet`, `hoodi`
467+ - For a custom Network, you must specify the following parameters:
468+ - `--aligned_service_manager <aligned_service_manager_contract_address>`
469+ - `--batcher_payment_service <batcher_payment_service_contract_address>`
470+ - `--batcher_url <batcher_websocket_url>`
471+
472+ #### Example:
473+
474+ ```bash
475+ aligned withdraw-funds \
476+ --network holesky \
477+ --rpc_url https://ethereum-holesky-rpc.publicnode.com \
478+ --amount 0.5ether \
479+ --keystore_path <KEYSTORE_PATH>
480+ ```
481+
360482---
361483
362484### **verify-agg-proof**
0 commit comments