Annual Election Process

Timeline and Rules for Elections

Each year, SagaDAO holds elections for:

• Working Group seats

• Community-at-Large seat

Working Group Seats (2 seats)

• Reserved for active working group teams aligned with DAO priorities.

• If more than two working groups, DAO members votes to decide what group fills the seats.

• If fewer than two are active, the Core Team may temporarily fill the seat(s).

Community-at-Large Seat (1 seat)

• Open to DAO members who are not affiliated with a working group.

• Candidates represent the broader community perspective.

• Elected directly by DAO membership to bring diverse voices into high-tier governance.

Election Timeline

• Day 1-3: Threshold voting

• Day 1-7: Nominations open in Discord

• Day 8-10: Voting is free on Tap In

• Day 11+: Runoff election (if necessary)

Set the Threshold

• Purpose: To confirm active voters and set the percentage of votes required to win.

• Where: Conducted in Tap In.

• Duration: Lasts 3 days, starting at the beginning of nomination week.

Threshold Options:

• Simple Majority: 50% + 1 vote

• Supermajority: 66%

• High Supermajority: 75%

The selected threshold will apply to all roles.

Nominations

Where: In the DAO’s Discord Duration: Open for 1 week

How It Works:

• A nomination form will be posted for each open seat:

  • 2 Working Group Seats (team-led)

  • 1 Community-at-Large Seat (individual)

• Working groups may nominate themselves for a seat by completing the designated group form.

• Individuals may apply for the Community-at-Large seat using a separate form.

• All completed forms will be posted in Discord for public review.

How to Vote

• Where: Voting will take place on SagaDAO Tap In.

• Duration: Voting lasts 3 days.

Format:

• Voting is multiple-choice

• Each open seat — Working Group or Community-at-Large — is a separate question on the ballot

Ballot Order:

• Working Group Seats: Groups are listed based on when they were officially established

• Community-at-Large Seat: Ballot order is based on Raider Rank, which reflects social media support activity. This order has no impact on voting results. Join date in the SagaDAO Discord is used as the tiebreaker.

Winning Conditions:

• The candidate or group with the most votes who also meets the required voting threshold wins.

• If no one qualifies, a runoff election will be held.

Additional Election Rules

Runoff Elections

• When: Runoff elections will begin immediately after the initial vote concludes.

• Duration: Voting for runoff elections will last 3 days, just like the normal election period.

Format:

• Only the top 2 groups or candidates from the previous round will appear on the ballot.

• Voting will follow the same multiple-choice format as the initial vote.

Winner:

• The groups or candidate with the majority of votes in the runoff election wins.

Tiebreakers:

• Working Group Seats: Tie goes to the group that was officially established earlier.

• Community-at-Large Seat: Tie goes to the individual who joined the SagaDAO Discord first.

Vacancies

• If any seat becomes vacant, whether held by a group or an individual, the Core Team will temporarily fill the seat until it can be filled.

  • A special election will be held to fill the remainder of the term, using the standard nomination, voting, and runoff procedures.

  • If only one valid group or individual is nominated, they may run uncontested and be confirmed with a simple majority vote on Realms.

Doxxing

To maintain accountability, only elected individuals or group representatives must complete a basic verification step before taking their seat.

What’s Required:

• A brief video call with the Core Team

• Privately share:

  • A real name (can be first + last or commonly used name)

  • A social profile (e.g. LinkedIn, GitHub, or similar) to verify identity and background

For Groups:

• Only one representative needs to complete the process, other members do not need to doxx.

This info stays private and is only used if serious issues (like fraud or abuse) arise.

Enforcement: Violations of these policies, including failure to complete the verification steps will result in automatic removal from the core team and suspension of access rights. Any sitting core team member who refuses to complete these steps will also be removed from their position.