We need a way to schedule a reducer that will be called with the identity of the caller of the current reducer

Open cloutiertyler opened this issue 1 year ago • 3 comments

Tyler notes: BitCraft has worked around this for now.

Jun 11 '24 14:06 cloutiertyler

@kim Is going to write a small proposal based on @gefjon's constraints

Jul 26 '24 17:07 cloutiertyler

We've decided this is not an API break because ctx.sender being the module's identity is correct. So any change to this would be in addition. Something something ethereum tx_origin

Jan 13 '25 21:01 cloutiertyler

It looks like we just have a proposal, not an implementation PR. I think it would make sense to review the proposal soon, but not necessarily to implement ASAP unless it becomes a blocker for something.

Apr 21 '25 18:04 bfops