For example, firefly.eth currently resolves to 0xce31f0ad68d9565004bbe351a8677eb74c86866d
Without my software knowing or looking up the specific address "0xce31f0ad68d9565004bbe351a8677eb74c86866d" before it creates the transaction (the way almost all wallet software supporting ENS does/will do), can I sign a transaction which sends funds from my externally owned secp256k1 account directly to "whatever firefly.eth resolves to" without knowing that information at the time the transaction is created? I dont want to send it to some type of custom built contract that first resolves firefly.eth and then forwards my funds to "0xce31…" once it obtains it. I want the funds to go directly from my account to "0xce31…" so that if "0xce31" checked the msg.sender it would consider the funds to have come from my account directly.
Is this possible?
Best Answer
The answer is "no". You either need to resolve the address outside the chain (via web3 or whatever), or have an on-chain contract do it for you.
If the hard requirement is that
msg.senderis your address, then you would need to resolve the address via an off-chain solution.