Developer infrastructure for distributed systems.
Work across proving systems, zkVMs, rollups, and privacy-preserving compute, with a focus on turning early protocol infrastructure into tools developers can understand, test, and integrate.
The main operating area is the space between protocol engineering and developer adoption: SDK validation, reference implementations, technical documentation, onboarding flows, integration feedback, and ecosystem coordination.
Making verifiable execution usable as developer infrastructure.
Core areas of work include:
- developer experience for zkVMs and proving systems
- SDK and API design for cryptographic infrastructure
- reference implementations and integration examples
- observability for proving workflows
- documentation systems for technical protocols
- feedback loops between external builders and engineering teams
- ecosystem strategy for early infrastructure adoption
The broader question behind the work:
How can complex cryptographic systems become usable without forcing every developer to understand the entire proving stack?
Current work is centered on zkVM infrastructure, rollup proving workflows, and verifiable execution.
Areas of exploration:
- proof generation as a developer workflow
- execution receipts as application infrastructure
- rollup proving pipelines that are observable and debuggable
- privacy-preserving context and policy verification
- developer-facing abstractions for distributed proving
- agent and application workflows that require verifiable computation
| Project | Focus |
|---|---|
| hydradb-zisk-receipts | Private agent context receipts using HydraDB retrieval and ZisK verification |
| OP-ZisK | OP Stack proving experiments with ZisK |
| op-zisk-prover-Dashboard | Observability for prover jobs, execution state, and proving workflows |
| ZisK-BPF | Experiments around verifying Solana BPF execution in a zkVM context |
| Poseidon_zisk | Rust implementation work around Poseidon for ZisK experiments |
| Miden-Zcash | Exploratory privacy-flow experiments using ZK tooling |
| ZisK-Docs | Draft documentation and onboarding resources for ZisK developers |
These projects are mostly experiments, working references, and technical notes used to understand where developer tooling, documentation, and workflows need to improve.
ZisK — Developer Experience / Growth Engineer Developer workflows, SDK validation, reference implementations, documentation, proving experiments, and ecosystem integrations around zkVM infrastructure.
Vana — Product & Ecosystem Strategy Decentralized AI, DataDAOs, data ownership, builder programs, product feedback, and ecosystem development around data economy infrastructure.
Polygon Labs — Growth & Strategy, Developer Ecosystem Developer ecosystem work across Polygon PoS, zkEVM, CDK, Plonky3, Nightfall, ZK ecosystem initiatives, technical community programs, and infrastructure adoption.
Onecdot — Co-Founder NFT API infrastructure focused on making Web3 application development easier to integrate and scale.
Systems: zkVMs, rollups, Ethereum infrastructure, proving systems, privacy-preserving compute Developer infrastructure: SDKs, APIs, documentation, reference implementations, dashboards, onboarding flows Research direction: verifiable execution, private context, agent receipts, distributed proving, cryptographic developer tools
- X: @0xAbix
- LinkedIn: Ayush Bhadauria
- GitHub: amiabix