SOST — Mining Launchpad (prototype D)

STEP 1 Choose your system

SOST runs on Linux. On Windows it runs inside WSL2 (a Linux system that Windows installs for you).

Press Win+R, type cmd and press Enter. In the black window run:

Windows command prompt

wsl --install

EXPECTEDIt downloads and installs Ubuntu (2–5 min, needs internet) and asks you to restart.

IF IT FAILSIf Ubuntu does not open after the restart, press Win+R again, type ubuntu and press Enter.

NEXTUbuntu asks for a new username and password. That window is your terminal: continue with step 2.

Open your terminal application and continue with step 2.

macOS is not validated. The current guide only mentions installing dependencies with Homebrew; the install, build and run steps below were validated with apt on Linux / WSL2 only. Until a procedure is tested on macOS, this launchpad does not give macOS commands. Use a Linux machine or a Linux VM, or follow the Getting Started page at your own risk.

STEP 2 Check your resources

Requirements
Memory, mining	8 GB RAM or more (4 GB dataset + 4 GB scratchpad). Several threads share one scratchpad.verified in source: src/pow/convergencex.cpp:48-50 · include/sost/params.h:847 (CX_SCRATCH_M = 4096) · src/sost-miner.cpp:2482 (“Share 1 scratchpad”)
Memory, node only	About 500 MB. A node verifies blocks without building the 4 GB dataset.documented in the Quick Start; not measured here · O(1) verification: include/sost/pow/convergencex.h:34
CPU	A regular CPU. Use `--threads N` for N cores. No specialised hardware, no pools.
Disk	The source tree, the build and the chain data. NOT DOCUMENTED
Connection	Any connection. The node connects to `seed.sostcore.com:19333`.
Time	About 30 minutes. The build takes 2–5 minutes; the first sync from minutes to a quarter of an hour.

Not enough free memory? See “std::bad_alloc” in step 7. No compatibility is promised beyond what is listed here.

STEP 3 Install the tools and build SOST

No validated macOS commands. The commands below are for Linux / WSL2.

1 · install the build tools

sudo apt update && sudo apt install -y build-essential cmake libssl-dev libsecp256k1-dev git

EXPECTEDIt asks for your password (nothing appears while typing, that is normal) and finishes in 1–2 minutes without red errors.

IF IT FAILSRed text: run the same command again.

NEXTDownload and build SOST.

Run these one at a time, pressing Enter after each:

2 · download the source

git clone https://github.com/Neob1844/sost-core.git

EXPECTEDA folder sost-core is created.

IF IT FAILSgit: command not found: repeat command 1.

NEXTEnter the folder.

3

cd sost-core

4

git fetch --tags

5 · the production release tag

git checkout v30000-final.1

EXPECTEDGit reports that you are at 59a4e666 (“detached HEAD” is normal for a tag).

IF IT FAILSdid not match any file(s): run git fetch --tags again, then this command.

NEXTBuild. Do not build another branch: the tag is the production source.

6

mkdir build && cd build

7

cmake .. -DCMAKE_BUILD_TYPE=Release

EXPECTEDEnds with “Build files have been written to …/build”.

IF IT FAILScmake: command not found, openssl/sha.h or secp256k1.h: No such file: repeat command 1.

NEXTCompile.

8 · compile (2–5 min)

make -j$(nproc)

EXPECTEDLots of text, then [100%] Built target.

IF IT FAILSThe build stops with an error: check the messages for a missing package (step 7), fix it and run the same command again.

NEXTStep 4: start the node. Prefer prebuilt binaries? Use the upgrade guide and check them against the release SHA256SUMS.

STEP 4 Start your node

The node joins the SOST network and downloads the chain. First choose your own RPC password and keep it in a private file. There is no SOST-wide password: it protects your node, and the miner reads the same file.

1 · create a private password file

mkdir -p ~/.sost && umask 077
openssl rand -base64 30 > ~/.sost/rpc.pass
chmod 600 ~/.sost/rpc.pass

EXPECTEDNo output. The file ~/.sost/rpc.pass exists and only you can read it.

IF IT FAILS“Permission denied”: you are not in your own home folder; open a new terminal and repeat.

NEXTStart the node from the build/ folder.

2 · only if genesis_block.json is missing in build/

cp ../genesis_block.json .

3 · start the node (replace PICK_A_USERNAME)

./sost-node --genesis genesis_block.json --connect seed.sostcore.com:19333 \
    --rpc-user PICK_A_USERNAME --rpc-pass-file ~/.sost/rpc.pass --profile mainnet --p2p-enc on

EXPECTEDIt connects to the seed and syncs. You see lines like [BLOCK] Height N accepted. Fast sync is on by default.

IF IT FAILS--rpc-pass-file error: the file from command 1 is missing or not private (mode 600).

NEXTLeave this window open. Open a new terminal (WSL: Win+R, ubuntu) for step 5.

Why a file? Anything typed on a command line is visible to other users of the machine. The RPC password is not your wallet passphrase. If you mine against a remote node, use an SSH tunnel; same-machine setups need nothing else.

STEP 5 Create your wallet and mining key

Since block #7,100 every block must be signed by a mining key (SbPoW). The miner reads that key from your wallet file.

1 · in the new terminal, inside sost-core/build

./sost-cli newwallet

EXPECTEDA file wallet.json is created.

IF IT FAILS“not found”: you are not in sost-core/build.

NEXTCreate the mining address.

2 · the address labelled “mining”

./sost-cli getnewaddress "mining"

EXPECTEDAn address like sost1c6dac46bb3a43cefe…. Write it down.

IF IT FAILSwallet.json not found: run command 1 first.

NEXTBack up the wallet, then step 6.

Your wallet file is your money. wallet.json holds your private keys, including the mining key. Never share it, never upload it, never paste it anywhere, and nobody from SOST will ever ask for it. If you lose it, the coins are gone: copy it to a USB drive now and keep that copy offline.

STEP 6 Start, watch and stop the miner

1

cd ~/sost-core/build

2 · start mining (replace SAME_USERNAME_AS_STEP_4)

./sost-miner --wallet wallet.json --mining-key-label mining \
    --genesis genesis_block.json --chain chain.json \
    --rpc 127.0.0.1:18232 \
    --rpc-user SAME_USERNAME_AS_STEP_4 \
    --rpc-pass-file ~/.sost/rpc.pass \
    --blocks 999999 --profile mainnet --threads 4

EXPECTEDNumbers scroll. When it finds a block it prints BLOCK FOUND!. Finding blocks is a matter of probability, not a schedule.

IF IT FAILSConnection refused: the node from step 4 is not running. std::bad_alloc: not enough memory (step 7).

NEXTLeave it running. Stop it any time with Ctrl+C in its window.

3 · check your balance (third terminal, in build/)

./sost-cli getbalance --rpc 127.0.0.1:18232 \
    --rpc-user YOUR_USER --rpc-pass-file ~/.sost/rpc.pass

EXPECTEDTotal / Available / Locked (immature).

IF IT FAILSAuthentication error: use the same username and password file as the node.

NEXTMined coins become spendable after 1,000 confirmations (about 7 days).

Rewards depend on how many other miners are active and are never guaranteed. Each block currently splits its reward 50 % miner / 50 % DTD. See the 288 Orbit for how the DTD works.

STEP 7 Guided diagnostic

Pick what you see. This check runs only in your browser and asks for nothing else.

Never paste private keys, seed phrases, passwords, the contents of ~/.sost/rpc.pass or your wallet.json into any website, chat or support request, including this one.

Select a symptom above.