You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
^ Looking at this code it appears to me that transactions with the higher number of bytes per fee paid (i.e. lower fee per byte) would be sorted before (and added to the template before) those with lower bytes per fee.
I see several blocks mined which appear to confirm this behavior:
https://github.com/monero-project/monero/blob/master/src/cryptonote_core/tx_pool.cpp#L256
https://github.com/monero-project/monero/blob/master/src/cryptonote_core/tx_pool.h#L65
^ Looking at this code it appears to me that transactions with the higher number of bytes per fee paid (i.e. lower fee per byte) would be sorted before (and added to the template before) those with lower bytes per fee.
I see several blocks mined which appear to confirm this behavior:
https://xmrchain.net/block/1231370
https://xmrchain.net/block/1231373
Suggested fix: either invert the current bytes/fee calculation or reverse the sort order for the std::set
The text was updated successfully, but these errors were encountered: