Signal voting · opens with the token
Governance
Holders of the Pawcket token vote on the levers that shape the protocol. The operator commits to honor passing votes within an explicit scope. Voting opens once the token is live on Pons; the rules below are fixed now so nobody is surprised later.
0proposals
0active
1 = 1token, vote
14 daysto implement a passing vote
Tier A · what holders can vote on
Six explicit categories
- The fee split between holders, lenders, referrers and the reserve
- Tier constants: LTV, term and fee per tier, within the safety bounds of the contract
- The holder distribution window and the dust threshold
- The screener listing bar (liquidity, volume, market cap, holders, age, drawdown)
- Per token caps and the keeper bounty
- Use of the protocol reserve
Tier B · operator discretion
Out of scope
- Emergency pause and unpausing of borrows
- Delisting a token that fails a safety gate
- Contract upgrades and security fixes
- Slippage caps and oracle tolerances
- Anything that would let a vote move user collateral
How it works
Proposal lifecycle.
Draft
Anyone holding the token posts a proposal with the exact parameter change and its rationale.
Vote
Seven days, one token one vote. Tokens locked as loan collateral count for their borrower. Quorum 5% of circulating supply.
Execute
A passing Tier A vote is implemented by the operator within 14 days, forward only, and journaled on the stats page.
Onchain later
Once volume justifies the audit, tier constants move behind a timelocked governor so votes execute without the operator.
01When does voting open?
The first proposal opens with the launch of the Pawcket token. Until then every parameter is set by the operator and listed in the docs.
02Is a vote binding?
Tier A votes are a commitment the operator publishes in advance. Tier B stays with the operator because a vote should never be able to endanger user funds.
03Where are the results?
On this page and in the changelog, with the transaction that applied the change.