# Propagate msg.caller across multiple canisters? (ethereum equivalent of tx.origin)

**URL:** https://forum.dfinity.org/t/propagate-msg-caller-across-multiple-canisters-ethereum-equivalent-of-tx-origin/9177
**Category:** Developers
**Created:** [November 29, 2021, 8:45pm UTC](https://forum.dfinity.org/t/propagate-msg-caller-across-multiple-canisters-ethereum-equivalent-of-tx-origin/9177 "2021-11-29T20:45:57Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![skilesare](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/skilesare/32/5609_2.png) [@skilesare](https://forum.dfinity.org/u/skilesare)
#### Post date: [November 29, 2021, 9:27pm UTC](https://forum.dfinity.org/t/propagate-msg-caller-across-multiple-canisters-ethereum-equivalent-of-tx-origin/9177/2 "2021-11-29T21:27:03Z")

</div>

See a bit of healthy discussion: [Request - Inter Canister Calls - Add Original Caller() - #7 by skilesare](https://forum.dfinity.org/t/request-inter-canister-calls-add-original-caller/6796/7)

I’m still in favor of exposing almost every system variable through the msg interface(origin, block number, coinbase, etc). Having the data available only increases the kinds of systems that we build. The motoko devs generally feel differently and I appreciate their desire to keep the language simple and keep users from shooting themselves in the foot, but still…I like having the data rather than not having it.

---

_[View the full topic](https://forum.dfinity.org/t/propagate-msg-caller-across-multiple-canisters-ethereum-equivalent-of-tx-origin/9177)._