Proposal: Decoupling Object Ownership for On-chain Privacy via ZK-Proofs (Ghost Circle)

[Cipher3033]

Hi everyone,

I've been diving deep into Sui’s object centric model lately, and while the performance is impressive, the transparency is still a bit of a hurdle for real-world institutional use.

My team and I (we’re a group of 4 with backgrounds in Cybersecurity, AI, and CS Masters) are currently building Ghost Circle. It’s a privacy protocol that aims to fully decouple the sender/receiver relationship. We’re using a ZK-based logic we call 'Triple Match' basically trying to fit high-level anonymity directly into the Move execution flow.

The way we’re approaching it right now:

We move assets into a 'Ghost' state using commitment objects.

Users provide ZK-SNARKs to prove they have the right to spend without leaking the object’s ID or history.

For the nullifiers, we’re looking at Dynamic Fields to keep double-spending checks fast without killing the performance.

Sui feels like the perfect place for this because of how it handles objects independently, but I’d love to get some 'sanity checks' from the core devs or anyone working on the crypto side here.

A couple of things we’re scratching our heads over:

Any tips for keeping gas costs down when verifying these ZK-proofs in a Move entry function?

Are there any upcoming updates to sui: :zklogin or the cryptography modules that might overlap with what we're building?

Really keen to hear some feedback and see if we’re aligned with where Sui is heading.

Cheers, Magic | Lead Dev @ghost-circle