Proposal 4857 · Text / signal

Community governance and independent Foundation accountability

Voting nowends 24 Nov 2026

  • 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 56.23M
  • No 0
  • No with veto 0
  • Abstain 17k
Turnout, needs 30%
18.2% · not met
Yes, needs more than 50%
100.0% · met
Veto, must stay at or below 33.4%
0.0% · met
What would change the outcome

253M LUNA of stake has not voted. Quorum needs another 36.47M LUNA.

Now Below quorumThen PassingTurnout 34.6%, yes 75.2%, veto 4.7%

How validators voted

From the chain

18 of 100 active validators voted, with 17.6% of voting power. 53 addresses voted directly.

  • Smart Stake#1 · 6.89% of voting powerNo vote
  • Allnodes#2 · 6.01% of voting powerNo vote
  • KuCoin LUNA Node#3 · 5.98% of voting powerNo vote
  • VegasNode#4 · 4.98% of voting powerNo vote
  • Galactic Punks Validator#5 · 4.89% of voting powerNo vote
  • polkachu.com#6 · 4.18% of voting powerYes
  • DELIGHT#7 · 3.00% of voting powerNo vote
  • Stakely.io#8 · 2.96% of voting powerNo vote
  • ERIS ⚡️ Delegate for claimdrop#9 · 2.88% of voting powerNo vote
  • cosmosrescue#10 · 2.79% of voting powerNo vote
  • Orbital Command#11 · 2.77% of voting powerNo vote
  • HighStakes.ch | Stake for Airdrop#12 · 2.68% of voting powerNo vote
  • 🦁 The Lion DAO#13 · 2.68% of voting powerNo vote
  • Lavender.Five Nodes 🐝#14 · 2.31% of voting powerYes
  • Terrascope#15 · 2.14% of voting powerNo vote
  • 01node#16 · 2.11% of voting powerNo vote
  • Synergy Nodes#17 · 1.97% of voting powerYes
  • Active Nodes#18 · 1.65% of voting powerNo vote
  • Stakin by The Tie#19 · 1.64% of voting powerYes
  • WildSage 🧙#20 · 1.55% of voting powerYes
  • BackBone Labs | Delegate for $SOUL Claim Drop#21 · 1.53% of voting powerNo vote
  • SOLID#22 · 1.44% of voting powerYes
  • SCV-Security#23 · 1.42% of voting powerNo vote
  • Pro-Nodes75#24 · 1.41% of voting powerNo vote
  • LUNAStaker#25 · 1.28% of voting powerNo vote
  • 0base.vc#26 · 1.24% of voting powerNo vote
  • TdrSys | Auto-Compound#27 · 1.22% of voting powerYes
  • Aardvark#28 · 1.08% of voting powerNo vote
  • Centauri Alpha#29 · 0.91% of voting powerNo vote
  • Orion - Auto-Compound#30 · 0.77% of voting powerNo vote
  • Coinage x DAIC#31 · 0.76% of voting powerNo vote
  • ISS#32 · 0.76% of voting powerNo vote
  • Node39.TOP#33 · 0.68% of voting powerYes
  • Ceres Ventures#34 · 0.68% of voting powerYes
  • owlstake#35 · 0.68% of voting powerNo vote
  • Interstellar 🍸#36 · 0.67% of voting powerYes
  • Burrito Node#37 · 0.66% of voting powerNo vote
  • NFTSwitch.xyz | Delegate for $SOUL Claim Drop#38 · 0.62% of voting powerNo vote
  • HEXXAGON#39 · 0.58% of voting powerNo vote
  • Secure Secrets#40 · 0.58% of voting powerNo vote
  • Y#41 · 0.57% of voting powerNo vote
  • TERRA-FIRMA#42 · 0.57% of voting powerNo vote
  • Luna Whale#43 · 0.55% of voting powerNo vote
  • Futura Meridian#44 · 0.53% of voting powerNo vote
  • Free Do#45 · 0.51% of voting powerYes
  • Core Dev (Engineering@Terra)#46 · 0.51% of voting powerNo vote
  • Easy 2 Stake#47 · 0.50% of voting powerNo vote
  • Talis Protocol#48 · 0.50% of voting powerNo vote
  • LUNA REWARDS#49 · 0.49% of voting powerNo vote
  • Autism Staking#50 · 0.48% of voting powerNo vote
  • Mario#51 · 0.47% of voting powerNo vote
  • Solva (CryptoCrew)#52 · 0.47% of voting powerNo vote
  • TCB @THORmaximalist#53 · 0.47% of voting powerNo vote
  • Monster Node#54 · 0.46% of voting powerNo vote
  • AutoStake 🛡️ Slash Protected#55 · 0.42% of voting powerNo vote
  • Nodeplus#56 · 0.41% of voting powerNo vote
  • FreshSTAKING#57 · 0.38% of voting powerNo vote
  • stakingcabin#58 · 0.35% of voting powerNo vote
  • Moon Platoon#59 · 0.34% of voting powerYes
  • moonshot#60 · 0.34% of voting powerNo vote
  • MissionControl#61 · 0.32% of voting powerNo vote
  • 🙏 uGaenn ⛅#62 · 0.30% of voting powerNo vote
  • Interstake One#63 · 0.28% of voting powerNo vote
  • KK Validator#64 · 0.25% of voting powerNo vote
  • AuraStake#65 · 0.22% of voting powerNo vote
  • Wave#66 · 0.22% of voting powerNo vote
  • Stakeflow#67 · 0.22% of voting powerNo vote
  • Staker Space#68 · 0.22% of voting powerNo vote
  • SafePoint#69 · 0.22% of voting powerNo vote
  • StakeSabai#70 · 0.21% of voting powerNo vote
  • Enigma#71 · 0.21% of voting powerNo vote
  • 8moon#72 · 0.21% of voting powerNo vote
  • OneStar#73 · 0.21% of voting powerNo vote
  • Luna Station 88#74 · 0.20% of voting powerNo vote
  • Inotel#75 · 0.20% of voting powerNo vote
  • NITAWA#76 · 0.20% of voting powerNo vote
  • Sapient Nodes#77 · 0.19% of voting powerNo vote
  • BIG Labs#78 · 0.18% of voting powerNo vote
  • RuneTerra#79 · 0.18% of voting powerNo vote
  • Encapsulate#80 · 0.18% of voting powerNo vote
  • The Bear Validator#81 · 0.18% of voting powerYes
  • Defi Suffrage#82 · 0.17% of voting powerNo vote
  • Lunatic Validator#83 · 0.16% of voting powerNo vote
  • Noderunners#84 · 0.16% of voting powerNo vote
  • Long Live Luna#85 · 0.14% of voting powerNo vote
  • Crypto Plant#86 · 0.13% of voting powerNo vote
  • Bit Cat🐱#87 · 0.13% of voting powerYes
  • DEEPSTATE#88 · 0.07% of voting powerNo vote
  • Noddex#89 · 0.06% of voting powerYes
  • 0%(100% cashback)#90 · 0.01% of voting powerNo vote
  • NODESYNC#91 · 0.01% of voting powerYes
  • Basement 🗲 Nodes#92 · 0.01% of voting powerYes
  • NodesHub#93 · 0.01% of voting powerNo vote
  • Cosmos Spaces#94 · 0.00% of voting powerAbstain
  • LuckyStar#95 · 0.00% of voting powerNo vote
  • VALIDATORSG#96 · 0.00% of voting powerNo vote
  • hhhhhhhhhhhhhhh#97 · 0.00% of voting powerNo vote
  • BoyGau#98 · 0.00% of voting powerNo vote
  • Shazoes#99 · 0.00% of voting powerNo vote
  • navs#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.

# Proposal 2 — Community governance and independent Foundation accountability In this proposal, **PD** means the Phoenix Foundation and its relevant PD Stewardship officeholders. This proposal can operate with the existing directors if Proposal 1 fails. It removes no named director and grants no 2-of-3 permission. ## Decision requested Approve the exact prospective bylaw changes in Appendix A, lawful alignment of the Foundation's governing instruments, a neutral financial and authority review, and consistent conflict controls for all directors. The purpose is accountable community direction over Foundation affairs while preserving the legal responsibilities, private rights and execution safeguards that cannot lawfully be overridden. A binding decision requires implementation within the Foundation's lawful authority. It does not require directors to carry out an unlawful act or breach a non-waivable duty. Directors must assess a specific legal or execution obstacle case by case under Article 1.11.5, disclose the affected act and reasons, obtain independent assessment through the approved route, and pursue a lawful remedy while continuing unaffected work. This preserves necessary judgment without creating a general discretion to disregard a passed decision because the Board disagrees with its policy. The community decision and legal adoption are distinct events. The proposed final-authority rule does not supply the authority to adopt itself. Until adoption is completed, existing documents and legal requirements remain controlling. The proposed ordinary-governance rule neither declares an emergency nor revives rejected emergency-supervisor proposals. ## 1. Post-vote directions to PD and lawful adoption The "Passage Date" is the date this proposal is recorded as finally passed on chain. From that date, PD is directed to start implementation work within its existing lawful authority and publish progress weekly. Within 21 calendar days of passage, publish an implementation dossier covering the governing instruments, adoption and enforcement route, review arrangements, contract schedule, funding and completion dates specified in Sections 1–3. The Board is responsible for coordinating the response with relevant records custodians and publishing the responsible implementers. This community reporting deadline starts at passage and does not wait for bylaw adoption, counsel or a preferred set of records. If an item is unavailable, identify its custodian, the request made, the exact gap, next action, responsible person and dated completion plan. Missing material is not deemed supplied. Within seven calendar days of passage, PD must publicly acknowledge the passed decision, name the responsible implementers and confirm that it will comply with the mandate through the applicable lawful procedures and provide the required documents and implementation response within 21 calendar days of passage. The acknowledgement records the community decision; it is not a second approval or an opportunity to reopen its merits. Late or withheld acknowledgement does not postpone or restart the 21-day deadline. A specific legal or technical obstacle must be identified and handled under the reporting and referral procedure below, with unaffected work continuing. Publish the effective Charter, later amendments and relevant participation/authority agreements, or an authorized explanation of a publication restriction with the operative provisions made available for independent verification. Identify the precise provisions requiring amendment, exact replacement text, competent approvers, current signing thresholds, vetoes, required consents and filing/notice requirements. Seek independent Cayman advice on compatibility with applicable duties and the existing dispute process. An unproduced instrument must be identified, requested and reported under the implementation process. Seek an independent adoption/enforcement coordinator, counsel and alternate, and publish their proposed scope, acceptance, independence disclosures and quotations. Identify persons with legal standing, records-access arrangements and the legal funding route. Consider the standing Supervisor, secretary or other competent office according to actual powers; community designation alone does not confer them. Identify the route if incumbents refuse necessary signatures, including applicable Article 7.2 notice/arbitration steps and any competent court remedy. No judicial outcome or substitute signing power is assumed. PD may obtain records, request quotations and perform preparatory work within existing authority. Paid engagements may proceed only within a specific existing valid budget and approval route that covers them, with the required disinterested approvals. This proposal appropriates no unspecified amount and authorizes no unfunded commitment. Where further funding or appointment approval is needed, PD must publish the proposed provider, scope, amount or cap, duration, funding source and approval route within the same 21-day period and promptly put the specific request to the competent approver, including Terra Governance where required. Missing funding does not suspend records disclosure, available preparatory work or weekly reporting. The 21-day dossier must also identify the lawful contingency for too few disinterested signers, refusal to execute, or resignations or disqualifications leaving fewer than three directors. State the existing authority, authorized actors and necessary approvals. If no such route is available, disclose the precise missing authority and promptly seek the specific further approval; do not invent a lower quorum or suspend an existing duty to resign. The dossier is an implementation record produced after passage, not an undisclosed document incorporated into this vote. It may identify factual details and conforming execution steps within the approved policy. It may not change the allocation of power, expenditure authority, review scope, thresholds, safeguards or deadlines. Publish its dated versions and exact instruments before use. A material departure or additional authorization requires a fresh express governance decision and applicable legal approvals. Authority to prepare implementing documents does not authorize a different constitutional settlement. Continue implementation steps that do not depend on a further approval. PD must promptly pursue valid adoption of the exact Appendix A amendments through the existing instruments. The new bylaw duties take legal effect only upon valid adoption of the instruments that make them operative (the "Adoption Date"). The adopted instruments must expressly give the resolution obligations and Appendix A their intended legal effect and identify the persons bound. The Adoption Date is the objectively evidenced completion of the last condition required for those instruments to take effect, subject to independent verification and any competent authority's jurisdiction. Publish the evidence and exact date promptly; delayed publication does not change the event or restart a clock. Until adoption, the post-passage directions are the community's mandate to PD to act through its existing powers. Amendments and contracts take legal effect through their applicable adoption and execution procedures. The independent review and funding must use valid engagement instruments and cannot use the proposed new powers to authorize themselves. The Passage Date reporting mandate remains applicable throughout. An incomplete reviewer appointment or funding process does not postpone adoption of otherwise valid amendments or other unaffected work. Identify a genuine dependency on the affected act specifically. From passage, PD is also directed to follow the reporting, assessment and referral procedure in Appendix A Articles 1.11.5 and 1.11.7 through existing lawful authority. Pending an independent appointment, the Board must publish requests for assessment and notify the standing Supervisor and secretary within their existing remits. At a 21-day assessment deadline, publish the independent assessment or provisional assessment if available; otherwise publish the missing appointment or funding, requests and quotations, proposed lawful next step and dated completion plan. A Board status report is not an independent assessment and does not discharge the open obligation. Withholding a notice, referral or records does not postpone the deadline. ## 2. Independent financial and authority review Within 21 calendar days of passage, PD must seek and publish independent reviewer candidates or a proposed firm/team, qualifications, independence disclosures, written availability or acceptance, proposed engagement terms, quotations, cost cap, funding source and lawful appointing/payment route. Directors and funded projects under examination may supply records and request quotations but may not decide the reviewer's substantive selection, findings, publication, dismissal or fee releases. Use an existing competent, disinterested appointing authority where available. Otherwise put the reviewer and bounded engagement to Terra Governance for express selection and obtain any required legal approvals. Any legally unavoidable formal execution by incumbents must be distinguished from those discretionary powers. Publish any absence of a lawful independent arrangement and the proposed remedy; do not invent an office with no authority. Pursue appointment promptly under existing lawful authority; adoption of the new bylaws is not a reason to delay an otherwise authorized engagement. The target is appointment no later than seven calendar days after the Adoption Date. If a specific funding or appointment approval remains outstanding, publish it and pursue the Section 1 approval route; do not incur an unauthorized commitment or silently reset the target. The engagement must protect independent access to records and direct publication of authorized findings; neither favorable findings nor consent from subjects may condition payment or publication. Removal requires documented cause, an independent determination and an accepted replacement under the same approved process, with preservation of work and funds. Publish conflicts, decisions and reasons. The reviewer receives no power to sign Treasury transactions, seize assets, remove directors or exercise Emergency Supervisor powers. The review covers Foundation-controlled funds and authority and relevant predecessor TLA commitments from the published TLA launch commitment dated 12 August 2024 through the Passage Date. Include earlier agreements only where necessary to establish opening balances, continuing obligations or authority relevant to that period, and subsequent transactions only to verify implementation or resolution of an in-scope item. PD must publish the corresponding block/date boundaries and entity/contract inventory within the 21-day implementation response; those factual particulars may not narrow the approved scope. Follow assets and counterparties only to the extent necessary to reconcile that scope. Do not imply an unlimited examination of unrelated private businesses. Preserve relevant records from passage, including off-chain agreements and acceptance records; publish a record-request index and report access denials. The approved access route must cover private documents lawfully, without publishing identity documents, keys or privileged advice. Reconcile approved funding, actual transfers and ultimate recipients where verifiable, paid versus conditional amounts, milestone acceptance, fees and commissions, Treasury investments, liquidity positions, lending collateral, and identified claims and liabilities. Review privileged contract operations against the authority, disclosures and approvals applicable when they occurred. Count each economic transfer once and show internal transfers, refunds, overlapping grants and investment positions separately. Publish the complete in-scope transaction/authority population and explain which items receive detailed testing, the selection method, materiality, excluded records and confidence limits. Distinguish the reviewer's own testing from earlier published analyses. Sampled testing must not be represented as an independent audit of every transaction. Apply the same questions and evidence standards to decisions involving every director and funded team in scope, including decisions critical of or supporting any director. A recorded payment is not proof of personal profit or non-delivery. Approval for continued service, approval of a grant, milestone acceptance, payment execution and actual receipt are distinct events. Consider contemporaneous explanations and test delivery claims; subsequent website captures alone do not establish that work was not performed. Publish preliminary findings within 30 calendar days and a final report within 60 calendar days of the Adoption Date, not appointment or receipt of a preferred set of records. Before adverse findings are finalized, give affected parties the relevant evidence and at least seven calendar days to respond; a fair opportunity may require reporting an item as unresolved at day 60. The day-60 report must identify established facts, disputed matters, unavailable evidence and further work rather than manufacture certainty or silently extend scope. If appointment, funding or access prevents an independent report at either deadline, PD must publish the exact outstanding item, requests and approvals sought, work completed, responsible person and dated remedy. Such a status report is not an independent review or satisfaction of the reporting obligation. The item remains open, with weekly progress reporting and any further timetable or funding approval made expressly. Any additional funded phase requires specific approval with a cap and deadline; findings may be corrected publicly with a dated explanation. For each discrepancy, publish the response, analysis, recommended corrective act and the authorized decision on whether to pursue recovery or enforcement. Qualified counsel assesses legal remedies, limitation periods, standing, costs and contractual rights; the reviewer does not declare automatic clawbacks. Preserve rights and evidence while the competent body decides. Identify who must act, its deadline and any unresolved obstacle. No historical conduct is evaluated as a breach of a new rule that was not in force at the time. ## 3. Conflicts, commitments and public accountability Within seven calendar days of the Adoption Date, every current director must publish ongoing material financial conflicts, dated disclosures previously supplied to both Board and community, the disinterested-director approvals for continued participation under existing §4.6.2 and their conditions. This covers project ownership, paid roles, validator operations, commissions, protocol fees and other material economic relationships relevant to Foundation decisions. Publish missing records as missing, and supply protected material lawfully to the reviewer. Provide a response opportunity before an adverse compliance conclusion. Subsequent disclosure or approval is not proof of historical compliance or retrospective absolution. Apply §4.6.2 according to its actual awareness, ongoing-material-conflict, disclosure and majority-of-disinterested-directors conditions, including its resignation requirement where applicable. Participation approval is distinct from transaction approval. New grants, fee increases, Treasury allocations and payment amendments benefiting a director or related business require the new public declaration, justification and independent approval controls in Appendix A once validly adopted. Beneficiaries may not approve their budgets, milestone acceptance or releases. Preserve enforceable obligations and independent approval of bounded essential-service arrangements; resolve insufficient disinterested signers through the actual lawful contingency, not a reduced numerical minimum. Preserve the original TLA administration-after-one-month and ownership-after-three-month commitments in the [launch document]. They concern specified contract powers, not automatic title to all ERIS infrastructure. This proposal neither waives those commitments nor retrospectively approves departures, and it does not adjudicate contested enforceability. Any variation requires its exact scope and applicable separate approvals. A claim of private ownership alone does not resolve a promised transfer. Within 21 calendar days of passage, PD must publish a contract/control schedule identifying chain/address, code/version, migration administrator, internal owner, controllers, pending transfers, role-granting and upgrade powers, current holder with evidence block/time, direct and indirect control paths, intended successor, original commitment or other transfer basis, required transactions/acceptances, dependencies and verification tests. Identify missing entries under Section 1's reporting rule. Distinguish historical captures and unresolved attribution from verified current state. Verify completed transfers through published transactions and independent post-change checks for any retained direct or indirect privileged route to restore or override the authority without fresh authorization. Credit completed handovers and publish the unfinished scope. The schedule, independent access and review appointment must serve this mandate if Proposal 1 fails; no mutable reference to that proposal supplies or changes the approved scope. The same 21-day schedule must explicitly cover TLA global configuration and the Treasury and v3 contracts used by the Foundation, where applicable. Trace who can change owners, administrators, role grants, fee settings, asset destinations or upgrade permissions, including through shared configuration contracts. Identify retained privileged control and its basis; a transfer of one local role is not evidence that upstream control has also transferred. Inventorying a contract does not establish a right to take ownership of it. For each in-scope deployment, record the matching source repository and commit, deployed code identifier and checksum, build instructions and toolchain, licence, operating documentation and maintenance dependencies. Identify whether the Foundation and an independent replacement operator have the access and rights needed to inspect, reproduce, maintain and, where authorized, upgrade it without continuing dependence on the outgoing provider. Publish materials where rights permit; explain restrictions and provide lawful independent verification of protected material. A missing public repository alone does not establish what rights or access exist. Distinguish existing delivery obligations from any new licence or service that would require negotiation and separate approval. Before reporting software handover or independent operating readiness complete, publish the independent verifier's build and operational checks and any unresolved dependency. This is a separate milestone from director removal and permission-transfer transactions. Within the same 21-day period, publish a costed contingency plan for unavailable cooperation, code, permissions or operating support. Compare feasible continued operation, replacement operators, migration and orderly withdrawal options; identify Treasury and user-fund exposure, dependencies, costs, funding, timescales, approvals and service risks. If an option is not yet costable, identify the missing evidence and a dated plan to obtain it. Explain whether any option would require reconsidering the Alliance or its incentives. Put any proposed material change to Treasury exposure, custody, protocol arrangements or Alliance incentives to Terra Governance with its exact scope and required lawful approvals. This planning direction authorizes no automatic withdrawal, shutdown, inc
Details
Submitted
17 Nov 2026
Voting
17 Nov 2026 to 24 Nov 2026
Messages
0
Tallied by
the gov module, at the end of voting
Individual votes
available
Voting power now
309M LUNA