A few days ago I posted about building ZKCG — a Rust-based ZK framework to replace trusted compliance/oracle APIs.

After going deeper into the design + use cases, I think we were framing it slightly wrong.

This isn’t just about replacing oracles.

It might actually be a programmable compliance / verification layer.

What changed in our thinking

Originally:

→ “Replace trusted APIs with ZK proofs”

Now:

→ “Enforce rules using verifiable computation”

That shift matters.

Because the real value isn’t just proving data is correct
It’s proving that a system followed specific constraints

Examples:

• “This user is allowed to hold this asset”
• “This transaction complies with jurisdiction rules”
• “This off-chain computation followed defined logic”

All without revealing underlying data.

Current progress

We now have:

• Halo2-based proving engine
• Modular Rust crates (circuits / prover / common)
• Working pipeline: input → witness → proof (~70ms)

Still early, but the foundation is there.

Open questions

• Where would YOU actually use something like this?
• What would make you integrate it vs ignore it?
• Is “ZK compliance layer” even the right direction?

Repo:
https://github.com/MRSKYWAY/ZKCG

Appreciate all the feedback on the last post — it genuinely helped shape this direction 🙏