-
Notifications
You must be signed in to change notification settings - Fork 1k
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
fix trusts conflicts #2892
fix trusts conflicts #2892
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.
Thanks for an attempt though, this should be fixed one way or another before 3.6.
should we keep the logic of "of any of the permission is wildcard, then the trust is wildcard" |
Signed-off-by: Anna Shaleva <shaleva.ann@nspcc.ru>
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.
Let's add the Jim8y#1 test, please.
LGTM.
Add unit test to check manifest Trusts serialization to stack item
@superboyiii Good to review and merge. |
Wait for @superboyiii test |
I'm resyncing full data on testnet with this implemented, result will come out soon. |
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.
Tested OK on my privatenet
If manifest trusts presented as Null stackitem, then they should be treated as wildcard, not as restricted. It's not the same problem as described and fixed in neo-project/neo#2901 and neo-project/neo#2892, although these two PRs are related. Signed-off-by: Anna Shaleva <shaleva.ann@nspcc.ru>
Fix #2890