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

MD-30: Movement Name Service #30

Open
wants to merge 5 commits into
base: main
Choose a base branch
from
Open

MD-30: Movement Name Service #30

wants to merge 5 commits into from

Conversation

0xPrimata
Copy link


### D2: Bonding Curve for Key Minting and Burning

**User Journey**: Users or services can mint or burn access keys based on a bonding curve.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe suggest some example bonding curves that have been used with Name Services. Are there any particular concerns we should have around the curve? Are there DOS vectors via economic attacks?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From the get-go it's important to figure out what the price should be. This depends on what we expect regarding the token price, but the friend.tech bonding curve math is pretty good.


### D3: Community-Driven Revenue Models

**User Journey**: The community can implement their own revenue models via Rooms and Keys. Movement drives the first implementation with Ductus, a backend serving the name service and rooms, and Domus, the frontend that allows minting, trading, viewing of names and keys, and using chat rooms.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See note on moving Domus and Ductus up with other terms.


**Guidance and suggestions**:

- Name and Room ownership should be tied to flexible access key resources, allowing for extensibility through third-party integrations and custom services.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Define Name and Room here.

### D5: Each Movement Name should grant access to its own Domain for .move TLD

**User Journey**: Users acquire a `.move` domain. This allows the user to host an application running on http/https.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

MNS Manager APP will probably be a correlated of this.


### Protocol Units

- **NameRegistry**: Manages the registration and ownership of Names on the Movement blockchain, similar to the Aptos Name Service.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This starts to get more towards the actual proposal or recommendations herein. I would move this up to the top under a Terms section.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can also put all of this down in the appendix.


The protocol should utilize a bonding curve model for minting and burning access keys, with funds flowing through the following structure:

```move
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can Domus and Ductus be represented here?

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

Successfully merging this pull request may close these issues.

2 participants