Skip to content

Project Proposal: ZKML Workflows on Akave O3 - ezkl Artifact Storage & Integration #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Patrick-Ehimen wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Project Proposal: ZKML Workflows on Akave O3 - ezkl Artifact Storage & Integration #3

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions zkml-o3/PROPOSAL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,10 @@
# ZKML Workflows on Akave O3: ezkl Artifact Storage, Integration, and Testing

**Status**: Ready to submit the plan
**Contributor**: Patrick-Ehimen
**Date**: February 3, 2026
**Note**: Open for potential collaborators

Comment on lines +3 to +7
Copy link
Collaborator

@Abhay-2811 Abhay-2811 Feb 5, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No need for changes in PROPOSAL.md , please create a PLAN.md and layout specific detailed technical plan and milestones

## Problem Statement
Zero-knowledge machine learning (ZKML) pipelines produce and consume large artifacts across multiple stages (model formats, compiled circuits, proving/verification keys, proofs, witness data, calibration artifacts, etc.). Today these artifacts are typically stored locally or in centralized object stores, which introduces:
- Fragile workflows (local-only artifacts, poor portability)
Expand Down