-
Notifications
You must be signed in to change notification settings - Fork 60
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
Issue 1884 - contract ID generation mechanism #2003
Conversation
2c06c85
to
15b009c
Compare
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 there a reason why the contract ID generation needs to be in rusk-abi
? It seems to me that it is only used - and will only ever be used - in rusk
proper.
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'm not convinced by how the contract ID is calcualted. Also, I think some things should be managed in rusk, rather then piecrust (for instance, the nonce check).
3f54ef8
to
57308ad
Compare
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
contract ID generation mechanism
extends current deployment transaction format to support contract nonce
implements issue #1884