Satoshi CashNetwork

Protocol overview

Bitcoin-compatible foundations, RandomX mining

Scash builds on Bitcoin Core, retaining familiar transaction, scripting, wallet, and RPC concepts while changing proof-of-work and network-specific parameters.

Read the protocol specificationInspect the source

Design

What stays familiar and what changes

Compatibility reduces the amount of new infrastructure and knowledge required, while targeted consensus changes define Scash as a separate network.

Proof-of-work

RandomX 1.2.1 with header commitments

Miners compute RandomX work using epoch-derived keys. Extended block-header data commits to that work, while block identifiers retain Bitcoin-style double-SHA256 behavior.

See how CPU mining works →

Transactions

Bitcoin-style model

Familiar unspent transaction outputs, transaction scripts, addresses, fees, and confirmation concepts remain useful to wallet and integration developers.

Difficulty

2,016-block retargets

Difficulty targets a ten-minute block interval and adjusts every 2,016 blocks, with the documented historical off-by-one calculation corrected.

Interfaces

Core-style GUI and RPC

Node operation, wallet management, block inspection, and integration workflows build on familiar Bitcoin Core concepts and commands.

Network identity

Separate consensus network

Scash uses its own network identifiers, ports, address prefixes, genesis data, and RandomX-specific fields. Bitcoin and Scash assets are not interchangeable.

Validation path

Specification and software versions

The protocol specification describes Scash’s original Bitcoin Core v26 basis. The linked Scash 2.0.0 release identifies a Core 27.0.0 basis. Treat the specification as a protocol reference and check the implementation and release notes for version-specific behavior.

How a node evaluates work

A miner assembles a candidate block, derives the required RandomX work for the active epoch, and searches for a result below the current target. The block carries the data required for other nodes to verify the proof under Scash consensus rules.

Independent nodes then validate proof-of-work, block structure, transactions, scripts, monetary issuance, and chain history. Explorers provide convenient public views, but they do not replace validation by software you control.

The verification rules and 2,016-block retarget interval are documented in the specification’s block validation and difficulty adjustment sections.

Why RandomX targets general-purpose processors

RandomX uses memory-intensive, dynamically generated workloads intended to make efficient implementation resemble a general-purpose CPU. That design narrows the advantage available to narrowly specialized mining hardware, but it does not make every processor equally fast or guarantee permanent hardware equality.

Integration checklist

  • Use the current specification. Confirm network magic, ports, address encodings, header format, and consensus constants from maintained sources.
  • Do not assume Bitcoin defaults. Similar interfaces do not mean the networks or all policy settings are identical.
  • Test against your own node. Exercise address creation, transaction handling, reorganization behavior, and RandomX-specific RPC data.
  • Track releases. Experimental network software can change; pin compatible versions and read release notes before deployment.

Updated · About this website and corrections