Identity generation is too difficult now
The latest version of v0.26.3 I use
Difficulty factor 36
It’s been 34. It’s hard to reach 36
I want to know
If the identity is generated
Can multiple tokens generate 6 key files here?
Otherwise, it’s hard to generate identity every time
Its a matter of luck so why don’t you let it finish.
So now I want to know
If the identity is generated
Can multiple tokens generate 6 key files here?
Otherwise, it’s hard to generate identity every time
When identity is generated it will show the message on the screen as shown in documentation
You will have to take backup of your identity to create another identity or give location of another folder with <executable in linux/windows> authorize storagenode <auth-token> --identity-dir <drive letter>
You would have to generate identity for every node the same way. It will take variable time to generate it. Alternatively you can use flag batch-generate (I haven’t used it so you might have to test it)
PS: Remember to take backup of identity after its created. If you lose your identity you lose your node
I spent abou 20-30min for identity generation with difficult 36 on 4 core CPU.
@pony I look into your screenshot and see that you are using dual cpu motherboard, you can try
--concurrency 12 or 24 (default concurrency is 4)
1 Like
How can I use it?
What are the commands under windows?
Forgive me for being a programming idiot. I don’t know how to input commands
I just copied the official documents directly
Thank you for your advice
1 Like
Here is example:
./identity_windows_amd64.exe create storagenode --concurrency 12
For what it’s worth this is precisely the intention of this process. It’s meant to prevent people from quickly spinning up lots of nodes.
3 Likes
This is gold! I knew there was a reason to get a 16 core CPU after all.