-
Notifications
You must be signed in to change notification settings - Fork 148
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
pink: Use customized ink address as contract id #610
Conversation
a9c61c5
to
e32e89e
Compare
There some unresolved compilation errors:
|
1f598b2
to
58cfa7d
Compare
e32e89e
to
7d92ef0
Compare
Oh, I know this one. There's an upstream bug fix to a security problem. As a part of the fix, default value (0x0) for AccountId was disabled. So here we need to either remove the default derivation or manually assign the zero value to the account field. The later case is suboptimal because we may accidentally trigger the security problem. Side note: if the zero account is used as the public key, anyone can make a zero signature that can bypass some ill crypto implementation |
The other problems are mostly additional generic config items by the pallets. Usually we can follow the upstream usage to give it some config. You can take a look at Substrate bin/runtime and Polkadot's runtime code |
7d92ef0
to
1c844ab
Compare
58cfa7d
to
998d1a9
Compare
1c844ab
to
2e3f0ef
Compare
Waiting for this upstream PR.