Add Implementation to Tokenizer Module and OwnableERC20 #144
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.
Description
This PR introduces implementations and interfaces for the new
TokenizerModule
andOwnableERC20
contracts, as outlined in #143.New Contracts
IOwnableERC20
: Defines the standard interface for ERC20 templates used in theTokenizerModule
.ITokenizerModule
: Specifies the interface for theTokenizerModule
.OwnableERC20
: A base implementation ofIOwnableERC20
. This contract is integrated with theTokenizerModule
via the Beacon Proxy pattern. When theTokenizerModule
fractionalizes an IP, it deploys a Beacon Proxy instance of theOwnableERC20
template, and ties each instance to a specific IP.TokenizerModule
: Manages the fractionalization of IP assets (IPA). It allows IP owners to select from whitelistedOwnableERC20
templates for their fractionalized tokens and enables developers to whitelist new templates for others to use.Tests
Test cases have been added for all functions in both contracts. All tests pass locally.