Identity signing (identity authorize) is not required any more

Node Operators getting started
,
1

Earlier the identity generation required one additional step: Storj satellites accepted Storagenodes only, if they were signed by a specific authority (using identity authorize)

This check is developed during the early beta phase of the network, to control how many storagenodes are joining during beta tests.

I am glad to share that this step (Step 2. Get an Authorization Token - Storj Docs + authorization) is not required any more.

I hope this one makes the Storagenode operation a little more simple…

Docs will be updated soon…

20 Likes
How to get more Token
Back but have some Q's
Problem with Authorise your Storage Node identity
Where is the Request Authorization Token link?
2

That’s moderately exciting!

you know what would be even more exciting? Eliminating the slowness of generating a identity on slow computers!

3

Unfortunately, we couldn’t do that easily.

Search for “proof of work” in storjv3.

2 Likes
4

We obviously need a unique identity but what was the reason for adding this proof of work thing?

5

Protection against Sybil attack

2 Likes
6

C’mon, how often do you have to endure this painful process? Perhaps let it run in the background and I suppose it’ll be done before your current node get full :smiley:

2 Likes
7

By default it uses 4 threads. You can pass number of CPUs you have to speed it up, e.g. --concurrency $(sysctl -n hw.ncpu)