Pinned
zkPass
2,025 posts
zkPass
@zkPass
Introducing @zkPass Arena: an autonomous reputation engine for the agent economy. Launched with support from the @BinanceWallet Booster Program. Arena is a structured environment where AI agents interact, compete, and build reputation through verifiable actions. Trust does not
- Smart contracts made money programmable. Proofs make facts programmable. We're still very early in figuring out what that unlocks.
- Most "growth programs" look good on paper Few actually translate into real users and real capital @BinanceWallet booster is one of the exceptions Next week, we go againOne program. 19 launches. Real impact. Binance Alpha Booster Program continues to accelerate project growth by connecting Web3 projects with a highly engaged community. 📊 Booster by the numbers: - 19 projects launched - 86.4M total audience reach - 2.45M verified users engaged
- zkPass reposted
요즘 커뮤니티 분위기가 꽤 흥미롭네요. 다음 주가 기대됩니다. g $ZKP - zkPass reposted
The question isn't whether a system uses ZK. The question is whether privacy remains guaranteed when ZK is removed. If a privacy-preserving system can fall back to identity disclosure, then privacy isn't a property of the system. It's a policy choice. And policy choices canThe EU age verification app is presented as “completely anonymous”. But the risk is that member states (the countries are supposed to create their own versions of the open-source EU app) use it to introduce identity verification that makes it impossible to post anonymously on - Replying to @zkPass6/6 The real reframe: a TEE verifier turns "do N verifiers behave?" into "did this exact program run inside this exact measurement?" You stop negotiating with incentives and start reading evidence. Fishermen do not die, they get promoted from recomputing every proof to
- Replying to @zkPass5/6 The kill shot is KMS. Even if the operator owns the EC2 host, they cannot pull the signing key out to sign by hand. The key is generated in the enclave, never exported, sealed by a KMS data key, and unsealed only after an NSM document matching ImageSha384 and PCRs. The
- Replying to @zkPass4/6 "Trustworthy" here does not mean trust our server. It means every result drags an externally checkable evidence chain behind it. Each artifact does exactly one job. ImageSha384 pins which EIF is running. PCR0/1/2 prove image, kernel and verifier app are untouched. The nonce
- Replying to @zkPass3/6 That circus "works," and it taxes you forever. Every proof costs N times the latency and N times the compute. Threshold protocols bloat your product surface. Fishermen have to stay online around the clock recomputing everything. You are not buying trust, you are renting it
- Replying to @zkPass2/6 A verifier architecture is not a backend detail. It is a decision about where trust lives. At product scale you ask about latency, cost, fraud. At civilization scale you ask who controls compute, who can inspect it, who gets silently excluded. The brutal question every
