Timeline for Who is msg.sender in a nested call chain?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 18, 2022 at 9:01 | vote | accept | Paul Razvan Berg | ||
| Jul 23, 2019 at 14:30 | comment | added | Ismael♦ | Contracts are not aware of the call context, they cannot know if they have more than one ancestor in the call chain (they can check tx.origin != msg.sender). You have codecall and delegatecall that change msg.sender but otherwise they do not affect the call context. | |
| Jul 21, 2019 at 17:58 | comment | added | Paul Razvan Berg | @Ismael it's not a duplicate, I specifically mentioned that I'd already checked that question. | |
| Jul 21, 2019 at 5:15 | review | Close votes | |||
| Jul 27, 2019 at 6:53 | |||||
| Jul 21, 2019 at 4:57 | comment | added | Ismael♦ | Possible duplicate of Who is msg.sender when calling a contract from a contract | |
| Jul 19, 2019 at 23:05 | answer | added | Rob Hitchens | timeline score: 3 | |
| Jul 19, 2019 at 23:05 | history | edited | Rob Hitchens |
edited tags
|
|
| S Jul 19, 2019 at 19:58 | answer | added | Paul Razvan Berg | timeline score: 5 | |
| S Jul 19, 2019 at 19:58 | history | asked | Paul Razvan Berg | CC BY-SA 4.0 |