BRIDGE · GOLD RESERVE · GOVERNANCE

wSOST & Gold Reserve V2

RESEARCH / DEVELOPMENT ROADMAP #40,000 RESEARCH HORIZON NOT AN ACTIVATION COMMITMENT

How SOST could reach Ethereum wallets, DEXs and exchanges without creating a single new coin, and how a separate, publicly verifiable reserve of tokenized gold could grow around the ecosystem — governed by the miners who also run nodes.

⛔ NOT LIVE

⛔ NO MAINNET BRIDGE DEPLOYED

⛔ NO GOLD RESERVE V2 FUNDS YET

✅ CURRENT SOST CONSENSUS UNCHANGED

#30,000 → #40,000

#30,000 built the current foundation (V30000 is live). #40,000 is the current coordinated research horizon for the next major phase. Nothing activates automatically at #40,000. If engineering, external audit, legal or operational gates are not complete, the work moves later (for example #50,000). Every consensus change would need its own release, tests, audit and public notice.

wSOST Why wSOST / native SOST How to wrap / gas Price discovery Value sources Five boxes Historical Gold Vault Gold Reserve V2 Gold → wSOST desk Bridge trust Proof of reserves Emergency Governance Voting Check eligibility #40,000 BTC / ETH / SOST Get SOST Status matrix

BRIDGE

What is wSOST?

RESEARCH NOT DEPLOYED

wSOST is not another coin. It is a token on Ethereum that represents native SOST one-for-one. The SOST it represents stays on the SOST blockchain, locked in a dedicated Bridge Vault, until the wSOST is turned back into SOST.

CANONICAL RULE

1 wSOST = 1 native SOST locked

Example — John wraps 500 SOST

JOHN HAS 1,000 SOST John wraps 500 SOST 500 SOST ──LOCK──▶ Bridge Vault (SOST chain) ══▶ 500 wSOST (Ethereum) RESULT 500 SOST remain native in John's wallet 500 SOST are locked in the Bridge Vault 500 wSOST exist on Ethereum NO NEW SOST WAS CREATED. The same 1,000 SOST still exist.

Example — John unwraps 200 wSOST

John burns 200 wSOST (Ethereum) 200 wSOST destroyed ══▶ 200 native SOST released from the Bridge Vault (minus the SOST network fee)

PERMANENT SOST INVARIANT

Only wSOST is burned during unwrap. Native SOST is never burned.

How a deposit would work (design)

sost-cli send <BRIDGE_VAULT> 500 --capsule-mode open-note \ --capsule-text "WSOST:0x9f2c…41aa" # 48 bytes of the 80-byte capsule limit

The Ethereum recipient travels inside a capsule, a data field active on SOST since block 7,350. No consensus change, no new transaction type and no special wallet are needed.

Why wSOST would exist

Integrating a brand-new Layer-1 is real work for wallets and exchanges; Ethereum and ERC-20 tokens are already integrated almost everywhere. wSOST would make SOST reachable from:

Ethereum wallets;
DEX liquidity pools and therefore public price discovery;
exchanges where ERC-20 support reduces Layer-1 integration work;
future DeFi compatibility.

WHAT IT DOES NOT DO

wSOST may reduce technical integration friction, but listing, liquidity, legal review and exchange due diligence remain independent requirements. It guarantees no listing anywhere.

ACCESS LAYER

Why wSOST — and why native SOST stays the real asset

RESEARCH NOT DEPLOYED

The integration barrier

One practical barrier to wider SOST market access is the technical burden a centralized exchange faces when it integrates a new, independent Layer-1 blockchain. Listing native SOST would require the exchange to:

run and maintain a SOST full node;
integrate SOST deposits and withdrawals;
implement a SOST-specific confirmation and reorganisation policy;
monitor wallet and node infrastructure around the clock;
review SOST RPC and transaction semantics;
build custody and operational tooling for a new chain;
carry the security and maintenance work specific to SOST.

Ethereum and ERC-20 infrastructure, on the other hand, is already in place at virtually every major centralized exchange: deposits, withdrawals, custody and monitoring for ERC-20 tokens are standard operations there. For such a venue, integrating an ERC-20 representation is operationally much simpler than integrating a new chain.

WHAT wSOST IS FOR

wSOST is intended to reduce integration friction for venues that already support Ethereum/ERC-20 infrastructure. It is being researched as an access layer. It does not guarantee that any exchange will list it, and listing, liquidity, legal review and exchange due diligence remain independent requirements.

native SOST → lock 1:1 → wSOST (ERC-20) → Ethereum wallets · DEX · compatible CEX infrastructure

What would be listed

The initial exchange-access target is wSOST: the representation offered to CEX and DEX venues where integrating the native SOST chain is impractical or unnecessarily complex. wSOST does not replace SOST. wSOST is designed to make SOST easier to integrate without replacing the native SOST network.

NATIVE SOST — THE CANONICAL ASSET

Native SOST remains:

the real Layer-1 asset;
the asset created and distributed by SOST consensus;
the asset received through mining, through normal DTD and through the DTD Jackpot;
the asset used for native transfers and in the SOST-side atomic swap;
the asset locked behind wSOST;
the final settlement asset when wSOST is unwrapped.

1 wSOST = 1 native SOST locked. Native SOST is the source asset; wSOST is only its external Ethereum representation. There is no independent wSOST monetary policy, no new native SOST is created by wrapping, and native SOST is never burned.

Example — John reaches an Ethereum-compatible exchange

JOHN HAS 1,000 native SOST He wraps 400 SOST RESULT 600 native SOST remain in his wallet 400 native SOST are locked in the Bridge Vault 400 wSOST are issued → he can send them to a compatible Ethereum / exchange address Later he unwraps 100: 100 wSOST are burned → 100 native SOST are released wSOST is the transport and market representation. Native SOST remains the underlying asset.

Three roles, three layers

NATIVE SOST

Canonical Layer-1 asset. Mining, DTD, Jackpot and native settlement. Created only by SOST consensus. LIVE

wSOST

1:1 Ethereum representation. Intended CEX/DEX access layer. Always backed by locked native SOST. Not a new monetary asset. PLANNED NOT DEPLOYED

GOLD RESERVE V2

External tokenized-gold reserve: XAUT first, other approved gold assets later. Does not mint SOST. Does not mint wSOST. Creates no peg and no guaranteed floor. PLANNED NOT FUNDED

MINING / DTD / ATOMIC SWAP ↓ NATIVE SOST ↓ WRAP 1:1 ↓ wSOST ↓ CEX / DEX / ETHEREUM XAUT / APPROVED GOLD → GOLD RESERVE V2 Historical Gold Vault: SEPARATE → DTD JACKPOT

Native SOST remains the canonical protocol asset. wSOST is the planned Ethereum-compatible market-access representation. Gold Reserve V2 is the planned external gold-reserve layer.

From the Genesis Gold Vault to Gold Reserve V2

The original SOST design introduced a Gold Vault concept from Genesis: part of the early block distribution accumulated in a constitutional reserve, with the long-term idea of connecting SOST with an external gold reserve. That historical architecture later changed. From block #25,000:

the Gold Vault receives 0% of new emission;
the PoPC Pool receives 0% of new emission;
the current block distribution is 50% miner / 50% DTD;
the historical Gold Vault + PoPC balances are frozen and committed to the DTD Jackpot.

THE HISTORICAL GOLD VAULT IS NOT REOPENED — ITS FUNDS ARE NOT REUSED

Gold Reserve V2 is a new and completely separate external reserve. Gold Reserve V2 is intended to continue the reserve philosophy introduced at Genesis, while preserving the historical Gold Vault exactly as committed under the current DTD Jackpot architecture. The old Gold Vault does not back wSOST, and Gold Reserve V2 does not reuse or alter its balances. HISTORICAL DTD JACKPOT RESERVE

Why wSOST helps the gold-reserve model

wSOST would give SOST an Ethereum-compatible representation, and Gold Reserve V2 would live on the same Ethereum-compatible infrastructure as tokenized gold such as XAUT. In a future, gated phase that makes mechanisms like this possible:

XAUT → Gold Reserve V2 existing treasury wSOST → user without creating new native SOST, without creating unbacked wSOST, and without touching the historical Jackpot reserve.

That gives the Genesis reserve philosophy a practical modern infrastructure — SOST L1 + the wSOST access layer + an external tokenized-gold reserve — while every accounting layer stays separate. GATED OFF

USER GUIDE (DESIGN)

How wrapping would feel — wallets, gas and exchanges

RESEARCH NOT DEPLOYED

Nothing below can be done today. It describes how the planned bridge is designed to work from the user's side.

1 · SOST → wSOST (wrap)

John holds 1,000 SOST and wants 400 of them as wSOST. On the bridge page he enters the amount and an Ethereum address that will receive the wSOST:

Amount 400 SOST Ethereum destination 0x1234… (MetaMask, Rabby, a hardware wallet or any EVM wallet)

His SOST wallet sends an ordinary SOST transaction to the Bridge Vault; the transaction carries his Ethereum address in a capsule. The 400 SOST are locked, not destroyed.

JOHN'S SOST WALLET ──400 SOST──▶ BRIDGE VAULT (SOST chain) capsule: 0x1234… after 30 SOST confirmations (provisional), the observers check: 400 SOST arrived ..................... ✓ to the correct Bridge Vault .......... ✓ Ethereum address is valid ............ ✓ this deposit was never used before ... ✓ 2 of 3 observers sign → a relayer submits → Ethereum mints Bridge Vault 400 SOST locked John's wallet 400 wSOST

Do I need MetaMask?

Not specifically — but you need an Ethereum address if you want to hold the wSOST yourself. MetaMask, Rabby, a compatible hardware wallet or any other EVM wallet works. MetaMask is a convenience, not part of the protocol.

Do I need ETH for gas?

Action	Who pays what
Wrap (SOST → wSOST)	You pay only the normal SOST fee. The design has the bridge relayer pay the Ethereum gas for the mint, so you need no ETH to wrap.
Send wSOST, use a DEX, add liquidity	You need a little ETH for gas in your Ethereum wallet. ETH is not backing and does not buy SOST; it only pays Ethereum to run the transaction.
Unwrap (wSOST → SOST)	Normally a little ETH for gas for the burn on Ethereum. Gas sponsorship could make this easier later.

2 · wSOST → SOST (unwrap)

UNWRAP 200 wSOST → destination sost1abc… Ethereum 200 wSOST burned (you pay the gas) ↓ observers confirm the burn SOST the Bridge Vault releases 200 SOST (minus a small published fee allowance) to sost1abc… John keeps 200 wSOST + 200 SOST back in his SOST wallet

A complete example

John starts with 1,000 SOST and wraps 500: 500 SOST stay native · 500 SOST locked · 500 wSOST in his Ethereum wallet He sells 100 wSOST on a DEX: 500 SOST native · 400 wSOST · plus whatever the 100 wSOST sold for The 400 remaining wSOST are still backed by 400 locked SOST.

If an exchange lists wSOST

An exchange that supports the wSOST ERC-20 does not have to integrate the SOST chain first. A user could even put the exchange's own wSOST deposit address as the Ethereum destination when wrapping, so the wSOST land directly in the exchange account — saving one Ethereum transaction. Only do that if the exchange explicitly supports wSOST deposits; tokens sent to an address that does not credit them can be lost.

Trading inside an exchange (for example USDT ↔ wSOST) needs no MetaMask and no ETH: the exchange runs its own infrastructure. Ethereum only matters when you withdraw wSOST to your own wallet or use contracts directly.

SOST MAINNET │ 400 SOST ▼ BRIDGE VAULT │ 30 confirmations · 2-of-3 observers ▼ ETHEREUM ──▶ 400 wSOST ┌──────────┼──────────┐ ▼ ▼ ▼ Ethereum DEX CEX wallet back: wSOST → burn on Ethereum → observers → Bridge Vault → native SOST

IN ONE SENTENCE

To wrap SOST into wSOST you would not need ETH: you send SOST to the bridge and the relayer pays for the mint. Once wSOST sits in your own Ethereum wallet, moving it, using a DEX or unwrapping normally needs a small amount of ETH for gas.

MARKETS

Price discovery — the 1:1 arbitrage

RESEARCH

Native SOST offered at $0.30 wSOST trading at $0.80 buy 1 SOST at $0.30 → wrap 1:1 → receive 1 wSOST → sell near $0.80 = +$0.50 Many people do it → SOST demand ↑ · wSOST supply ↑ → prices move together

So, once the bridge is liquid and freely usable, the wSOST market price is expected to become a market reference for native SOST. Prices are not guaranteed identical: bridge risk, fees, liquidity, access restrictions and finality delays can create temporary premiums or discounts. A large, persistent gap would mean wrapping is not freely available or the bridge is impaired.

CONCEPT

Five sources of SOST value

#	Source	What it means	Status
1	Monetary scarcity	Hard cap 4,669,201 SOST, smooth decaying emission	LIVE
2	PoW network security	ConvergenceX Proof of Work, nodes verifying every rule	LIVE
3	Utility	DTD, Jackpot V2, capsules, atomic swaps, future native assets	LIVE PARTLY GATED
4	Market access & liquidity	wSOST on Ethereum, DEX pools, exchange integration	RESEARCH
5	External Gold Reserve V2	Publicly verifiable tokenized gold held by the ecosystem	RESEARCH

GOLD DOES NOT SET THE PRICE

The market determines the price of SOST. A gold reserve is verifiable ecosystem wealth — like the cash a company holds, its shares can trade far above or below it.

ACCOUNTING

Five accounts — never mixed

BOX 1 · NATIVE SOST

Ordinary circulating SOST on the SOST chain. LIVE

BOX 2 · BRIDGE-LOCKED SOST

Native SOST locked specifically against wSOST. RESEARCH

BOX 3 · wSOST

The ERC-20 representation of BOX 2, one for one. RESEARCH

BOX 4 · GOLD RESERVE V2

External tokenized-gold reserve on Ethereum. RESEARCH

BOX 5 · HISTORICAL GOLD VAULT + PoPC

Legacy SOST reserve already committed to the DTD Jackpot. HISTORICAL FROZEN · LIVE

RULE

THESE FIVE BALANCES MUST NEVER BE COMBINED OR DOUBLE-COUNTED. Box 2 backs Box 3 and nothing else. Box 4 never backs wSOST. Box 5 is never used by the bridge or by Gold Reserve V2.

HISTORY

The historical Gold Vault

HISTORICAL · BLOCKS 0–24,999

50% miner · 25% Gold Vault · 25% PoPC Pool (draw blocks from #7,100 paid 50% miner / 50% lottery). HISTORICAL

CURRENT · FROM #25,000

50% miner · 50% normal DTD. Gold Vault and PoPC receive 0% of new emission. Their balances are frozen by consensus and pay the DTD Jackpot. LIVE

Live reserve: loading…

The Genesis Gold Vault is the conceptual ancestor of Gold Reserve V2 — a rule-bound reserve with one purpose and public accounting — but it is not the same reserve. It accumulated SOST; Gold Reserve V2 would hold tokenized gold. Historical Gold Vault ≠ Gold Reserve V2.

RESERVE

Gold Reserve V2

RESEARCH NOT DEPLOYED

A new, external reserve on Ethereum. It receives tokenized gold — not newly emitted SOST — and it never mints wSOST.

Asset	Role	Status
XAUT (Tether Gold)	initial intended asset	RESEARCH
PAXG (Paxos Gold)	possible later asset; reportedly not offered in the EU	GATED UNTIL LEGAL / AVAILABILITY REVIEW

SOST LOCKED → backs wSOST 1:1 GOLD RESERVE V2 → holds external gold assets these two statements are never mixed

What the reserve means — and what it does not

ALLOWED WORDING

publicly verifiable reserve · on-chain reserve · rule-constrained reserve · ecosystem reserve · informational reserve ratio

NEVER SAID

gold-backed SOST · guaranteed backing · peg · price floor · redeemable gold · guaranteed value · "$X guaranteed per SOST"

Gold Reserve V2 $250,000 Circulating SOST 2,000,000 Informational ratio $250,000 / 2,000,000 = $0.125 of gold reserve per circulating SOST

READ THIS

THIS IS NOT A REDEMPTION VALUE. THIS IS NOT A GUARANTEED FLOOR. A SOST holder has no right to claim any of the gold.

ISSUER RISK

XAUT and PAXG are issued by companies that can freeze, upgrade or retire their tokens. "Perpetual" can only ever mean "under the reserve's own rules", which is why an emergency migration path exists.

FUTURE MODULE

Gold → wSOST desk

NOT LIVE GATED OFF

Treasury holds 10,000 wSOST already backed by 10,000 native SOST locked A user contributes XAUT worth $1,000 Gold Reserve V2 receives $1,000 of XAUT (permanently) The user receives EXISTING treasury wSOST at the applicable market / auction price Native SOST supply unchanged wSOST supply unchanged — gold arriving does not mint wSOST

Pricing must eventually use a transparent auction or a reliable liquid-market / TWAP methodology — never an arbitrary permanent founder price. This is a sale, not a donation, so the module stays off until legal review and pricing gates pass.

TRUST MODEL

How the bridge would be secured

HONEST STARTING POINT

SOST mainnet does not have operational native multisig today (it exists only as library code). A fully trustless bridge would need Ethereum to verify ConvergenceX blocks, which is impractical in gas. So the bridge relies on attestations — and we say so.

Option	SOST side	Use
A — Capped operator bridge pilot	one cold single-key Bridge Vault (sost1), offline signing, hard exposure cap, public proof of reserves	TEMPORARY · RESEARCH
B — custom threshold / MPC cryptography	key never assembled	REJECTED FOR NOW
C — native SOST multisig	real M-of-N SOST outputs via a future, explicitly activated consensus upgrade	TARGET

The pilot is called a capped operator bridge pilot — federated attestation plus a capped native vault. It is not trustless and not decentralized. The release path talks to a swappable signer interface, so moving from A to C does not redesign deposits, attestations or the Ethereum contract.

Observers — the attestation network

Stage-1 example: 3 observers · 2-of-3 threshold each observer checks independently: correct SOST transaction ................ ✓ pays the Bridge Vault ................... ✓ amount .................................. ✓ Ethereum address from the capsule ....... ✓ confirmations / canonical block ......... ✓ deposit id (txid:vout) never minted ..... ✓ → signs an EIP-712 attestation (chain id, contract, version, nonce) → wSOST contract mints only with ≥ 2 of 3 valid attestations

RELAYER ≠ SIGNER

Anyone may relay signatures to Ethereum; a relayer has no mint authority. During the pilot the observers are operator machines — a 2-of-3 operator quorum, not independent parties.

Confirmations

SOST has observed real short reorganisations (one block replaced at #30,297). The provisional pilot value is 30 confirmations ≈ 5 hours at 10-minute blocks. PROVISIONAL POLICY — not a protocol constant; it will be recalibrated from measured network behaviour.

TRANSPARENCY

Proof of reserves

RESEARCH

CONFIRMED NATIVE DEPOSITS PENDING DEPOSITS MINTED wSOST BURNS PENDING RELEASES COMPLETED RELEASES BRIDGE VAULT BALANCE wSOST TOTAL SUPPLY STATUS: BALANCED · PENDING · CRITICAL

The basic invariant is wSOST.totalSupply ≤ confirmed native SOST backing. That inequality is necessary but not sufficient: a deposit minted twice and a release paid twice can cancel out in the balance. So the indexer reconciles every deposit id, mint, burn and release separately. The SOST side is derived from the SOST chain; the Ethereum side from Ethereum; the browser is never the source of truth.

HEALTHY

500 SOST deposit → waiting confirmations PENDING → 500 wSOST minted BALANCED

FAILURE

100,000 SOST locked 150,000 wSOST supply STATUS CRITICAL ACTION MINTING PAUSED

A failure is shown, never hidden. Transfers of existing wSOST continue while minting is paused.

SAFETY

Withdrawals & emergency powers

RESEARCH

NORMAL WITHDRAWALS: NOT ALLOWED

Gold Reserve V2 contains no withdraw(address) and no equivalent unrestricted destination. The reserve can never go to a founder wallet, a guardian wallet, an arbitrary wallet, an exchange deposit or a treasury account.

Power	Who	Effect
PAUSE	2-of-5 guardians	stops relevant reserve operations. Pause does not move gold. Stolen pause keys can only stop the safe.
CRITICAL RESCUE	4-of-5 guardians, short timelock	Gold Reserve → the predefined Quarantine Vault only, which itself has no withdrawal. Temporary safe custody, not a final migration.
FINAL MIGRATION	all four keys at once (below)	moves assets only to the exact successor vault in the frozen proposal
Guardian recovery	6 months inactivity + public notice + long timelock	replaces guardians; cannot move assets

Critical rescue example

XAUT issuer announces a critical freeze in 6 hours — no time for a 48-hour vote 4/5 guardians → CRITICAL RESCUE → Quarantine Vault (fixed at deployment) later, calmly: guardians + SOST vote → final successor vault never possible, even with 100% of signers: → founder wallet ✗ → exchange ✗ → sold for USDT ✗ → shared out to miners ✗

Final migration — every key at the same time

1. Guardians 4-of-5 2. SOST governance YES from at least 2/3 OF THE FULL ELIGIBLE CENSUS 3. Timelock completed 4. Destination only the exact successor Gold Reserve Vault in the frozen proposal If ANY one fails → NO MIGRATION

Guardians	SOST vote	Destination	Timelock	Result
4/5 ✓	8/12 ✓	approved successor ✓	done ✓	MIGRATES
5/5 ✓	7/12 ✗	approved successor ✓	—	DOES NOT MOVE
4/5 ✓	10/12 ✓	personal wallet ✗	—	DOES NOT MOVE
4/5 ✓	10/12 ✓	approved successor ✓	running ✗	NOT YET

contract surface (design): NO withdraw(address destination) — does not exist YES pause() — 2/5; moves nothing YES rescueToQuarantine(asset) — 4/5; fixed Quarantine Vault only YES migrate(asset, successorVault, proposalId) — registered successor, approved code hash, allowed gold asset, same restrictions, recorded SOST tally hash, timelock elapsed

GOVERNANCE

The second key: SOST participants

RESEARCH PHASE A: ADVISORY

The proposal is frozen before anyone votes

PROPOSAL_ID GRV2-004 SOURCE_VAULT GoldReserveVaultV2 SOURCE_ASSET XAUT v1 SUCCESSOR_VAULT GoldReserveVaultV3 SUCCESSOR_ASSET XAUT v2 SUCCESSOR_CODE_HASH 0x1234… TIMELOCK 7 days SNAPSHOT_HEIGHT #35,712 VOTING_CLOSE #36,000 REASON official XAUT protocol migration

Miners do not vote on "should we move the gold?" — they vote on one exact instruction. If any material field changes, the old vote is invalid and a new proposal and a new vote are required.

Who can vote

Check	Rule (frozen at the snapshot)
Mining identity	valid SbPoW mining identity with the required recent mining activity
NODE_BIND	active binding of that identity to a node key
Heartbeats	required heartbeat participation (the Jackpot V2 framework)
Snapshot	eligibility is fixed at SNAPSHOT_HEIGHT; a later NODE_BIND or later mining does not enter that proposal
Binding age	a minimum NODE_BIND age before the snapshot — value under research

ONE IDENTITY = ONE VOTE

Governance is not weighted by PoW block count (the Jackpot is; governance is not), so a dominant miner cannot decide the reserve alone. NODE_BIND does not prove one unique human: this is protocol-identity governance, not one-human-one-vote.

ON-CHAIN

How a vote is cast and counted

RESEARCH

sost-cli send <identity> 0.001 \ --from-address <identity> \ --capsule-mode open-note \ --capsule-text "SOSTGOV1|GRV2-004|S35712|YES" # or NO / ABSTAIN

The vote is a normal SOST transaction from the eligible identity to itself, carrying the choice in a capsule (28 of the verified 80 bytes). Because it spends from that identity, chain validation itself proves control of the private key — no new message-signing tool is needed. The website never asks for a private key, seed phrase, wallet file or password, and it does not run a central poll: the votes are on the SOST blockchain, and anyone can recount them.

Rule	Exact definition
Valid vote	all inputs spend from the identity; the capsule output pays the same identity; text exactly `SOSTGOV1\|<proposal>\|S<snapshot>\|YES\|NO\|ABSTAIN`; confirmed in (snapshot, close]
Changing a vote	allowed — the last valid confirmed vote before VOTING_CLOSE counts; earlier votes stay on chain
Approval	YES ≥ ceil(2/3 × TOTAL FIXED ELIGIBLE CENSUS) — not 2/3 of those who voted
ABSTAIN	recorded as participation; never counts as YES
Finality	VOTING CLOSED → FINALITY PENDING → FINAL RESULT once the close block is buried by the governance finality depth

Census 12 → YES needed = ceil(12 × 2/3) = 8 Case A 8 YES · 2 NO · 2 no vote → APPROVED Case B 7 YES · 0 NO · 5 no vote → NOT APPROVED (100% of voters said YES — only 7 of 12) Case C 7 YES · 0 NO · 5 ABSTAIN → NOT APPROVED (abstention is not YES) Change #35,800 YES → #35,850 NO → counted as NO; both remain on chain

Status panel — example

ILLUSTRATIVE EXAMPLE · NO LIVE PROPOSAL EXISTS

PROPOSAL GRV2-004 STATUS VOTING ELIGIBLE CENSUS 12 REQUIRED YES 8 YES 8 · NO 2 · ABSTAIN 1 · NO VOTE 1 VOTE PASSED GUARDIANS 4 / 5 TIMELOCK 4d 11h remaining SUCCESSOR GoldReserveVaultV3 EXECUTION WAITING

WHAT THE VOTE IS NOT

SOST voting does not execute Ethereum state directly; guardians execute. If a sufficient guardian majority deliberately ignored a valid vote, the breach would be publicly provable from both chains, but SOST consensus cannot itself stop it. Security comes from four layers — guardians, SOST vote, timelock and the contract's destination restrictions. This is not trustless cross-chain governance.

Advisory first, binding later

Phase	Meaning
A — Advisory	votes run, are public and verifiable, but do not control a vault. The network is small today (very few eligible identities); calling that "the community" would not be honest.
B — Binding	only after an objective, persistent participation condition is met. Maturity criteria under research — no threshold is set without simulation. A UI existing does not make governance binding.

TRY IT

Check my voting eligibility

PREVIEW

No proposal is open, so this checks your mining identity against the current Jackpot V2 participation framework — the base of the planned voter census — using the chain-derived participation index. Binding age is still under research.

If a future wallet integration exists, it would build the vote transaction locally. This page never collects keys.

#40,000

Research horizon — not an activation commitment

RESEARCH NOTICE

#30,000 builds the foundation. #40,000 is the current target research horizon for the next coordinated upgrade — not an activation commitment. Nothing is scheduled until code, tests, external audit and a public announcement exist. If not ready, it moves later (for example #50,000). Current consensus remains 50% miner / 50% DTD.

PILLAR 1 · REWARD EVOLUTION

Research scenario: 80% direct PoW miner · 15% normal DTD · 5% into the existing DTD Jackpot pool. The 5% is not a direct node payment: it accumulates in the Jackpot pool, paid under the applicable Jackpot eligibility rules. No new supply — all from existing block emission. RESEARCH

PILLAR 2 · DECENTRALIZATION

Peer persistence, independent seeds, address gossip, autonomous peer discovery; more independent nodes, operators, providers, jurisdictions and miners; no consensus dependency on sostcore.com infrastructure. Full decentralization is not claimed. RESEARCH

PILLAR 3 · ECONOMIC INFRASTRUCTURE

A mature native-asset framework and the SOST Asset Market: order book, price discovery, atomic settlement, deeper Asset Passport integration, economic-right descriptions and regulatory classification. Intended initial state: technically functional but developer-gated. RESEARCH

NATIVE ASSETS TODAY

At #30,000 V30000 introduced the technical foundation for native assets in a restricted form: ADMIN / DEVELOPER GATED FAIL-CLOSED NOT PUBLICLY ACTIVATED — no public activation date. The Asset Market is not live.

wSOST, Gold Reserve V2 and governance are part of this research horizon. Unlike the 80/15/5 scenario, they need no SOST consensus change: they would run on Ethereum and on existing SOST capsules, behind their own engineering, audit and legal gates.

CONTEXT

Bitcoin · Ethereum · SOST

BITCOIN

Consensus: PoW (SHA-256d). Incentive: the miner/pool receives subsidy + fees. Nodes: validate every rule, unpaid. Wrapped: external wrapped-BTC products exist. Gold reserve: none at protocol level.

ETHEREUM

Consensus: PoS. Participants: validators stake ETH (32 ETH solo). Execution: smart contracts, ERC-20 tokens, DeFi.

SOST

Consensus: ConvergenceX PoW. Block: 50% direct miner / 50% normal DTD. Also: DTD Jackpot V2 with NODE_BIND + heartbeats; SOST-side atomic swap HTLC; PLANNED wSOST bridge and Gold Reserve V2.

SOST COMBINES WORK + PARTICIPATION INCENTIVES

No claim of superiority is made. Nodes are a gate, not a multiplier: the direct mining reward does not grow because a miner runs a node; normal DTD does not require NODE_BIND today; Jackpot V2 uses node participation as an eligibility condition, with weight set by real PoW blocks.

One Proof of Work, two control dials. ConvergenceX defines the work of every attempt. bitsQ sets how rare a winning commit must be (every block; 288-block average; ±15 s dead band; steps 0.5% / 1% / 2% / ≈3.03%). The Equalizer sets how demanding each attempt is (43 profiles E7…B0…H35 from the schedule lag) and never changes bitsQ. Full rules: Technology · comparison with examples: SOST vs Bitcoin vs Ethereum.

HOW TO GET SOST

Three ways — plus wrapping

⚒ 1 · MINE IT

ConvergenceX on CPU + RAM; the finder receives 50% of the block reward. LIVE

🎲 2 · EARN IT THROUGH DTD

Every block, the other 50% goes to one eligible recent miner; plus the Jackpot every 288 blocks. LIVE

⚛ 3 · SWAP FOR IT

Atomic swap: SOST-side HTLC consensus-active since #16,000. SOST SIDE LIVE EVM contract CODE COMPLETE NOT DEPLOYED. An atomic swap transfers existing SOST; it creates none.

WRAP IT — SOST ↔ wSOST

PLANNED Wrapping is not a fourth issuance source: it moves existing SOST into a 1:1 representation on Ethereum.

STATE

Current / future status matrix

Item	State
Block reward 50% miner / 50% DTD	LIVE
DTD Jackpot V2 (NODE_BIND + heartbeats)	LIVE
Gold Vault 25% / PoPC 25% emission	HISTORICAL (blocks 0–24,999)
Gold Vault + PoPC balances	FROZEN · fund the Jackpot
"Gold floor" / gold backing per SOST	RETIRED DESIGN
Native multisig (sost3)	NOT ACTIVE · library code only
SOST-side HTLC	LIVE (consensus since #16,000)
EVM atomic-swap contract	CODE COMPLETE NOT DEPLOYED
BTC atomic-swap signing	lab-verified on a development branch · DISABLED ON MAINNET
Native assets / Asset Market	DEVELOPER GATED
wSOST bridge	RESEARCH NOT DEPLOYED
Gold Reserve V2	RESEARCH NOT DEPLOYED
Gold → wSOST desk	GATED OFF
On-chain SOST governance	RESEARCH · advisory first
80 / 15 / 5 reward scenario	RESEARCH · would need a future hard fork

NO PRICE PROMISES

Nothing on this page is a price forecast, a guaranteed appreciation, a price floor, an investment return or a listing guarantee. Price-discovery mechanics are explained for education only. Full technical detail: Explorer · Whitepaper §3.16.

// BEACON

Beacon — Advisory Channel

Signed operator notices, propagated between nodes. Advisory only. Does not affect mining rewards, block validity, chain selection, transaction validation, wallet balances, PoPC, Gold Vault, or consensus.

Phase II-A — local notices

Each node reads notices.json on startup. ECDSA-SHA256 signature verification against a hardcoded operator pubkey. Failure modes (bad signature, wrong network, expired, malformed) are silent drops. Active at V13_HEIGHT (12,000).

Phase II-B — threshold + revocation

Adds N-of-M threshold signatures (default 3-of-5), revocation by notice ID (only threshold-signed notices can revoke), and an optional mirror_url metadata field (never fetched by the node). Active at V13_HEIGHT.

Phase III — P2P gossip

Nodes gossip verified notices via a BCNN dispatcher with hard limits: 4 KB max notice, 32-notice LRU dedup cache, 8 notices/peer/min rate limit. Bad-signature notices are silently dropped; oversized/malformed/rate-limit hits earn peer misbehavior. Active at V13_HEIGHT.

Hard invariant. No Beacon code path links into block validation, mining validity, or chain commit. Beacon cannot reject, invalidate, or affect the canonical chain. Rollback is a single-line constant revert (BEACON_P2P_ACTIVATION_HEIGHT to INT64_MAX in include/sost/params.h).