From 6e4bd431e2e7f5f98194c27cc03cd3600e9114e0 Mon Sep 17 00:00:00 2001 From: Sam Ricotta Date: Wed, 8 Jan 2025 19:30:21 +1100 Subject: [PATCH 1/2] Update finality-provider-operation.md --- docs/finality-provider-operation.md | 29 ++++++++++++++++++++++++++--- 1 file changed, 26 insertions(+), 3 deletions(-) diff --git a/docs/finality-provider-operation.md b/docs/finality-provider-operation.md index 3ad8ac6..77a78b9 100644 --- a/docs/finality-provider-operation.md +++ b/docs/finality-provider-operation.md @@ -504,8 +504,6 @@ fpd create-finality-provider \ --home ./fpHome ``` - - Required parameters: - `--chain-id`: The Babylon chain ID (e.g., for the testnet, `bbn-test-5`) - `--eots-pk`: The EOTS public key maintained by the connected EOTS manager @@ -528,6 +526,31 @@ Optional parameters: - `--daemon-address`: RPC address of the finality provider daemon (default: `127.0.0.1:12581`) + +Alternatively, you can create a finality provider by providing a JSON file +with the finality provider details, similar to the following: + +```json +{ + "keyName": "The unique key name of the finality provider's Babylon account", + "chainID": "The identifier of the consumer chain", + "passphrase": "The pass phrase used to encrypt the keys", + "commissionRate": "The commission rate for the finality provider, e.g., 0.05"", + "moniker": ""A human-readable name for the finality provider", + "identity": "A optional identity signature", + "website": "Validator's (optional) website", + "securityContract": "Validator's (optional) security contact email", + "details": "Validator's (optional) details", + "eotsPK": "The hex string of the finality provider's EOTS public key" +} +``` + +To create a finality provider using the JSON file, you can use the following command: + +```shell +fpd create-finality-provider --json-file +``` + Upon successful creation, the command will return a JSON response containing your finality provider's details: @@ -673,7 +696,7 @@ When you are ready to withdraw your rewards, you have the option first to set the address to withdraw your rewards to. ```shell -fpd set-withdraw-addr --from +fpd set-withdraw-addr --from --keyring-backend test --home --fees ``` From 4673b262c883b48c9fabd010d50c276a23340596 Mon Sep 17 00:00:00 2001 From: Sam Ricotta Date: Wed, 8 Jan 2025 19:50:48 +1100 Subject: [PATCH 2/2] Update finality-provider-operation.md --- docs/finality-provider-operation.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/finality-provider-operation.md b/docs/finality-provider-operation.md index 77a78b9..7b6d937 100644 --- a/docs/finality-provider-operation.md +++ b/docs/finality-provider-operation.md @@ -535,8 +535,8 @@ with the finality provider details, similar to the following: "keyName": "The unique key name of the finality provider's Babylon account", "chainID": "The identifier of the consumer chain", "passphrase": "The pass phrase used to encrypt the keys", - "commissionRate": "The commission rate for the finality provider, e.g., 0.05"", - "moniker": ""A human-readable name for the finality provider", + "commissionRate": "The commission rate for the finality provider, e.g., 0.05", + "moniker": "A human-readable name for the finality provider", "identity": "A optional identity signature", "website": "Validator's (optional) website", "securityContract": "Validator's (optional) security contact email",