Skip to content

[review] MD-30: Movement Name Service - #30

Open
Primata wants to merge 5 commits into
mainfrom
primata/md-30
Open

[review] MD-30: Movement Name Service#30
Primata wants to merge 5 commits into
mainfrom
primata/md-30

Conversation

@Primata

@Primata Primata commented Oct 9, 2024

Copy link
Copy Markdown
Contributor

Comment thread MD/md-30/README.md

### 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
Copy Markdown
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
Copy Markdown
Contributor 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.

Comment thread MD/md-30/README.md

### 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
Copy Markdown
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.

Comment thread MD/md-30/README.md

**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
Copy Markdown
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.

Comment thread MD/md-30/README.md
### 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
Copy Markdown
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.

Comment thread MD/md-30/README.md

### Protocol Units

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

Copy link
Copy Markdown
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
Copy Markdown
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.

Comment thread MD/md-30/README.md

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

```move

Copy link
Copy Markdown
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?

@apenzk apenzk changed the title MD-30: Movement Name Service [review] MD-30: Movement Name Service Oct 28, 2024
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