-
Notifications
You must be signed in to change notification settings - Fork 141
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
Would TxId be better if it inherits HashDigest<SHA256>? #79
Comments
I think considering So, I suggest to make some other concrete type for these type like |
Having a distinct type for each |
I call dibs on this issue |
|
@qria You're right. The idea in itself seems invalid. |
I no longer am working on this until there's a new idea for this. |
I'll close this issue until we have a new idea to address this issue. |
Fix casting bug on Address type.
…-notification Fix bug in ring notification condition.
…c-release feat: Apply specific release
Since
TxId
is a SHA-256 digest, the most of things are in common withHashDigest<SHA256>
. WouldTxId
be better to inheritHashDigest<256>
? Or, rather, would it be fine even if we get rid ofTxId
at all and replace them withHashDigest<256>
?The text was updated successfully, but these errors were encountered: