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

make nut06 fields optional #157

Merged
merged 1 commit into from
Sep 2, 2024
Merged

Conversation

thesimplekid
Copy link
Collaborator

No description provided.

- `modt` is the message of the day that the wallet must display to the user. It should only be used to display important announcements to users, such as scheduled maintenances.
- `nuts` indicates each NUT specification that the mint supports and its settings. The settings are defined in each NUT separately.
- (optional) `name` is the name of the mint and should be recognizable.
- (optional) `pubkey` is the hex pubkey of the mint.
Copy link
Collaborator

@prusnak prusnak Aug 31, 2024

Choose a reason for hiding this comment

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

isn't at least the pubkey mandatory?

Copy link
Contributor

Choose a reason for hiding this comment

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

Nope, this pubkey isn't used for anything productive yet. The relevant ecash pubkeys are found in /v1/keys

06.md Outdated
- `contact` is an array of contact objects to reach the mint operator. A contact object consists of two fields. The `method` field denotes the contact method (like "email"), the `info` field denotes the identifier (like "[email protected]").
- `modt` is the message of the day that the wallet must display to the user. It should only be used to display important announcements to users, such as scheduled maintenances.
- `nuts` indicates each NUT specification that the mint supports and its settings. The settings are defined in each NUT separately.
- (optional) `name` is the name of the mint and should be recognizable.
Copy link
Collaborator

Choose a reason for hiding this comment

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

maybe we should make the name mandatory too?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I think at the spec level we should leave it optional so its not relied on for serialization but implementation should strongly encourage setting one.

Copy link
Contributor

@callebtc callebtc left a comment

Choose a reason for hiding this comment

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

LGTM

Good strategy to make everything optional now and later decide what should be mandatory.

- `modt` is the message of the day that the wallet must display to the user. It should only be used to display important announcements to users, such as scheduled maintenances.
- `nuts` indicates each NUT specification that the mint supports and its settings. The settings are defined in each NUT separately.
- (optional) `name` is the name of the mint and should be recognizable.
- (optional) `pubkey` is the hex pubkey of the mint.
Copy link
Contributor

Choose a reason for hiding this comment

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

Nope, this pubkey isn't used for anything productive yet. The relevant ecash pubkeys are found in /v1/keys

@callebtc callebtc merged commit b933ead into cashubtc:main Sep 2, 2024
1 check passed
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.

3 participants