!QOQfggNBhPYxvbQdNm:matrix.org

Akash Lobby

165 Members
General chat and conversations 17 Servers

Load older messages


Timestamp Message
30 Mar 2020
18:29:16@bryanchriswhite:matrix.orgbryanchriswhite you can always append -h to the end of a command to get specific help (e.g. akash -h)
19:35:25@bitcoinera:matrix.orgbitcoineraOh, thank you so much. Let me try that
19:37:52@bitcoinera:matrix.orgbitcoinera

I get this when I do akash keys create -h

Usage:
  akash keys [command]

Available Commands:

  add         Add an encrypted private key (either newly generated or recovered), encrypt it, and save to disk
  delete      Delete the given keys
  export      Export private keys
  import      Import private keys into the local keybase
  list        List all keys
  migrate     Migrate keys from the legacy (db-based) Keybase
  mnemonic    Compute the bip39 mnemonic for some input entropy
  parse       Parse address from hex to bech32 and vice versa
  show        Show key info for the given name
19:38:00@bitcoinera:matrix.orgbitcoineraYes, probably I have the wrong version
19:40:37@bitcoinera:matrix.orgbitcoinera

akash version outputs master

git rev-parse HEAD in the repo root outputs ffb270b53be675b2404d157f42caea97d16747bc

19:41:36@bitcoinera:matrix.orgbitcoinera

akash -h outputs all this:

Akash Network CLI Utility.

Akash is a peer-to-peer marketplace for computing resources and
a deployment platform for heavily distributed applications.
Find out more at https://akash.network

Usage:
  akash [command]

Available Commands:
  config      Create or query an application CLI configuration file
  help        Help about any command
  keys        Add or view local private keys
  query       Querying subcommands
  rest-server Start LCD (light-client daemon), a local REST server
  status      Query remote node for status
  tx          Transactions subcommands
  version     Print the app version

Flags:
  -e, --encoding string   Binary encoding (hex|b64|btc) (default "hex")
  -h, --help              help for akash
      --home string       directory for config and data (default "/root/.akash")
  -o, --output string     Output format (text|json) (default "text")
      --trace             print out full stack trace on errors

Use "akash [command] --help" for more information about a command.
19:41:54@bitcoinera:matrix.orgbitcoineraThank you so much for your help 🙏
31 Mar 2020
11:07:42@bryanchriswhite:matrix.orgbryanchriswhite bitcoinera: the output is trying to tell you where you went wrong... it looks like the version of the cli that you have installed has a subcommand akash keys add but not akash keys delete. I guess they changed some stuff since the tutorial was written.
11:09:17@bryanchriswhite:matrix.orgbryanchriswhitethat commit hash is HEAD of master on github so you're on the bleeding edge :D
11:10:06@bryanchriswhite:matrix.orgbryanchriswhiteyou could alternatively checkout the most recent release candidate which is likely be more stable (and I think uses the old cli)
11:15:16@bryanchriswhite:matrix.orgbryanchriswhite

The simplest way to do that is probably git checkout 5ac4f29b6. That's the hash of the tag v0.5.5-rc3, which you can see here: https://github.com/ovrclk/akash/commits/v0.5.5-rc3.

Alternatively you can fetch the tags from github git fetch -t origin && git rev-parse v0.5.5-rc3).

11:16:39@bryanchriswhite:matrix.orgbryanchriswhite bitcoinera: ^
11:46:14@bryanchriswhite:matrix.orgbryanchriswhite

bitcoinera: the output is trying to tell you where you went wrong... it looks like the version of the cli that you have installed has a subcommand akash keys add but not akash keys delete. I guess they changed some stuff since the tutorial was written.

Should say create instead of delete

14:58:31@bitcoinera:matrix.orgbitcoineraOh wow, thank you so much! I'll try this real soon!
15:08:39@bitcoinera:matrix.orgbitcoinera

OK, at the end I just did akash keys add master. Also the last release has no create anymore 😆

{
  "name": "master",
  "type": "local",
  "address": "akash1pz20sgjqxvcvz8t45rcxes657fwuv8qzd2frj3",
  "pubkey": "akashpub1addwnpepq29j8ltmcveutj0dzqw28aggvw37wurfme886sc7q6v99teh3gfg6t3pqdq",
  "mnemonic": "xxxx"
}
15:09:10@bitcoinera:matrix.orgbitcoineracan I join the garuda testnet now? 🤩 How do I do it? Where is the genesis
15:12:00@bitcoinera:matrix.orgbitcoineraIs this one the same than garuda? I guess not. It says beacon: https://github.com/ovrclk/net/blob/master/055/genesis.json
15:13:43@bitcoinera:matrix.orgbitcoineraAh no wait. I think that is the one right? Four months ago: https://akash.vitwit.com/ Sorry, it took me a while to find it 😅
15:18:08@bryanchriswhite:matrix.orgbryanchriswhite@bitcoinera:matrix.org: I think that is for the alpha network which is pre switch to cosmos-sdk
15:31:23@bitcoinera:matrix.orgbitcoineracan someone please pass me the genesis.json for the garuda testnet?
15:39:45@bryanchriswhite:matrix.orgbryanchriswhite I don't think it exists yet. You would also need a seed peer address
15:44:48@bryanchriswhite:matrix.orgbryanchriswhite That would go in your akashd config in seeds = "". It's a comma separated list of <id>@<ip>:<port> where id is the tendermint node id and the ip/port are the akashd grpc server
15:46:35@bryanchriswhite:matrix.orgbryanchriswhite Again, I'm not sure if this information is already available anywhere for testnet.
15:47:42@bryanchriswhite:matrix.orgbryanchriswhiteMy guess is not
16:13:57@bitcoinera:matrix.orgbitcoineraOh I see
16:14:20@bitcoinera:matrix.orgbitcoineraIt is still in the very early stages as I understand. Still a private-beta testnet
1 Apr 2020
11:55:23@bryanchriswhite:matrix.orgbryanchriswhite bitcoinera: fwiw I also just discovered that the community faucet only accepts "legacy" addresses (the legacy cli calls them public keys). Legacy seems to be at least <= v0.5.5-rc3 and master includes a subcommand for migrating legacy keys, akash keys migrate.
11:55:35@bryanchriswhite:matrix.orgbryanchriswhite * bitcoinera: fwiw I also just discovered that the community faucet only accepts "legacy" addresses (the cli calls them public keys). Legacy seems to be at least <= v0.5.5-rc3 and master includes a subcommand for migrating legacy keys, akash keys migrate.
12:05:29@bryanchriswhite:matrix.orgbryanchriswhite * bitcoinera: fwiw I also just discovered that the community faucet only accepts "legacy" addresses (the legacy cli calls them public keys). Legacy seems to be at least <= v0.5.5-rc3 and master includes a subcommand for migrating legacy keys, akash keys migrate.
14:13:49@bitcoinera:matrix.orgbitcoineraoh, very interesting. Thank you! Yes, it seems this protocol is still in the very early stages...

There are no newer messages yet.


Back to Room List