Phoenix Foundation: community selection of a fifth director and future appointments
- A text proposal. Passing it records a position; nothing on chain changes by itself.
The vote so far
From the chain
Below quorum so farIf voting closed now
- Yes 25.35M
- No 0
- No with veto 0
- Abstain 15k
What would change the outcome
278M LUNA of stake has not voted. Quorum needs another 65.71M LUNA.
Now Below quorumThen Below quorumTurnout 26.7%, yes 63.1%, veto 6.9%
How validators voted
From the chain
7 of 100 active validators voted, with 8.2% of voting power. 11 addresses voted directly.
- Smart Stake#1 · 6.95% of voting powerYes
- Allnodes#2 · 6.45% of voting powerNo vote
- KuCoin LUNA Node#3 · 5.41% of voting powerNo vote
- VegasNode#4 · 5.07% of voting powerNo vote
- Galactic Punks Validator#5 · 4.66% of voting powerNo vote
- polkachu.com#6 · 4.23% of voting powerNo vote
- DELIGHT#7 · 3.02% of voting powerNo vote
- Stakely.io#8 · 2.98% of voting powerNo vote
- Orbital Command#9 · 2.81% of voting powerNo vote
- ERIS ⚡️ Delegate for claimdrop#10 · 2.78% of voting powerNo vote
- 🦁 The Lion DAO#11 · 2.69% of voting powerNo vote
- cosmosrescue#12 · 2.69% of voting powerNo vote
- HighStakes.ch | Stake for Airdrop#13 · 2.61% of voting powerNo vote
- Lavender.Five Nodes 🐝#14 · 2.33% of voting powerNo vote
- Terrascope#15 · 2.17% of voting powerNo vote
- 01node#16 · 2.01% of voting powerNo vote
- Synergy Nodes#17 · 1.99% of voting powerNo vote
- Stakin by The Tie#18 · 1.66% of voting powerNo vote
- Active Nodes#19 · 1.66% of voting powerNo vote
- WildSage 🧙#20 · 1.55% of voting powerNo vote
- SOLID#21 · 1.48% of voting powerNo vote
- BackBone Labs | Delegate for $SOUL Claim Drop#22 · 1.45% of voting powerNo vote
- SCV-Security#23 · 1.43% of voting powerNo vote
- Pro-Nodes75#24 · 1.42% of voting powerNo vote
- TdrSys | Auto-Compound#25 · 1.29% of voting powerNo vote
- LUNAStaker#26 · 1.28% of voting powerNo vote
- 0base.vc#27 · 1.26% of voting powerNo vote
- Ceres Ventures#28 · 1.12% of voting powerNo vote
- Aardvark#29 · 1.10% of voting powerNo vote
- Centauri Alpha#30 · 0.93% of voting powerNo vote
- Coinage x DAIC#31 · 0.78% of voting powerNo vote
- ISS#32 · 0.77% of voting powerNo vote
- Orion - Auto-Compound#33 · 0.77% of voting powerNo vote
- Interstellar 🍸#34 · 0.69% of voting powerNo vote
- owlstake#35 · 0.69% of voting powerNo vote
- Node39.TOP#36 · 0.68% of voting powerYes
- Burrito Node#37 · 0.67% of voting powerNo vote
- HEXXAGON#38 · 0.64% of voting powerNo vote
- NFTSwitch.xyz | Delegate for $SOUL Claim Drop#39 · 0.63% of voting powerNo vote
- Secure Secrets#40 · 0.59% of voting powerNo vote
- Y#41 · 0.58% of voting powerNo vote
- TERRA-FIRMA#42 · 0.58% of voting powerNo vote
- Luna Whale#43 · 0.56% of voting powerNo vote
- Futura Meridian#44 · 0.54% of voting powerNo vote
- Free Do#45 · 0.52% of voting powerYes
- Easy 2 Stake#46 · 0.51% of voting powerNo vote
- Talis Protocol#47 · 0.51% of voting powerNo vote
- LUNA REWARDS#48 · 0.50% of voting powerNo vote
- Core Dev (Engineering@Terra)#49 · 0.49% of voting powerNo vote
- Autism Staking#50 · 0.49% of voting powerNo vote
- TCB @THORmaximalist#51 · 0.48% of voting powerNo vote
- Solva (CryptoCrew)#52 · 0.48% of voting powerNo vote
- Monster Node#53 · 0.46% of voting powerNo vote
- AutoStake 🛡️ Slash Protected#54 · 0.43% of voting powerNo vote
- Nodeplus#55 · 0.41% of voting powerNo vote
- FreshSTAKING#56 · 0.38% of voting powerNo vote
- stakingcabin#57 · 0.36% of voting powerNo vote
- Moon Platoon#58 · 0.35% of voting powerNo vote
- moonshot#59 · 0.34% of voting powerNo vote
- MissionControl#60 · 0.33% of voting powerNo vote
- 🙏 uGaenn ⛅#61 · 0.31% of voting powerNo vote
- Interstake One#62 · 0.29% of voting powerNo vote
- KK Validator#63 · 0.25% of voting powerNo vote
- AuraStake#64 · 0.23% of voting powerNo vote
- Wave#65 · 0.23% of voting powerNo vote
- Stakeflow#66 · 0.23% of voting powerNo vote
- Staker Space#67 · 0.22% of voting powerNo vote
- SafePoint#68 · 0.22% of voting powerNo vote
- StakeSabai#69 · 0.22% of voting powerNo vote
- Enigma#70 · 0.22% of voting powerNo vote
- OneStar#71 · 0.21% of voting powerNo vote
- 8moon#72 · 0.21% of voting powerNo vote
- Luna Station 88#73 · 0.21% of voting powerNo vote
- Inotel#74 · 0.20% of voting powerNo vote
- NITAWA#75 · 0.20% of voting powerNo vote
- Sapient Nodes#76 · 0.20% of voting powerNo vote
- RuneTerra#77 · 0.18% of voting powerNo vote
- Encapsulate#78 · 0.18% of voting powerNo vote
- The Bear Validator#79 · 0.18% of voting powerNo vote
- Defi Suffrage#80 · 0.17% of voting powerNo vote
- Lunatic Validator#81 · 0.16% of voting powerNo vote
- Noderunners#82 · 0.16% of voting powerNo vote
- BIG Labs#83 · 0.16% of voting powerNo vote
- Long Live Luna#84 · 0.14% of voting powerNo vote
- Crypto Plant#85 · 0.13% of voting powerNo vote
- Bit Cat🐱#86 · 0.13% of voting powerNo vote
- DEEPSTATE#87 · 0.07% of voting powerNo vote
- NodesHub#88 · 0.01% of voting powerNo vote
- NODESYNC#89 · 0.01% of voting powerNo vote
- Foundation bans validators from validator discord for asking questions#90 · 0.01% of voting powerNo vote
- Cosmos Spaces#91 · 0.00% of voting powerAbstain
- Noddex#92 · 0.00% of voting powerYes
- hhhhhhhhhhhhhhh#93 · 0.00% of voting powerNo vote
- VALIDATORSG#94 · 0.00% of voting powerNo vote
- BoyGau#95 · 0.00% of voting powerYes
- navs#96 · 0.00% of voting powerNo vote
- Shazoes#97 · 0.00% of voting powerNo vote
- LuckyStar#98 · 0.00% of voting powerNo vote
- InnoS#99 · 0.00% of voting powerYes
- Aeris#100 · 0.00% of voting powerNo vote
Today’s active set and voting power. Every validator’s record
Proposal text
Written by the proposer; links are not clickable. What runs is what it does, above.
# Phoenix Foundation: community selection of a fifth director and future appointments
This proposal opens a public process to select one additional independent director for the Phoenix Foundation. The intended result is five equally weighted directors, with three approvals required for Stewardship multisig decisions.
**A YES vote opens nominations for a fifth director, approves the election process and Treasury-funded ballot deposits, and requests appointment of the selected eligible candidate with three affirmative multisig approvals required out of five. It also approves the specific bylaw amendment below requiring community elections for future director appointments, for adoption under §7.3.**
## Purpose and authority
[Proposal 4853][proposal4853] brought a dispute over the Stewardship's composition to Terra governance. It was rejected. This proposal offers a community-selected fifth director as a way to address the disagreement over the Board’s composition, without asking voters to decide the underlying allegations or declare an emergency.
This proposal makes no findings about any current Director and grants no special investigative, disciplinary or removal powers. Any such action must follow its own applicable authority and procedure.
The fifth director would hold a full director and Stewardship multisig seat with the same responsibilities and voting weight as the others. They would have no additional casting vote or unilateral authority, consistent with [§2.2.1.1][bylaws-board].
The [founding discussion][founding] linked from approved [proposal 4816][proposal4816] assigns ultimate decision or veto power over the Phoenix Directive to Terra stakers and validators through governance. [Bylaw §1.4.1][bylaws-principles] refers to that Directive. This founding commitment supports community selection; the actual appointment must also follow the Foundation's governing documents.
The published bylaws provide the appointment route:
- **[§2.2.2][bylaws-board]:** the initial four-director board can change size through Stewardship multisig membership changes.
- **[§2.2.3.2][bylaws-appointment] and [§2.4.2.2][bylaws-onboarding]:** subsequent directors and multisig members are appointed through the corresponding multisig upgrade.
- **[§2.1][bylaws-board] and [§2.4.3.1][bylaws-onboarding]:** the candidate must meet eligibility, participation-agreement, identity-information and legal requirements.
- **[§3.1.3.2(c)][bylaws-quorum]:** actions requiring the Stewardship multisig must meet its signing threshold and be successfully executed.
- **[§3.2.1.3(d) and §3.2.1.4][bylaws-schedule]:** Schedule 3 records the signing threshold and must be updated following multisig changes.
These provisions support expanding the board through the existing appointment procedure. This non-executable proposal establishes the requested selection process; it does not itself execute a multisig change or complete a legal appointment. The new standing election requirement below must also be adopted through the applicable bylaw procedure.
## Three approvals out of five
The voting configuration would change alongside appointment of the fifth equally weighted member to require affirmative approval from at least three of the five members. A percentage setting alone is not sufficient proof of this requirement: formal abstentions reduce the denominator in the percentage calculation in the [DAO DAO v2.4.0 source][threshold-source], matching the version reported by the Foundation’s proposal module. Keeping a 75% percentage threshold with five equally weighted members would require four affirmative approvals when no formal abstentions are cast, allowing two members to block the other three.
The membership and voting-configuration changes must be tested and executed together through an authorized procedure. The resulting configuration, and any intermediate state introduced by implementation, must not permit execution with fewer than three affirmative member approvals. Testing must cover formal abstentions, recusals and membership changes. The implementation plan must also address pending proposals that retain earlier membership or threshold snapshots. Existing conflict-of-interest obligations continue to apply.
## Call for volunteers
For this fifth-director election, nominations open when this proposal passes Terra governance and remain open for 14 days. People may nominate themselves or another person who publicly accepts the nomination.
Each candidate should post:
- Relevant governance, financial oversight, security or technical experience.
- Their availability and ability to review proposals and sign transactions securely.
- Material financial, employment and business relationships with current directors, funded teams and applicants, including any interests that could require recusal.
- How they would fulfil the responsibilities of a director and contribute to board decisions.
- Any requested compensation or expenses.
- Their public acceptance of the nomination and the candidate declaration below, with their public name and date.
Appointment checks must address the eligibility requirements in §2.1 and the participation agreement, required identity information and legal requirements in [§2.4.3.1][bylaws-onboarding]. Identity documents must be verified privately, respecting [§§5.1–5.2][bylaws-confidentiality]. This proposal authorizes no compensation; the Board sets director compensation under [§2.2.7][bylaws-appointment], and any requested terms must be disclosed before candidate voting through an authorized process.
**By nominating themselves, or accepting another person's nomination, candidates acknowledge that this is a Foundation director and Stewardship multisig position requiring KYC/identity verification. They commit to completing the required checks, signing the Multisig Participation Agreement and satisfying the same applicable legal and bylaw obligations as other stewards before taking office.** A nomination is complete only when the candidate publishes the following declaration:
> I nominate myself, or accept this nomination, for a Phoenix Foundation director and Stewardship multisig seat. I have read the eligibility and onboarding requirements in §§2.1 and 2.4.3.1. I commit to completing the required KYC/identity verification, signing the Multisig Participation Agreement, providing accurate and complete information through the designated secure process, and satisfying the same applicable legal and bylaw obligations as other stewards before taking office. I will disclose material conflicts and cooperate with the published eligibility and review process. I understand that withdrawal, refusal to complete required onboarding, or a final finding of ineligibility under that process forfeits my eligibility for appointment, and the next qualifying candidate may be considered under the election rules. If appointed, I will exercise independent judgment and fulfil the responsibilities of the role.
**Accepted by:** candidate public name and public account or wallet confirming acceptance.
**Date:** UTC date.
The checks include legal capacity and conflicting obligations (§§2.1.1–2), applicable sanctions restrictions (§2.1.3), the convictions or findings of liability specified in §2.1.4, and the blockchain knowledge and experience required by §2.1.5. References to “good character” mean these identified eligibility requirements and any specifically identified applicable legal requirement; they do not authorize a subjective reputation or political-alignment test.
Before candidate voting, publish the full checklist, secure submission route, named person or body responsible for the initial eligibility determination, and the independent person or body reviewing a disputed determination. Publish their respective roles and the review procedure. Apply the same criteria to every candidate. Candidates must supply requested onboarding documents within 14 calendar days after receiving the complete requirements and a secure submission route. Give at least seven calendar days to answer an adverse assessment or correct a remediable omission. Publish any reasonable extension and its basis. Delay by the Foundation or its reviewer is not candidate refusal or failure. Identity documents and protected background-check information must remain private.
Candidates must exercise independent judgment, without pledging support to an existing director or a predetermined finding about past conduct.
## Candidate votes
Allow seven days after nominations for public questions. Before voting, publish the candidate list, appointment route and tested membership and threshold changes. Publish authorised, non-confidential summaries of eligibility concerns and the candidate’s response, without disclosing protected identity documents, background-check information or confidential deliberations. Any disqualification must cite an objective requirement and allow a response.
Before the ballot batch enters voting, publish the required appointment approvals, the eligibility reviewer and review process, and the secured deposit funding. Identify any later bylaw amendment or Charter provision affecting the appointment. If a required step remains unresolved, publish the specific obstacle and proposed resolution.
For this election, the proposal author will coordinate one non-executable proposal per candidate and an option to appoint none and reopen nominations. Publish the authorized submitter address and complete ballot register before funding the batch into voting; each proposal must link both this process and the register. Only registered proposals count.
Use equal voting periods starting within one hour across the complete batch. If this condition is missed, rerun the complete ballot. Determine the result only after every proposal closes.
The election rules are:
1. Voters may vote YES for every candidate they consider suitable. This is approval voting; there is no one-candidate-only restriction.
2. Each option must pass Terra's normal governance requirements to qualify. NO, NO WITH VETO and ABSTAIN retain their normal effects.
3. Among qualifying candidates, the candidate receiving the greatest absolute amount of final YES voting power is provisionally selected, subject to completing the required onboarding. Use voting power, not wallet count or YES percentage.
4. If the reopen-nominations option passes and receives at least as much YES voting power as the leading qualifying candidate, no candidate is selected. If no candidate qualifies, reopen nominations.
5. An exact tie between leading candidates triggers one runoff including those candidates and the reopen-nominations option, using the same rules. If no unique candidate wins, reopen nominations.
6. **If the leading candidate withdraws, refuses the required KYC or other onboarding, or is finally found ineligible under the published requirements, that candidate forfeits eligibility for appointment in this election. The next-highest qualifying candidate is then considered under the same rules.** A final adverse determination requires a documented, specific basis and completion of the response/review process. Unresolved allegations or delay caused by the Foundation do not justify forfeiture.
7. Reapply the passing-proposal, eligibility, reopen-nominations and tie rules after each exclusion. The successor must have passed their own candidate vote and must complete the same checks. If the passing reopen-nominations option equals or exceeds that successor's YES voting power, or no qualifying candidate remains, reopen nominations. Votes remain on the public record; votes for an excluded candidate are not transferred to another candidate.
8. If a runoff was needed but its candidates are later excluded, return to the original ballot's remaining qualifying candidates and apply these rules again. A candidate who failed the runoff's normal governance requirements is also excluded. If the reopen-nominations option already won the runoff, the election has ended and nominations reopen. The limit of one runoff per election remains; an unresolved later tie reopens nominations.
Delegators must vote separately on each proposal where they want to override their validator's vote. Voting on one candidate does not override the other ballots.
## Treasury funding of nomination-vote deposits
The Phoenix Treasury will pay the required governance deposits for every registered candidate proposal, the reopen-nominations option and any runoff or replacement ballot conducted under this process, including future elections governed by the standing rule below. Candidates will not be required to fund these deposits personally.
Funding is limited to the minimum deposit required for each registered proposal, after accounting for deposits already supplied by others. Before each batch is submitted, publish the number of proposals, required deposit per proposal and total Treasury funding, and complete the applicable Treasury approvals. This text proposal does not itself transfer funds or bypass the signing and execution requirements in [§3.1.3.2(c)][bylaws-quorum].
All returned Treasury-funded deposits must return to the Treasury. If an authorized submitter receives a refund, they must remit it to the Treasury and publish the transaction. Deposits not returned under Terra's governance rules are a Treasury cost, not a personal cost imposed on candidates. Publish a reconciliation of amounts deposited, returned and not returned for each batch.
## Completing the appointment
Within seven calendar days of this proposal passing, the Foundation is asked to identify those responsible for onboarding, deposit funding and appointment, and the approvals needed to complete them. Any objection should identify the specific bylaw, legal or technical requirement and a proposed resolution.
After selection and completion of onboarding, the Foundation is asked to execute the membership and threshold changes within seven calendar days, then publish the transaction and updated Schedule 3 under [§3.2.1.4][bylaws-schedule]. If implementation remains incomplete, publish the outstanding step and expected completion date through an authorized summary consistent with [Article 5][bylaws-confidentiality].
This proposal uses the existing board-expansion route and requests the corresponding Schedule 3 update. The standing election amendment below requires adoption under [§7.3][bylaws-amendment], subject to applicable governing documents and veto requirements. If any further amendment or waiver is needed specifically for this appointment or voting configuration, identify its exact text and obtain the applicable approval. This vote grants no unspecified waiver. The election rules and timelines are proposed requirements; they are not presented as provisions already contained in the published bylaws.
## Future director appointments: specific bylaw amendment
The community election procedure should also apply when a director leaves or an additional seat is lawfully created. This proposal therefore approves the following addition to **§2.2.3.2**, for adoption under §7.3:
> **Community selection of subsequent Directors**
>
> Every subsequent appointment of a Director, including an appointment to fill a vacancy or an additional seat, shall first undergo public nomination and selection through Terra Governance using the election procedure approved by this proposal, or a replacement procedure expressly approved by Terra Governance. This requirement includes temporary and interim appointments.
>
> Each election shall be separately announced, identifying the seat, election coordinator and nomination timetable. Nominations shall remain open for 14 calendar days from the announced opening date, followed by at least seven calendar days for public questions before candidate voting. The approved rules for candidate declarations, eligibility checks and review, separate candidate ballots, reopening nominations, ties, succession following disqualification, and Treasury-funded deposits shall apply. Where several seats are vacant, fill them through separately identified, sequential elections using the approved single-seat procedure. A person already serving as a Director may not fill a second seat.
>
> The selected candidate must satisfy Articles 2.1 and 2.4.3.1 before appointment. Appointment shall then be completed through the Stewardship Multisig upgrade required by Articles 2.2.3.2 and 2.4.2.2. Following a final result and completed onboarding, the BORG shall seek to complete appointment within seven calendar days or publish an authorized summary of the remaining requirement and expected completion date.
>
> This requirement does not end or renew any serving Director’s term, authorize additional seats, or change the voting threshold for a different board configuration. Amendment or waiver of this community-selection requirement requires express Terra Governance approval in addition to the approvals required by Article 7.3.
Add the following sentence to **§2.4.2.2**:
> Appointment to the Stewardship Multisig as a Director is also subject to the community-selection requirement in Article 2.2.3.2.
For adoption, the amendment must identify this governance proposal by its on-chain ID and preserve an immutable copy of its election procedure. Publish the adoption record, effective date and updated bylaws under [§1.5][bylaws-publication]. Until validly adopted, the standing requirement must not be represented as already legally operative. The initial fifth-director selection remains subject to the existing appointment requirements described above.
This is a standing rule for director selection. It leaves existing directors in office and requires an election even for a temporary or urgent vacancy.
## Voting on this process proposal
**YES:** Approve the nomination and selection process, Treasury-funded ballot deposits, and appointment of the selected eligible candidate as a fifth equal director with three affirmative multisig approvals required out of five. Also approve the exact additions to §§2.2.3.2 and 2.4.2.2 above requiring community elections for future director appointments, for adoption under §7.3.
**NO:** Oppose this proposal, including its election process, board configuration or standing election requirement.
**ABSTAIN / NO WITH VETO:** These retain their normal Terra governance meanings and effects.
## Precedent and adaptation
Osmosis used a process proposal followed by separate option votes for its April 2022 bridge selection: [205](https://www.mintscan.io/osmosis/proposals/205) and [206](https://www.mintscan.io/osmosis/proposals/206). This adaptation retains ordinary Terra pass requirements and uses an exact-tie runoff, rather than Osmosis's special quorum and runoff rules.
Bylaw references are to the published Phoenix Foundation bylaws, which state that they were adopted on 22 December 2025. Before candidate voting, the implementation plan must identify the effective Charter, any subsequent bylaw amendments and other governing documents that affect the appointment or adoption of the standing election requirement.
[bylaws-board]: https://raw.githubusercontent.com/phoenix-directive/docs/main/Phoenix%20Foundation%20-%20Bylaws.pdf#page=6
[bylaws-appointment]: https://raw.githubusercontent.com/phoenix-directive/docs/main/Phoenix%20Foundation%20-%20Bylaws.pdf#page=7
[bylaws-onboarding]: https://raw.githubusercontent.com/phoenix-directive/docs/main/Phoenix%20Foundation%20-%20Bylaws.pdf#page=8
[bylaws-quorum]: https://raw.githubusercontent.com/phoenix-directive/docs/main/Phoenix%20Foundation%20-%20Bylaws.pdf#page=15
[bylaws-conflicts]: https://raw.githubusercontent.com/phoenix-directive/docs/main/Phoenix%20Foundation%20-%20Bylaws.pdf#page=23
[bylaws-confidentiality]: https://raw.githubusercontent.com/phoenix-directive/docs/main/Phoenix%20Foundation%20-%20Bylaws.pdf#page=24
[bylaws-amendment]:
Details
- Submitted
- 5 Nov 2026
- Voting
- 5 Nov 2026 to 12 Nov 2026
- Proposer
- terra1hr7…4qac8
- Messages
- 0
- Tallied by
- the gov module, at the end of voting
- Individual votes
- available
- Voting power now
- 304M LUNA