David Braun

```Solidity // Disallow withdraws that exceed current rate limit require(currentPeriodAmount + amount < limit, 'exceeds period limit'); currentPeriodAmount += amount; msg.sender.transfer(amount); ``` [Elsewhere](https://consensys.github.io/smart-contract-best-practices/development-recommendations/general/external-calls/#dont-use-transfer-or-send) the guide recommends against using `transfer`.

Explain difference between `tx.origin` and `msg.sender`.

1

In the [tx.origin](https://consensys.github.io/smart-contract-best-practices/development-recommendations/solidity-specific/tx-origin/) page it would be helpful to include short background information on what `tx.origin` is and how it differs from `msg.sender`.

[Event Monitoring suggests using `transfer()`](https://consensys.github.io/smart-contract-best-practices/development-recommendations/solidity-specific/event-monitoring/) but [External Calls warns against it](https://consensys.github.io/smart-contract-best-practices/development-recommendations/general/external-calls/#dont-use-transfer-or-send). > Patterns like `require(msg.sender.send(1 ether))` can also be simplified to using `transfer()`, as in `msg.sender.transfer(1 ether)`. > Don't use...

Delete "Insecure Arithmetic" Page?

1

Now that "Solidity automatically reverts on integer overflow and underflow, as of version 0.8.0." shall we delete the [Insecure Arithmetic](https://consensys.github.io/smart-contract-best-practices/attacks/insecure-arithmetic/) page?