From dde46b6a4869ccc6d0c98830912713f011c1cbe0 Mon Sep 17 00:00:00 2001 From: Olexandr88 Date: Wed, 24 Sep 2025 14:08:59 +0300 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 606a400..938fcf4 100644 --- a/README.md +++ b/README.md @@ -108,7 +108,7 @@ In order to make a deposit and start an ETH validator, you need to make an on-ch You will be presented with two options for data export type: -1. **JSON file for Ethereum Launchpad (default)** - if you choose this option, the CLI will create a `deposit-data-{timestamp}.json` file containing an array of objects mapping to the set of validators you want to create. You can take this `.json` file and drop it directly into the [Launchpad](https://launchpade.ethereum.org). +1. **JSON file for Ethereum Launchpad (default)** - if you choose this option, the CLI will create a `deposit-data-{timestamp}.json` file containing an array of objects mapping to the set of validators you want to create. You can take this `.json` file and drop it directly into the [Launchpad](https://launchpad.ethereum.org). 2. **Raw transaction calldata** - if you choose this option, the CLI will create a `deposit-calldata-{timestamp}.json` file which contains an array of objects, each of which has a pubkey (for reference) and the raw transaction calldata which should be included in a transaction to the deposit contract. This is a more advanced option, so care should be taken if you choose it. For example, your deposit transaction's `msg.value` *must* match the amount specified when creating the data. ### 5️⃣ Build Deposit Data