From fbb72c0a3cfe3e1ab84c226cd1775f3abdc57975 Mon Sep 17 00:00:00 2001 From: quasystaty <121364949+quasystaty1@users.noreply.github.com> Date: Fri, 26 Apr 2024 17:23:17 +0300 Subject: [PATCH] Chore(docs): fix go-cli commands (#56) ## Description changes to current commands ## Motivation and Context Our official docs has commands that does not work ## Types of changes - [x] Edits to existing documentation - [ ] Changing documentation structure (relocating existing files, ensure redirects exist) - [ ] Stylistic changes (provide screenshots above) --------- Co-authored-by: jesse snyder --- docs/developer/tutorials/1-using-astria-go-cli.md | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/docs/developer/tutorials/1-using-astria-go-cli.md b/docs/developer/tutorials/1-using-astria-go-cli.md index 59d8103e..e58af8ed 100644 --- a/docs/developer/tutorials/1-using-astria-go-cli.md +++ b/docs/developer/tutorials/1-using-astria-go-cli.md @@ -102,6 +102,7 @@ just clean-restart ### Start the Local Astria Sequencer ```bash +astria-go dev clean astria-go dev init astria-go dev run --local ``` @@ -115,8 +116,9 @@ additional genesis information to work with the remote sequencer. Run the following using the Astira cli: ```bash +astria-go dev clean astria-go dev init -astria-go sequencer get-blockheight +astria-go sequencer blockheight --url=https://rpc.sequencer.dusk-4.devnet.astria.org ``` Then, open the `geth-genesis-local.json` file and update the chain ID and rollup @@ -145,6 +147,7 @@ Then initialized and start Geth: ```bash # in go-etherium dir +just clean just init just run ``` @@ -162,8 +165,9 @@ When running against the remote sequencer, you will also need to create a new sequencer account. ```bash +astria-go dev clean astria-go dev init -astria-go sequencer create-account +astria-go sequencer createaccount ``` Navigate to the `~/.astria` directory. If you have run the commands shown above, you should find a `default` directory. @@ -218,7 +222,8 @@ just generate-transactions If everything worked correctly you see the transactions going through in both the `forge` script and in the `conductor` and `composer` windows in the go cli. -:::note +:::info + These test transactions should work if you are running everything locally with `astria-go dev run --local` or if you are running against a remote sequencer with `astria-go dev run --remote`. If test transactions are not going through