Standardization of block retrieval
Currently we have 6 different functions to retrieve information from blocks:
With few exceptions, they each have a different parameters format and provide different results (structure, format, ...).
[1,2,3] do not return vops
[4,5] return ops and/or vops but not block data  returns vops but not ops nor block data [1,2] return tx ids as a global array
 returns tx ids as a global array and inside transactions objects (the latter is easier to manage)  returns tx ids in each operation object  returns result as an array
 returns result is an object containing an array
 is the only one to effectively return
Properties like block_num, timestamp are sometimes duplicated in each transaction/operation which increases the volume of data returned and transferred.
Some APIs return operation type with the
_operation suffix, some not.
... and so on
Couldn't we optimize all this by providing one API call and above all standardize how data are returned?
get_block_range looks like the favorite candidate to me.
It is quite new, less used up to now, and therefore less prone to break things if we change it.
My wish is it could return vops and has
transactions_ids in each transaction object instead of being grouped in an array at the end.