A native PoW chain. CPU-friendly, memory-hard. No pool required, no pool offered — SOST is experimenting with a solo-miner-first model. Pre-market testing only.
sostcore.com/rpc/public is not a mining server, what the three different
things called “encryption” actually protect, how normal DTD differs from the Jackpot V2 draw,
and what to back up before you need it.
chain.json is no longer required.
Full status →
| OS | Ubuntu 22.04 or 24.04 (other Debian-family distros likely work) |
| RAM | 8 GB recommended for mining (4 GB dataset + 4 GB scratchpad per worker thread is shared) |
| Disk | 20 GB recommended |
| Network | stable internet connection — the node syncs and connects to peers over P2P (port 19333) |
| Skill | basic terminal: cd, copy/paste, run a command |
The recommended path: download, inspect, then run.
The quick version is also available, but inspect-first is always safer:
build-essential, cmake, git, libssl-dev, libsecp256k1-dev), clones (or pulls) github.com/Neob1844/sost-core into ~/sost-core, and builds the binaries. It then prints the next manual steps.Same result as the script, just typed by hand.
main branch does not currently reproduce the V30000 release, so a node built from main would apply the old rules at #30,000 and fork off the network. New operators must build from the v30000 tag — or use the published V30000 binaries.SHA256SUMS).From block 7,100 every block must carry a Schnorr signature from the miner (Phase 2 SbPoW). The miner key lives inside a wallet file and is referenced by a label. The miner is launched with --wallet + --mining-key-label; --address alone is rejected by the network. Pick a wallet filename and a label you will remember — both are freeform strings, the only rule is that the label you pass to getnewaddress must be character-for-character identical to the one you pass to --mining-key-label later.
phase2-miner is the example; home-rig, node-3 or whatever you remember works the same way. The miner derives its address from the wallet key automatically — you do not need to copy the address anywhere.The node and the miner talk to each other over local RPC with HTTP Basic Auth. Choose any user/pass — both processes need to know them.
127.0.0.1 by default, never to the public internet — the password protects you from other local users on the same box. Keeping it in a mode-600 file instead of the command line matters for the same reason: anything on a command line is visible through ps.You should see lines like Chain loaded: NNNN blocks and the node connecting to peers. Leave this terminal open. To run as a service later, create a systemd unit (sample under docs/systemd/ in the repo).
Use the same wallet and label you created in step 1. Do not pass --address; the miner derives the address from the wallet key automatically.
Expected startup lines (the label echoed back is whichever one you chose):
8, try 16, and keep whichever gives the higher stable/s figure in your own miner log. The example above uses 16; the guide and the BitcoinTalk notice use 8 for the same reason — neither number is a rule.Three checks:
[MINING] H... bitsQ=... lines and a periodic effective stable/s rate.A 4.8 TH/s SHA-256 Bitcoin miner does not become a 4.8 TH/s SOST miner. The two numbers describe fundamentally different workloads. A Bitcoin ASIC runs one fixed SHA-256d pipeline over 80-byte block headers. A SOST miner must run the complete ConvergenceX computation that consensus requires: about 8 GB of working memory, 100,000 sequential rounds whose results decide the next memory reads, a 32×32 integer system and a stability proof.
ConvergenceX performance should be compared in valid attempts per second, under the active bitsQ target and Equalizer profile — not in Bitcoin-equivalent TH/s. ConvergenceX is ASIC-resistant by design; that does not mean specialized hardware is impossible, only that a useful accelerator would have to implement the real memory-hard, sequential workload instead of reusing Bitcoin hashrate. Technical detail: Technology → Strong ASIC resistance by design.
SOST is currently solo-miner-first — there is no official pool. That has consequences you should know up front:
For more context on the lack of pools, read Why no pools — or see the live Founding Miners hall of fame below, read straight from the chain.
Check P2P connectivity. The node listens on :19333. Allow outbound connections in your firewall. If you are behind NAT, you do not need to forward 19333 to mine, but you need outbound TCP.
Normal in solo mining. It means the network found a block before yours arrived — your block referenced a now-stale parent and gets dropped. The miner will automatically pull the new tip and continue. No data lost, just one round of work.
Drop to 16, then 8 threads. ConvergenceX is bandwidth-bound; very wide thread counts (64+) on machines with lots of cores can stress the monitor path. Always run the current V30000 miner (an early block-monitor race was fixed long ago):
Solo mining variance. The expected time to your first block is 1 / miner_share blocks × 10 min. With ~5% network share that is on the order of 200 minutes; you will sometimes wait 3-4× that just from variance. The calculator shows the probabilities for your hashrate.
Or simply re-run install-sost.sh — it is idempotent.
In each terminal: Ctrl-C. The node flushes its state to disk before exiting. The miner aborts its current attempt; nothing is lost — it just doesn't finish that nonce sweep.
Since V11 Phase 2 (#7,100) every SOST block is signed — SbPoW binds the proof-of-work to one key, so each block was found and signed by an individual solo miner. There are no pools. This hall of fame is read live from the chain; nothing here is curated or invented.
Source: live node RPC (geteligibleminers + per-block scan). Want to be on this list? Start mining and check your odds in the calculator. Solo mining is high variance; SOST is in pre-market testing.