⚙️ V15 FULL DECENTRALIZATION FORK — block 25,000 PoW · ConvergenceX RELEASE PUBLISHED · update before #24,900 · tap to expand
FULL DECENTRALIZATION — PROTOCOL READY
V15 final is deployed on mainnet.
Permissionless mining and node operation.
From block #25,000: no protocol treasury, and no operator control over the reserve funds.
Final consensus activation at block #25,000.

SOST already has a Proof-of-Work network that works.

Making it more complex than it needs to be only makes the protocol harder for everyone to run and use. That is why we pursued the full decentralization of the protocol — native PoW + ConvergenceX, no operator and no treasury. The consensus rules that enforce it are published and running on mainnet; they take effect at block #25,000.

⚠️ EXPERIMENTAL · NOT FORMALLY AUDITED. This protocol has been hardened empirically — through its live mainnet history and a disciplined trial → error → diagnosis → resolution engineering cycle, with every issue and fix recorded on-chain for full traceability. The result is a system that behaves reliably and securely in practice, but it has not undergone an independent third-party security audit. Run, mine and participate accordingly — at your own risk, with no guarantees.
MINER (direct)
50%
DTD distribution
50%
Gold Vault · PoPC
0%

Future emission that went to Gold Vault / PoPC is redirected to DTD. SOST is not backed by gold — SOST is backed by its own rules.

How DTD works

  • Permanent 1-of-3 cadence: the DTD share accumulates for 2 blocks and pays on the 3rd (lottery block).
  • No valid winner → not lost: it rolls forward and grows.
  • Eligibility: mined ≥1 block at any point in chain history — once an address has produced a block it stays in the eligible set.
  • Kept: recent-winner cooldown · anti-dominance gate · SbPoW gate · uniform per-address selection.

🏦 What happens to the existing Gold Vault + PoPC SOST

The SOST already accumulated in Gold Vault + PoPC are not kept as a treasury and not sold for listings. They are progressively returned to active miners through a Historical DTD Jackpot: about 100 SOST every ~288 blocks (~48 h) to the DTD winner, using the very same DTD eligibility rules, until the historical balance is exhausted (~3 years). It is a real protocol spend of those coins — no new emission. The reserve returns to the network, not to a founder. This is enforced, not promised: from block #25,000 those coins are locked by consensus and can only ever move through the canonical Historical DTD Jackpot transaction — a valid signature is no longer authority over them.

⚠️ V15 hard fork — mandatory node & miner update

V15 activates on SOST mainnet at block 25,000. This is a consensus-breaking upgrade. Every node operator and every miner must be running the final V15 release before block 24,900.
UPDATE DEADLINE:             BEFORE #24,900
FINAL RELEASE:               PUBLISHED — v0.4.1-v15-final
V15 CONSENSUS ACTIVATION:    #25,000
FIRST HISTORICAL JACKPOT:    #25,290
SECOND CONSENSUS ACTIVATION: NONE
V15 ACTIVATION AT #30,000:   NONE
#24,900 is a deadline, not a start date. Do not plan to upgrade between #24,900 and #25,000 — that gap is only 100 blocks, and SOST block times are highly variable. In the last seven days, 100 consecutive blocks have passed in as little as 5 h 50 min of wall-clock time.

What changes at #25,000. Emission becomes 50 % miner / 50 % DTD. Gold Vault and PoPC Pool stop receiving new emission (0 %). The balance already accumulated is locked by consensus and becomes spendable only through the canonical Historical DTD Jackpot transaction — a valid signature is no longer authority over those coins. The Historical DTD mechanism becomes part of the V15 rules at #25,000; its first scheduled jackpot payout is #25,290.

There is no second consensus activation at #30,000. DTD stays permissionless — no bond, no registration, no whitelist. One upgrade, one activation height: #25,000.

Binaries. Node operators must update sost-node; miners must update sost-miner. The canonical V15 release also includes matching sost-cli and sost-signtx, which should be updated where installed. The release will publish the final commit, SHA256 for all four binaries and the build manifest, so every operator can verify their binaries independently.

The final release is published. Release v0.4.1-v15-final · release commit bacd6281 · consensus commit 16b50a4b. Download the binaries and verify the SHA256 before installing: github.com/Neob1844/sost-core/releases/tag/v0.4.1-v15-final

🔑 SHA256 of the released binaries

Published here as well as on GitHub, so you can cross-check the two sources independently. If they ever disagree, do not install — ask on Telegram first.

8c8ff89740d1b43a8c925d7d9ec398e4989a3d4de5759785aa84e3945b79bc4c  sost-node
7379d34b74a34463745ad0885c170d2ca3bbd77efadf689aef6039ae34c1dace  sost-cli
1a21a962c67b400814edde214d52176c28538c35ae67c8a366d7fde6ad34b9ab  sost-miner
ac08c347ad315d3e1fb6bbbd49ebb6079ecdf5f1e914278a9df0f295e0fa67d9  sost-signtx

🔧 How to update

Option A — download the released binaries and verify them (recommended):

cd /tmp && R=https://github.com/Neob1844/sost-core/releases/download/v0.4.1-v15-final
for b in sost-node sost-cli sost-miner sost-signtx; do curl -LO $R/$b; done
curl -LO $R/SHA256SUMS_V15_FINAL.txt
sha256sum -c SHA256SUMS_V15_FINAL.txt        # must print OK for all four

sudo systemctl stop sost-node                # node operators only
sudo install -m 0755 sost-node sost-cli sost-signtx /opt/sost/build/
sudo install -m 0755 sost-miner /opt/sost/build/
sudo systemctl start sost-node
sha256sum /opt/sost/build/sost-node          # must equal the published hash

Option B — build from source and reproduce the release:

cd /opt/sost && git fetch origin && git checkout main && git pull --ff-only origin main
git rev-parse HEAD                            # must be bacd6281…
cmake -S . -B build -DSOST_ENABLE_PHASE2_SBPOW=ON -DSOST_TESTNET_FORKS=OFF \
      -DSOST_DEVNET_FORKS=OFF -DCMAKE_BUILD_TYPE=Release
cmake --build build --target sost-node sost-cli sost-miner sost-signtx -j$(nproc)
sudo systemctl restart sost-node

The three build flags are mandatory. A binary built without them will not follow mainnet consensus. Toolchain used for the published binaries: g++ 11.4.0, cmake 3.22.1, ld 2.38, glibc 2.35, OpenSSL 3.0.2 — a different toolchain produces a different SHA256 for the same source, which is expected; verify against the manifest.

Check afterwards: sost-node --version, getblockcount advancing, and getpeerinfo showing at least one peer.

Nodes and miners still running the earlier build will diverge from the main chain after activation.

⚛️ Atomic Swap stays in controlled founder testing (not a public DEX). V15 final is published and deployed; consensus activates at block #25,000. The final build and exact upgrade steps will be published before activation. Details: sostcore.com · t.me/SOSTProtocolOfficial
◈ UPDATE — gold store-of-value plan no longer active. The initial plan (Perpetual Gold Vault · PoPC gold emission · “up to 50% → Gold”) has been temporarily replaced by the DTD (Deterministic Token Distribution) at V15 (block #25,000): the 50%/block that would have funded gold is redirected to the DTD, and the reserve already accumulated is returned to participants via the DTD Jackpot. This page is kept for the historical record. Learn about the DTD →
BOND STAKING

PoPC
Bond Staking

A single native SOST bond is the only collateral and the only thing slashable — a voluntary, time-bound commitment with automatic economic consequences. Create, monitor, and claim your bond. No oracle. No custodian. No governance. PoPC bonds are not tradeable in V15.

PoPC | 25% of coinbase · ConvergenceX entropy audits · Automatic slashing
⚠ CURRENT STATUS

PoPC is implemented in the SOST node software and fully documented, but it is not yet active on mainnet. The single-bond model activates at V15 / block 25,000; from block 30,000 holding an open PoPC contract is required to be eligible for the DTD lottery (a 5,000-block grace window after activation). Gold Boost is disabled on mainnet (deferred, optional reward only — never collateral, never slashed). PoPC bonds are not tradeable in V15. Activation is protocol-scheduled and subject to network readiness, external audit, and all technical validation prerequisites being met.

✔ Implemented in software ✔ Documented publicly ✔ RPC interfaces ready (create / monitor / claim) ● Single native SOST bond model ✘ Activates at V15 / block 25,000 ✘ Gold Boost disabled on mainnet ✘ Not tradeable in V15 (no contract/position trading)
OVERVIEW

What PoPC Is

NOT A GOLD TOKEN
PoPC does not tokenize gold. Does not promise yield, stability, or redeemability. It is a commitment protocol with automatic consequences.
VOLUNTARY COMMITMENT
A participant locks a native SOST bond for a defined period — a voluntary, time-bound commitment. The bond is the only collateral. No gold is required.
ONE SLASHABLE ASSET
The native SOST bond is the only thing that can be slashed — automatically, no human judge, on a protocol-defined bond failure. Settlement & audit schedule derives from PoW entropy.
GOLD IS AN OPTIONAL BOOST
Optionally, holding tokenized gold (XAUT/PAXG) adds a reward boost on top of the base. Gold is never collateral and never slashed — if it can’t be verified, you simply get no boost. No custodian. No bridge.
AUDIT SYSTEM

ConvergenceX Entropy Audits

Deterministic Audit Schedule
ENTROPY-DERIVED

No party — not the protocol, not any server — decides when a user gets audited. The schedule is derived deterministically from the ConvergenceX entropy triple: (block_id, commit, checkpoints_root).

// Native SOST bond (Phase 1 — in-consensus, trustless) // base reward by lock duration; the bond is the ONLY // slashable asset. slash trigger: protocol-defined bond failure. // Optional Gold Boost (Phase 2 — off-consensus, non-critical) seed = SHA256( block_id || commit || checkpoints_root ) r = PRF( seed, contractId, periodIndex ) if r < p: GOLD-BOOST CHECK verify tokenized gold (XAUT/PAXG) ≥ eligibility if verified: boost continues if not verified: no boost // never a slash, lock or penalty
Gold 0–30 days verified
boost = +0% — base reward only
Gold 31–90 days verified
boost = +10% — on top of base
Gold 91+ days verified
boost = +20% — operational cap
Gold withdrawn / unverifiable
revert to base — no penalty, no slash
⚠ HISTORICAL — SUPERSEDED DESIGN

The Model A / Model B design and the Ethereum SOSTEscrow contract below are historical. PoPC has been redesigned into a single native SOST bond (the only collateral, the only thing slashable). Gold is an optional reward boost — never collateral, never slashed — and is disabled on mainnet. There is no PoPC contract trading and no SOSTEscrow-based PoPC product in V15. The sections below are kept for reference only; the live behaviour is the single-bond model that activates at V15 / block 25,000.

MODEL A — HISTORICAL

Commitment with SOST Bond

Model A — Autocustody
FOR CRYPTO NATIVES

The gold never leaves the user’s wallet. Only the SOST bond is at risk. The protocol has no access to, custody of, or control over the user’s gold tokens.

1. User buys SOST on CEX 2. Declares Ethereum wallet holding XAUT/PAXG 3. Locks SOST bond (dynamic, based on ratio SOST/gold) 4. Commits to maintain custody for 1/3/6/9/12 months 5. ConvergenceX entropy schedules random audits 6. Script verifies XAUT/PAXG balance via Ethereum RPC 7. On completion: recovers bond + reward from PoPC Pool 8. On failure: bond SLASHED automatically
1 monthup to 1% of bond in SOST
3 monthsup to 4% of bond in SOST
6 monthsup to 9% of bond in SOST
9 monthsup to 14% of bond in SOST
12 monthsup to 20% of bond in SOST

Rates are base maximums (Tier 1 — first 25 contracts). A dynamic participation tier system reduces rates as the number of active contracts grows: 100% (0-25), 75% (26-50), 50% (51-100), 30% (101-200), 15% (201-500), 8% (501-1000). Hard cap: 1,000 SOST max per contract. Max 1,000 active contracts. Anti-whale tiers apply above 10 oz. Protocol fee: 3% (Model A — lower fee rewards risk-taking).

Dynamic Bond Sizing
CONSTITUTIONAL C9

Bond percentage depends on the SOST/gold price ratio. As SOST appreciates relative to gold, the bond percentage decreases (less SOST needed). Pricing initially fixed (SOST=$1, gold=$10,000/oz), updated when SOST trades on exchanges.

ratio < 1%25% bond // SOST very cheap vs gold (current)
ratio 1-5%20% bond
ratio 5-10%15% bond
ratio 10-50%12% bond
ratio ≥ 50%10% bond (minimum)

Source: compute_bond_pct() in src/popc.cpp

MODEL B — HISTORICAL

Timelocked Escrow

Model B — No Audits, No Slash
FOR GOLD INVESTORS

User deposits XAUT/PAXG into an immutable escrow timelock contract (no admin key, no upgrade proxy, no pause function). Receives SOST immediately. At expiry, only the original depositor can withdraw full gold. No early exit.

// Escrow architecture contract = immutable // no proxy, no UUPS, no admin functions: deposit(token, amount, unlockTime) + withdraw(depositId) withdraw = ONLY by original depositor withdraw reverts if block.timestamp < unlockTime Protocol CANNOT access escrowed gold // SOST reward delivered IMMEDIATELY at deposit SOST_reward = gold_value × APR(duration) × (months / 12) / sost_price // User keeps SOST from day 1 — no vesting, no clawback
1 monthup to 0.4% of gold value, paid in SOST at deposit
3 monthsup to 1.5% of gold value, paid in SOST at deposit
6 monthsup to 3.5% of gold value, paid in SOST at deposit
9 monthsup to 5.5% of gold value, paid in SOST at deposit
12 monthsup to 8% of gold value, paid in SOST at deposit

Rates are base maximums (Tier 1). Same dynamic participation tiers apply as Model A. Hard cap: 1,000 SOST max per contract. Anti-whale tiers apply. Protocol fee: 8% (Model B — higher fee compensates zero risk).

GUIDE

How to Create a PoPC Contract

Model A — Step-by-Step
AUTOCUSTODY

Prerequisites

• An Ethereum wallet (MetaMask, Ledger, etc.) holding XAUT or PAXG tokens
• A SOST wallet with enough SOST to cover the bond
• Access to the SOST web wallet at sostcore.com/sost-wallet.html

Step 1: Calculate Your Bond

Go to the PoPC Registration section in the SOST wallet. Enter:
• Your Ethereum wallet address (0x...)
• How much XAUT you hold (in oz)
• How much PAXG you hold (in oz)
• Commitment duration (1, 3, 6, 9, or 12 months)

The calculator will show you exactly how much SOST you need to lock as bond and your expected reward (adjusted by current pool utilization).

Step 2: Register Your Commitment

Click "Register & Lock Bond". This calls the popc_register RPC command, which:
• Validates your Ethereum address and gold amounts
• Calculates your bond based on the current SOST/gold price ratio
• Calculates your dynamic reward (based on pool utilization)
• Reserves your reward in the PoPC Pool
• Returns your commitment_id and the exact bond amount to lock

Step 3: Lock Your Bond

Create a BOND_LOCK transaction for the exact SOST amount shown:
• In the SOST wallet: go to Send
• Or via CLI: sost-cli create-bond <amount> <lock_blocks>
• The bond is time-locked on the SOST blockchain (cannot be spent until your commitment period ends)
• Your bond is safe — it returns to you on successful completion

Step 4: Maintain Custody

Keep your XAUT/PAXG in your Ethereum wallet for the entire commitment period.
• Random audits are scheduled by ConvergenceX block entropy (you cannot predict when)
• An automated script checks your Ethereum balance periodically
• If your balance drops below the committed amount → your bond is slashed
• If you maintain custody → you receive bond + reward at the end

Step 5: Collect Bond + Reward

When your commitment period ends:
• The operator runs popc_release for your commitment
• Your bond is unlocked and returned to your SOST address
• Your reward is sent from the PoPC Pool to your SOST address
• Your reputation increases (more reputation = higher gold limits, fewer audits)

// Example: 1 oz gold ($10,000), 6-month commitment, SOST=$1 1. Gold value: $10,000 = 10,000 SOST equivalent 2. Bond: 25% of gold value = 2,500 SOST locked 3. Max reward: 9% of bond = 225 SOST (dynamic, adjusted by PUR) 4. Protocol fee: 3% of reward = 6.75 SOST 5. Net reward: ~213.75 SOST (at PUR=0%) 6. Total return: 2,500 + 213.75 = 2,713.75 SOST 7. Your gold: never moved — stays in your Ethereum wallet
Model B — Step-by-Step
ESCROW

Prerequisites

• XAUT or PAXG tokens in an Ethereum wallet
• A SOST wallet address to receive rewards
• Access to the escrow contract on Ethereum (address provided by SOST Governance)

Step 1: Deposit Gold into Escrow

Send your XAUT or PAXG to the immutable escrow contract on Ethereum:
• The contract has no admin key, no upgrade proxy, no pause function
• Call deposit(token, amount, unlockTime)
• Your gold is locked until the unlock time (1-12 months from now)
• Only YOU can withdraw after the lock expires — the protocol cannot access it

Step 2: Register on SOST

In the SOST wallet, register your escrow:
• Enter the Ethereum escrow contract address
• Enter your gold amount and duration
• The system calls escrow_register which verifies your deposit
• Your SOST reward is calculated and paid IMMEDIATELY

Step 3: Receive Reward Immediately

Unlike Model A, Model B pays the SOST reward upfront:
• Reward is sent from the PoPC Pool to your SOST address
• No vesting, no clawback
• You can use the SOST immediately

Step 4: Wait for Lock to Expire

• No audits — your gold is provably locked in the escrow contract
• No slash risk — there is no bond to lose
• Just wait for your chosen duration to pass

Step 5: Withdraw Your Gold

After the lock expires:
• Call withdraw(depositId) on the Ethereum escrow contract
• 100% of your gold is returned to your Ethereum wallet
• Register completion on SOST via escrow_complete

// Example: 1 oz XAUT ($10,000), 6-month escrow, SOST=$1 1. Deposit 1 oz XAUT into escrow contract (Ethereum TX) 2. Register on SOST → system verifies escrow deposit 3. Max reward: 3.5% of gold value = 350 SOST (dynamic, Tier 1) 4. Protocol fee: 8% = 28 SOST 5. Net reward: ~427.50 SOST paid immediately 6. After 6 months: withdraw 1 oz XAUT from escrow 7. Result: you keep 427.50 SOST + your 1 oz gold
// SOSTEscrow.sol — IMMUTABLE TIMELOCKED GOLD ESCROW CONTRACT
SOSTEscrow — Solidity ^0.8.24 — MIT License

Constitutional Properties:
NO admin key • NO upgrade proxy • NO pause • NO emergency withdrawal
Only the original depositor can withdraw • Only after timelock expires
Accepted tokens: XAUT (Tether Gold) + PAXG (Paxos Gold) — immutable allowlist
Lock duration: 28–366 days • ReentrancyGuard on all external calls

Functions:
deposit(token, amount, unlockTime) → depositId
  Transfers ERC-20 gold tokens to contract. Records deposit. Emits GoldDeposited.
withdraw(depositId)
  Returns tokens to depositor after timelock. Checks-effects-interactions pattern. Emits GoldWithdrawn.
getDeposit(id) • canWithdraw(id) • getUserDepositIds(user) • totalLocked(token)

Minimum Deposits:
XAUT: 1,000 units (6 decimals) ≈ 0.001 oz troy
PAXG: 1,000,000,000,000,000 units (18 decimals) ≈ 0.001 oz troy

Trust Model:
The contract holds gold tokens on Ethereum. SOST rewards are paid on the SOST chain by an off-chain watcher daemon that detects GoldDeposited events. The contract does NOT know or control SOST chain addresses. Reward payout, PoPC Pool, and Gold Vault are SOST-side consensus logic — separate from this Ethereum contract.

Status: Internally hardened and reviewed. Not externally audited. Testnet deployment pending.

Full source: contracts/SOSTEscrow.solFull contracts directoryInternal review report
Model A vs Model B — Which to Choose?
FeatureModel A (Autocustody)Model B (Escrow)
Gold locationYour Ethereum walletEscrow contract
SOST bond required?Yes (25% of gold value)No
When do you get reward?At completion (end)Immediately
Audits?Yes (random, PoW entropy)No
Slash risk?Yes (bond lost if custody fails)No
Max reward (12mo)20% of bond (Tier 1)8% of gold value (Tier 1)
Hard cap1,000 SOST max per contract · 1,000 active contracts max
Best forCrypto natives, HODLersGold investors, risk-averse
Dynamic Participation Tiers
AUTO-REGULATING

Reward rates decrease automatically as the number of active contracts grows. Early adopters receive the highest rates. This prevents pool depletion while incentivizing early participation.

TierActive ContractsMultiplierModel A 12moModel B 12mo
EARLY ADOPTER0 – 25100%20% of bond8% of gold
GROWTH26 – 5075%15%6%
ESTABLISHED51 – 10050%10%4%
MATURE101 – 20030%6%2.4%
SCALE201 – 50015%3%1.2%
MASS501 – 1,0008%1.6%0.64%
HARD CAPS
Max reward per contract1,000 SOST — absolute ceiling regardless of tier
Max active contracts1,000 — no new registrations beyond this
Max gold per contract200 oz — anti-whale hard cap (above 10 oz: reduced rates)
Reward floor10 SOST (Model A) / 5 SOST (Model B) — minimum per contract
Protocol fee3% Model A (risk-taker discount) / 8% Model B (zero-risk premium)
Pool protectionPUR quadratic curve (1-PUR)² + solvency check at registration
Where Rewards Come From
TRANSPARENT

PoPC rewards are funded exclusively by the PoPC Pool, which receives 25% of every mined block by consensus rule. This is not printed money — it is a fixed share of new SOST emission, allocated at genesis and enforced by every node on the network. The pool grows with every block and shrinks only when rewards are paid out.

Source25% of coinbase reward → PoPC Pool (consensus-enforced)
Income~283 SOST/day at current emission rate (~8,479 SOST/month)
ProtectionPUR (Pool Utilization Ratio) closes new registrations before pool is depleted
SustainabilityPool income continues for 30+ years (smooth emission decay, no halvings)
⚠ Important Notice
All SOST and USD values shown in examples are illustrative only, based on temporary reference prices. Actual values depend on market conditions at the time of contract creation. Reward percentages are fixed protocol rules; SOST and USD equivalents are not. PoPC is not a yield product, not a price guarantee, and not financial advice. It is a structured incentive mechanism with transparent, predefined rules.
DEPLOYMENT

Activation Conditions

PoPC Activation Requirements
CONDITION-DEPENDENT

The single native SOST bond model activates at V15 / block 25,000, once the following technical and network conditions are met. Activation proceeds only when the system is stable, all components are operational, and external audit is complete.

Block height ≥ 25,000 (V15)PoPC subsystem activation. Tied to the V15 protocol milestone; will not occur before this threshold.
Block height ≥ 30,000 (DTD lottery eligibility)From this height, holding an OPEN PoPC contract is required to be eligible for the DTD lottery. Activation at 25,000 + a grace window (5,000 blocks) before eligibility is enforced.
Sustained network stabilityConsistent block production, stable sync across nodes, no critical consensus or networking issues.
Sufficient participationMinimum level of independent nodes and active miners to ensure reliable operation.
Single-bond contract validationRegistration, audit, reward, and slashing flows for the native SOST bond fully validated under live network testing.
Explorer & wallet integrationCreate / monitor / claim flows correctly reflected in public interfaces (pending, active, completed, slashed). Gold Boost and any Ethereum escrow path are historical / deferred — not required for V15.

Activation note: PoPC activation is protocol-scheduled but condition-dependent. The protocol will announce activation with sufficient advance notice once all conditions are verified.

ENFORCEMENT

Slash Mechanics

Automatic Slashing (native SOST bond)
CONSTITUTIONAL C7/C8

If the native SOST bond commitment fails under consensus rules, the bond is slashed automatically — no human can override once triggered. Gold is never slashed. The recycled bond remains inside the PoPC economic system according to protocol rules.

Trigger
Protocol-defined bond failure
automatic
no human override
Slashed bond
Recycled per protocol rules
stays in the PoPC
economic system
Gold
Never slashed
optional boost only
never collateral
EXTENSIONS

Physical Gold & ZK Proofs

Year 2–3: Physical Gold
EXTENSION

PoPC extends to physical gold (bars, coins, ingots). Users commit to custody of physical precious metals. Audit challenges derived from ConvergenceX entropy, executed via mobile app. No gold amount, location, or identity on-chain.

Year 3+: ZK Proofs
R&D

Zero-Knowledge proofs certify that the correct challenge algorithm executed correctly — without revealing data. Scope extends to platinum, palladium, rhodium. Will not deploy in a degraded state. Participants’ physical security is a non-negotiable prerequisite.

Timeline Flexibility Notice: The protocol reserves the right to accelerate or delay any committed timeline if it determines that the protocol can be implemented with maximum guarantees of technical reliability and security, or if additional development time is required to meet those standards.
TOOLING

Operator & Participant Tools

Read-only scripts for monitoring the pool, auditing commitments, and understanding Model B's roadmap. All live in scripts/ in the repository.

popc_monitor.py

Live dashboard for the PoPC Pool. Shows pool balance, active contracts, PUR%, current reward tier, dynamic factor, and effective rewards at the current tier. Alerts when PUR crosses 50%.

python3 scripts/popc_monitor.py \
  --rpc-user USER --rpc-pass PASS \
  --watch 30

Read-only · no consensus interaction · one-shot or --watch N mode.

popc_oracle.py

Etherscan audit tool. For each active commitment, queries the declared Ethereum wallet's XAUT/PAXG balance and compares it to the committed gold amount. Prints PASS/FAIL/ERROR per commitment and writes a CSV snapshot.

python3 scripts/popc_oracle.py \
  --rpc-user USER --rpc-pass PASS \
  --etherscan-key KEY \
  --csv /tmp/audit.csv

Read-only · never slashes automatically · operator decides on failures.

Model B roadmap (historical)

Historical roadmap for the Ethereum escrow smart contract that the old Model B required. Kept for reference only.

Status: historical / superseded — replaced by the single native SOST bond model (activates at V15 / block 25,000). The SOSTEscrow / Model B path is not part of V15.

Read the roadmap on GitHub →
First-time participant? Read the step-by-step guide at sost-popc-quickstart.html — no prior SOST experience required.
🎮