# Syscoin developer and agent reference > Public RPC endpoints, UTXO transaction tools, and release status for Syscoin Core, NEVM and zkSYS Genesis. ## Commands and references [Canonical page](https://docs.syscoin.org/docs/reference/overview) **Reading UTXOs or building a SYS payment?** Blockbook gives a script public access to indexed blocks, transactions and unspent outputs. SyscoinJS (SJS) builds UTXO transactions in JavaScript. A local Core node exposes the consensus and mempool RPCs, including ChainLocks and Z-DAG. **Calling an EVM contract?** Use the NEVM or zkSYS JSON-RPC endpoint for the chain where the contract lives. Public reads work without a wallet. [SyscoinJS examples](https://docs.syscoin.org/docs/dev-resources/documentation/javascript-sdk-ref/syscoinjs) · [EVM RPC endpoints and ChainList](https://docs.syscoin.org/docs/reference/nevm#endpoints-and-wallet-settings) ### Start on zkSYS Genesis Open the [zkSYS Portal](https://portal.tanenbaum.io) to connect a wallet and view balances. For a first transaction, get test gas from the [Genesis faucet](https://faucet-zk.tanenbaum.io) and look up the receipt in the [Genesis explorer](https://explorer-zk.tanenbaum.io). The [zkSYS Bridge](https://bridge-zk.tanenbaum.io) shows the available routes for moving supported assets. Scripts connect directly to `https://rpc-zk.tanenbaum.io` on chain ID `57057`. [Genesis quickstart, RPCs and settlement explorers](https://docs.syscoin.org/docs/reference/zksys#start-on-zksys-genesis) ### Read a Syscoin block from a terminal This example uses `curl` and `jq`. The first request identifies the indexer’s chain and sync state. The next two read a public mainnet block and its first transaction. Use `https://blockbook-dev.syscoin.org` for Tanenbaum UTXO reads with a testnet block height or transaction ID. [Mainnet indexer](https://blockbook.syscoin.org/api/v2) · [Testnet indexer](https://blockbook-dev.syscoin.org/api/v2) ```bash book=https://blockbook.syscoin.org curl -fsS "$book/api/v2" | jq '{coin: .blockbook.coin, chain: .backend.chain, inSync: .blockbook.inSync}' txid=$(curl -fsS "$book/api/v2/block/2345720?pageSize=1" | jq -er '.txs[0].txid') curl -fsS "$book/api/v2/tx/$txid" | jq '{txid, blockHeight, confirmations}' ``` The transaction belongs to block **2,345,720**. To read a public address, use `GET /api/v2/address/{address}?details=basic`. To get spendable candidates from confirmed transactions, use `GET /api/v2/utxo/{address}?confirmed=true`. UTXO values are integer strings in satoshis, with 100,000,000 satoshis per SYS. [Blockbook API](https://docs.syscoin.org/docs/dev-resources/documentation/javascript-sdk-ref/blockbook) ### Call your own Core node With a running local daemon, `syscoin-cli` uses the node’s local RPC credentials. Run `syscoin-cli help` to list commands available in that build and `syscoin-cli help ` for parameters and result fields. The example reads the active chain and its tip. On Tanenbaum, add `-testnet` to each call. [Core ports and commands](https://docs.syscoin.org/docs/reference/core) ```bash syscoin-cli getblockchaininfo tip=$(syscoin-cli getbestblockhash) syscoin-cli getblockheader "$tip" ``` ### Build or inspect an application | I want to… | Start here | | --- | --- | | Read a UTXO transaction in JavaScript or build a partially signed Bitcoin transaction (PSBT) for Syscoin | [SyscoinJS installation and runnable examples](https://docs.syscoin.org/docs/dev-resources/documentation/javascript-sdk-ref/syscoinjs) | | Let a user connect or sign a UTXO payment in Pali | The browser dapp uses `window.pali`. [Pali account API](https://docs.paliwallet.com/docs/utxo-syscoin-api/overview) · [Pass a SyscoinJS PSBT to Pali for approval](https://docs.syscoin.org/docs/dev-resources/documentation/javascript-sdk-ref/syscoinjs#hand-a-payment-to-pali-in-a-browser) | | Read EVM balances, contract state or receipts | [NEVM RPC endpoints, ChainList and first request](https://docs.syscoin.org/docs/reference/nevm) · [zkSYS Genesis settings and faucet](https://docs.syscoin.org/docs/reference/zksys#public-genesis-testnet) | | Deploy a Solidity contract on Tanenbaum | [Foundry](https://docs.syscoin.org/docs/dev-resources/nevm/foundry) · [Hardhat](https://docs.syscoin.org/docs/dev-resources/nevm/hardhat) | | Check an unconfirmed Syscoin Platform Token payment | [Z-DAG status codes](https://docs.syscoin.org/docs/dev-resources/sys/z-dag) · [Local Core commands](https://docs.syscoin.org/docs/reference/core#z-dag-status) | | Retrieve a blob and verify its BLAKE2s digest | [Read and hash a Core blob](https://docs.syscoin.org/docs/reference/zksys#read-a-core-blob) | | Follow an Edgechain payment to settlement | [Genesis, Gateway and NEVM transaction trace](https://docs.syscoin.org/docs/reference/zksys#trace-a-public-testnet-transaction) | | Check which features are live on the selected network | [Network status](https://docs.syscoin.org/docs/intro/status) · [Protocol glossary](https://docs.syscoin.org/docs/reference/glossary) · [Research and specifications](https://docs.syscoin.org/docs/reference/research) | | Inspect a funding proposal, vote, or treasury payment | [Governance commands](https://docs.syscoin.org/docs/guides/governance#inspect-proposals-and-the-schedule) · [Dynamic budget and payout example](https://docs.syscoin.org/docs/governance/dynamic-governance) | | Understand the project’s purpose and current work | [Syscoin’s mission](https://docs.syscoin.org/docs/intro/nutshell#mission) · [Current research and development](https://docs.syscoin.org/docs/intro/nutshell#current-research--development) · [How the design developed](https://docs.syscoin.org/docs/reference/research#from-a-computational-court-to-authority-over-scarce-resources) | For agents, the [plain-text developer reference](https://docs.syscoin.org/llms.txt) includes the first requests, SDK examples, and deployment status with canonical links. ## zkSYS and DA commands [Canonical page](https://docs.syscoin.org/docs/reference/zksys) ### Start on zkSYS Genesis Genesis is the public zkSYS Edgechain testnet. You can read it immediately over JSON-RPC. To try an application with a wallet, start at the [zkSYS Portal](https://portal.tanenbaum.io). 1. **Choose the network.** In the Portal, select **zkSYS Tanenbaum** and connect your EVM wallet. For manual setup, use the Genesis RPC and chain ID **57057** below. Chainlist calls the same network *zkTanenbaum Testnet*. [Chainlist wallet settings](https://chainlist.org/chain/57057) 2. **Get gas for a first transaction.** Give the Genesis faucet your public `0x` address to request native test SYS. The Portal and faucet label that balance **TSYS**. The separately issued **zkSYS** reward token has its own contract and Gas Tank. [Genesis faucet](https://faucet-zk.tanenbaum.io) · [Gas Tank and issuance](https://docs.syscoin.org/docs/architecture/zksys#sys-collateral-issuance-and-gas) 3. **Bring existing testnet funds.** The Portal’s **Bridge** moves supported assets between Tanenbaum NEVM and zkSYS Genesis. The separate **zkSYS Bridge** also offers Ethereum Sepolia as a source. The Sepolia-to-Genesis route moves supported tokens through Tanenbaum NEVM before depositing them on Genesis. Choose the source, destination and token shown by the bridge to get the available route. [Portal bridge](https://portal.tanenbaum.io/bridge) · [zkSYS Bridge](https://bridge-zk.tanenbaum.io) · [Sepolia route](https://github.com/syscoin/zksys-bridge/blob/49e733e27504965fb1c871faae6058fcbe28a9a9/bridge-dapp/docs/HYPERLANE_TESTNET_LAUNCH.md#L16-L32) 4. **Find the result.** The Portal’s **Assets** and **Transfers** views show activity for the connected wallet. Paste the Genesis transaction hash into the Genesis explorer to see the receipt and events. A bridge deposit can have a source transaction and a separate destination transaction. [Genesis explorer](https://explorer-zk.tanenbaum.io) · [Portal source](https://github.com/syscoin/dapp-portal/tree/b0bf31c73aaf338d627806d819df57d84b617428) For a first read without a wallet, this request returns the Genesis chain ID (`0xdee1`), client version and sync status. Match the results by request ID. ```bash zk_rpc=https://rpc-zk.tanenbaum.io curl -fsS "$zk_rpc" -H 'Content-Type: application/json' --data '[ {"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}, {"jsonrpc":"2.0","id":2,"method":"web3_clientVersion","params":[]}, {"jsonrpc":"2.0","id":3,"method":"eth_syncing","params":[]} ]' | jq '.[] | {id, result, error}' ``` ### Public Genesis testnet The application executes on Genesis. Its Edgechain batch settles on Gateway, and Gateway’s own batch settles on Tanenbaum NEVM. Each chain has its own block heights, transaction hashes and explorer. [Published network settings](https://syscoin.org/news/zksys-genesis-public-testnet-is-live) | Test network and role | Chain ID | RPC | Public explorer | | --- | --- | --- | --- | | zkSYS Genesis · application execution | 57057 · `0xdee1` | [Public Genesis RPC](https://rpc-zk.tanenbaum.io) | [Genesis explorer](https://explorer-zk.tanenbaum.io) | | Gateway · Edgechain settlement | 57001 · `0xdea9` | [Gateway RPC, operator access](https://rpc-gw.tanenbaum.io) | [Gateway explorer](https://explorer-gw.tanenbaum.io) · [Public blocks API](https://explorer-gw.tanenbaum.io/api/v2/blocks) | | Tanenbaum NEVM · Gateway settlement | 5700 · `0x1644` | [Public NEVM RPC](https://rpc.tanenbaum.io) | [Tanenbaum explorer](https://explorer.tanenbaum.io) | Gateway restricts its JSON-RPC by operator IP allowlist. Public clients can read indexed Gateway blocks and execution events through the explorer API. This call returns the latest indexed Gateway block. [Gateway access policy](https://github.com/syscoin/zksync-os-server/blob/v0.24.4/docs/src/guides/gateway_launch.md#L1767-L1772) ```bash curl -fsS https://explorer-gw.tanenbaum.io/api/v2/blocks | jq -e '.items[0] | {height, hash}' ``` The next request returns the latest and finalized block hashes reported by this node. If the finalized query returns `null` or an error, the endpoint has supplied no finalized block for that request. The worked transaction below follows settlement on Gateway and NEVM. ```bash curl --fail --silent --show-error "$zk_rpc" \ -H 'content-type: application/json' \ --data '[ {"jsonrpc":"2.0","id":1,"method":"eth_getBlockByNumber","params":["latest",false]}, {"jsonrpc":"2.0","id":2,"method":"eth_getBlockByNumber","params":["finalized",false]} ]' | jq '.[] | {id, error, block: (.result | if . then {number, hash} else null end)}' ``` ## NEVM JSON-RPC [Canonical page](https://docs.syscoin.org/docs/reference/nevm) NEVM exposes Ethereum JSON-RPC for accounts, contracts, logs and transaction receipts. The public endpoints below accept reads without a wallet or API key. ### Endpoints and wallet settings | Network | Chain ID | Native currency | Public RPC | Explorer and wallet discovery | | --- | --- | --- | --- | --- | | Syscoin NEVM mainnet | 57 · `0x39` | SYS | [rpc.syscoin.org](https://rpc.syscoin.org) | [Block explorer](https://explorer.syscoin.org) · [Chainlist](https://chainlist.org/chain/57) | | Tanenbaum NEVM testnet | 5700 · `0x1644` | tSYS | [rpc.tanenbaum.io](https://rpc.tanenbaum.io) | [Block explorer](https://explorer.tanenbaum.io) · [Chainlist](https://chainlist.org/chain/5700) | Choose Tanenbaum to deploy a first contract. A wallet can import the network from Chainlist or use the values above. Test accounts can request gas through the community’s **Syscoin NEVM Testnet** faucet. [Pali and MetaMask setup](https://docs.syscoin.org/docs/guides/nevm/wallet-setup) · [Tanenbaum faucet instructions](https://support.syscoin.org/t/how-to-get-a-syscoin-faucet/876) For an application on a zkSYS Edgechain, connect to **Genesis testnet** at [rpc-zk.tanenbaum.io](https://rpc-zk.tanenbaum.io), chain ID **57057** (`0xdee1`). Chainlist lists it as *zkTanenbaum Testnet*. Genesis has a separate faucet, explorer and batch RPCs. [Genesis commands and settings](https://docs.syscoin.org/docs/reference/zksys#public-genesis-testnet) · [Genesis on Chainlist](https://chainlist.org/chain/57057) · [Genesis faucet](https://faucet-zk.tanenbaum.io) ### Read the chain This batch returns the chain ID and current block height. Match the results by request ID. On Tanenbaum, request `1` returns `0x1644` and request `2` returns the height in hexadecimal. ```bash RPC=https://rpc.tanenbaum.io curl -fsS "$RPC" -H 'Content-Type: application/json' --data '[ {"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}, {"jsonrpc":"2.0","id":2,"method":"eth_blockNumber","params":[]} ]' ``` | Task | JSON-RPC method | Parameters | | --- | --- | --- | | Read a public address’s native SYS balance (wei) | `eth_getBalance` | `["0x…address", "latest"]` | | Read a contract view | `eth_call` | `[{"to":"0x…contract","data":"0x…ABI_encoded_call"}, "latest"]` | | Read a transaction’s outcome and event logs | `eth_getTransactionReceipt` | `["0x…transaction_hash"]` | | Fetch a block with transaction hashes | `eth_getBlockByNumber` | `["latest", false]` | Replace the abbreviated addresses and hashes with their full hex values. A transaction receipt supplies `blockHash`, `status` and `logs` once the transaction is mined. For UTXO balances, outputs and SPT transfers use [Blockbook REST](https://docs.syscoin.org/docs/dev-resources/documentation/javascript-sdk-ref/blockbook) or [Syscoin Core RPC](https://docs.syscoin.org/docs/reference/core). For deployment, use [Foundry](https://docs.syscoin.org/docs/dev-resources/nevm/foundry) or [Hardhat](https://docs.syscoin.org/docs/dev-resources/nevm/hardhat). For the managed client and its version pairing, see [Syscoin Geth](https://docs.syscoin.org/docs/guides/nevm/sysgeth). For general method semantics, see the [Ethereum JSON-RPC reference](https://ethereum.org/en/developers/docs/apis/json-rpc/). ## SyscoinJS for UTXO applications [Canonical page](https://docs.syscoin.org/docs/dev-resources/documentation/javascript-sdk-ref/syscoinjs) SyscoinJS connects JavaScript applications to Syscoin’s UTXO chain. It can look up transactions and available outputs through Blockbook, select inputs, and build a partially signed Bitcoin transaction (PSBT) for a wallet to approve. Pali v5 uses `syscoinjs-lib@2.0.0` to retrieve previous transactions and interpret PSBT inputs and outputs. The examples below use the same version. [Pali’s package pin](https://github.com/syscoin/pali-wallet/blob/6d711f162f8bd64a7ac8c408bedeaf918381c0c3/package.json#L108) · [Pali’s transaction lookup](https://github.com/syscoin/pali-wallet/blob/6d711f162f8bd64a7ac8c408bedeaf918381c0c3/source/scripts/Background/controllers/transactions/syscoin.ts#L142) · [Pali’s PSBT handling](https://github.com/syscoin/pali-wallet/blob/6d711f162f8bd64a7ac8c408bedeaf918381c0c3/source/utils/syscoinPsbtValues.ts) · [Published SDK](https://www.npmjs.com/package/syscoinjs-lib/v/2.0.0) ### Install in a Node.js project The examples run with Node.js 22. In a new directory, initialize the project before installing the SDK. ```bash mkdir syscoinjs-quickstart cd syscoinjs-quickstart npm init -y npm install --save-exact syscoinjs-lib@2.0.0 ``` ### Read a transaction on mainnet Run this in the project directory. The SDK takes the Blockbook **base URL** and adds the API path itself. This example reads the coinbase transaction in Syscoin block **2,345,720**. It prints the containing block’s height and hash. The current index height changes as new blocks arrive. ```bash node <<'JS' const { utils } = require('syscoinjs-lib'); async function main() { const blockbook = 'https://blockbook.syscoin.org'; const txid = 'f86cd23a46b743acff73119dd1e5df02661a19dbac43c0bca75460de410468d3'; const info = await utils.fetchProviderInfo(blockbook); if (info?.blockbook?.coin !== 'Syscoin' || info?.backend?.chain !== 'main') { throw new Error('Expected a Syscoin mainnet indexer'); } const tx = await utils.fetchBackendRawTx(blockbook, txid); if (tx?.txid !== txid) throw new Error('Transaction lookup failed'); console.log({ indexHeight: info.blockbook.bestHeight, txid: tx.txid, blockHeight: tx.blockHeight, blockHash: tx.blockHash }); } main().catch(error => { console.error(error.message); process.exitCode = 1; }); JS ``` The transaction’s `blockHash` is `6c5dc51f2e929822702fcac8281081f05088972c1ddd6eaeb11e0d20014079ac`. You can open the same record directly over HTTPS or query your own Core node for the block and its ChainLock. [Blockbook transaction](https://blockbook.syscoin.org/api/v2/tx/f86cd23a46b743acff73119dd1e5df02661a19dbac43c0bca75460de410468d3) · [Core commands](https://docs.syscoin.org/docs/reference/core#chainlocks-and-sentry-node-status) ### Build an unsigned Tanenbaum payment This offline example spends a **fictional** 100,000-satoshi output, pays 40,000 satoshis to a testnet address, and returns the change. The builder has no signer or backend. It returns the unsigned PSBT for inspection. One SYS is 100,000,000 satoshis. SDK output amounts are `utils.BN` values in satoshis and the fee rate is in satoshis per virtual byte. [SDK builder and return values](https://github.com/syscoin/syscoinjs-lib/blob/05f2e08a46c0eae74e1c5ee06d1099e37f9f73d4/index.js#L739-L788) · [Syscoin address networks](https://github.com/syscoin/syscoinjs-lib/blob/05f2e08a46c0eae74e1c5ee06d1099e37f9f73d4/utils.js#L87-L111) ```bash node <<'JS' const { syscoin: Syscoin, utils } = require('syscoinjs-lib'); async function main() { const builder = new Syscoin(null, null, utils.syscoinNetworks.testnet); const change = 'tsys1qzyg3zyg3zyg3zyg3zyg3zyg3zyg3zyg3g9m666'; const recipient = 'tsys1qyg3zyg3zyg3zyg3zyg3zyg3zyg3zyg3z8c7ujd'; const utxos = [{ txid: 'ab'.repeat(32), vout: 0, value: '100000', address: change, confirmations: 6 }]; const outputs = [{ address: recipient, value: new utils.BN(40000) }]; const feeRate = new utils.BN(2); const { psbt, fee } = await builder.createTransaction( { rbf: true }, change, outputs, feeRate, undefined, utxos ); console.log({ inputs: psbt.inputCount, outputs: psbt.txOutputs.map(out => ({ address: out.address, sats: out.value.toString() })), feeSats: fee.toString(), unsignedPsbt: psbt.toBase64() }); } main().catch(error => { console.error(error.message); process.exitCode = 1; }); JS ``` With this fixture and SDK version, the PSBT contains one input, the **40,000-satoshi payment**, **59,706 satoshis of change**, and a **294-satoshi fee**. In a wallet integration, the inputs come from the user’s actual outputs, change goes to their wallet, and the wallet authorizes the payment. Supplying a signer to `createTransaction` enables the SDK’s signing and submission path when no funding address or xpub is passed. Use the signer-free builder above when your application hands the PSBT to a wallet for approval. [Signing and submission behavior](https://github.com/syscoin/syscoinjs-lib/blob/05f2e08a46c0eae74e1c5ee06d1099e37f9f73d4/index.js#L761-L788) ### Hand a payment to Pali in a browser A connected dApp can let the user review and sign a PSBT built from their **actual wallet inputs**. Build for the network selected in Pali’s UTXO mode. On the user’s approval action, pass the SDK’s JSON wrapper to `sys_sign`. The wrapper contains the Base64 PSBT and its serialized asset map. For an ordinary SYS payment the map is empty. `sys_sign` requests a signature in Pali. Broadcasting is a separate action. [SDK serialization](https://github.com/syscoin/syscoinjs-lib/blob/05f2e08a46c0eae74e1c5ee06d1099e37f9f73d4/utils.js#L2077-L2080) · [Pali signing method](https://github.com/syscoin/pali-wallet/blob/6d711f162f8bd64a7ac8c408bedeaf918381c0c3/source/scripts/Background/controllers/message-handler/method-registry.ts#L1297-L1309) · [Pali’s approval payload](https://github.com/syscoin/pali-wallet/blob/6d711f162f8bd64a7ac8c408bedeaf918381c0c3/source/scripts/Background/controllers/message-handler/popup-promise.ts#L173-L195) ```js import { utils } from 'syscoinjs-lib'; export async function requestPaliSignature(psbt, assets = new Map()) { if (!window.pali?.request) throw new Error('Pali provider unavailable'); await window.pali.request({ method: 'sys_requestAccounts', params: [] }); return window.pali.request({ method: 'sys_sign', params: [utils.exportPsbtToJson(psbt, assets)] }); } ``` ### Other SDK calls | Task | Entry point | | --- | --- | | Look up available outputs for a public address | `utils.fetchBackendUTXOS(blockbook, address)`. The indexer reports values in satoshis. [UTXO lookup](https://github.com/syscoin/syscoinjs-lib/blob/05f2e08a46c0eae74e1c5ee06d1099e37f9f73d4/utils.js#L310-L359) | | Read an indexed block by hash | `utils.fetchBackendBlock(blockbook, blockHash)`. [Block lookup](https://github.com/syscoin/syscoinjs-lib/blob/05f2e08a46c0eae74e1c5ee06d1099e37f9f73d4/utils.js#L629-L659) | | Build a Syscoin Platform Token allocation transfer | `builder.assetAllocationSend(...)` takes an asset map keyed by GUID. Its outputs carry asset amounts and it uses SYS inputs for fees. [Allocation builder](https://github.com/syscoin/syscoinjs-lib/blob/05f2e08a46c0eae74e1c5ee06d1099e37f9f73d4/index.js#L790-L847) · [UTXO assets and Z-DAG](https://docs.syscoin.org/docs/tech/tokens) | For raw REST calls, use the [Blockbook API reference](https://docs.syscoin.org/docs/dev-resources/documentation/javascript-sdk-ref/blockbook). To call an EVM contract, use [NEVM JSON-RPC](https://docs.syscoin.org/docs/reference/nevm) or the [zkSYS Genesis RPC](https://docs.syscoin.org/docs/reference/zksys#public-genesis-testnet). ## Syscoin in a Nutshell [Canonical page](https://docs.syscoin.org/docs/intro/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](https://docs.syscoin.org/docs/architecture/core#what-bitcoin-merge-mining-contributes) · [System architecture](https://docs.syscoin.org/docs/architecture/overview) ### 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](https://docs.syscoin.org/docs/intro/human-and-ai) · [Governance](https://docs.syscoin.org/docs/governance/overview) ### 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](https://docs.syscoin.org/docs/intro/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](https://docs.syscoin.org/docs/architecture/post-quantum#what-a-full-node-verifies) - **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](https://docs.syscoin.org/docs/architecture/zksys#what-gateway-changes) · [Trace the payment](https://docs.syscoin.org/docs/reference/zksys#trace-a-public-testnet-transaction) · [Sequencing and proving](https://docs.syscoin.org/docs/architecture/zksys#sequencing-proving-and-recovery) - **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](https://docs.syscoin.org/docs/architecture/zksys#wallets-and-post-quantum-account-authorization) - **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](https://docs.syscoin.org/docs/architecture/bitcoin-bridge#inspect-a-tag-in-a-bitcoin-block) · [How a withdrawal would be enforced](https://docs.syscoin.org/docs/architecture/bitcoin-bridge#from-detection-to-enforcement-on-bitcoin) ## Network and release status [Canonical page](https://docs.syscoin.org/docs/intro/status) As of **November 19, 2026**, Core and NEVM operate on mainnet, PQ ChainLocks are a release candidate, and zkSYS Genesis runs on public testnet. [Developer quickstart and status in plain text](https://docs.syscoin.org/llms.txt) ### Released networks and public records | Claim and scope | What the evidence establishes | How to check it | | --- | --- | --- | | `sys-producer-income` · **Released** · Core v5.1.3 and sysgeth v5.1.0 mainnet | A participating miner can earn SYS under the Core coinbase split. The paired NEVM block credits its beneficiary with 10.55 SYS issuance and effective priority tips. Core and NEVM follow different issuance rules. Continued participation or additional Bitcoin hashpower is an economic response. | Check Core’s coinbase recipients, the NEVM beneficiary, and the applicable fee and issuance rules. [Funding rules and pinned sources](https://docs.syscoin.org/docs/architecture/modular-alignment#who-pays-for-the-shared-infrastructure) · [Bitcoin and Syscoin mining relationship](https://docs.syscoin.org/docs/architecture/core#why-bitcoin-and-syscoin-fit-together) | | `core-auxpow` · **Released** · Core mainnet, v5.1.3 | Participating miners can reuse SHA-256 work. Core validates the parent proof against its own target and checks the Syscoin block under its own rules. | Read the Core block’s AuxPoW header, coinbase and Merkle branch. A Bitcoin best-chain inclusion claim needs a separate Bitcoin header check. [Released AuxPoW checks](https://github.com/syscoin/syscoin/blob/ff8df9b44d603faf3cf78af28c633a066a8ec9a7/src/auxpow.cpp#L39-L110) · [Core commands](https://docs.syscoin.org/docs/reference/core#merge-mining) | | `btc-tag` · **Observed** · Bitcoin mainnet, November 19, 2026 | Bitcoin blocks 976,621 and 976,623 both contain a `sys` reference to Syscoin ancestor 2,345,720. The tag records what the miner published. | Inspect both coinbases, verify inclusion in Bitcoin and match the referenced ancestor against the Syscoin block. To establish who mined that Syscoin block, inspect its own AuxPoW parent. [Transactions and block hash](https://docs.syscoin.org/docs/architecture/bitcoin-bridge#inspect-a-tag-in-a-bitcoin-block) | | `core-finality` · **Released** · Core mainnet, v5.1.3 | Sentry ChainLocks use BLS quorum signatures and distributed key generation on the released line. The node enforces the finality boundary it has accepted. | Match the daemon version and network, inspect the accepted ChainLock, then check the target block’s ancestry. [Released handler](https://github.com/syscoin/syscoin/blob/ff8df9b44d603faf3cf78af28c633a066a8ec9a7/src/llmq/quorums_chainlocks.cpp) · [Core command reference](https://docs.syscoin.org/docs/reference/core) | | `core-poda` · **Released** · Core v5.1.3 | Core supports whole-blob commitments using legacy Keccak-256 or versioned BLAKE2s-256. A matching digest authenticates bytes supplied by a peer or archive. | Retrieve the blob, recompute its declared hash, and check its publication in the canonical block. Long-term replay needs a retained copy and authenticated replay inputs. [Released digest check](https://github.com/syscoin/syscoin/blob/ff8df9b44d603faf3cf78af28c633a066a8ec9a7/src/validation.cpp#L2491-L2506) · [Read and hash a blob](https://docs.syscoin.org/docs/reference/zksys#read-a-core-blob) · [Replay requirements](https://docs.syscoin.org/docs/architecture/data-availability#what-can-someone-verify-a-week-later) | | `nevm-account` · **Released** · NEVM mainnet 57 and Tanenbaum 5700 | Ordinary EVM transactions authenticate the sender using classical secp256k1 signatures. Moving Sentry authority to hash-based keys would leave this separate account path in place. | Query `eth_chainId`, inspect the signed transaction and its receipt, and identify any additional contract account policy. [Released chain IDs](https://github.com/syscoin/go-ethereum/blob/73b431a9e695948ab6b2c483641e0b350a13972c/params/config.go#L74-L110) · [Sender recovery](https://github.com/syscoin/go-ethereum/blob/73b431a9e695948ab6b2c483641e0b350a13972c/core/types/transaction_signing.go#L461-L484) · [RPC commands](https://docs.syscoin.org/docs/reference/nevm) | | `genesis-mock` · **Observed mock proof** · Genesis 57057 → Gateway → Tanenbaum NEVM 5700, November 18, 2026 | Gateway batch 9,448 settled on NEVM. Its successful proof submission uses the V8 test format. This observation covers that batch and that settlement step. | Decode the four submitted proof words. The first, `0x803`, selects mock type 3. At NEVM block 1,009,179 the [settlement diamond](https://explorer.tanenbaum.io/address/0x2d2d8853F547Ee15e7C90997e1d74AaFa607050C) returned [this wrapper](https://explorer.tanenbaum.io/address/0xE80e02d59549261eCcd5E44C92d7921115A6A361) from `getVerifier()`. Its `IS_TESTNET_VERIFIER()` returned `true` at the same block. Recheck the historical contract for the batch you rely on. [Original proof transaction](https://explorer.tanenbaum.io/api/v2/transactions/0xc82091801f6b0947db4bed5fb2400e07313e2730b0c37d389d2b3c5dba9fdde0) · [Pinned encoding](https://github.com/syscoin/zksync-os-server/blob/d22deb8a5ba6ab96296a913d34934d6af27b6909/lib/l1_sender/src/commands/prove.rs#L437-L465) · [Reproduce the trace](https://docs.syscoin.org/docs/reference/zksys#trace-a-public-testnet-transaction) | ### Candidate rules, design targets and research | Claim and scope | What the evidence establishes | How to check it | | --- | --- | --- | | `pq-chainlock` · **Candidate** · Core #609 | Under activated rules, SLH-DSA authenticates Sentry authority and child-key roots. Core checks 801 scheduled WOTS+ roster-slot signatures directly. The pinned public compatibility-replay profile starts neither legacy nor PQ ChainLock service. The active path is exercised on regtest. | Check the release’s network parameters, the authenticated legacy predecessor at `A−1` and the certificate on its target branch. The pinned public profile has no production activation height. [Activation and handoff](https://github.com/syscoin/syscoin/blob/b3b4f643383a2149807a25fe38d26b5f058daa60/doc/pq-chainlocks.md#L2622-L2678) · [Verify a certificate](https://docs.syscoin.org/docs/architecture/post-quantum#what-a-full-node-verifies) | | `nevm-membership` · **Candidate** · Paired sysgeth #42 | The `0x63` precompile queries the **current** canonical 50,001-block digest-membership window, including during a historical `eth_call`. It answers a different question from the original publication’s inclusion or continued byte availability. | Match the deployed sysgeth revision, query the digest, then verify the original Core block and retrieve its bytes if those facts matter. [Candidate semantics](https://github.com/syscoin/go-ethereum/blob/1c046ba92f8ea95be024a790e9444b80ccbf019a/docs/syscoin-data-hash-index-upgrade.md#L72-L96) · [Read the precompile](https://docs.syscoin.org/docs/reference/zksys#check-nevm-registration) | | `zk-real-proof` · **Design target and supported configuration** · zkSYS server v0.24.4 | Airbender proves batch execution bound to the data commitment. The real settlement wrapper adds its own cryptographic assumptions, including setup for a PLONK wrapper. Verification still depends on the deployed program, wrapper and key. | Read the settlement diamond’s verifier at the relevant block. For real proving the server requires `IS_TESTNET_VERIFIER=false` and the expected canonical verification key. Decode the submitted proof and match its receipt. [Pinned verifier readiness rules](https://github.com/syscoin/zksync-os-server/blob/d22deb8a5ba6ab96296a913d34934d6af27b6909/docs/src/design/prover_api.md#L11-L24) · [Proof stages](https://docs.syscoin.org/docs/architecture/zksys#why-there-are-two-proof-stages) | | `zksys-issuance` · **Reference design** · zkSYS v0.24.4 | Eligible SYS stake or Sentry collateral determines reward weight. The separate zkSYS asset can fund Gas Tank credit for eligible fees. Burning surplus reduces zkSYS supply while the rewards budget follows its scheduled issuance. | Check the chain ID, deployed proxies, role holders, period records, and both token and native balances. A network identifier by itself says nothing about those controls. [Pinned issuer](https://github.com/syscoin/zksync-os-server/blob/d22deb8a5ba6ab96296a913d34934d6af27b6909/contracts/src/zksys/ZkSysIssuer.sol#L353-L391) · [Inspect issuance and gas credit](https://docs.syscoin.org/docs/reference/zksys#inspect-issuance-and-gas-credit) | | `btc-withdrawal` · **Research** · Proposed Syscoin–Bitcoin bridge | The BitVM paper proposes using a timely, qualifying Bitcoin coinbase conflict to veto a withdrawal. Its assumptions include an authenticated Bitcoin window and a challenger able to act before the deadline. Witness encryption is a separate research direction. Both BTC release mechanisms are proposals. | Inspect the tag and both histories, then identify the actual vault, withdrawal predicate, challenge window and enforcement mechanism before relying on an exit. [Syscoin bridge paper](https://syscoin.org/btc_bridge.pdf#page=8) · [BitVM and witness-encryption research boundaries](https://docs.syscoin.org/docs/architecture/bitcoin-bridge#from-detection-to-enforcement-on-bitcoin) | ### Follow the evidence across services - **A receipt identifies local execution.** Find its Edgechain batch, then look for the full publication on Core and the proof checked at settlement. Match the Edge execution event to its Gateway block and the enclosing Gateway batch to NEVM. A receiving contract has its own execution record. [Evidence at each stage](https://docs.syscoin.org/docs/architecture/overview#which-record-answers-which-question) - **A commitment identifies data.** Verify a reachable copy against its digest. For a dispute after the serving window, an operator needs retained data, a known state and the replay inputs. [Evidence a week later](https://docs.syscoin.org/docs/architecture/data-availability#what-can-someone-verify-a-week-later) - **Eligibility is the start of a payment check.** Identify the asset, accepted duty or block, and rules for its payee, then check what was actually issued, transferred, or burned. [Who pays whom](https://docs.syscoin.org/docs/architecture/modular-alignment#who-pays-for-the-shared-infrastructure) - **An observer, signer, and rule administrator have different powers.** Verify the account’s grant and a revocation’s inclusion. To recover or leave a censored service, identify a deployed route and the authority that can enforce it. [Powers and remedies](https://docs.syscoin.org/docs/intro/human-and-ai#if-the-operator-stops-cooperating) For the argument connecting the layers, start with [Syscoin in a nutshell](https://docs.syscoin.org/docs/intro/nutshell) or the [system map](https://docs.syscoin.org/docs/architecture/overview). To check a live service, use the [command reference](https://docs.syscoin.org/docs/reference/overview).