💥 Gate Square Event: #PostToWinCC 💥
Post original content on Gate Square related to Canton Network (CC) or its ongoing campaigns for a chance to share 3,334 CC rewards!
📅 Event Period:
Nov 10, 2025, 10:00 – Nov 17, 2025, 16:00 (UTC)
📌 Related Campaigns:
Launchpool: https://www.gate.com/announcements/article/48098
CandyDrop: https://www.gate.com/announcements/article/48092
Earn: https://www.gate.com/announcements/article/48119
📌 How to Participate:
1️⃣ Post original content about Canton (CC) or its campaigns on Gate Square.
2️⃣ Content must be at least 80 words.
3️⃣ Add the hashtag #PostTo
It's quite ironic to say - a bunch of projects claim to prioritize "privacy first" but then ask you to submit your identification scans, bind your email, and even dig into your Wallet history. Not many truly understand it, but zkPass is one.
The idea is actually quite straightforward: the verification should not be controlled by others; it should be up to you to decide. The process is not complicated—first, connect to any Web2 account (Twitter, GitHub, or any exchange will do), then run a zero-knowledge proof locally, and finally, send this proof to the party that needs to verify it. Throughout the entire process, your original data does not leave your premises.
The charm of this thing called ZKP lies in this: I can prove that I am me, but you can't see exactly who I am. It sounds esoteric, but it is actually one of the most essential infrastructures that should be popularized in the current Web3 identification layer.