From 15afbfee56d221989eead5f68a1616edc4222b72 Mon Sep 17 00:00:00 2001 From: MarcusWentz Date: Fri, 29 Sep 2023 15:47:29 -0400 Subject: [PATCH 1/2] proposer + prover private key format and status log command to find errors --- .../pages/docs/guides/enable-a-proposer.mdx | 23 ++++++++++++++++--- .../pages/docs/guides/enable-a-prover.mdx | 21 +++++++++++++++-- 2 files changed, 39 insertions(+), 5 deletions(-) diff --git a/packages/website/pages/docs/guides/enable-a-proposer.mdx b/packages/website/pages/docs/guides/enable-a-proposer.mdx index 22407398590..b7f75120086 100644 --- a/packages/website/pages/docs/guides/enable-a-proposer.mdx +++ b/packages/website/pages/docs/guides/enable-a-proposer.mdx @@ -57,6 +57,15 @@ nano .env Set the following environment variables to enable your node as a proposer: + + For `L1_PROPOSER_PRIVATE_KEY` + make sure your private key is in hexadecimal format and with the `0x` prefix removed! + Otherswise you will get this error in your proposer status logs: + ``` + simple-taiko-node-taiko_client_proposer-1 | invalid L1 proposer private key: invalid length, need 256 bits + ``` + + - Set `ENABLE_PROPOSER` to `true` - Set `L1_PROPOSER_PRIVATE_KEY` to the private key of your L1 account (with balance) who will send TaikoL1.proposeBlock transactions - Set `L2_SUGGESTED_FEE_RECIPIENT` to the address of your L2 account who will be the tx fee beneficiary of the L2 blocks that you proposed @@ -69,15 +78,23 @@ If you are not running a local prover, then you can specify a prover from the [p - `PROVER_ENDPOINTS` -### Verify proposer logs +### Check proposer status logs + +To see if your proposer is running correctly or has errors run: + +```sh +docker compose logs -f taiko_client_proposer +``` + +### See proposed blocks -Run this command to verify you have some proposer logs: +When you run: ```sh docker compose logs -f taiko_client_proposer | egrep "Propose transactions succeeded" ``` -You should see a log if you have proposed a block: `📝 Propose transactions succeeded`. +if your proposer successfully proposed a block, your logs should show: `📝 Propose transactions succeeded`. You can check all commands to see proposer logs in the [node runner manual](/docs/manuals/node-runner-manual#view-client-proposer-logs). diff --git a/packages/website/pages/docs/guides/enable-a-prover.mdx b/packages/website/pages/docs/guides/enable-a-prover.mdx index c558ff92e84..ac35465b3d7 100644 --- a/packages/website/pages/docs/guides/enable-a-prover.mdx +++ b/packages/website/pages/docs/guides/enable-a-prover.mdx @@ -54,6 +54,15 @@ nano .env Open the `.env` file and set the following environment variables to enable your node as a prover: + + For `L1_PROVER_PRIVATE_KEY` + make sure your private key is in hexadecimal format and with the `0x` prefix removed! + Otherswise you will get this error in your prover status logs: + ``` + simple-taiko-node-taiko_client_prover_relayer-1 | invalid L1 prover private key: invalid length, need 256 bits + ``` + + - Set `ENABLE_PROVER` to `true` - Set `L1_PROVER_PRIVATE_KEY` to your L1 account private key (with balance of TTKOj on TaikoL1), we will the public key of this account in the next Steps @@ -85,15 +94,23 @@ Finally, click the **Write** button. > Note: If you were already running a prover from your address when you approved TaikoL1 as a spender, the contract may directly drain up to the approved amount of TTKOj from your wallet to use as bond for proving. This may cause `depositTaikoToken` transactions to fail. +### Check prover status logs + +To see if your prover is running correctly or has errors run: + +```sh +docker compose logs -f taiko_client_prover_relayer +``` + ### Verify prover logs -Run this command to verify you have some prover logs: +When you run: ```sh docker compose logs -f taiko_client_prover_relayer | egrep "block proof was|proof submission error|Block proven" ``` -You should see logs like this if it was successful: +if your prover has successfully proven a block, your logs should show: - `💰 Your block proof was accepted` means you successfully submitted a proof and your bond is returned. - `✅ Block proven` means a proposed block was successfully proved on TaikoL1 (by anyone). From aa867d25625bb631de948ec2299bd944741b6644 Mon Sep 17 00:00:00 2001 From: Roger <50648015+RogerLamTd@users.noreply.github.com> Date: Fri, 29 Sep 2023 14:55:21 -0700 Subject: [PATCH 2/2] typos --- packages/website/pages/docs/guides/enable-a-proposer.mdx | 2 +- packages/website/pages/docs/guides/enable-a-prover.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/packages/website/pages/docs/guides/enable-a-proposer.mdx b/packages/website/pages/docs/guides/enable-a-proposer.mdx index b7f75120086..fb800dc2839 100644 --- a/packages/website/pages/docs/guides/enable-a-proposer.mdx +++ b/packages/website/pages/docs/guides/enable-a-proposer.mdx @@ -60,7 +60,7 @@ Set the following environment variables to enable your node as a proposer: For `L1_PROPOSER_PRIVATE_KEY` make sure your private key is in hexadecimal format and with the `0x` prefix removed! - Otherswise you will get this error in your proposer status logs: + Otherwise you will get this error in your proposer status logs: ``` simple-taiko-node-taiko_client_proposer-1 | invalid L1 proposer private key: invalid length, need 256 bits ``` diff --git a/packages/website/pages/docs/guides/enable-a-prover.mdx b/packages/website/pages/docs/guides/enable-a-prover.mdx index ac35465b3d7..d060819452e 100644 --- a/packages/website/pages/docs/guides/enable-a-prover.mdx +++ b/packages/website/pages/docs/guides/enable-a-prover.mdx @@ -57,7 +57,7 @@ Open the `.env` file and set the following environment variables to enable your For `L1_PROVER_PRIVATE_KEY` make sure your private key is in hexadecimal format and with the `0x` prefix removed! - Otherswise you will get this error in your prover status logs: + Otherwise you will get this error in your prover status logs: ``` simple-taiko-node-taiko_client_prover_relayer-1 | invalid L1 prover private key: invalid length, need 256 bits ```