You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Regarding EmptyTransaction, EmptyTransaction2, EmptyTransaction3, the result of executing the EmptyTransaction should behave differently depending on if the EIP158.
I don't understand how its suppose to create an empty account because this transaction doesn't pass the validation as per Eq.(58) of the YP (g_0 <= T_g).
g_0 = 21000 (because it's the cost of G_transaction paid for every tx)
T_g = 0
So I guess we shouldn't execute this transaction at all (that's how it currently works after I've added transaction validation). But how not executing transaction results in a newly created account?
If I understand correctly the problem is that if we're testing against the Frontier chain then the correct behavior (not executing such transaction) is considered incorrect.
The text was updated successfully, but these errors were encountered:
Regarding
EmptyTransaction
,EmptyTransaction2
,EmptyTransaction3
, the result of executing theEmptyTransaction
should behave differently depending on if the EIP158.< EIP158
- creates an empty account https://github.com/ethereum/tests/blob/develop/src/GeneralStateTestsFiller/stTransactionTest/EmptyTransactionFiller.json#L24>= EIP158
- doesn't create an empty account https://github.com/ethereum/tests/blob/develop/src/GeneralStateTestsFiller/stTransactionTest/EmptyTransactionFiller.json#L42I don't understand how its suppose to create an empty account because this transaction doesn't pass the validation as per Eq.(58) of the YP (
g_0 <= T_g
).So for our empty transaction we have:
So I guess we shouldn't execute this transaction at all (that's how it currently works after I've added transaction validation). But how not executing transaction results in a newly created account?
If I understand correctly the problem is that if we're testing against the Frontier chain then the correct behavior (not executing such transaction) is considered incorrect.
The text was updated successfully, but these errors were encountered: