Users will now have an option to enable Native Token Voting alongside ERC20 voting. This update consolidates the options under ERC20 or Native Token Voting and refines the voting setup process for contests.
Updates to Existing Functionality:
Option 1 Card Copy: Update to display ERC20 or Native Token Voting (e.g., 1inch or ETH).
Form Changes:
Retain Chain Selection, defaulting to Base. The chain field should remain inactive for now.
Token Selector:
Update to a dropdown with “search” functionality.
Dropdown should include default options like ETH and a subset of popular tokens.
Users should still be able to add custom token addresses, which will render as-is in the selector.
Remove the charge per vote option entirely.
Add a new option for upvote weight to allow users to configure the weight for each vote.
Project Owner
No response
Bucket ID
No response
User Stories / Acceptance Criteria
As an admin, I should be able to set up voting using native tokens or ERC20 tokens on a contest topic.
As an admin, I should be able to configure the token from a dropdown or by entering a custom token address.
As an admin, I should only be able to configure the upvote weight for voting, without options for a charge per vote.
As a user, I should see ERC20 or Native Token Voting clearly labeled and can use default or custom tokens for voting.
Description
Users will now have an option to enable Native Token Voting alongside ERC20 voting. This update consolidates the options under ERC20 or Native Token Voting and refines the voting setup process for contests.
Updates to Existing Functionality:
Form Changes:
Project Owner
No response
Bucket ID
No response
User Stories / Acceptance Criteria
Design Devlink
none
Design Screenshot
none
Additional Context
No response