https://github.com/Stizerg/sm-multi-gpu-init

Spacemesh
https://github.com/Stizerg/sm-multi-gpu-init

Last synced: 3 months ago
JSON representation

Spacemesh

• Host: GitHub
• URL: https://github.com/Stizerg/sm-multi-gpu-init
• Owner: Stizerg
• License: mit
• Created: 2023-10-23T09:13:57.000Z (over 1 year ago)
• Default Branch: main
• Last Pushed: 2024-03-17T07:39:57.000Z (11 months ago)
• Last Synced: 2024-08-01T10:17:24.916Z (6 months ago)
• Language: Shell
• Size: 5.46 MB
• Stars: 2
• Watchers: 1
• Forks: 1
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

• awesome-spacemesh - sm-multi-gpu-init - GPU init on Ubuntu) (Utilities)

README

        
# sm-multi-gpu-init




For Ubuntu





The script creates files sequentially, each file created by one provider, using all available providers until all files are created.

If one of the providers finishes the job before others, it will start to create the next file without waiting.


Initialization will continue from where it was interrupted.





To start you need to download postcli to the same folder


https://github.com/spacemeshos/post/releases





To generate the key.bin I'm using postkey created by Doge Monster


https://github.com/DogeMonster/shibamesh_post_key_generator/releases


(unfortunately this page isn't available anymore)


The program will generate key.bin and display the node ID you will need to insert into the script (hex)





Also you need to make sure that for new POST you are using the latest Highest ATX


If you updating the script you need to use the same atx as before.







The section below about the nonce is obsolete, starting from version 1.1.0 the script doesn't create subfolders and you don't need to merge files manually


If you updating the script in the middle of creating the files you still need to check for lowest nonce.


## Merging files

If you used previous version of the script and when the job is done you got multiple folders with files, you will need to merge all .bin files into one folder.


You also need to copy postdata_metadata.json with lowest "NonceValue".


To make it easy you can use any HEX calculator.


For example this one: https://www.calculator.net/hex-calculator.html


Lets say in your postdata_metadata.json files you have values:


"NonceValue": "000000000b53681ee56a5966681182e4" (file in 0)


and


"NonceValue": "0000000002d053f72a322196f61849e5" (file in 1)


Using simple substruction 000000000b53681ee56a5966681182e4 – 0000000002d053f72a322196f61849e5


you will get this result:


Hex value:


000000000b53681ee56a5966681182e4 – 0000000002d053f72a322196f61849e5 = BB38380000000000


Decimal value:


3.5051676471105E+27 – 8.7082310592693E+26 = 2.6343445411835E+27


Positive result means the second value is smaller, negative result means the first value is smaller.

In this case the second nonce value is smaller and we need to copy the json file from folder 1.


If you copy this values manually ***don't forget to copy "Nonce" too.***











Happy smeshing!