I restarted my auth using safe auth restart
Then I ran safe auth unlock
using the same passphrase/password as before. That succeeded. I do the same NRS command and still get the InvalidSignature error I saw before.
I tried creating an NRS with wydileie1 as the short name, and it succeeded. As a note to the devs, I accidentally forgot to put the 1, and tried to create wydileie when it already existed, and it seemed to just hang indefinitely. It was running for at least 5, probably 10 minutes.
I don’t know what that is… the only secret key I’d noted was the one I created a lump of credit on to gift others… which I expect is different key. Not sure I’ve seen CLI key declared for noting unless that occurs at the setup.
Good feedback on the waiting to join from many of you - we didn’t anticipate it would be a huge issue and expected it to fill faster but clearly the combination of slow uploads & us needing to up the size of our D.O. nodes at the last minute (due to an issue we suspected would occur if left too small) means that this has become an issue.
Spoke with a cpl of the guys in the team & we agree we will implement a way to auto retry you if Network is not accepting, or something along those lines
I think it’s just a slight delay caught me… the absence of that try again message had my hopes up… I don’t know if Southside turned off verbose logging or if that is what we would see… but expect to wait a moment until something is either ok or “try again”.
I’m sorry for confusing you, when the CLI is self-authorised with authd what it gets is its own keypair preloaded with some test-coins, this keypair is stored at ~/.safe/cli/credentials and it uses it for every write operation you execute with CLI. Running $ safe keys balance will check the current balance of that key, so I was just wondering if perhaps the error was incorrect and the issue you are facing is that you have not more funds…I doubt that’s the case but just asking if you can confirm
Inability to join network as node is a little disappointing.
It makes testing harder (only few users can give feedback).
But look at it other way: network is running and continues to grow.
This is the final goal, right?
I agree, except for the slow throughput many of us experiencing, this is how Safe network works, no new nodes are allowed unless the network needs it, once resources are needed more nodes are allowed to join. As you say it’s harder to test but we are testing the real flow of events instead of trying some shortcuts which may prevent us from facing potential issues in the natural flow/progress of things.
$ cat ~/.safe/cli/credentials
cat: /home/safe/.safe/cli/credentials: No such file or directory
I don’t understand it but the same terminal that was apparently stuck; if I stop the request ctrl-c and try again, get no luck but a new terminal does work. Perhaps just an oddity of what is occurring… or perhaps I’m too tired now as well. I’ll try logging out and with a new account tomorrow.
I think I must have borked something up on mine. I don’t have any credentials in my .safe/cli/credentials file, trying to send coins just hangs, and I can’t change my NRS entries. Maybe I’ll try to start fresh tomorrow.
Ok, well, it seems we have some better clues here, not sure what could have happened you lost that file. Re-authorising CLI with same passphrase and password should re-generate it.
Thank you all guys who participate/d in this project for you great and hard work. I am not friend with command line, but I hope that mine node will join the testnet soon.
I do have the file, unlike David, but there is nothing inside it. I removed it and then did an auth restart and unlock, and it did not regenerate the file.
Hi,
I had a similar problem. Looks like your path env. Variable isnt bring appended. If you type:
echo $PATH
You should see an entry for safe - I suspect you wont. If not try typing:
export PATH=$PATH:/Users/your.name/,safe/cli
