New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[FEATURE] Enable issuers to use their own PersonalInfo contract #644

Open

purplesmoke05 opened this issue Jun 12, 2024 · 0 comments

Assignees

Labels

Member

purplesmoke05 commented Jun 12, 2024

Is your feature request related to a problem? Please describe.

To reduce the amount of EVM memory consumed by a single PersonalInfo contract and to increase the tx throughput of the PersonalInfo register(), issuers should not use a shared PersonalInfo contract, but should use their own PersonalInfo instead.
In the current implementation, the PersonalInfo contract registered in the Token contract can be set by the API POST parameter, and the API user can only use the existing deployed PersonalInfo contract.

Describe the solution you'd like

Allow issuers to use their own PersonalInfo contract.
- Deploy a new PersonalInfo contract for each issuer.
- Use the above PersonalInfo contract address when the issuer deploys a newer token contract.

purplesmoke05 added the enhancement label

purplesmoke05 self-assigned this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment