static mixin (protocol level) #30

Merged
wowario merged 1 commits from mixin into release-v0.2.1.0 6 years ago
wowario commented 6 years ago (Migrated from github.com)
Owner

After hard fork version 9, all transactions must have the same ring size.

After hard fork version 9, all transactions must have the same ring size.
stoffu (Migrated from github.com) reviewed 6 years ago
stoffu (Migrated from github.com) commented 6 years ago
Owner

This seems to overwrite the variable mixin as calculated above, making the if section below a no-op. Or am I missing something?

This seems to overwrite the variable `mixin` as calculated above, making the `if` section below a no-op. Or am I missing something?
wowario (Migrated from github.com) reviewed 6 years ago
wowario (Migrated from github.com) commented 6 years ago
Owner

yes, it overwrites the variable mixin (which is set to max) to make sure mixin and min_mixin always equal DEFAULT_MIXIN after v9. I could separate the section to make it cleaner.

yes, it overwrites the variable `mixin` (which is set to max) to make sure `mixin` and `min_mixin` always equal `DEFAULT_MIXIN` after v9. I could separate the section to make it cleaner.
stoffu (Migrated from github.com) reviewed 6 years ago
stoffu (Migrated from github.com) commented 6 years ago
Owner

I don't get it - isn't the idea to reject txes whose mixins are different from the default mixin? Currently it doesn't do so.

I don't get it - isn't the idea to reject txes whose mixins are different from the default mixin? Currently it doesn't do so.
wowario (Migrated from github.com) reviewed 6 years ago
wowario (Migrated from github.com) commented 6 years ago
Owner

Currently, users can pick any mixin above the min_mixin. After v9, users can only pick the default mixin.

Currently, users can pick any mixin above the `min_mixin`. After v9, users can only pick the default mixin.
wowario (Migrated from github.com) reviewed 6 years ago
wowario (Migrated from github.com) commented 6 years ago
Owner

would this make more sense?: 02ca1bc7b8

would this make more sense?: https://github.com/wowario/wownero/commit/02ca1bc7b8b12d9587e3609deba6b354ad15ef7d
stoffu (Migrated from github.com) reviewed 6 years ago
stoffu (Migrated from github.com) commented 6 years ago
Owner

No, it doesn't make sense. This code is for verifying the validity of a given transaction, and the transaction's mixin value is obtained in the above loop for (const auto& txin : tx.vin) {...}. Then the obtained mixin variable is ignored and overwritten by const size_t mixin = DEFAULT_MIXIN;, so this code will accept txes with any mixin. Or am I reading anything wrong?

No, it doesn't make sense. This code is for verifying the validity of a given transaction, and the transaction's mixin value is obtained in the above loop `for (const auto& txin : tx.vin) {...}`. Then the obtained `mixin` variable is ignored and overwritten by `const size_t mixin = DEFAULT_MIXIN;`, so this code will accept txes with any mixin. Or am I reading anything wrong?
wowario (Migrated from github.com) reviewed 6 years ago
wowario (Migrated from github.com) commented 6 years ago
Owner

Ah, okay. I see what you mean. Let me try to express it a different way.

Ah, okay. I see what you mean. Let me try to express it a different way.
The pull request has been merged as 0548011ca5.
Sign in to join this conversation.
No reviewers
No Milestone
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

No dependencies set.

Reference: wownero/wownero#30
Loading…
There is no content yet.