Exchange integration guide

Logo alternatives (clickable)

Universal logo, round, transparent background
Coinlike, transparent background
Transparent background, black
Transparent background, white
Recommended logo, round, transparent background


The complete specification is on this page.

The SCS network has confirmation counts depending on the sent coins amount, however the simplest solution is just set a required confirmation count to 7 (maximal amount).

TX fees are depending on TX size, coins amount and message included but should be never more than 0.05 SCS.

Technically minimum payment is 0.001 SCS but it is reasonable to set it to at least 0.1 - 0.5 SCS to prevent network spamming and additional node overhead.

Obtaining sources

Current/work version of sources is on github.
To avoid some shortcomings, it is preferable to get the release version instead of current one.
Latest release (and recommended link) is version v1.2.4


In case that all required prerequisites are installed, the required compilation command is just "make" in "src" directory. This will produce wallet daemon (scashd in the same folder). You don't have to work with ./buildsystem because all committed makefiles are actual for generic linux/unix system.


The RPC command list is the same as for Bitcoin 0.8, with the exception that we are not supporting multisig addresses.


Like in Bitcoin, rpcuser/rpcpassword/rpcport should be added to Scash.conf file.

If your platform does not support PoS staking (the most current cases) please add:


to the Scash.conf file. Otherwise, the withdrawals may not function properly because of locked "staking" coins.

To gain better network stability, it is preferable to add trustnodes section. Trustnode is a node that will never be auto-banned even in the case that we receive some malformed data from it. Of course, this does not mean we trust its data blindly, but it protects the network from connection interruption and network splitting.


Explorer integration

Any object on SpeedCash network can be found in the block explorer with the following query:{object}

Where object can be one of following:

  • Full transaction id (txid)
  • Block id
  • Address

To validate block hash by block index (and check possible network splitting scenarios) the following request can be applied:{blockNumber}

This will return data in JSON format:



In case you have address validator, the Scash addresses are standard Base58 ones with:


2 Replies to “Exchange integration guide”

  1. after i “make” in “src” directory. and the (daemon scashd ) produce wallet is thier how i can run the “scashd “

    1. Just start it:

      The wallet daemon requires configuration with filled
      rpcpassword and
      in file ([somepath]/Scash.conf that fill be displayed after first launch.

Leave a Reply

Your email address will not be published. Required fields are marked *