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

UI Design: Asset Creation/Management #1062

Open
achamely opened this issue Oct 27, 2014 · 9 comments
Open

UI Design: Asset Creation/Management #1062

achamely opened this issue Oct 27, 2014 · 9 comments

Comments

@achamely
Copy link
Contributor

The new asset creation / management features of Mastercoin need an interface.
Asset creation can probably be rolled into the existing 'create smart property page with minor tweak to tx type' But the management of the property (revoking tokens, adding new tokens) will need new ui design. This issue is to track the design of the new interface which will then need to be implemented.

@oktype
Copy link

oktype commented Oct 27, 2014

You mean 'Asset management', not 'Asset creation' right?
Revoking tokens should be accessible from the token page (same as when stopping a crowd sale)
Adding new tokens should be also accessible from the token page itself (should be near the amount of tokens, need to check it first). we can also make a single interface in addition which will allow all the available edits.

We better make/discuss all the available features we want to give access to and make some sort of specifications list. @achamely

@achamely
Copy link
Contributor Author

@oktype I do mean create and manage. There are currently 2 types of tokens / properties (managed/unmanaged). And while the initial creation of both is almost identical it does still require creating to start. Here is the list of properties and what the creator/owner should be able to do with them. Take a look and let me know if it make sense

Unmanaged Properties:
Start Crowdsale / Stop Crowdsale
Create Fixed number Tokens
Managed properties:
Create Property (0 tokens at start)
Add/issue tokens for Property
Remove/Revoke tokens for Property

@achamely
Copy link
Contributor Author

@oktype We would like to have this designed ready for/by stand-up Tomorrow Oct 29

@oktype
Copy link

oktype commented Oct 28, 2014

For tracking purposes:

  • Once you created a token you can't toggle divisible <> indivisible
  • Token manager can only remove (destroy?) tokens that he owns in the same address
  • There is no difference between remove and revoke

@achamely
Copy link
Contributor Author

@oktype After talking with @marv-engine we are going to push this out and add 1 more day, Oct 30

@oktype
Copy link

oktype commented Oct 28, 2014

Thanks @achamely

@oktype
Copy link

oktype commented Oct 29, 2014

Can we allow the user create initial amount of tokens when creating managed property?
(using the same block to create the property and add tokens, or alternatively sign in advance the add tokens transaction for sending it in the next block)

@oktype
Copy link

oktype commented Oct 29, 2014

@achamely

@achamely
Copy link
Contributor Author

@oktype Unfortunately we can not use the same transaction/block, according to the spec it is a two part process (https://github.com/mastercoin-MSC/spec#new-property-with-managed-number-of-tokens). We might be able to do the advanced signing but there is a certain amount of infrastructure upgrade/change that will need to take place to allow this action to happen. For now (at least for the initial setup) it will most likely need to be a two part process (mostly because we do not know what the currency id for the new property will be until it is accepted in the block chain (think two people creating a managed property around the same time. If we assume the next available property id is our users and it turns out someone else creates a property before their property gets accepted in block chain their presigned token grant becomes invalid.

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

No branches or pull requests

2 participants