While reviewing the previous parts of this issue (manager registration) I ran into an issue in the exist registration functions 'name-claim-fast' & 'name-preorder.' The first (stx-burn? ...) function for the namespace manager is not correct / not needed.
The point of exposing a namespace manager interface is to allow for customizations such as:
SIP10 payments
Different pricing structures
Free mints
Currently, both of these functions explicitly burn-stx. This is not correct. The manager path for both of these functions should be free since it's assumed that the manager namespace is calling into this with the customized logic in their contract.
User Stories
User, through a managed namespace, can fast-claim a name for free
User, through a managed namespace, can name-preorder for free
Action Items
[x] Create three new functions 'mng-name-preorder', 'mng-name-register,' & mng-name-claim-fast'
[x] Refactor the existing registration functions to only account for native paths, just check that namespace being called into is NOT a managed namespace
Description
While reviewing the previous parts of this issue (manager registration) I ran into an issue in the exist registration functions 'name-claim-fast' & 'name-preorder.' The first (stx-burn? ...) function for the namespace manager is not correct / not needed.
The point of exposing a namespace manager interface is to allow for customizations such as:
Currently, both of these functions explicitly burn-stx. This is not correct. The manager path for both of these functions should be free since it's assumed that the manager namespace is calling into this with the customized logic in their contract.
User Stories
Action Items
Open Questions