Syscoin in a Nutshell
Syscoin is a Bitcoin-merge-mined blockchain with its own rules for asset transfers, data publication, and programmable settlement. Its design lets people and autonomous agents act through independently operated applications while sharing a history they can verify for themselves. Core and merge-mining · System architecture
Mission
An open source community dedicated to scaling Bitcoin, especially its proof-of-work security, to meet global needs and emerging use-cases, while sticking as close as possible to Bitcoin's original ideals.
As intelligence gets cheaper, people still have to decide how to share water, energy and computing power. We want communities to make those decisions on their own terms, give their agents limited authority, and leave a record others can verify across distance. Human and AI coordination · Governance
Current Research & Development
Core and its Ethereum-compatible settlement layer, NEVM, run on mainnet. As of November 19, 2026, four projects extend what a node, a wallet holder, or a Bitcoin bridge can verify. Network and release status
- Post-quantum finality · Release candidate. Core nodes verify the hash-based signatures that lock a block directly. SLH-DSA authenticates Sentry operators and their voting keys. WOTS+ signs the scheduled votes. The candidate exercises the handoff on regtest and has no mainnet activation height. How a node verifies a ChainLock
- zkSYS scaling · Public Genesis testnet. Applications run on execution chains called Edgechains. Gateway is their shared settlement chain. It checks Edgechain batches under its configured verifier rules and submits its own batches to NEVM for settlement. Core carries the full batch data, and Gateway carries a 32-byte BLAKE2s identifier per blob. You can follow one payment all the way to Tanenbaum NEVM, where Gateway batch 9,448 used a mock proof. Sharing proof work among independent operators and decentralizing transaction ordering are separate rollout steps. What Gateway does · Trace the payment · Sequencing and proving
- Post-quantum spending · Experimental smart accounts. We’re adding hash-based signing to Pali v5 smart accounts on zkSYS. The account needs the SLH-DSA module, and the native zkSYS verifier checks the signature. Ordinary SYS outputs and NEVM accounts use separate spending rules. Pali’s signing module and the zkSYS verifier
- Bitcoin withdrawals · Bridge research. Participating miners already name Syscoin blocks in Bitcoin coinbases. The proposed BitVM2 bridge would let a challenger use a timely conflicting tag to veto a BTC withdrawal. Witness encryption is a separate line of research into releasing funds against verified evidence. Inspect a miner’s tag · How a withdrawal would be enforced
Why build on Bitcoin mining?
A participating pool can use the same hash attempts to compete for BTC on Bitcoin and SYS on Syscoin. Bitcoin validates its own blocks. Syscoin’s nodes validate the additional transactions, data commitments, and settlement rules. SYS pays for using those services and helps fund the operators who provide them. zkSYS adds a separate reward token tied to SYS stake or eligible Sentry collateral. Whether the revenue attracts more independent operators depends on demand, costs, and who controls the equipment. Follow the mining work and revenue · Who pays whom · zkSYS issuance and fees
Syscoin’s 2021 scaling proposal began with a wallet holder’s problem. Keeping control of your coins is one requirement. Being able to spend them when an operator goes offline is another. Moving execution off the shared chain makes room for more applications, but it also means someone else must be able to recover the data and check the result. The same reasoning applies to an agent acting for a community. Who gave it the right to act, and what can a member verify after the operator is gone? How the design developed, from the wallet holder’s problem to Truth States
Follow the payment
Suppose your wallet sends a payment on zkSYS. It gets a local receipt. Later, someone who never used your wallet wants to check the result after the original operator has gone offline. This example assumes the new finality rules are active and settlement enforces real execution proofs.
- Get a receipt. An operator called a sequencer orders the payment on zkSYS and executes it. The receipt tells your wallet the local outcome. The batch containing the payment still has to reach shared settlement. zkSYS transaction lifecycle
- Inspect the publication. zkSYS groups transactions into a batch and publishes its encoded data on Syscoin Core. A reader can retrieve each blob and hash it to check the batch’s ordered identifiers. After Core’s serving window, the reader needs an archive that kept those bytes. Data publication and retention
- Check which history counts. Bitcoin miners can reuse their work to mine Core blocks. Under the post-quantum rules, a quorum of Sentry Nodes signs the block history, and Core nodes verify those signatures directly. A ChainLock gives readers a common finalized history in which to locate the batch publication. Mining and finality
- Check the result. A prover supplies evidence that the batch obeyed the execution rules. Find the payment’s batch and its acceptance record on Gateway. Then find the Gateway batch that contains that record and follow it to settlement on NEVM. To re-execute the blocks yourself, start from authenticated state and restore the replay inputs, including transactions, block context, protocol version and required preimages. Proof and settlement · Replay inputs
The division of work lets zkSYS respond on its own schedule. Applications that join an Edgechain add execution work there. Their publications consume Core bandwidth and storage, and Core nodes validate blocks and check finality. System map · Costs of independent validation
Try the settlement check on a public Genesis testnet transaction. Follow its receipt to the Edgechain batch on Gateway, then find the Gateway batch on Tanenbaum NEVM. Trace a public testnet transaction
Where the other pieces fit
| Component | Purpose |
|---|---|
| Core | Tracks balances as unspent transaction outputs (UTXOs). Accepts Bitcoin-compatible parent mining work through auxiliary proof of work (AuxPoW). |
| Syscoin Platform Tokens and Z-DAG | Let applications transfer assets directly as Core outputs. For eligible payments, wallets can ask a node for an early mempool conflict signal. |
| Post-quantum ChainLocks | Release candidate. Authenticate Sentry operators with SLH-DSA hash-based signatures. Operators sign scheduled block votes with WOTS+ keys. |
| Proof of Data Availability | Publishes payloads through Core. Gateway can carry compact identifiers while independent readers retrieve and check the larger payloads. |
| NEVM | Runs Ethereum-compatible contracts, including verification and settlement contracts. |
| Gateway | Checks and settles batches from Edgechains. NEVM settles the Gateway batches that record those results. |
| zkSYS | Runs applications on an Edgechain. Genesis is the public testnet. The reference contracts link reward eligibility to SYS and let users pay eligible fees in zkSYS. |
Some of this history is visible from Bitcoin itself. Participating miners publish references to Syscoin ancestors in Bitcoin coinbases. Those references give the proposed BTC bridge a way to detect a withdrawal that points to a conflicting Syscoin history. Two Bitcoin coinbases carrying the same Syscoin reference · How other chains handle settlement and data · Core and NEVM commands
A payment is one example of a state change. A grant to use a shared resource is another. The human and AI design thesis follows a community deciding who can reserve a scarce hour of compute.