English
Public bug reports
Use the forum or GitHub Issues for ordinary bugs, documentation errors, interoperability questions, and feature requests. Include:
- affected version, commit or release source, operating system, and desktop or CLI;
- exact preconditions and minimal reproduction steps;
- expected and observed behavior;
- short logs or test fixtures with all secrets and personal data removed;
- whether the issue is consistent or intermittent.
Search existing topics and issues first. Keep one independently reproducible problem per report.
Security vulnerabilities
Do not publish an unpatched vulnerability, exploit, production credential, private key, or recovery phrase. Report security issues privately through GitHub Security Advisories. If private reporting is unavailable, open only a minimal public issue asking for a private contact channel.
Improvement proposals
A useful proposal states the problem before the solution. Describe who is affected, current behavior, the proposed change, compatibility and migration impact, security and consensus risks, alternatives, and how the change can be tested.
Forum agreement is discussion, not activation. Changes to consensus require explicit implementation, review, cross-version tests, a published release, and a defined activation rule. Public Seed nodes are network entry points and cannot unilaterally change rules accepted by independent nodes.
Source, protocol documents, and accepted changes remain authoritative in the Entcoin repository.
中文
公开问题反馈
普通程序问题、文档错误、兼容性疑问和功能建议可以发布在论坛或 GitHub Issues。请包含：
- 受影响的版本、提交或下载来源、操作系统，以及桌面端还是 CLI；
- 准确前置条件和最小复现步骤；
- 预期行为与实际行为；
- 已移除秘密和个人数据的简短日志或测试样例；
- 问题是稳定出现还是偶发。
请先搜索已有主题和 Issue，每份报告只描述一个可以独立复现的问题。
安全漏洞
不要公开尚未修复的漏洞、利用代码、生产凭据、私钥或恢复词。安全问题请通过 GitHub Security Advisories 私下报告。如果暂时无法使用私密报告，只能发布一个不含技术细节的最小说明，请求建立私下联系渠道。
改进提案
有用的提案应先说明问题，再说明方案。请描述受影响的人、当前行为、建议改动、兼容与迁移影响、安全和共识风险、替代方案，以及如何验证改动。
论坛达成一致只代表讨论结果，不等于规则已经生效。共识改动必须有明确实现、审查、跨版本测试、正式发布和激活规则。公共 Seed 节点只是网络入口，不能单方面改变独立节点接受的规则。
源码、协议文档和已接受改动以 Entcoin 仓库为准。