▲ node offline — rpc unreachable
⛏ NEW BLOCK MINED
RPC> USER> PASS> MY MINER>
Developer Note: ALL NODES AND MINERS MUST UNDERSTAND THAT THIS PROJECT IS BEING BUILT WITH A LOT OF WORK, BUT THAT DOES NOT GUARANTEE THAT IT WILL SUCCEED OR HAVE FUTURE VALUE. RIGHT NOW, YOU ARE MINING WITH VERY LOW ENERGY COST, USING ONLY CPU AND 8 GB RAM, BUT THE SUCCESS OF THE PROJECT DEPENDS ON THREE CRUCIAL FACTORS, NONE OF WHICH IS GUARANTEED: FIRST, THAT IT COMPLIES WITH ALL APPLICABLE CRYPTO AND POSSIBLY FINANCIAL REGULATIONS IN THE COUNTRIES WHERE IT MAY OPERATE, WHICH IS COMPLEX; SECOND, THAT THE CRYPTO COMMUNITY ACCEPTS AND SUPPORTS THE PROJECT; AND THIRD, THAT ONE OR MORE CEXs DECIDE TO LIST THE PROJECT ON THEIR EXCHANGES. IN ADDITION, WE ARE OPERATING ConvergenceX, A NATIVE AND EXPERIMENTAL PROOF-OF-WORK SYSTEM, DISTINCT FROM OTHER POW DESIGNS, WHICH HAS BEEN DEPLOYED DIRECTLY ON MAINNET. ALTHOUGH IT HAS HUNDREDS OF TESTS BEHIND IT, IT HAS NOT BEEN AUDITED BY ANY INDEPENDENT OR REPUTABLE FIRM IN THE SECTOR; THEREFORE, WE ARE WALKING AN UNKNOWN PATH TOGETHER. WITHOUT THESE FACTORS, THE TOKEN MAY HAVE NO VALUE. THIS MUST BE CLEAR TO EVERYONE, SO THAT NO FALSE EXPECTATIONS ARE CREATED.
⚡ 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 V11 PHASE 2 — CHAIN RESUMED, LOTTERY LIVE ⚠ MINERS: UPDATE REQUIRED
⚠ HOW TO KNOW IF YOU NEED TO UPGRADE
Your node or miner needs upgrading 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 wallet-backed signing).
⚠ 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

# Restart the node (it can now follow Phase II)
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 in the response should match (or be within a couple of blocks of) the height shown at the top of this explorer. If it stays below 7,100, the rebuild step did not complete or the wrong binary is running — re-check which sost-node and the systemd unit's ExecStart= path.
Network status update — block 7,100 incident resolved
SOST V11 Phase 2 activated at block 7,100 with:
  • SbPoW — miner identity bound to the block through miner_pubkey + signature
  • DTD Lottery — deterministic lottery payout on scheduled reward blocks
  • PAYOUT coinbase shape — miner share + lottery winner output
After activation, the network paused at height 7,099 because several external peers were submitting invalid v2 blocks rejected by validators with:
[BLOCK] REJECTED: submitblock: v2 header missing miner_pubkey
After review, the production source was verified. The issue was not a consensus rollback problem. A correctly rebuilt miner from current main produced valid Phase 2 blocks.

The chain has resumed successfully.
First valid Phase 2 block: #7100
Status now verified through: #7104
SbPoW submit path: OK
DTD lottery payouts: OK
Gold / PoPC reactivation on normal blocks: OK
Pending jackpot: 0
Blocks 7,098–7,104
Block   Type                Miner          Lottery Winner   Gold   PoPC
7098    NORMAL pre-Phase2   ca9097...bc18  —                25%    25%
7099    NORMAL pre-Phase2   191f95...a21f  —                25%    25%
7100    PAYOUT              ca9097...bc18  d0a1cf...45c9    0      0
7101    NORMAL              ca9097...bc18  —                25%    25%
7102    PAYOUT              ca9097...bc18  9f15d9...5e19    0      0
7103    PAYOUT              ca9097...bc18  4dc422...1265    0      0
7104    NORMAL              ca9097...bc18  —                25%    25%
DTD lottery verification
Phase 2 has already paid 3 deterministic lottery rewards:
#7100 -> d0a1cf...45c9 -> 3.92550431 SOST
#7102 -> 9f15d9...5e19 -> 3.92550431 SOST
#7103 -> 4dc422...1265 -> 3.92550431 SOST
Total DTD lottery paid:
11.77651293 SOST = 3 x 3.92550431 SOST
There is currently no pending jackpot:
pending_lottery_before = 0
expected_pending_after = 0
The jackpot only accumulates if a scheduled lottery block has no eligible address after cooldown filtering. With 36 eligible addresses, payouts cleared normally.

Cooldown clarification
The 5-block cooldown applies to miners who produced recent blocks, not to lottery winners.
  • An address that mines one 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 lottery does not trigger cooldown.
  • Mining a block does not automatically win the lottery.
This matches the C7.1 Phase 2 design.

Explorer v121 update
Explorer v121 adds a new address-panel field:
DTD LOTTERY RECEIVED
Example:
DTD LOTTERY RECEIVED   3.92550431 SOST   (1 win)
This lets any address verify lottery winnings directly from public chain data.

If the field says:
open DTD section to scan
open the DTD dashboard once and the explorer will compute lottery winnings per address.

ACTION REQUIRED FOR MINERS AND NODE OPERATORS
All miners and node operators should update to the latest main now.

Node operators:
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
sudo systemctl restart sost-node
Then verify:
curl -s -u "USER:PASS" -d '{"method":"getinfo"}' http://127.0.0.1:18232/
You should see the chain above block 7,100.

Miners:
Stop old miners:
pkill -9 -f sost-miner 2>/dev/null || true
Update and rebuild:
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-miner
From block 7,100, miners must run with wallet-backed SbPoW signing:
./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
Do not use address-only mining after block 7,100. Phase 2 requires the block to carry a valid miner_pubkey and SbPoW signature.

Important:
  • If you run only a node, update and restart the node.
  • If you run only a miner, update and restart the miner.
  • If your node and miner are on different machines, update both.
  • If your miner starts with --address only, it will not produce valid Phase 2 blocks.
  • If your miner starts with --wallet and --mining-key-label, it is Phase 2 compatible.
Final status
  • Pre-7,100 chain history: intact
  • Holder funds: safe
  • Phase 2 activation: live
  • SbPoW: confirmed working with valid rebuilt miner
  • DTD lottery: confirmed paid and verifiable
  • Gold / PoPC normal allocation: confirmed on non-lottery blocks
  • Pending jackpot: 0
Thank you to everyone who stayed patient during the activation window.

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
◆ GOLD VAULT BALANCE
25% · click for UTXOs
◇ POPC POOL BALANCE
25% · click for UTXOs
MEMPOOL
0
pending txs
EST. HASHRATE
H/s (Bitcoin-style)
NEXT BLOCK IN
estimated
⚒ UNIQUE MINERS
last 288 blocks
⚒ UPDATED MINERS
since #7100
⚒ MINING ATTEMPTS
received · accepted · rejected
📡 RPC ACTIVITY
methods · calls · errors
☍ UNIQUE NODES
0
seed-visible peers
⚖ MINING DISTRIBUTION
top 10 addresses
Token Distribution
DTD
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)
// connecting to node...
// XAUT PRICE — Tether Gold
LIVE
// PAXG PRICE — Pax Gold
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
TXIDBLOCKTYPEINOUTAMOUNTFEE
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.
🎮