Skip to content
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 ClaimTransaction for IsLowPriority #510

Merged
merged 1 commit into from
Dec 8, 2018
Merged

Conversation

shargon
Copy link
Member

@shargon shargon commented Dec 7, 2018

Is not necessary because according to neo-project/neo-modules#33 (comment) we can check that for ClaimTransaction is not possible to assign fee.

Is not necessary because according to neo-project/neo-modules#33 (comment) we can check that for `ClaimTransaction` is not possible to assign fee.
@erikzhang erikzhang merged commit 37f2894 into master Dec 8, 2018
@erikzhang erikzhang deleted the shargon-patch-1 branch December 8, 2018 14:04
@@ -49,7 +49,7 @@ public UInt256 Hash

InventoryType IInventory.InventoryType => InventoryType.TX;

public bool IsLowPriority => Type == TransactionType.ClaimTransaction || NetworkFee < Settings.Default.LowPriorityThreshold;
public bool IsLowPriority => NetworkFee < Settings.Default.LowPriorityThreshold;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we change it to this?

public bool IsLowPriority => Type != TransactionType.ClaimTransaction && NetworkFee < Settings.Default.LowPriorityThreshold;

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The problem that I see of not having it in a configuration, is that if it is spam, it is difficult to change. It would be easy to temporarily go to the configuration and disable the ClaimTransaction as a priority.

Copy link
Contributor

@igormcoelho igormcoelho Dec 10, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree Erik, because setting ClaimTransaction as low priority is unfair since it cannot attach fees. These transaction types should be removed anyway, let's keep just one :)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In NEO 3.0, there will be only one type of transaction.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants