Choose where your application runs
Syscoin is a Bitcoin-merge-mined blockchain. It supports direct asset payments and Ethereum-compatible contracts on mainnet, and the zkSYS design adds execution chains that settle batches back to the base. Choose the record your application needs and the parties your users will rely on to verify it. Syscoin in a nutshell · Network and release status
| I need to… | Execution path | First thing to inspect |
|---|---|---|
| Send SYS or transfer a supported UTXO asset | Core checks the inputs, outputs, and spending conditions. For eligible asset transfers, Z-DAG offers an early conflict check. | Look up the transaction on the active Core chain. For a pending allocation transfer, read the Z-DAG status. |
| Deploy a contract directly in Syscoin’s Ethereum-compatible environment | NEVM executes the contract in blocks paired with Core. | Check the network’s chain ID, then the transaction receipt. NEVM commands |
| Give users fast local execution and settle batches on the base | A zkSYS Edgechain executes the application. Core carries its batch data. Gateway is the shared chain that settles Edgechain batches and submits its own batches to NEVM. Genesis is a public testnet. | Inspect the local receipt, then follow the covering batch through the configured verifier. zkSYS lifecycle |
An application's evidence path determines what its users can check after an operator goes offline. A UTXO recipient can verify the output on Core. An Edgechain reader who wants to replay old batches also needs a known prior state and someone who kept the batch bytes. UTXO assets · Retention and replay
Choose the deployed network before choosing a wallet or endpoint. The public zkSYS Genesis testnet and Tanenbaum NEVM have different chain IDs and separate balances. Network and release status · Public Genesis settings