Research and design sources
Our 2021 scaling proposal started with a question about custody. What good is a balance you control if the only operator who will process your payment disappears? The essays below follow that question from payments to shared computing and, eventually, to the rights people can delegate to autonomous agents.
Read the implementation
Follow a payment through the layers to see where mining, data, and settlement meet. Then check who earns SYS and zkSYS, who can change the rules, and which networks you can inspect. One payment through the stack · Funding and governance · Network status
| Subject | Source and scope |
|---|---|
| Core and NEVM | Core v5.1.3 runs the released rules. We pair our PQ migration candidate at Core commit b3b4f643383a with sysgeth PR #42. The public candidate profiles are for compatibility replay and have no configured production activation height. Core v5.1.3 · Core PR #609 · sysgeth PR #42 |
| Post-quantum operator identity and finality | In the PQ candidate, we use SLH-DSA for operator identity and scheduled WOTS+ signatures for ChainLock votes. The candidate protocol notes give the certificate format and handoff rules. Candidate protocol notes · Candidate SLH-DSA implementation notes |
| zkSYS and PoDA | Genesis is our public zkSYS testnet. The v0.24.4 server batches Edgechain transactions for Gateway and can recover stalled Core publications within its configured limits. zkSYS server v0.24.4 · Bitcoin DA publication queue · Genesis announcement |
| Proving and account authorization | In the real-proof configuration, Airbender proves the compiled RISC-V batch program. The zkSYS V8 verifier checks the expected program and batch public input. ERC-4337 specifies how smart accounts authorize user operations. Pinned Airbender design · zkSYS V8 verifier · zkSYS SHA-2 precompile · ERC-4337 |
Use the RPC commands to inspect a deployment, or compare what users can recover across DA networks. Commands and endpoints · Data availability across chains
Cryptography and proofs
- Stateless hash-based signatures. FIPS 205 defines SLH-DSA from SPHINCS+ and standardizes SHA-2 and SHAKE parameter sets. The candidate Core identity profile,
SLH-DSA-SHAKE-128s, has a 32-byte public key and a 7,856-byte signature. Scheduled WOTS+ is a separate Syscoin protocol with a one-time-use signing rule. NIST FIPS 205 · Syscoin's ChainLock design - Limited-signature smart accounts. The zkSYS precompile uses the separate
SLH-DSA-SHA2-128-24profile from the NIST SP 800-230 initial public draft. That profile limits each signing key to 2²⁴ signatures. The account or signer must enforce its key-use limit because a stateless verifier cannot count signatures. NIST SP 800-230 draft · Pinned verification and conformance notes - Module-lattice signatures. FIPS 204 defines ML-DSA. For a wire-size example, ML-DSA-44 uses a 1,312-byte public key and a 2,420-byte signature. Public-key size, signature size, signing policy, and cryptographic assumptions all matter when deciding what to deploy. NIST FIPS 204
- Hash functions. RFC 7693 defines BLAKE2s, FIPS 202 defines SHAKE and SHA-3, and FIPS 180-4 defines SHA-256. Core PoDA accepts both BLAKE2s and legacy Ethereum Keccak-256. Exact algorithm, encoding, and domain matter when comparing or recomputing digests. RFC 7693 · NIST FIPS 202 · NIST FIPS 180-4 · PoDA encoding
- Hash-based proof systems. The original FRI paper from 2018 introduces a Reed–Solomon proximity test. Airbender uses DEEP-FRI, a refinement that queries the polynomial outside the original evaluation domain, as part of proving RISC-V execution. When zkSYS settles a wrapped proof, the assumptions of the deployed wrapper also apply to that batch. Original FRI paper · DEEP-FRI · zkSYS proving and wrapping
- What a program proof covers. A zkVM proves execution of compiled code against specified inputs. A November 2026 preprint uses SP1 and Jolt to study how a compiler can change a program’s behavior while the proof still verifies the compiled execution. This is one reason the program and toolchain matter as well as the cryptography. Tan, Chaliasos and Donaldson, Proving the Wrong Program
- UTXO assets and Z-DAG. The original Syscoin asset model uses explicit output dependencies. Z-DAG adds a pre-confirmation conflict signal for merchants. The Whiteblock report describes a controlled Core 4 workload. Syscoin 4 whitepaper · Z-DAG paper · Whiteblock report · Current SPT flow
- Bitcoin interoperability research. Our BitVM2 withdrawal proposal uses Bitcoin coinbase tags to detect forks. Witness encryption is a separate research direction that could use Bitcoin-anchored evidence as an input. Design and assumptions · Bitcoin bridge paper · BitVM2 · PVUGC draft
Design essays by Jagdeep Sidhu
From a computational court to authority over scarce resources
The 2021 proposal starts with a wallet holder. She needs control of her coins and a timely way to spend them. She can still hold the only signing key while an operator refuses to process her payment. Sidhu calls the shared base a computational court. Applications can do their own work if users have a common place to settle claims under rules they can check. Even after the court has settled her balance, the wallet holder still needs a way to get her next payment included. Coordinated Financial Computing, 2021 · Rights when an operator stops cooperating
Moving execution away from that court creates a data problem. What can a stranger recover and check when the computer that ran the payment disappears? The 2022 Von Neumann essay gives execution, temporary data and persistent records different jobs. Later that year the private Rollux testnet made the distinction visible. A user sent a transaction from Pali, the rollup published its batch, and a reader could retrieve the bytes from an indexer and check them against the recorded hash. The same question applies to zkSYS today. Gateway can carry compact references while readers retrieve the data from Core or an archive. Replaying execution also takes the agreed starting state and the block inputs. Von Neumann architecture, 2022 · Rollux demonstration · What survives the serving window
Who keeps that shared infrastructure running? The 2024 Bitcoin modularity essay considers execution, data and the conditions for releasing BTC together. The April 2025 interview explains why Sidhu sees a role for BTC as reserve capital. Participating Bitcoin miners already reuse work on Syscoin and can earn SYS. A BTC bridge needs its own enforceable withdrawal rule. zkSYS takes the funding question one layer further. Its reference design ties reward eligibility to SYS stake or eligible Sentry collateral while letting applications choose their own execution rules. Bitcoin modularity, 2024 · April interview at 20:18 and 23:07 · Bridge design · zkSYS issuance
Truth States brings the question back to the person holding the right. Anyone may observe that a machine is free. Who may reserve it, for whom, and who may change that rule? As intelligence gets cheaper, many agents can propose good uses for the same scarce resource. A community can give an agent limited authority, publish the rule and let others check how it was applied. Distance makes the value of delegation especially clear. If Mars has exclusive authority over a resource, its users can act locally. Earth can verify the proof when it and the required data arrive. A transfer between the two still takes communication, and people still decide which allocation rules they consider fair. Truth States, 2025 · Verification across distance
The same division of work appears in Core’s PQ candidate. Each Core node verifies the hash-based finality signatures directly and can identify who signed. The zkSYS design puts application execution and proving above Core so new applications can do more work without making every Core node run them. A public Genesis payment has receipts on each leg of that journey. Its Gateway batch reached NEVM with a mock verifier. Production settlement would need an enforcing verifier, and the hardware and bandwidth an independent PQ node needs during a burst remain unmeasured in the published results. Direct finality checks · Public testnet trace · Operator measurements
Essays and demonstrations by date
| Dated source | Design question and reasoning | How the idea appears in Syscoin |
|---|---|---|
| February 2021 · Coordinated financial computing | Must every participant execute every application? A common ordering layer can coordinate specialized execution. | The original four-layer model was conceptual. In today’s Genesis testnet, readers can match an Edge execution event on Gateway to the enclosing Gateway batch on NEVM. Public receipt trace |
| December 2021 · The Ultimate Guide to Rollups | What evidence lets others accept a state update? Validity proofs and fraud challenges impose different verification jobs. Both leave readers who want to reconstruct the state dependent on data. | On zkSYS, the settlement contract selects the verifier for a batch. Replay also needs the original inputs. Gateway testnet batch 9,448 used the mock format on NEVM. Proof stages · Decode the testnet submission |
| January and April 2022 · Blockchain Idealisms · Layer 1 design | What belongs in the shared base? Keep independent validation feasible, use merge-mined work, and expose programmable settlement and data publication. | Core and NEVM are released. Classical ChainLocks and the candidate’s scheduled hash-based votes have different keys and validation rules. Core architecture · PQ candidate |
| June 2022 · Coordinated global Von Neumann architecture | Can parts of a shared computer act at different speeds? Specialized execution can proceed locally while other participants wait for verifiable updates. | Edge receipts, Core publication and Gateway settlement have distinct clocks. The interplanetary extension is a thought experiment about delegated authority and signal travel. Application lifecycle · Verification across distance |
| December 24, 2022 · Revealing the Method in the Madness | How do the abstractions meet in a wallet transaction? The Pali/Bedrock demo follows an optimistic Rollux transaction on private testnet through publication, a hash in an inbox, and recovery from an indexer. | We launched Rollux mainnet on June 28, 2023. zkSYS uses its own settlement path, with ordered blob references on Gateway and a wrapped execution proof in real-verifier mode. Historical demo and update · zkSYS transaction path |
| March 2024 · Rollux and Bitcoin modularity | How much of Bitcoin security carries over to a new service? Mining, data publication and withdrawals each have their own evidence and participants. | Participating miners already publish Syscoin references in Bitcoin coinbases. The BitVM withdrawal rule and witness-encryption direction remain proposals. Bitcoin-anchored fork detection |
| February 2025 · Dealing with social conditions in a decentralized world | Can shared infrastructure keep getting funded when the original team’s priorities or finances change? Open proposals and bounded budget changes give the community a public funding process. | The Nexus upgrade adjusts future budgets using actual superblock payouts. The essay explains the design goals. Core defines the exact thresholds and limits. Dynamic governance |
| August 2025 · Truth States, Consciousness, and Decentralized Intelligence | If an agent can observe shared state, who authorizes it to change that state? Exclusive authority can permit local decisions that others verify later. | The reservation and Earth–Mars examples are hypothetical. Checking the program and the grant is a technical task. Deciding whether an allocation rule is legitimate and who can hear an appeal is an institutional one. Delegated authority and remedies |
Interviews and listening guide
- April 2, 2025 · Crypto Coin Show. At 1:32–7:26, Sidhu describes keeping the shared base accessible to independent operators. At 8:32–14:08 he considers wallet authority and competition for compute. 20:18 separates work reused by Bitcoin miners from the additional mechanism needed to release BTC. 23:07–27:15 gives his economic rationale for treating BTC as a reserve asset. The publisher’s timestamped transcript was generated automatically and lightly edited. A public Bitcoin coinbase carrying a Syscoin tag illustrates the mining relationship he describes. Recording · Publisher transcript · Inspect a live tag
- June 9, 2025 · Token for Your Thoughts. The publisher’s show notes and chapter markers locate modular scaling at 9:50, AI and Sentry Nodes at 18:30, the then-discussed Robin Bridge at 27:40, and long-term development at 37:45. The bridge discussion records the proposal as it stood in June 2025. Episode, show notes and chapters · Mining incentives · BTC bridge research
Earlier proposals for cross-chain data and Bitcoin collateral
We proposed a zkDA light client that could verify Syscoin data commitments on another chain. zkSYS addresses a narrower version of that problem today. Gateway receives the ordered hashes for one batch, and a reader can retrieve the bytes from Core and check them independently. The earlier Bitcoin Layer 0 work also explored difficulty-based stBTC. The later bridge paper gives a concrete withdrawal rule based on Syscoin references that miners publish on Bitcoin. Original zkDA proposal · Bitcoin Layer 0 essay · Earlier Syscoin R&D overview · BTC bridge proposal
Institutions, computation, and shared resources
- Machine intelligence. Alan Turing's 1950 paper frames machine intelligence through the imitation game and examines objections to machine thinking. It provides the historical context for Sidhu's later question about the institutions that coordinate powerful machine actors. Computing Machinery and Intelligence · Turing's typescript, King's College archive
- Common-pool resources. Elinor Ostrom compared successful and failed forms of self-governance of shared resources. Her prize lecture describes recurring features of durable arrangements, including clear membership and resource boundaries, participation by affected users, accountable monitoring, and local dispute resolution. Her later diagnostic work asks how rules should fit the actual participants, incentives, and resource. A cryptographic ledger can make parts of such a process auditable. Eligibility, dispute resolution, and the accuracy of physical measurements still depend on the institutions that supply and govern them. Governing the Commons, Cambridge University Press excerpt · Ostrom's 2009 prize lecture · A diagnostic approach for going beyond panaceas
Project milestones
We enabled PoDA on Tanenbaum and opened the zkSYS Genesis public testnet. To reduce the data Gateway has to carry, we shifted to compact references and checked availability through a Core DA node. We also tested hash-based signing for Pali smart accounts during that testnet period. PoDA on Tanenbaum · Genesis testnet launch · The Final Ledger Is Taking Shape
Public posts by Jagdeep Sidhu
Selected public posts, dated in UTC, follow the design from the early Sentry proposal to the candidate implementation and zkSYS testnet. Current network and release status
| Date (UTC) | Subject | What the post discusses |
|---|---|---|
| 2026-11-19 | Hash-first design | Reaffirms the project direction in discussion of research on algebraic cryptography. Post |
| 2026-11-18 | Coordinated computing | Revisits the 2022 essay on separating and coordinating the jobs of a shared computer. Post |
| 2026-11-07 | Hash-based Sentry signatures | Discusses quantum search, hash parameters, and direct scheduled WOTS+ signatures for Sentry finality. Post |
| 2026-10-28 | SLH-DSA experiments | Discusses smart-account signature verification and the bandwidth trade-off for directly verified finality signatures. The current Core candidate's parameter set is recorded in its protocol notes above. Post |
| 2026-10-21 | Validity proofs over distance | Discusses why independent proof verification and asynchronous settlement are interesting when participants communicate slowly. Post |
| 2026-10-21 | Whole-payload DA | States the preference for retrieving the exact payload and checking its digest. The DA comparison explains the scope of that evidence and the trade-off with sampling. Post |
| 2026-10-21 | Direct finality and recursive execution | Describes a conservative base layer that can afford direct threshold signature checks, alongside recursive proof experiments higher in the stack. Post |
| 2026-10-18 | SLH-DSA and ML-DSA | Explains the design preference to pay for larger hash-based signatures alongside a comparison of cryptographic assumptions. Post |
| 2026-10-16 | zkVM performance and proof parameters | Compares experimental proving configurations and asks how to preserve security when wrapping a proof. Throughput and security estimates depend on the specific workload, configuration, and verifier. Post |
| 2026-10-13 | Bitcoin interoperability research | Proposes studying witness encryption as a way to connect Bitcoin and Syscoin. Post |
| 2026-10-10 | Settlement and execution | Describes the combination of UTXO proof of work, EVM accounting, compact data commitments, and proof-based execution. Post |
| 2026-10-08 | Hash choices across layers | Connects PoW, DA, and planned signature and account upgrades. Post |
| 2026-10-07 | Migration boundaries | Discusses planned Sentry signatures and smart accounts, with separate migration decisions for UTXO and EOA spending. Post |
| 2026-08-19 | zkSYS SHA2 signature verification | We cut the guest-cycle cost of hash-based verification in the test configuration linked here. Thread · Implementation |
| 2026-08-15 | Early Sentry proposal | Sketches replacing DKG and BLS with explicit signatures. It records an earlier signature hierarchy and certificate estimate. See the current Core candidate for the revised format. Post |
| 2026-07-16 | Gateway deployment | Discusses how the Syscoin fork would continue its shared Gateway path after an upstream scope change. Post |
| 2026-07-03 | zkSYS issuance and gas | Describes how issuance relates to SYS collateral and how the Gas Tank puts zkSYS to use for execution fees. Post |
| 2026-06-25 | Pali signing experiment | Testing hash-based signing for Pali smart accounts. Thread · Hash cost discussion · Account policy implications |
| 2026-05-19 | Testnet rollout | Announces BLAKE2s DA and checkpoint work on the testnet path for zkSYS. Post |
| 2026-05-08 | Intelligence and coordination | Discusses the need to coordinate decisions and scarce resources as autonomous systems become more capable. Post |
| 2026-04-27 | How the layers developed | Summarizes the progression from merge mining and UTXO assets to finality, NEVM, PoDA, and proof-based execution. Post |
| 2026-04-13 | PoDA test results | Discusses the blob data path and test conditions later cited by the zkSYS update. Thread · Architecture summary |
| 2026-03-04 | PoDA commitment choice | Recounts why Syscoin chose a whole-payload hash commitment with no structured setup for PoDA. Post |
| 2025-09-25 | Bitcoin interoperability design | Shares an early Bitcoin verification proposal and separates the opcodes its designs assume. Post |
| 2025-08-31 | Decentralized intelligence | Introduces the essay on truth states and intelligence. Post |