Circuit Breaker logoCircuit Breaker

About

Sindri is modernizing the ZK DevOps and proving stack providing builders with accessible, streamlined infrastructure. It was built by developers, for developers after witnessing firsthand the difficulties with iterating and shipping ZK apps. ZK dev teams will find engaging with Sindri is very similar to how you might engage with Infura or Stripe via API calls that can be built right into application logic or the browser. The Sindri API offers out-of-the-box serverless proving deployments, adaptable support for your favorite proving systems with minimal refactoring required, built-in acceleration, and SDK/CLI tooling to deliver a phenomenal developer experience. Develop and deploy amazing ZK applications in minutes instead of weeks or months. We've built Sindri from a place that respects the builders and coders who need accessible, reliable infrastructure solutions to share their life work. We're excited to share it with you. To use Sindri, you will need an API key. Please request in Discord Circuit Breaker lobby (@stasia), by e-mail at [email protected] or message us on telegram at @etainos

Prizes

🔥 Most unique use of Sindri$2,500
🥇
1st place
$2,000
🥈
Runner-up
$500
To use Sindri, you will need an API key. Please request in Discord Circuit Breaker lobby (@stasia), by e-mail at [email protected] or message us on telegram at @etainos Use your creative power to build a ZK submission leveraging Sindri’s API and versatility. Your project should utilize one of Sindri's supported proving systems, including Gnark, Noir, Halo2, and Circom, to build something truly unique.Rollups, coprocessors, interoperability solutions, payment gateways, DePIN, and more can all leverage Sindri for scalable, elastic-proof generation. Our Python, Javascript, and Typescript SDKs and tooling allow you to build proving logic directly into the application layer, streamlining access to Sindri’s scalable, accelerated infrastructure stack. In turn, developers can build with large circuit structures and unexpected, high-volume request spikes, which are often challenging in ZK applications. Looking for a starting point? Browse the How-To Guides in our docs for examples of: - Circom + Python + Sudoku - Gnark + Javascript + String Compression - Halo2 + Rust + Floating Point Arithmetic - Noir + Javascript + PageRank**To use Sindri, you will need an API key.

Qualification Requirements

New projects only, please (one submission per prize category; it's okay to use pre-written open-source components, but specify what is original to this project) Must have Sindri integrated into the submission Must leverage Sindri for proof generation Ability to support multiple or concurrent proof request environments preferred (e.g., end users requesting proofs at scale, scheduled proof generation, etc). Bonus points for rollup-related submissions

🤖 Best use of Sindri in a ML x Web3 context$2,500
🥇
1st place
$2,000
🥈
2nd place
$500
To use Sindri, you will need an API key. Please request in Discord Circuit Breaker lobby (@stasia), by e-mail at [email protected] or message us on telegram at @etainos Develop a ZK application or use case that effectively combines AI with Web3. Your project should utilize one of Sindri's supported proving systems, including Gnark, Noir, Halo2, and Circom, to build something truly unique. Builders can utilize Sindri to expand the design space using zkML given Sindri’s streamlined tooling, scalability and versatility across app-level and browser level integrations. We're looking for applications that not only show technical skill but also creatively apply zkML in a meaningful way. Some examples we’ve implemented in-house include a PageRank algorithm implementation written in Noir and a neural net written in Circom.

Qualification Requirements

New projects only, please (one submission per prize category; it's okay to use pre-written open source components, but specify what is original to this project) Must have Sindri integrated into the submission Must leverage Sindri for proof generation The ML model or algorithm should demonstrate tangible utility or drive application logic; as opposed to technical sophistication or massive model size for little purpose Bonus points for a great front end