-
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
Remove some settings from policy contract #2300
Changes from all commits
f2036e8
f3361f1
07b145b
5b2bcde
e581dfa
102a4e9
2db418e
59ec71d
f7c1ea8
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -288,8 +288,6 @@ public virtual VerifyResult VerifyStateDependent(ProtocolSettings settings, Data | |
foreach (UInt160 hash in hashes) | ||
if (NativeContract.Policy.IsBlocked(snapshot, hash)) | ||
return VerifyResult.PolicyFail; | ||
if (NativeContract.Policy.GetMaxBlockSystemFee(snapshot) < SystemFee) | ||
erikzhang marked this conversation as resolved.
Show resolved
Hide resolved
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. If this check is removed, how to stop such transactions from getting into Mempool? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We should treat service, storage and CPU fees differently, otherwise the restrictions on fees are meaningless. This can be done later. |
||
return VerifyResult.PolicyFail; | ||
if (!(context?.CheckTransaction(this, snapshot) ?? true)) return VerifyResult.InsufficientFunds; | ||
foreach (TransactionAttribute attribute in Attributes) | ||
if (!attribute.Verify(snapshot, this)) | ||
|
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.
Should we eliminate the use of
ProtocolSettings.Default
here?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.
It should be fixed by #2337