Any command elicits this response. How to solve it?
#Could not find wallet at /root/.local/share/namada/shielded-expedition.b40d8e9055
violet bolt
The application panicked (crashed).
Message: Could not find wallet at /root/.local/share/namada/shielded-expedition.b40d8e9055.
Location: crates/apps/src/lib/cli/context.rs:152
Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
violet bolt
<@&833650360345559091> <@&1059560907589566464> Please note. I have been unable to connect to the network for 12 hours.
All, any, commands I enter result in this error.
drifting glade
<@&833650360345559091> <@&1059560907589566464> Please note. I have been unable ...
What steps have you taken as far as setting up a node locally on your machine?
vernal escarp
Have you run join network?
violet bolt
What steps have you taken as far as setting up a node locally on your machine?
To get the node running I had to grab the wallet.toml file from a previous test network. Just to have it in the shielded-expedition.b40d8e9055 directory. Only thanks to this file, I was able to start the node and create a new address.
All any other commands until I took the old wallet.toml file ended up with the same problem I described above.
violet bolt
Have you run `join network`?
Yes, of course. This command and any other commands resulted in the same problem (which I wrote about above).
I[2024-02-02|13:01:50.496] Version info module=main tendermint_version=0.38.5 abci=2.0.0 block=11 p2p=8 commit_hash= I[2024-02-02|13:01:50.496] This node is not a validator module=consensus addr=FB107F496046F9291F19B5455F99B1BE37A9A5B8 pubKey=PubKeyEd25519{F470B0D9729E86FE700F4A34CAA4AD541837128A9C3A843240018EE0EA66E936} I[2024-02-02|13:01:50.504] service start module=main msg="Starting Node service" impl=Node I[2024-02-02|13:01:50.505] service start module=statesync msg="Starting StateSync service" impl=StateSync I[2024-02-02|13:01:50.505] service start module=mempool msg="Starting Mempool service" impl=Mempool I[2024-02-02|13:01:50.505] service start module=blocksync msg="Starting Reactor service" impl=Reactor I[2024-02-02|13:01:50.505] service start module=blocksync msg="Starting BlockPool service" impl=BlockPool I[2024-02-02|13:01:50.505] service start module=consensus msg="Starting Consensus service" impl=ConsensusReactor I[2024-02-02|13:01:50.505] Reactor module=consensus waitSync=true I[2024-02-02|13:01:50.505] service start module=evidence msg="Starting Evidence service" impl=Evidence I[2024-02-02|13:01:50.505] serve module=rpc-server msg="Starting RPC HTTP server on 127.0.0.1:26657" I[2024-02-02|13:01:50.506] Started node module=main nodeInfo="{ProtocolVersion:{P2P:8 Block:11 App:0} DefaultNodeID:e68a282cb937eba73bf7485700e76d5c7e20c127 ListenAddr:tcp://0.0.0.0:26656 Network:shielded-expedition.b40d8e9055 Version:0.38.5 Channels:40202122233038606100 Moniker:technodrome-v0.31.0 Other:{TxIndex:off RPCAddress:tcp://127.0.0.1:26657}}"
But now there's a new problem. The node has stopped at this stage and there are no new logs and errors for three hours already.
drifting glade
To get the node running I had to grab the wallet.toml file from a previous test ...
Do you have the menmonic?
violet bolt
Do you have the menmonic?
First I took the wallet.toml file with old data from past test networks. Without that nothing worked (always got an error that there was no wallet). Then I was able to import my wallet by mnemonic, but for some reason my mnemonic pulled up a completely different wallet address. This is probably due to a different coding system, because I created the address for the expedition through namada wallet in chrome browser, besides I have a mnemonic of 12 words, not 24.
drifting glade
First I took the wallet.toml file with old data from past test networks. Without...
Did you start with the extension to make the account or CLI?
violet bolt
Did you start with the extension to make the account or CLI?
Based on these instructions. I am co-pilot.
drifting glade
Based on these instructions. I am co-pilot.
### CLI BIP39 PASSPHRASE to Extension
# If used a BIP39 passphrase in wallet generation, you can't add it to the extension.
# Here's the solution:
# on a separate machine (rent a cheap VPS by the minute/hour)
# install namada/namadaw
# Recover your wallet with this command:
namadaw --pre-genesis derive --alias 123 --unsafe-dont-encrypt
# Grab the private key from a file:
cat ~/.local/share/namada/pre-genesis/wallet.toml
# Add account to Extension with the private key
That worked, but what to do about the new problem? Node stands still for three hours without moving?