Network and release 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
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 · Bitcoin and Syscoin mining relationship |
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 · Core commands |
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 |
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 · Core command reference |
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 · Read and hash a blob · Replay requirements |
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 · Sender recovery · RPC commands |
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 returned this wrapper 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 · Pinned encoding · Reproduce the trace |
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 · Verify a certificate |
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 · Read the precompile |
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 · 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 · 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 · BitVM and witness-encryption research boundaries |
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
- 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
- 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
- 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
For the argument connecting the layers, start with Syscoin in a nutshell or the system map. To check a live service, use the command reference.