Skip to main content

Bitcoin technology in Syscoin

Syscoin Core derives its UTXO transaction model, Script interpreter, and wallet tooling from Bitcoin Core. Syscoin uses its own network parameters, block format, and consensus rules. AuxPoW adds Bitcoin-compatible merge-mining, and Syscoin’s separate NEVM chain executes EVM transactions. Core architecture · Core release history

Taproot/Schnorr​

Core v5.1.3 enables Taproot on the Syscoin UTXO chain on mainnet and Tanenbaum. Taproot is a SegWit version 1 output type. A key-path spend reveals a BIP340 Schnorr signature for the output key. A Tapscript spend reveals the selected script and control block, which the node checks against the output’s commitment. Unused script branches stay hidden. The amount of witness data and what the spend reveals depend on the path used. Mainnet parameters · Tanenbaum parameters · Syscoin script validation

StandardRole
BIP340Defines Schnorr signatures and x-only public keys on secp256k1.
BIP341Defines the Taproot output, commitment, and key and script spending paths.
BIP342Defines the Tapscript language used by the corresponding script-path leaf version.

Syscoin uses Bech32m for Taproot addresses and applies the selected network’s address prefix. Query the network and deployment on your node before integrating wallet or transaction tooling. Add -testnet for Tanenbaum. Released address encoding · Deployment RPC

syscoin-cli getblockchaininfo
syscoin-cli getdeploymentinfo

Taproot spends rely on secp256k1. The proposed hash-based ChainLocks and Sentry Node identities use separate keys and consensus rules. PQ ChainLocks