Skip to content

HIP 149: Council vote notice rule and Nova voting position#1212

Open
madninja wants to merge 1 commit into
mainfrom
council
Open

HIP 149: Council vote notice rule and Nova voting position#1212
madninja wants to merge 1 commit into
mainfrom
council

Conversation

@madninja

Copy link
Copy Markdown
Member

Decision 4 additions from the advisory council review.

5-day notice rule. Council votes require 5 days' written notice to all seven seats, waivable only by unanimous consent. The quorum rules mandate community-seat minimums but are silent on Nova seats, so as written, community seats alone could convene and vote. A Nova-presence mandate was considered and rejected: it would let either bloc block a vote by absence, contradicting the stated property that Nova's 2 seats alone cannot trigger or block. Notice guarantees each seat the opportunity to participate without making attendance a veto.

Nova voting position. Nova votes its veHNT like any other holder, including on votes arising from Council escalation; all votes are public on-chain. Supplement HNT is the exception: Nova does not lock or delegate it for voting while it is under Nova's control. The vault address is fixed at the program upgrade, so outflows into lockup positions are publicly traceable.

Decision 4 additions: Council votes require 5 days' written notice to
all seven seats, waivable only by unanimous consent, with quorum
independent of any particular seat attending. New Nova voting position
paragraph: Nova votes its veHNT like any other holder, and does not
lock or delegate supplement HNT while it is under Nova's control.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@jaym2518

Copy link
Copy Markdown
Contributor

5 days seems excessive. 3 days would be more than sufficient.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants