Welcome to the Bounties node! 
This is a technical marketplace for paid requests and offers, as well as a competitive arena where tech enthusiasts can pit their skills against one another. You have resources and challenges; I have the technology and solutions. To ensure employers’ commissions are delivered quickly and hunters’ rights are protected, please read these guidelines carefully before posting or taking on a task.
I. Posting Guidelines and Tag Workflow 
To keep the forum organized and ensure useful information can be found promptly, all posts must use the forum’s built-in Tags and standard title format.
1. Required Forum Tags
When posting, select the following two types of tags in the editor:
- Task type (choose one):
Bounty/Bounty Contest - Status (update as the task progresses):
Open
/ In Progress
/ Settled
/ Closed
2. Title Format
After removing the category and status, the title field only needs to follow this format:
[Reward] One-sentence summary of the core requirement or challenge
-
State the price clearly—no empty promises: The reward must be direct and specific. Do not use vague terms such as “DM me,” “negotiable,” or “perks.”
-
Standard title examples:
- Cash:
[￥300] Fix connection-pool leaks under high concurrency in a Go gateway - Resources:
[1-year US West high-spec VPS] Write a set of Shell scripts for automated container disaster recovery and off-site synchronization - Community:
[8,000 Energy + exclusive “Elite Reverse Engineering” title] First Lightweight Model Evaluation Benchmarking Competition
- Cash:
II. Operating Rules
This node operates under two tracks: “Single-User Directed Bounties” and “Bounty Competitions”, each with a different focus:
| Dimension | Directed Bounty (first come, first served / single-person lock) |
Bounty Competition (open submissions / race)  |
|---|---|---|
| Use cases | Bug investigation, custom script development, protocol reverse engineering, operations troubleshooting | Algorithm accuracy contests, performance benchmarking, thematic design, lightweight hackathons |
| Execution | Once both parties reach an agreement, the thread starter must change the status tag to In Progress and designate the participant, preventing multiple hunters from wasting effort on the same task. |
Everyone may submit freely; public evaluation criteria and a submission deadline must be set. |
| Acceptance | The full reward is paid once the agreed acceptance criteria are met. | An evaluation script, leaderboard, or public review period is established, and the prize pool is divided according to the overall rankings. |
III. Reward Fulfillment and Transaction Security
1. Reward Commitments Must Be Genuine
- Virtual resources (VPS / computing power / accounts): Posts must specify the exact specifications, remaining validity period, and transfer method (e.g., an official account push, email reassignment, or dedicated credentials).
- Community assets (Energy / virtual titles): Before posting, confirm that your account has sufficient Energy, or report the event-specific title permissions to the moderation team in advance
. - Cash payments: Specify the payment channel. Do not request a change to discounted goods after delivery.
2. Anti-Free-Riding and Anti-Fraud Measures
- Protecting core code: Before delivering the results, hunters are advised to demonstrate functionality through sanitized logs, screen-recording videos, online API test demos, or similar means. Deliver the complete unobfuscated source code only after receiving payment or having the resources transferred.
- Strict penalties for free-riding: Posters are strictly prohibited from privately extracting deliverables under the pretext of “testing a solution” or “providing ideas” and then unilaterally closing the bounty. Once verified, the account will be permanently banned and listed on the blacklist.
- Milestone-based delivery: For large projects, it is strongly recommended to split the work into stages, with acceptance and payment handled in batches to reduce both parties’ performance risk.
IV. Disclaimer and Red-Line Rules
- Platform mediation disclaimer: This node only provides a space for technical competitions, request matching, and discussion. The community assumes no responsibility for fund guarantees, escrow, or joint liability for offline breaches by either party to a transaction. Please assess transaction risks yourself.
- Prohibited illicit and destructive activities: Do not post tasks involving Trojan evasion, unauthorized system penetration, the collection of sensitive personal data, account theft, or any other activity that violates local laws and regulations. Violating content will be deleted and accounts banned immediately; serious cases will be referred to the relevant authorities.
Appendix: Sample Post Template
Markdown
### 1. Requirement Details / Challenge Description
- Business background:
- Core objective:
- Technology stack and environment constraints:
### 2. Acceptance and Delivery Criteria
- Deliverable format (e.g., GitHub PR / standalone source package / reproduction environment script / operation screen recording):
- Delivery requirements (e.g., runs without errors, performance throughput metrics, test-case coverage):
### 3. Bounty and Fulfillment Method
- Reward (e.g., cash amount / specific VPS specifications and duration / community Energy and title):
- Payment method (e.g., WeChat transfer / USDT / platform push provisioning):
### 4. Deadline and Mode
- Mode: Select the corresponding system tag at the top of the post (Bounty / Contest)
- Deadline: YYYY-MM-DD
- Candidate selection strategy (single-person lock / open leaderboard):
