It is as simple as copying the files from the powerful computer to the machine you plan on using for your storage node. In fact, all of the Storj Labs employees have Storj Boxes (https://storj.io/blog/2019/04/introducing-the-new-storj-box-shawn-wilkinson-signature-edition-iii/) which run a Storage node off a raspberry pi and 2 TB hard drive. We all generated our Identities on other machines and copied the files over. When you are generating your identity it is actually a game of luck, section 4.15 of the V3 white paper talks about one of the reasons we need proof of work.
excerpt from section 4.15:
"The goal of the first system is to require a short proof that the storage node operator is invested, through time, stake, or resources. Initially, we are using proof of work. As mentioned in section 4.3, storage nodes require a proof of work as part of identity generation. This helps the network avoid some Sybil attacks , but we glossed over how proof of work diculty is set. We will let Satellite operators set per-Satellite minimum diculty required for new data storage. If a storage node has an identity generated with a lower diculty than the Satellite’s configured minimum, that storage node will not be a candidate for new data. We expect Satellite operators to naturally increase the minimum proof of work diculty requirements over time until a reasonable balance is found. In the case of a changing diculty configuration, Satellites will leave existing data on existing nodes where possible. Other investment proof schemes are possible, such as a form of proof of stake as we proposed in our previous work ."
You won't be notified about changes to this idea.