You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current implementation of Assist Credits via FractionToken causes confusion about its purpose and usage. As discussed in issue #336, users don't understand:
How much credit to send
What sending credits means (sharing role responsibility vs expressing thanks)
What happens when initial 10,000 credits are depleted
Proposed Solution
Refactor the FractionToken contract to clearly implement the "Role Share" concept:
Rename "Assist Credit" to "Role Share" in UI and documentation
Maintain the ERC1155 implementation but make it clearer this represents shared ownership of a role
Add ability for role holders to mint additional tokens up to 1,000,000 (to avoid classification as a crypto asset)
Update UI to clearly explain this is for role responsibility sharing, not general thanks
Update relevant frontend components to reflect new terminology
Implementation Notes
Modify FractionToken.sol contract to support additional minting (maximum 1,000,000)
Update useFractionToken.ts to reflect new terminology and limits
Update UI components that reference "assistcredit" to use "roleshare" terminology
Add clear explanations about token purpose in the UI
- Rename TOKEN_SUPPLY to INITIAL_SUPPLY
- Add MAX_SUPPLY parameter (default 1,000,000)
- Update mint function to check against maximum supply
- Update initialize function to accept maxSupply parameter
- Update deployment helper and tests to accommodate changes
Resolves#345
Related to #336
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
Problem
The current implementation of Assist Credits via FractionToken causes confusion about its purpose and usage. As discussed in issue #336, users don't understand:
Proposed Solution
Refactor the FractionToken contract to clearly implement the "Role Share" concept:
Implementation Notes
Related Issues
Part of issue #336
The text was updated successfully, but these errors were encountered: