On 2026-06-25, gonka-docs PR #1257 by @tcharchian added the Report a Vulnerability page to the documentation navigation. The page already existed in the repository; this change makes it reachable from the menu on both the English and Chinese sites.

What changed

The PR is small by line count — 2 additions across a single file — but it closes a visibility gap. Two content files, docs/report-vulnerability.md and docs/zh/report-vulnerability.md, had been committed earlier but were never linked anywhere in the menu, so a reader could only reach them with a direct URL.

PR #1257 adds the page to the Resources section, next to "Get help". It also adds the Chinese navigation label (报告漏洞) so the entry shows up under 资源 on the 中文 site, not only in English.

The placement is deliberate. Resources groups support- and contact-oriented links such as the FAQ and Get help, which is a more natural home for a security disclosure form than the static Reference section that holds protocol documentation.

Why it matters

A vulnerability disclosure page is only useful if people can find it. Until this change, a security researcher who wanted to report an issue in the Gonka stack — chain node, API node, ML node, or the Ethereum bridge — had no menu path to the reporting form and would have had to already know the URL. That is the wrong moment to add friction.

Linking the page from Resources gives every visitor, in either supported language, a one-click route to report a problem. The bilingual fix matters for a network with a large Chinese-speaking validator and host community: a disclosure channel that only surfaces in English reaches a fraction of the people who might spot a bug.

This is documentation plumbing, not a protocol change. It is the kind of plumbing that decides whether a responsible-disclosure process actually gets used.