feat: Enhance TokenCreation
Contract with Inheritance & Storage Variables
#201
+8
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR expands the
TokenCreation
contract by introducing inheritance from OpenZeppelin’s ERC20 and Ownable contracts, along with storage variables for token metadata and creator tracking. These changes set the foundation for a fully functional and customizable token deployment system.Key Changes
Contract Inheritance
TokenCreation
now inherits fromERC20
andOwnable
, providing standard ERC20 functionality and secure ownership controls.Added Storage Variables
uint8 private _decimals
→ defines token decimal precision.uint256 public maxSupply
→ enforces token supply cap.string private _description
→ stores descriptive metadata for the token.string private _imageUrl
→ allows optional image/logo association for UI integrations.address public creator
→ tracks the original deployer/creator of the token.NatSpec Section Update
Why This Change?
Next Steps
Notes
This update transitions
TokenCreation
from a placeholder contract into a functional ERC20 framework, ready for further feature development like metadata handling, supply constraints, and minting/burning capabilities.