— Focused on Technical Exchange, Building a High-Quality Developer Ecosystem
—— 专注技术交流，共建优质开发者生态

I. Encouraged Content Types ✅

In-depth technical discussions

• Blockchain development (Solidity / Rust / Smart Contracts, etc.)

• Protocol layer research (ZK-Rollup, Sharding, Consensus Mechanisms, etc.)

• Infrastructure tutorials (Node deployment, contract testing, toolchain usage)

Original technical articles

• Code analysis, architecture design, security attack/defense practices

• Gas optimization solutions, off-chain computation, and other engineering experiences

Hackathon collaboration

• Team recruitment (must specify project direction / tech stack requirements)

• Project development updates (include GitHub or HackQuest project links)

Ecosystem education

• Illustrated explanations of new protocol technical principles

• Evolution of development environments, industry standards

一、鼓励发布内容类型 ✅

技术深度讨论

• 区块链开发（Solidity / Rust / Smart Contract 等）

• 协议层研究（ZK-Rollup、分片、共识机制等）

• 基础设施教程（节点部署、合约测试、工具链使用）

原创技术文章

• 代码解析、架构设计、安全攻防实践

• Gas 优化方案、链下计算等工程经验

黑客松协作

• 组队招募（需注明项目方向 / 技术栈需求）

• 项目开发进展同步（附 GitHub 链接或在 HackQuest 上的项目链接）

生态科普

• 新协议技术原理图解

• 开发环境变迁史、行业标准演进

II. Strictly Prohibited Content 🚫

二、严格禁止内容 🚫

III. Posting Standards 📝

Clear Titles

• Use technical keywords (e.g., "[EVM] Gas Optimization Vulnerability Analysis")

• Prohibit vague titles like "Urgent Help!" or "Newbie Question"

• Label reposts/translations with "[Repost]" or "[Translation]" at the beginning

Structured Content

• Write posts using Markdown formatting

• Use clear subheadings and organized sections

Resource Attribution

• Technical articles must cite references (whitepapers/GitHub issue links)

• Prohibit recommending third-party tools without sources

Reposting/Translation Guidelines

• Clearly mark "[Repost]" or "[Translation]" at the start. Unmarked content will be hidden and moved to drafts.

• When reposting/translating others’ work, credit the original author and source link.

• If the original content lacks public licensing, provide written permission from the author.

三、发帖规范要求 📝

标题清晰

• 使用技术关键词（如：[EVM] Gas优化漏洞分析）

• 禁止"紧急求助！""新人提问"等无信息量标题

• 转载/翻译请在最开始标注「转载/翻译」

内容结构化

• 使用 Markdown 格式书写文章

• 分标题清晰，内容分类

资源引用

• 技术文章需标注参考文献（白皮书/GitHub Issue链接）

• 禁止无来源的第三方工具推荐

关于转载/文章翻译

• 转载/翻译请在最开始标注「转载/翻译」，未标注将屏蔽文章并移至草稿箱

• 如搬运或翻译某位大佬的文章/白皮书，请标注原作者信息及来源链接

• 若原始内容无公开授权，需提供作者书面同意证明

IV. Violation Handling Process ⚖️

1. First offense:

• Content hidden + notification of specific violated rules via private message.

• Allowed to revise and resubmit (technical content only).

2. Second offense:

• Content permanently deleted (unrecoverable from drafts).

3. Malicious violations:

• Publishing gambling/fraudulent content → Permanent ban.

• Bypassing restrictions via multiple accounts → Associated accounts banned.

四、违规处理流程 ⚖️

1. 首次违规

• 屏蔽并站内信告知具体规则条款

• 允许修改后重新提交（限技术类内容）

2. 二次违规

• 内容强制删除，无法在草稿箱找回

3. 恶意违规

• 发布黄赌/欺诈内容直接永封

• 绕过屏蔽多账号发布广告连带封禁

V. High-Quality Content Incentives 🌟

• Featured technical posts: Pinned display + badge award (TBD, launching in Forum V2.0).

• Consistent contributors: Community contribution points + priority invites to offline events.

五、优质内容激励 🌟

• 技术精华帖：置顶展示并授予徽章（TBD, 本功能 论坛V2.0上线）

• 持续贡献者：社区贡献积分+线下活动优先邀请

- - Web3.0 Programming For Everyone - -