Paweł Bylica
Paweł Bylica
1. In EVMC it is called `account_exists()` although it works the same as described here. 2. You will need it to price `CALL` and `SELFDESTRUCT`. 3. In theory you can...
> > Is is also not extensible, i.e. we cannot change the account representation in the future. > > It can be mitigated easily though, by adding bitflags, integer or...
> Could you explain me why that matters? A contract is written against version 1 and explicitly requests v.1 and gets the result in v.1, that sounds good to me...
@pepyakin do you have anything similar in pwasm?
Hypothesis: (Not all) nodes would have to keep the original code, they can keep the compiled / optimized code and the hash of the original code.
This can definitely be postpones until Constantinople is activated.
@lrettig I'm fine with using git tags and branches for this.
Definitely, the prototype of the version with `getLeft` global variable should be done. > * Set the value of this global prior to execution to the gas limit of the...
Still you have to check if you have the access to non-static namespace at runtime, right? The call separation sounds good to me. At the moment the cost is different...
I'm aware of the cons of such transfer(). But you can emulate it in EVM1 by creating a temporary contract and selfdestructing it. Such ether transfer is unnoticed by the...