Add EIP: No-Ether transactions with free-for-all tips #8888
Conversation
github-actions
bot
added
c-update
File
|
fulldecent
force-pushed
the
patch-696834
branch
from
9fa5bad
to
8fb1734
Compare
github-actions
bot
added
c-new
fulldecent
changed the title
eth-bot
changed the title
EIPS/eip-8888.md
Outdated
| @@ -0,0 +1,106 @@ | |||
| --- | |||
| eip: 8888 | |||
There was a problem hiding this comment.
| eip: 8888 | |
| eip: 7768 |
Assigning next sequential EIP/ERC/RIP number. Numbers are no longer the issue number.
Please also update the filename.
EIPS/eip-8888.md
Outdated
| title: No-Ether transactions with free-for-all tips | ||
| description: Externally-owned account having no Ether can send transactions and pay tips using a new "free-for-all" bucket | ||
| author: William Entriken (@fulldecent) | ||
| discussions-to: https://ethereum-magicians.org/t/eip-8888-no-ether-transactions-with-free-for-all-tips/21108 |
There was a problem hiding this comment.
| discussions-to: https://ethereum-magicians.org/t/eip-8888-no-ether-transactions-with-free-for-all-tips/21108 | |
| discussions-to: https://ethereum-magicians.org/t/eip-7768-no-ether-transactions-with-free-for-all-tips/21108 |
I updated the topic title in Eth Magicians to use the assigned EIP number.
|
|
||
| ## Abstract | ||
|
|
||
| A technique is introduced where an externally-owned account having no Ether can send transactions and pay tips using a new "free-for-all" bucket and using their own `origin.tx`. This requires no client changes and is compatible with existing ecosystem parts. |
There was a problem hiding this comment.
You should provide a high-level (but still technical) overview here of how this works. For example, what's a bucket? How does the block producer get paid?
|
The commit acad221 (as a parent of 4ce5441) contains errors. |
|
|
||
| Other proposals require changes to the Ethereum client, that transactions be sent to the network (i.e. `tx.origin`) using a separate account and/or other additional things. | ||
|
|
||
| In contrast, this proposal introduces and standardizes a solution to this problem that works only with existing client and technology, and which preserves the `tx.origin` of the originator of a transaction. |
There was a problem hiding this comment.
can you explain how this is different from 7702 which is already included in the upcoming hardfork
There was a problem hiding this comment.
I do see that Pectra / 7702 is included in https://eips.ethereum.org/EIPS/eip-7600
However 7600 has not reached last call status. And therefore it is still in negotiation.
If Pectra in fact has already been decided, perhaps what you are saying here, then that is a violation of the community process we have set up here.
Discussing a new approach for third-party pay transactions