the reentrancy rules is out-of-date

[smartcontract-detect-yzu]

The send() cannot trigger the reentrancy. Meanwhile, the rule do not check the .call.value() can cause the reentrancy vulnerability.

[dbale-altoros]

@smartcontract-detect-yzu

Thanks a lot for posting !
Can you expand a little the issue you posted by putting some examples or giving further information ?
Thanks!

[gcf3711]

@smartcontract-detect-yzu

Thanks a lot for posting ! Can you expand a little the issue you posted by putting some examples or giving further information ? Thanks!

In this [document] (https://ethereum-contract-security-techniques-and-tips.readthedocs.io/en/latest/recommendations/#be-aware-of-the-tradeoffs-between-send-transfer-and-callvalue) published by Consensys, it states that "someAddress.send()and someAddress.transfer() are considered safe against reentrancy".

[dbale-altoros]

@smartcontract-detect-yzu sorry the delay
what this rule is checking is not the use of send or transfer
it is checking that the code does not change state variables after transfer or send

I closing this, but, feel free to open a new issue for further discussion, or even here if it is allowed