Timeline for why cant smart contract receive ether like externally owned account without a receive/fallback function?
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 19, 2022 at 6:19 | comment | added | Bobby Sebastian | @matank001 i understand there are certain ways to force ether but was looking for why contracts cant receive ether like EOA. | |
| Oct 19, 2022 at 6:16 | comment | added | Bobby Sebastian | @Ismael thanks i got it. there should be an EIP associated with the change, any idea which one is that? would like go in depth how the check is implemented. | |
| Oct 15, 2022 at 19:21 | comment | added | Ismael♦ | Mostly for security reason. In very old solidity versions contracts could accept ethers without requiring a fallback function that caused some issues for developers that weren't aware of that feature. Solidity developers decided that in order for a contract to accept payments it should enable it explicitly. It still possible to send ether to contracts without a receive function,. | |
| Oct 12, 2022 at 12:35 | review | Close votes | |||
| Oct 15, 2022 at 19:21 | |||||
| Oct 12, 2022 at 12:19 | comment | added | matank001 | Does this answer your question? Can a contract with no payable function have ether? | |
| Oct 12, 2022 at 12:17 | comment | added | matank001 | Read: ethereum.stackexchange.com/questions/63987/… | |
| Oct 12, 2022 at 8:24 | history | edited | Bobby Sebastian | CC BY-SA 4.0 |
added 33 characters in body
|
| Oct 12, 2022 at 8:24 | history | asked | Bobby Sebastian | CC BY-SA 4.0 |