🗳️Voting & Proposal Mechanism

How $BYTES are used to propose and vote on open-source projects

Server Protocol’s governance is fully on-chain and powered by $BYTES. These tokens are not only earned through staking but also spent (and burned) when used for voting or creating proposals. This section provides a complete breakdown of how project proposals and community voting work in practice.

---

🧾 Project Submission

Any user can propose a new open-source project to be evaluated and potentially funded by the community. To ensure commitment and filter out spam or low-quality proposals, users must meet the following criteria:

Requirements to propose a project:

• 🔥 Burn 1,000,000 $BYTES.

• 💸 Pay a fee of 100 $SERVER (sent to the Treasury wallet).

• 🗂️ This creates a Repository Account with on-chain metadata:

  • Project name

  • Repository owner

  • Target branch

  • Timestamp and creator

Once submitted, the project is immediately published on-chain and becomes available for voting.

⚠️ Only users with sufficient $BYTES and $SERVER can submit proposals.

---

🗳️ Voting Mechanism

Community members vote on whether a submitted project should receive funding by spending their $BYTES.

Rules for voting:

• ✅ Each user can vote only once per project.

• 🔁 The vote can be modified later (from positive to negative or vice versa), but:

  • ❌ The amount of $BYTES used in that vote cannot be increased.

  • ❌ Multiple votes for the same project by the same user are not allowed.

Voting parameters:

• 💰 Minimum amount of $BYTES per vote: 100

• 💰 Maximum amount of $BYTES per vote: 10,000

• 🧾 Fee in $SERVER for each vote: 5 $SERVER

• 🔥 All $BYTES used are permanently burned

• 🧮 Voting Power Formula:

textCopiarEditarVote Weight = $BYTES Used × Reputation Score

This means that two users spending the same number of $BYTES can have different influence depending on their on-chain reputation.

Positive vs Negative Votes:

• ✅ A vote in favor increases the net score of the project.

• ❌ A vote against subtracts from the project's total.

• ⚖️ What matters is the final net score of the project to determine its eligibility for funding.

---

🧠 Design Considerations

• Reputation prevents whale manipulation: Token holders with little participation have limited impact.

• Vote burning encourages responsible use: Spending $BYTES costs value, ensuring voters use it meaningfully.

• Fee-based votes sustain the ecosystem: All $SERVER fees go to the Treasury for long-term sustainability.

---

✅ Summary of Key Limits and Rules

Parameter	Value
Max votes per user per project	1
Vote direction change allowed	✅ Yes
Increase of $BYTES in existing vote	❌ No
$BYTES per vote (min)	100
$BYTES per vote (max)	10,000
$SERVER fee per vote	5 $SERVER
$BYTES burned per vote	Equal to amount used
Voting power formula	$BYTES × Reputation Score