Validators that do not obey gasPrice ordering rules

[Classical1956]

This validator does not obey the gasprice collation!

Here is one of the blocks:
https://bscscan.com/txs?block=22895318

txs:
https://bscscan.com/tx/0x1196db2f974098e9ca071b205185fcf5e37e4164dcde971264075b8bd525e092 (gasPrice: 5 Gwei index: 211)

https://bscscan.com/tx/0x9b20d03ba56011c27c837fb5e8fe14367f9f02172e95a2170ea4cdbd0f3560c5 (gasPrice: 5.453165044 Gwei index: 212)

This behavior is due to its own benefit, since it can be clearly seen that it is front-running on the same token to other swaps, ignoring the gas.

0x61Dd481A114A2E761c554B641742C973867899D3 must be jailed for it's malicious behavior

[0xdims]

Yes, almost all blocks validated by that validator don't rate gasprice. I think the validator is doing a fraudulent way to profit from some transactions, should be jailed

[0xLyon]

@Classical1956 Thanks for providing the information. Currently it seems that some validators are using customised code to adjust the order in which they process pending transactions. As of yet, this behaviour on its own does not seem malicious but we will continue to monitor.

[0xdims]

As of yet, this behaviour on its own does not seem malicious but we will continue to monitor.

Yes it's harmless, but isn't that kind of thing unfair? should be, Anyone paying higher gas prices should be processed first.

[Classical1956]

Nodes are reluctant to let tx with higher gasPrice be packaged first, so why not discard this tx?

With this manipulation of tx orders, I have reason to suspect that the node is profiting illegally.

it should be jailed

[48ClubIan]

Personally I don't think it's the right thing to disrespect gasPrice ordering.
But it doesn't justify a centralized punishment as jailing (it's also not possible).
Immoral yes, illegal might not.

[0xdims]

@48ClubIan That's right, validators have to respect gasprice, disadvantage for those who pay more expensive gasprice but the order is below the cheaper gasprice.

[kmalloc]

@Classical1956 Thanks for providing the information. Currently it seems that some validators are using customised code to adjust the order in which they process pending transactions. As of yet, this behaviour on its own does not seem malicious but we will continue to monitor.

it is malicious, txs ordering matters and someone can profit a lot from this.

[0xdims]

@0xLyon if such a thing is allowed, in the future all validators will follow it to take profit. and there will be no more healthy competition

[iamman2021]

@mas1337 Can't agree any more

[wardhunt]

someone developed or use this pr：#1152 , which caused problems

[TheUnknownDeveloper]

https://bscscan.com/txs?block=23102230

Position 11: 5 Gwei
https://bscscan.com/tx/0x21ca34e160fd514e7393c7b3a7444f41f42d98e13e24ca3da5ae2e47a6943200

Position 22: 10 Gwei
https://bscscan.com/tx/0x2f82b56f5b7166723f8f117af33d6f47cfd8c5a3c4f9895ad096b6c8cb264843

Validator:
0x61dd481a114a2e761c554b641742c973867899d3

Is this a new "feature"? How are the transaction sorted?

[0xLyon]

This is not a new feature. This is nodes performing customized sorting for picking up transactions. We are aware of this and are checking with the respective developers to get a solution soon.

[TheUnknownDeveloper]

@0xLyon thanks for the quick response!

[teebaumcrypto]

I'm also interested in the updates.
Just had a tx > 30gwei sorted nearly at the end of the block, rather than beeing first.

Same Validator:
0x61dd481a114a2e761c554b641742c973867899d3

Also based on research on p2p traffic, I see more validators not playing fairly (providing private endpoints to specific bots).

[DeepBorys]

The validator: 0xD1d6bF74282782B0b3eb1413c901D6eCF02e8e28 is working together with a MEV bot https://bscscan.com/address/0x319c6e576d7894cc99228ae361a84f19e5fcac82 and is doing sandwich attacks.