Skip to content
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.

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

Ticker registry: have it store token name as well #30

Closed
pabloruiz55 opened this issue Mar 23, 2018 · 3 comments
Closed

Ticker registry: have it store token name as well #30

pabloruiz55 opened this issue Mar 23, 2018 · 3 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@pabloruiz55
Copy link
Contributor

No description provided.

@pabloruiz55 pabloruiz55 added the bug Something isn't working label Mar 23, 2018
@pabloruiz55 pabloruiz55 added this to the V1 milestone Mar 23, 2018
@pabloruiz55 pabloruiz55 added this to Backlog in Core Features via automation Mar 23, 2018
@satyamakgec
Copy link
Contributor

STR need to get the token name from the user(or with the database). Because string can't be handled as the return variable in another contract. Or we should have to return bytes32 to handle it and convert those bytes32 into the string in the STR contract itself. that also lead to add one more byteToString function into the STR. What is your opinion @pabloruiz55?

@pabloruiz55
Copy link
Contributor Author

Let's solve this on the UI side.
Ticker Registry receives and stores the string token name.
Later on, on the token deployment, we ask again for the token name, populating the field from the ticker registry.
The user can even change the token name that will get saved to the deployed token.

@satyamakgec
Copy link
Contributor

The user can change the token name before the deployment of security token only from the Ticker Registry ?

Core Features automation moved this from Backlog to Done Mar 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
No open projects
Core Features
  
Done
Development

No branches or pull requests

2 participants