-
Notifications
You must be signed in to change notification settings - Fork 52
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
Conversation
- `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. |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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.
There was a problem hiding this 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. |
There was a problem hiding this comment.
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
e80b6a4
to
4ac9433
Compare
4ac9433
to
681103d
Compare
No description provided.