▲ node offline — rpc unreachable
⛏ NEW BLOCK MINED
RPC> USER> PASS> MY MINER>
search>
Developer Note

SOST is being developed with engineering rigor, but that does not guarantee success, future value, liquidity, exchange listings, or community adoption.

Right now, SOST is still an experimental native Proof-of-Work network in pre-market testing. Miners can participate with the current reference miner using CPU-oriented mining and approximately 8 GB of RAM, but this does not mean that SOST will necessarily become valuable.

The future of the project depends on several important factors, none of which is guaranteed:

  • That the project can comply with applicable crypto, tax, and possibly financial regulations in the places where it may operate.
  • That miners, node operators, developers, and the wider crypto community decide to support it.
  • That one or more exchanges may decide, at their own discretion, to list SOST in the future.

ConvergenceX is a native and experimental Proof-of-Work system. It is different from traditional PoW designs and has been deployed directly on mainnet. Although the code has many internal tests and is being tested publicly, it has not yet been audited by an independent security firm.

For that reason, we are walking an unknown path together.

SOST may never obtain market value. It may never be listed. It may fail. This must be clear to everyone so that no false expectations are created.

Mine, run a node, test, and participate only if you understand that this is an experimental project.

// TRINITY IS LIVE

SOST Discovery Engine

Registry: kalgoorlie_phase1 · registered at block #8085

Trinity is an integrated scientific discovery system. Its primary purpose is to turn data — Earth evidence today, materials intelligence next — into increasingly useful scientific outputs. GeaSpirit, Materials Engine and Useful Compute do the science; SOST adds the proof, reputation and future-reward rail around that work.

// OTC / P2P · ATOMIC SWAP V14 PREVIEW

SOST ↔ BTC / ETH / BNB / USDT / USDC / PAXG / XAUT

⚠ NOT ACTIVE V14 TARGET: BLOCK 15,000 Trustless cross-chain swaps. No custody. No escrow. No intermediary.

SOST OTC / P2P will let two strangers swap SOST for another cryptoasset without trusting each other and without SOST holding either side's funds. Either both legs settle, or both legs refund. There is no intermediary, no escrow operator, no admin key, and no upgrade path. The mechanism is a Hashed Time-Locked Contract (HTLC) on both chains — the same primitive that powers Lightning channels.

⚡ SOST V12 HARDFORK — ACTIVATION AT BLOCK 7,350 ⚠ ALL OPERATORS: UPDATE BEFORE 7,350
CURRENT HEIGHT
—
ACTIVATION
#7,350
BLOCKS LEFT
—
EST. TIME LEFT
—
⚠ WHAT V12 CHANGES
  • cASERT profile ceiling raised H13 → H20 — gives the equalizer 7 more profiles of headroom for transient hashrate spikes.
  • Triangular cascade extended to 7 steps (max drop 28). Cascade still reaches E7 floor from the new H20 ceiling within 900 s.
  • Slingshot redesign: same-block, single-gate, 5 tiers (emergency-only): 20 min → −6.5%, 30 min → −12.5%, 60 min → −25%, 120 min → −37.5%, 180 min → −50% (catastrophic). Self-resetting per block — no compounding.
  • Capsule activation lowered to #7,350 — on-chain messages become valid simultaneously with the fork (down from #10,000).
  • getminerstats diagnostics — new RPC + MINING ATTEMPTS dashboard card showing submitblock received / accepted / rejected per node, with per-reason breakdowns. Non-consensus telemetry, useful for spotting miners running stale binaries.
RECOMMENDED UPGRADE WINDOW
Restart between block #7,330 and #7,350. Earlier is safe but harder to coordinate; do not leave it past #7,349 — the first V12 block won't validate on a pre-V12 binary.
⚠ MINER ADVISORY — WALLET-BACKED MINING
Address-only mining has not been valid since Phase 2 (#7,100). V12 miners must still run with --wallet and --mining-key-label. If your miner is launched with only --mining-address, V12 blocks you produce will be rejected.
⚠ HOW TO UPGRADE
cd <your sost-core directory>
git pull --ff-only origin main
cd build
cmake .. -DCMAKE_BUILD_TYPE=Release -DSOST_ENABLE_PHASE2_SBPOW=ON
make -j$(nproc) sost-node sost-miner
sudo systemctl restart sost-node

# If you mine, also restart the miner with wallet-backed signing
pkill -9 -f sost-miner 2>/dev/null || true
./sost-miner \
  --wallet YOUR_WALLET.json \
  --mining-key-label YOUR_LABEL \
  --rpc 127.0.0.1:18232 --rpc-user USER --rpc-pass PASS \
  --blocks 999999 --profile mainnet --threads N
Verify your binary loaded V12 by checking the startup log — look for the "SOST V12 HARDFORK -- ACTIVATION AT BLOCK 7350" notice on every sost-node / sost-miner launch. Once your local height crosses 7,350 the notice flips to a one-line "[V12] active" confirmation.
⚡ SOST V13 RELEASE CANDIDATE (v13-rc1) — ACTIVATION AT BLOCK 12,000 ⚠ UPGRADE WINDOW: BLOCKS 11,900 – 11,999 ⚠ ALL OPERATORS: UPDATE V13 BINARY + NTP RECOMMENDED BY 12,000
RC ID
v13-rc1
ACTIVATION HEIGHT
#12,000
UPGRADE WINDOW
#11,900 – #11,999
V14 FALLBACK
#15,000
DTD DECISION
#12,100
⚠ V13 UPGRADE WINDOW — BLOCKS 11,900 → 11,999 (100 blocks before activation). Every miner and full-node operator MUST have the V13 binary running by block 11,999 at the latest — the binary swap is consensus-mandatory. NTP synchronisation is strongly recommended (not consensus-mandatory): with the V13 future-timestamp drift cap at 30 s, a host whose clock is more than 30 s ahead of true time will produce blocks that every validator rejects. The recommended window is #11,900 to #11,999 (~18 hours at the target block time, room for one full sleep cycle). Activation lands on block #12,000; from that block on, pre-V13 binaries will be on a stale rule set and pre-NTP hosts will produce blocks that every validator rejects. Recommended sequence inside the window: (1) stop your miner; (2) verify sha256sum -c SHA256SUMS && gpg --verify SHA256SUMS.asc SHA256SUMS against the SOST release key 41B1A46E626064AB524CB99EB6B9E2852AE41A04 once binaries are published; (3) swap the binary; (4) timedatectl and sudo timedatectl set-ntp true if NTP is not active; (5) restart miner with your existing --wallet + --mining-key-label. Do NOT wait until block #12,000 to start — by then any candidate block you mine on the wrong binary or with a drifted clock is already rejected. Last-resort cutoff is block #11,999.
⚠ WHAT V13 CHANGES AT BLOCK 12,000 (CONFIRMED, WIRED IN CODE)
  • All cASERT equalizer profiles E7-H35 active — ceiling rises from H20 to H35 via effective_profile_ceiling_at(height) + validator_profile_ceiling_at(height) in include/sost/params.h. Closes the equalizer calibration started in V6.
  • DTD lottery cooldown 5 → 6 blocks — lottery_exclusion_window_at(height) returns 6 for height ≥ V13_HEIGHT. Deterministic 2-firing exclusion under permanent 1-of-3 cadence.
  • Future-timestamp drift cap 60 s → 30 s — max_future_drift_at(height) returns 30 for height ≥ V13_HEIGHT. NTP synchronisation is strongly recommended post-V13; a host whose clock is more than 30 s ahead of true time will produce blocks validators reject.
  • Beacon Phase II-A — BEACON_PHASE2A_ACTIVATION_HEIGHT = V13_HEIGHT. Local notices.json, ECDSA-SHA256 single-sig, file-only, no HTTP from the node. Operator-signed advisory banner on miner / node startup.
  • Beacon Phase II-B — adds N-of-M threshold signatures (default 3-of-5) for critical notices, revocation by notice ID (only threshold-signed notices can revoke), and an optional mirror_url metadata field that the node never fetches. Active at V13_HEIGHT.
  • Beacon Phase III (P2P gossip) — BEACON_P2P_ACTIVATION_HEIGHT = V13_HEIGHT. The BCNN dispatcher relays valid signed notices between nodes with hard limits (4 KB max notice, 32-notice LRU dedup cache, 8 notices/peer/min rate limit, signature verify, network match, expiry). Pre-V13: DiscardDormant. Advisory only — never affects consensus, mining, or block validation.
  • SbPoW hardening — at V13_HEIGHT the signed PoW preimage grows from V11 layout (7 fields, 129 B) to V13 layout (11 fields, 205 B). New committed fields: timestamp, bits_q, merkle_root, and a chain-specific genesis_hash salt — closes timestamp-restamp, difficulty-fork, tx-set mutation, and cross-chain replay seams. Domain tag bumped to SOST/POW-SIG/v13. See docs/V13_SBPOW_HARDENING.md.
// TRADING — SIMPLE & SECURE BY DESIGN (DEX + OTC P2P)
  • SOST DEX (PoPC contracts ↔ gold) — ALREADY SECURE. Trades happen between users via client-side ED25519-signed offers + X25519 end-to-end encrypted relay messages + the on-chain Ethereum smart-contract escrow SOSTEscrow.sol. SOST Protocol holds no keys, custodies no funds, cannot reverse or arbitrate. The contract itself enforces the trade rules — no admin, no intermediary, no oracle. UI hardening (contract-address allowlist, WYSIWYS sign-time modal, offer fingerprint comparison) is the next web-only sprint. No further consensus change required for the DEX.
  • SOST OTC / P2P Board — crypto↔crypto only (BTC, ETH, USDT, USDC, BNB, PAXG, XAUT) — uses atomic swap HTLC for trustless settlement. The candidate branch feat/atomic-swap-htlc-v13-candidate ships HTLC_LOCK/CLAIM/REFUND validation, wallet helpers, RPC + CLI — all gated by ATOMIC_SWAP_HTLC_ACTIVATION_HEIGHT = INT64_MAX (sentinel OFF). Counterparty legs (Bitcoin Script + EVM contract) and external review are PENDING. Target activation: V14 / block 15,000 only after Phase 4 + Phase 5 sign-off. Until then the chain rejects every HTLC tx_type. See docs/reviews/ATOMIC_SWAP_PRE_ACTIVATION_REVIEW.md.
  • OTC / P2P with fiat (bank transfers, SEPA, wire) — NOT OFFERED AS A PROTOCOL FEATURE. The SOST chain cannot see a bank, cannot verify a SEPA transfer, cannot penalise an unpaid fiat leg without becoming a regulated intermediary or inviting Sybil/oracle attacks. SOST strongly recommends users stay in the crypto-to-crypto path (atomic swap above) and treat any fiat OTC as off-protocol, at user risk, with no protocol safety net. The community OTC board still hosts discussion but does not endorse, intermediate, or guarantee fiat trades. See docs/SOST_TALK_COMMUNITY_RULES.md.
  • Simplicity rule for both surfaces — every trade flow follows the same five-step UI discipline: (1) load the official URL (sostcore.com or sostprotocol.com) only; (2) read the signed offer fields before signing; (3) verify counterparty address against the LOCK/escrow payload; (4) confirm txids on-chain in the explorer; (5) do a small test transaction before any larger amount. Anything sold outside this flow (Telegram DM, screenshots, address-by-chat, advance-fee request) is a scam pattern — Sentinel flags 26 known variants at the chat layer, OTC and DEX pages document each pattern with worked examples.
⚠ FALLBACK TO V14 (BLOCK 15,000) — DO NOT EXPECT THESE AT 12,000
  • PoPC Model A + B — full automated lifecycle. Deferred to V14 / block 15,000 (high confidence). Five of nine PoPC consensus-readiness gates are RED today: POPC_ACTIVATION_HEIGHT missing, no audit daemon, no auto-slash, no auto-settlement, no Ethereum bridge, no end-to-end lifecycle test. SOSTEscrow.sol exists in source (contracts/SOSTEscrow.sol) but is not deployed. PoPC accumulation (25% per block to the PoPC Pool address) continues unchanged at consensus since genesis. PoPC is NOT half-shipped. Full audit: docs/V13_POPC_ESCROW_AUTO_ACTIVATION_GAPS.md.
  • Gold Vault governance — spend-side governance (purpose restriction, dual whitelists, per-spend cap, rate limit, 90% block-based miner signaling over a 67-block window ~12 h, Transitional Guardian with 10-block pronouncement window, auto-disconnect at block 25,000). Deferred to V14 / block 15,000. Five of six gates RED today; classify_gv_spend() exists and is unit-tested but is dead code (not called by the validator). Accumulation (25% per block to ADDR_GOLD_VAULT) continues unchanged at consensus since genesis. Full audit: docs/V13_GOLD_VAULT_GOVERNANCE_GATES.md.
  • Memory-Lock per-instance — second anti-pool mechanism originally proposed alongside SbPoW. REJECTED — not scheduled for V13 or V14. Numerical analysis of realistic hardware budgets shows the mechanism penalises small miners proportionally MORE than large rigs (small miners lose ~75% of their threads at the 8 GB RAM floor; rigs lose ~50%), achieving the opposite of the declared anti-pool goal. SbPoW (active since block 7,100) remains the protocol's only anti-pool defense.
Operator decision at block 12,100. ~100 blocks after V13 stabilises, the operator will open the DTD lottery decision in this thread: Option A keep the DTD lottery at 1-of-3 permanent (cooldown stays at 6) as supplementary redistribution alongside PoPC when PoPC is live · Option B disable the lottery; extra-coinbase rewards stay on the original PoPC + Useful Compute path only. The decision is community-driven, not unilateral.
Community OTC / P2P Board. Separate from Beacon (which is node-to-node gossip of signed advisory notices), the OTC / P2P Board is a community discussion room inside SOST Talk where users post voluntary buy/sell talk between each other (e.g. WTB 100 SOST / WTS 50 SOST). SOST Protocol does NOT intermediate trades. SOST Protocol does NOT custody funds. SOST Protocol does NOT provide escrow. No guarantee of buyer, seller, price, liquidity, settlement, or safety. Admins never DM first. Use small test transactions and verify all addresses independently. Anyone claiming "official escrow" or "guaranteed buyer/seller" is a scammer — Sentinel (the chat moderation bot) auto-flags these patterns and the chat rules block them.

Three rules that stop most OTC scams:
  1. Screenshots are NOT proof of payment. Editable, fakeable. Until the money is in your bank or wallet, you have not been paid.
  2. Verify funds DIRECTLY in your bank or wallet. Log in and check the balance yourself. Do NOT trust SMS / email / push notifications alone (spoofable, lag the actual settlement).
  3. Beware chargeback risk per payment method. Wait the FULL clearing window before releasing SOST: PayPal F&F (180 days), SEPA / instant bank transfer (8 weeks), Wise / Revolut instant (reversible on fraud claim). Irreversible methods: cash in person, on-chain USDC / USDT.
The first time you open the OTC room, SOST Talk shows a pre-trade safety checklist (acknowledgement persisted in browser localStorage). Sentinel auto-flags pressure patterns (release-first, hurry-up, move-to-DM, screenshot-as-proof, impersonation). Full guide at sost-otc.html, full rules at docs/SOST_TALK_COMMUNITY_RULES.md.
See also sost-community.html.
Beacon is a loudspeaker, not a remote control. Beacon Phase II-A, II-B, and Phase III (all V13 confirmed) MAY inform; they MAY NOT restart, MAY NOT block any block or transaction, MAY NOT change consensus rules, MAY NOT execute commands on the host, MAY NOT move coins. The validator and the static safety lint enforce these guarantees together (link-time invariant pinned by tests/test_v13_beacon_phase3_p2p.cpp:t15: Beacon code never depends on block_validation symbols).
DTD flip at block 12,100 — VERIFIED AUTOMATIC. 100 blocks after V13 activates, the V11 Phase 2 lottery cadence transitions from bootstrap (2-of-3) to permanent (1-of-3) without any operator action, node restart, miner restart, Beacon notice, RPC call, or config flag. The flip is a pure consequence of is_lottery_block(height, V11_PHASE2_HEIGHT) in include/sost/lottery.h:126; both validator and miner route through the single function. Six audit gates GREEN on main; companion doc docs/V13_DTD_FLIP_12100_AUTOMATIC.md; tag v13-dtd-flip-12100-verification-v01.
V13 Public Scope Update (2026-05-18). The operator-and-community version of V13 scope is at docs/V13_PUBLIC_SCOPE_UPDATE.md — read it before mining V13. Honest summary: V13 ships cASERT E7-H35, DTD cooldown 5→6, drift cap 60s→30s (NTP strongly recommended), SbPoW hardening, Beacon Phase II-A + II-B (3-of-5 threshold) + III (P2P gossip, advisory only). PoPC + Escrow + Gold Vault governance are DEFERRED to V14 / block 15,000 — five of nine PoPC gates and five of six Vault gates are RED today; shipping half-implemented consensus at block 12,000 is worse than waiting. Memory-Lock per-instance is REJECTED (numerical analysis shows it would penalise small miners more than rigs). The earlier "V15" label has been replaced by "V14" everywhere; the block height (15,000) is unchanged.
// MINER UPGRADE SEQUENCE
1. Pull V13 release tag
2. Verify min_commit matches
3. cmake / make
4. Sync NTP (clock not >30 s ahead)
5. Restart sost-node + sost-miner
   BEFORE block 12,000
// SbPoW UNCHANGED
--wallet + --mining-key-label
(mandatory since block 7,100)
NO new wallet migration
NO key export
NO pool key sharing
// IF BLOCKS REJECTED POST-V13
1. Clock > 30 s ahead of true?
2. Old binary?
3. Old cASERT ceiling assumption?
4. Old DTD cooldown assumption?
See docs/V13_MINER_OPERATOR_CHECKLIST.md
// PUBLIC RC MANIFEST
/api/v13_release_candidate.json
docs/V13_RELEASE_CANDIDATE.md
docs/V13_MINER_OPERATOR_CHECKLIST.md
docs/V13_ACTIVATION_PLAN.md
docs/V13_READINESS_GATES.md
// PUBLIC ARTIFACT METADATA (SHA256SUMS SIGNED, binaries NOT uploaded)
/api/v13_rc1_artifact_manifest.json
/api/v13_rc1_SHA256SUMS.txt
/api/v13_rc1_SHA256SUMS.asc
docs/V13_RC1_PUBLIC_ARTIFACT_METADATA.md
docs/V13_RC1_SIGNING_AND_PUBLICATION_CHECKLIST.md
docs/V13_RC1_ARTIFACT_BUNDLE.md
docs/V13_BINARY_PREFLIGHT.md
V13 RC1 SHA256SUMS is now SIGNED. /api/v13_rc1_SHA256SUMS.txt is signed with the SOST release key (primary fingerprint 41B1A46E626064AB524CB99EB6B9E2852AE41A04, signing subkey E2FCC898520842F0192EF7A46422CC120F51DCEA); the ASCII-armored detached signature is published at /api/v13_rc1_SHA256SUMS.asc (sha256 5e83889bb95d21404c3ae4faedfeb8c04729343fc88b03f5a9e608dd7c228779). release_status = signed_metadata_only. The binaries themselves are still NOT committed to this repo and have NOT yet been uploaded to a public distribution surface (binaries_uploaded = false). Anyone who later downloads V13 RC1 binaries from the operator's eventual release surface can already verify them offline with sha256sum -c SHA256SUMS && gpg --verify SHA256SUMS.asc SHA256SUMS against the release public key. Binary upload remains an explicit manual operator step and will be announced from the BitcoinTalk thread when it happens. See docs/V13_RC1_PUBLIC_ARTIFACT_METADATA.md and docs/V13_RC1_SIGNING_AND_PUBLICATION_CHECKLIST.md.
What V13 does NOT change. No change to the SbPoW signing contract (active since block 7,100). No change to the coinbase split (50% miner / 25% Gold Vault / 25% PoPC Pool). No change to the emission schedule or the 4,669,201 SOST hard cap. No new wallet format. No new network endpoint. Useful Compute rewards remain POSTPONED — block 12,000 will NOT activate Useful Compute rewards (post #133 invariant unchanged).
✅ SOST V11 PHASE 2 + V12 LIVE — wallet-backed SbPoW required ⚠ MINERS: --wallet + --mining-key-label
◆ HOW TO SET UP A MINING-KEY LABEL FOR SbPoW
From block 7,100 every block must carry a Schnorr signature from the miner. 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.
OPTION A — create a NEW dedicated Phase 2 mining wallet
The label is yours to choose freely. Anything you can type works — pick whatever helps you remember which machine or address it points to. The wallet does not validate the string; the only rule is that the label you pass to getnewaddress <label> must match the one you pass to --mining-key-label <label> later. Two example shapes follow; copy either one and edit it:
// EXAMPLE 1 — label "phase2-miner"
cd ~/SOST/sostcore/sost-core/build

./sost-cli --wallet phase2-miner-wallet.json newwallet
./sost-cli --wallet phase2-miner-wallet.json getnewaddress phase2-miner

# confirm the label exists
./sost-cli --wallet phase2-miner-wallet.json listaddresses

# back up the wallet file (it holds your private key)
cp -a phase2-miner-wallet.json phase2-miner-wallet.json.bak
chmod 600 phase2-miner-wallet.json phase2-miner-wallet.json.bak
// EXAMPLE 2 — label "home-rig" (any string works the same way)
cd ~/SOST/sostcore/sost-core/build

./sost-cli --wallet home-rig-wallet.json newwallet
./sost-cli --wallet home-rig-wallet.json getnewaddress home-rig

./sost-cli --wallet home-rig-wallet.json listaddresses

cp -a home-rig-wallet.json home-rig-wallet.json.bak
chmod 600 home-rig-wallet.json home-rig-wallet.json.bak
Then launch the miner with that wallet + label. The label after --mining-key-label must be identical to the one you used in getnewaddress in the same wallet. Do NOT add --address; the miner derives the address from the wallet key automatically.
# using EXAMPLE 1
./sost-miner \
  --wallet phase2-miner-wallet.json \
  --mining-key-label phase2-miner \
  --rpc 127.0.0.1:18232 --rpc-user USER --rpc-pass PASS \
  --blocks 999999 --profile mainnet --threads N

# using EXAMPLE 2
./sost-miner \
  --wallet home-rig-wallet.json \
  --mining-key-label home-rig \
  --rpc 127.0.0.1:18232 --rpc-user USER --rpc-pass PASS \
  --blocks 999999 --profile mainnet --threads N
Expected startup lines (the label echoed back is whichever one you chose): 
SbPoW signing key: label='<your-label>'
Miner address: sost1...   (derived from wallet key)
Note: a brand-new address is not lottery-eligible until it mines its first valid block. Eligibility is per-address and unlocks automatically once the address mines once.
OPTION B — use an EXISTING wallet/address
If your existing wallet already holds the address you want to mine with, just point the miner at it. First find the label:
cd ~/SOST/sostcore/sost-core/build
./sost-cli --wallet wallet.json listaddresses
Then launch with that wallet and label (replace YOUR_LABEL):
./sost-miner \
  --wallet wallet.json \
  --mining-key-label YOUR_LABEL \
  --rpc 127.0.0.1:18232 --rpc-user USER --rpc-pass PASS \
  --blocks 999999 --profile mainnet --threads N
If that address has already mined ≥ 1 block since genesis, it is already lottery-eligible. If it has never mined, eligibility unlocks after its first block.
⚠ HOW TO KNOW IF YOU NEED TO UPGRADE
Your node or miner is outdated if any of these is true:
  • Your getinfo reports a chain height below 7,100 while the public explorer is above it.
  • Your node is connected to peers but its tip stays stuck (e.g. at 7087, 7097) — it is rejecting Phase II v2 blocks.
  • Your miner exits with: FATAL: Phase 2 active ... wallet-backed mining key required.
  • Your submitblock is rejected with: v2 header missing miner_pubkey.
  • Your miner is launched with --address only (post-7,100 needs the label workflow above).
⚠ COMBINED UPGRADE — node + miner in one go
cd <your sost-core directory>
git pull --ff-only origin main
cd build
cmake .. -DCMAKE_BUILD_TYPE=Release -DSOST_ENABLE_PHASE2_SBPOW=ON
make -j$(nproc) sost-node sost-miner sost-cli

# Restart the node (it can now follow Phase II + V12)
sudo systemctl restart sost-node

# If you also mine, restart with wallet-backed SbPoW signing
pkill -9 -f sost-miner 2>/dev/null || true
./sost-miner \
  --wallet YOUR_WALLET.json \
  --mining-key-label YOUR_LABEL \
  --rpc 127.0.0.1:18232 --rpc-user USER --rpc-pass PASS \
  --blocks 999999 --profile mainnet --threads N
Verify your node has caught up: 
curl -s -u "USER:PASS" -d '{"method":"getinfo"}' http://127.0.0.1:18232/
The blocks field should match (or be within a couple of blocks of) the height shown at the top of this explorer. If it stays stuck, the rebuild step did not complete or the wrong binary is running — check which sost-node and the systemd unit's ExecStart= path.
What is currently active on chain
  • V11 Phase 2 (since #7,100): SbPoW signed identity + DTD lottery + PAYOUT coinbase shape on triggered blocks.
  • V12 (since #7,350): H20 cASERT ceiling, same-block 4-tier Slingshot, V12 miner rebuild protection, capsules, getminerstats diagnostics.
Cooldown clarification
The 5-block cooldown applies to miners who produced recent blocks, not to lottery winners.
  • An address that mined any of the previous 5 blocks is temporarily excluded from the lottery.
  • An address that only wins the DTD lottery remains eligible unless it also mined recently.
  • Winning the lottery does NOT trigger cooldown.
  • Mining a block does NOT automatically win the lottery.
This matches the C7.1 Phase 2 design.

Important — common pitfalls
  • If you run only a node, update and restart the node.
  • If you run only a miner, update and restart the miner.
  • If node and miner are on different machines, update both.
  • --address-only mining is rejected post-#7,100. Use --wallet + --mining-key-label.
  • Never share your wallet file or private key. Treat phase2-miner-wallet.json as a secret.
— NeoB
BLOCK HEIGHT
—
loading...
CONSENSUS
AVG BLOCK TIME
—
last 288 blocks
—
LONG AVG · 600
—
last 600 blocks · visual
—
LONG AVG · 1000
—
last 1000 blocks · visual
—
AVG · GENESIS
—
since block 0 · visual
—
TOTAL SUPPLY
—
SOST emitted
CIRCULATING SUPPLY
—
total − vault − pool
CIRCULATING MINING
—
total − vault − pool − lottery
◆ GOLD VAULT BALANCE
—
25% · click for UTXOs
◇ POPC POOL BALANCE
—
25% · click for UTXOs
⚡ DTD LOTTERY BALANCE
—
payouts distributed
MEMPOOL
0
pending txs
EST. HASHRATE
—
H/s (Bitcoin-style)
NEXT BLOCK IN
—
estimated
⚒ UNIQUE MINERS · DISTRIBUTION
—
last 288 blocks
top 3: —
⚒ UPDATED MINERS
—
since #7100
⚒ MINING ATTEMPTS
—
received · accepted · rejected
📡 RPC ACTIVITY
—
methods · calls · errors
☍ UNIQUE NODES
0
seed-visible peers
⚒ PEAK ACTIVE MINERS
—
Token Distribution
DTD Lottery
DASHBOARD
click to scan
BLOCK PRODUCTION · real vs expected ⓘ —
BLOCK INTERVALS · individual block times ⓘ — avg · — median
▮ block time (red glow = over target) ── 10 min target hover for detail · click to view block
BURST & VOLATILITY · last 288 blocks (~48h) ⓘ — · —
Burst = % of blocks <5min in last 72. Volatility = stdev(block_times)/600s. cASERT responds by hardening profiles.
DIFF HISTORY · last 288 blocks (~48h) ⓘ —
DIFF HISTORY · last 5000 blocks · loading… ⓘ
SCANNING DATA…
—
// connecting to node...
// XAUT PRICE — Tether Gold
LIVE
—
—
// XAUT / BTC — Tether Gold vs Bitcoin
LIVE
—
—
// PAXG PRICE — Pax Gold
LIVE
—
—
// PAXG / BTC — Pax Gold vs Bitcoin
LIVE
—
—
// SOST PRICE
LIVE
—
—
// EMISSION CURVE smooth exponential decay · q = e-¼ · Feigenbaum α epochs · δ supply cap ⓘ
EMISSION MODEL — Smooth Exponential Decay

SOST uses a smooth exponential decay emission model, not a sharp halving like Bitcoin. Each epoch, the block reward decreases by a factor of q = e-1/4 ≈ 0.7788, which means a ~22.12% reduction per epoch — a gradual, continuous curve instead of abrupt 50% drops.

The Mathematical Constants
• Decay factor q = e-1/4 — the natural exponential base raised to -1/4. This produces the smoothest possible decay curve: R(e) = R₀ × qe
• Feigenbaum δ ≈ 4.6692 — determines the hard supply cap: δ × 10⁶ = 4,669,201 SOST. This is the mathematical limit of the geometric series — no counter, no tracking, just convergence.
• Feigenbaum α ≈ 2.5029 — determines the epoch length: α × 10⁵ = 131,553 blocks per epoch ≈ 2.503 years.

Epoch Structure
• Epoch 0: 7.85100863 SOST/block (genesis reward)
• Epoch 1: 6.11448985 SOST/block (−22.1%)
• Epoch 2: 4.76155747 SOST/block (−22.1%)
• ...each epoch decays by the same smooth factor...
• Epoch 11: 0.60574158 SOST/block
• ~95% of total supply emitted by epoch ~12 (~30 years)
• Emission continues through ~82 epochs (~205 years) until rewards become negligible
• 100% emission is asymptotic — mathematically approaches but never reaches the cap

Coinbase Split (every block, forever)
50% Miner · 25% Gold Vault · 25% PoPC Pool

Why Feigenbaum?
The Feigenbaum constants (δ = 4.6692..., α = 2.5029...) are universal mathematical constants from chaos theory that describe the rate at which period-doubling bifurcations occur in dynamical systems. In SOST, they are used purely as irrational constants to set the supply cap and epoch length — values that cannot be derived from simple fractions, making them resistant to arbitrary parameter choices. The emission curve is deterministic, immutable, and verifiable by anyone from the genesis block.
─ █ block reward ┈ █ cumulative supply ┃ █ current position supplymax = δ·10⁶ ≈ 4,669,201 SOST
// FULL EMISSION · 82 EPOCHS · ~205 YEARS
// CHAIN TIMING · genesis 2026-03-15 18:00:00 UTC
WALL CLOCK ELAPSED
—
real time since genesis
CHAIN TIME ELAPSED
—
height × 10 min target
BLOCK LAG
—
expected − actual
EXPECTED BLOCKS
—
at 10 min/block target
ACTUAL BLOCKS
—
mined on chain
TIME OFFSET
—
at tip · — since last block
⛏ MINING BLOCK #—
Difficulty: — ⓘ
Elapsed: — ⓘ · Target: 10m 00s ⓘ
searching nonce...
NODE: CHECKING... MINER: CHECKING...
prev: — bitsQ: — ⓘ profile: — (scale=1 k=4 margin=165 steps=4) ⓘ stability: — ⓘ lottery: —
PROBABILITY ⓘ —
— ⓘ
— ⓘ
NONCE ⓘ ~0 / —
ANTI-STALL: ⓘ
SLINGSHOT: ⓘ
// LATEST BLOCKS
HEIGHTHASHTXSTIMEINTERVALDIFFICULTYMINERSUBSIDYLOTTERY
loading blocks
// LATEST TRANSACTIONS
TXIDCAPSULEBLOCKTYPEIN
UTXOs		OUT
outputs		AMOUNT
payment		FEE
loading transactions
// MEMPOOL
NO PRIORITY
1
stocks/byte
LOW
1
stocks/byte
MEDIUM
1
stocks/byte
HIGH
1
stocks/byte
NEXT BLOCKS ESTIMATE
TRANSACTION TREEMAP
TXIDSIZEFEERATE
empty
// ACTIVE NODES
refreshing...
CONNECTED
0
NEAR TIP
0
ENCRYPTED
0
PLAINTEXT
0
SEED CANDIDATES
0
NODEDIRECTIONHEIGHTDELTATRANSPORTUPTIMESTATUSRELIABILITY
loading...
★ SEED CANDIDATE = reliability ≥70 + synced + version acked + uptime >24h
Reliability score: uptime (0-40pts) + delta accuracy (0-30pts) + handshake (0-15pts) + encrypted (+10) + outbound (+5) − ban penalty
■ EXCELLENT (80-100) · ■ GOOD (60-79) · ■ FAIR (40-59) · ■ LOW (20-39) · ■ POOR (0-19)
Disclaimer: This view shows peers connected to YOUR node only. It is not a complete picture of the network. Node IDs are derived hashes — no IP addresses are exposed. Node count, heights, and encryption status reflect this node's local perspective and may differ from the global network state.
<!-- SOST Explorer v4.2 | sostcore.com | ConvergenceX PoW | Constitutional Gold Reserves -->
🎮