#零知識證明
Live, measured metrics for the hashtag #零知識證明 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #零知識證明
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · mastodon.social (Mastodon public tags API) · fetched 2026-08-24 17:59 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.social (Mastodon public search API) · fetched 2026-08-24 17:59 UTCNo related tags with measured usage found for #零知識證明.
Live pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-08-24 17:59 UTCEverything below is measured over the latest 8 public posts (spanning ~18136 hours).
Posting hours (UTC)
Languages: Chinese (Taiwan) (7)
Avg boosts / post: 0.1
Top of the latest posts
🌘 零知識證明速覽 ➤ 用 30 行 Python 程式碼，輕鬆理解無關加密貨幣的圖論零知識證明 ✤ https://bernsteinbear.com/blog/zkp/ 本文介紹如何透過圖形三色問題實作一個不涉及加密貨幣的零知識證明系統。作者參考經典學術論文，以 Python 實作證明者如何隨機排列顏色、加入隨機鹽值以產生雜湊，藉此在不透露具體著色方案的情況下向驗證者證明其擁有解答。 + 原來零知識證明可以用這麼簡單的圖形三色問題來解釋，看完程式碼後完全懂了！ + 使用
🌘 Dusk 網路 PLONK 協議中的未驗證評估漏洞分析 ➤ 致命的信任瑕疵：零知識證明中被忽視的評估驗證 ✤ https://osec.io/blog/2026-04-30-unverified-evaluations-dusk-plonk/ 研究人員在保護 Dusk Network 約 6000 萬美元資產的 PLONK 零知識證明實現（dusk-plonk）中，發現了一個關鍵的安全性漏洞。此漏洞源於驗證器在執行過程中，未對證明者提供的四個多項式選擇器（Selecto
🌘 GitHub - risc0/zirgen：Zirgen 編譯器與 RISC Zero 電路 ➤ 透過 DSL 優化算術電路，釋放零知識證明系統的極致效能 ✤ https://github.com/risc0/zirgen RISC Zero 開源了 Zirgen 編譯器，這是一款專為其證明系統設計的領域特定語言 (DSL) 工具。雖然多數開發者習慣以 Rust 撰寫 zkApp 並運行於 RISC-V zkVM，但 Zirgen 提供了一個更底層的選擇，讓開發者能直接
#零知識證明 across platforms
every network with a public tag surfaceFollow #零知識證明 straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/零知識證明