Guide to Voting
Last modified:
Guide to Voting
This page is a practical guide for participating in CenturionDEX governance.
For full contract-level details, see Governance Overview.
What You Need
- Governance tokens with voting power
- A wallet connected to the correct chain
- Native token for gas
- Access to a governance interface (or direct contract interaction)
Step 1: Delegate Voting Power
You must delegate before your voting power is counted.
Option A: Self-Delegate
Delegate to your own address if you plan to vote directly.
Option B: Delegate to Another Address
Delegate to a trusted representative if you want them to vote for you.
Delegation does not transfer token ownership. It only assigns voting power.
Step 2: Verify Delegation
Before a proposal goes active, verify that your delegated votes are visible.
You can verify via:
- Governance UI voting-power panel
- Block explorer contract reads
getCurrentVotes(address)on the governance token contract
Step 3: Cast a Vote
When a proposal is active:
- Open the proposal details
- Review payload and rationale
- Vote
FororAgainst - Confirm and sign the transaction
- Wait for confirmation
Votes are weighted by delegated voting power at the proposal snapshot block.
Optional: Vote by Signature
If your integration supports it, governance contracts also expose signature-based vote flows (castVoteBySig) for offline signing patterns.
Common Issues
No Voting Power Showing
- Delegation happened after snapshot
- Wrong wallet/network selected
- Delegation transaction not confirmed yet
Transaction Reverted
- Proposal no longer active
- Insufficient gas
- Stale nonce or replaced transaction
Proposal Visible But Vote Missing
- Transaction still pending
- Vote submitted from a different address than delegated account
Good Practices
- Delegate well before proposal start
- Read full proposal text and target calls
- Verify contract addresses against official sources
- Recheck status near voting deadline