-
Notifications
You must be signed in to change notification settings - Fork 54
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
feat: make MAX_DECIMALS public #1063
feat: make MAX_DECIMALS public #1063
Conversation
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.
Looks good to me! Left a minor nit. I'm not sure we need the max supply constant to be public but it probably does not hurt to expose anyway.
/// The maximum value for the `max_supply` field. | ||
pub const MAX_MAX_SUPPLY: u64 = (1 << 63) - 1; | ||
|
||
/// The maximum number of decimals supported by the component. |
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.
Is this enforced at the protocol-level? Because if so we could write something like this (same for above):
/// The maximum number of decimals supported by the component. | |
/// The maximum number of decimals supported by faucets in the protocol. |
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.
MAX_DECIMALS
is not enforced at the protocol level.
I'm not really happy with the result here. Maybe having these constants in the |
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.
Looks good! Thank you!
8488e8a
to
1c4b4c5
Compare
We need to use this values in the miden-client repo to avoid repetition. 0xPolygonMiden/miden-client#476