Hans Svensson

> > but that would not be a problem in practise > > Why not, if the client solely relies on this result and the last X blocks are empty?...

> @hanssv In the latest version, I can't distinguish if blocks are full and I should use min gas price + 1 or if there is space in blocks and...

> Another issue: > > * I've build this branch, run it with configuration for sdk tests > > * `recent-gas-prices` shows "min_gas_price": 0 everywhere > > * changed min...

So we decided on sticking to this approach (reporting minimum gas price that made it on chain in the last X, Y and Z minutes) - but we'll also add...

Any numbers on how much better this is?

Isn't this one different, though? A revoked name is only blocked for a period of time, right? While a non-payable account is never going to become payable. Still, it could...

You also have the case where there is a PreClaim involved, that is only valid for 300 generations (I think??) - so lot's of cases to cover in testing... Is...

The first problem here (I suspect there might be more things wrong with devmode) is that if you say `auto_emit_microblocks: false` - as far as I understand that means that...

As discussed elsewhere - changing this is trivial, and makes sense - question is how much of a breaking change is it?

A less breaking solution would perhaps be to _add_ a field with the the encoded key?