Question for all Ethereum enthusiasts around here:

inkan

npub16xnpfx85k8wzdhctang6860g3u64lds5kac73ddjwlg0lxdg9g3su56z6l

hex

563f5f454cd2e9048fe05031ac9756deb3f6f0632a12abf20dc96891a6931721

nevent

nevent1qqs9v06lg4xd96gy3ls9qvdvjatdavlk7p3j5y4t7gxuj6y356f3wggprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsdrfs5nr6trhpxmu97e5dra85g7d2lkc2twu0gkke8058lnx5z5gcderpt0

Kind-1 (TextNote)

2026-04-19T13:37:02Z

Question for all Ethereum enthusiasts around here:

Say you have a smart contract to which users can submit transactions for which they have to pay gas fees. You'd like to offer them the service of paying these gas fees on their behalf so they don't have to go go through the trouble of having to get their own ETH. But it's also important that msg.sender always be the address of the privkey with which the user signed the underlying transaction (rather than say the address of the payor). Is there an (easy?) way to do this?

#ethereum

原始 JSON

{
  "kind": 1,
  "id": "563f5f454cd2e9048fe05031ac9756deb3f6f0632a12abf20dc96891a6931721",
  "pubkey": "d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23",
  "created_at": 1776605822,
  "tags": [
    [
      "t",
      "ethereum"
    ]
  ],
  "content": "Question for all Ethereum enthusiasts around here:\n\nSay you have a smart contract to which users can submit transactions for which they have to pay gas fees. You'd like to offer them the service of paying these gas fees on their behalf so they don't have to go go through the trouble of having to get their own ETH. But it's also important that msg.sender always be the address of the privkey with which the user signed the underlying transaction (rather than say the address of the payor). Is there an (easy?) way to do this?\n\n#ethereum",
  "sig": "b56b7665c70a0edb36b9e8d85acf6b5a7a50b67ec00487bea83a5864e5b7a7d93732636dc9f655f0f65aaab507fab7417c1278dcd8c1906e6f3feb29c3729e6e"
}