-
Notifications
You must be signed in to change notification settings - Fork 4
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
Enhance server capabilities for miniwallet and sms callbacks #6
Conversation
Manual local deploy
|
It's insecure to rely on automatically managed contracts in deployment. We need set up our own proxy, understand the exact code within, and manage our own record and step-by-step calls during the use of proxy and follow-up contract upgrades. There also should not be "User APIs". See comments in #5 I am not following Operator API or Creator API. I need more details to understand the "Creator Functionality". I am not sure whether it is needed. The documented flow in the Wiki envisions all setup performed at the client side. There should not be any (REST) API. The current client and server do not support network switch so I don't think we need to concern testnet at this time |
Can #7 be merged in with this? Alternatively can the mini-wallet functionalities be removed from this PR? |
This PR is to work on functionality documented in #5
TODO
AssetManager.sol
Develop User API's
Add User Functionality to Client
Create Operator API's (transfer and pay)
Create Creator API's (transferRequest and billingRequest) should support multiple requests in one call
Creator Functionality
Additional development tasks
Acceptance Criteria