Skip to content

EIP-3074 Implementation - #38

Draft
adietrichs wants to merge 2 commits into
masterfrom
eip-3074
Draft

EIP-3074 Implementation#38
adietrichs wants to merge 2 commits into
masterfrom
eip-3074

Conversation

@adietrichs

@adietrichs adietrichs commented Mar 8, 2021

Copy link
Copy Markdown

Draft PR for an EIP-3074 implementation. WIP.

Comment thread core/vm/eips.go
@lightclient
lightclient force-pushed the eip-3074 branch 2 times, most recently from 7a357f3 to 49c6963 Compare August 14, 2021 20:00
Co-authored-by: lightclient@protonmail.com <lightclient@protonmail.com>
Co-authored-by: Ansgar Dietrichs <adietrichs@gmail.com>
Co-authored-by: Sam Wilson <sam.wilson@mesh.xyz>
@cyrusadkisson

Copy link
Copy Markdown

Hi. I'm an app/solidity dev but have an interest in 3074 implementations due to a technical quirk of a contract I deployed in 2015.

I'm keen to see the following in 3074 evm client implementations:
https://ethereum-magicians.org/t/eip-3074-auth-and-authcall-opcodes/4880/103

TL;DR - I think it makes the most sense, in an AUTHCALL, for tx.origin to be set to the address of the account being remote-controlled, not the account initializing the transaction (i.e. paying the gas) as it is, in spirit, the remote-controlled address performing the action.

I'm way out of my depth with your code, so a question: how does your implementation handle tx.origin?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants