# Development Update 4 ~ [20/12/2021]

The following document is a fourth development update for the project **Research Removal of Gas Stipend for `CALL` Opcodes**. The document describes the received input on the gas stipend and logging from the core developers.

## Summary
In the Ethereum R&D Discord, Vitalik mentioned that having an infinite gas stipend will "intuitively break more dapps and break them in a more severe way than zero stipend". This is because if all the remaining gas is forwarded for the computation, the contract's state is modifiable after the transfer of Ether. Therefore, Ether transfers made using the `CALL` opcode will become a trusted operation as contracts will be vulnerable to re-entrancy attacks if they do not follow the [common withdrawal pattern](https://docs.soliditylang.org/en/v0.5.3/common-patterns.html#withdrawal-pattern). The better option is to have zero gas stipend as it will only break logging. In addition, Micah described that having no gas for the transfer will trigger an OOG (out of gas) revert.

It was also mentioned that, in the long term, it would be ideal to remove logs from the protocol entirely. The reason is clients have to perform bloom filter checks for millions of blocks to find the emitted values in the topics. This process requires a long time that can degrade the UX for DAPPs. Instead, DAPPs nowadays use The Graph, a protocol for querying data from blockchains and IPFS, because it is faster for scanning logs. Ever since logs were implemented in the Ethereum protocol, there have been advancements in ways to retrieve on chain data. Before logs can be removed, there needs to be a protocol level standard that covers all cases of ETH transfers, including when `SELFDESTRUCT` is called. This is a potential topic that can be researched to ensure there no breaking changes.

## Next Steps
The upcoming developments updates will focus on how logs can be standardized so that the gas stipend feature is removable.