Damir Vodenicarevic

@gterzian I made a mistake in one of my comments above: the first criterion of the async pool sorting should not be msg.fee but rev(Ratio(msg.fee, max(msg.max_gas,1)))

Ideally, we should use the hash of the whole state (not only the ledger)

I agree with the following benefits: * being able to send many times the same transaction at the same time: this can currently be done by varying the expiration period...

> i think to ignore transactions is bad way, one byte can one transaction, but users are not send only one transaction, they send batch transactions, and one byte can...

> i mean, users will send more then 1 transaction pear a block, They already can. It's only fully identical transactions that can only be included once (more than 1...

@sydhds that's done right ?

This applies to the following commands from the client: * read-only executions * sending ExecuteSC operations

We need to figure this out.

Let's also add the following endpoints: * [ ] send endorsements * [ ] send block * [ ] get executed operations * [x] rpc.discover [eip-1901](https://eips.ethereum.org/EIPS/eip-1901) As well as json-rpc...

@BatiGencho your loop is calling get_status non-stop without delay ?