Alexey
Alexey
> The only issue is we can't return the total number of access keys until we iterate through them. Why not to track the number in the account storage?
> It decreases the size of the chunk by putting extra effort on the chunk producer, but decreases the load from everybody else who's validating this chunk. Size of the...
> The reason for the validation before including into the chunk is to only include the valid transactions in the chunk. It fact, the proposal simply changes the definition of...
@bowenwang1996 The problem is that right now people can spam block producer with invalid transactions even for free, since this operation (even if we suppose that it's a cheap operation,...
The contract itself must define a self-destruction logic.
Interesting side-effect on testing experience: seems like this might be a significant improvement for unit-testing also, since it's unlocking testability of a contract initialization.
Updated the text a bit.
Right. It must be allowed to call Deploy action if action was created by the contract code.
In short, we just restrict any "sender = receiver" calls if `account.code` is not empty. DeployAction can contain empty `Vec`.
But you're right, the problem is that it seems like we don't have action type witch just erases the contract state. AccountDelete does that (but it also deletes an account,...