support exfiltration of virtual ops via json rpc without current AH implementation

[sneak]

No description provided.

[sneak]

clarity: exfiltration via json-rpc response - so a new api call or modified get_ops_in_block api call.

[vogel76]

Implemented account_history_api.enum_virtual_ops method taking following parameters:

• block_range_begin - number of block (inclusive), starting the block range, the virtual ops should be iterated from
• block_range_end - number of block (exclusive), ending the block range, the virtual ops should be iterated from
  So the call:

{"jsonrpc": "2.0", "method": "call", "params": ["account_history_api","enum_virtual_ops",{"block_range_begin": 1, "block_range_end": 100}], "id": 2}

will retrieve all virt. ops existing in blocks [1..100).
Method returns pair: collection of operations (as ops member) and number of next block starting block range containing any virt. op as next_block_range_begin. If there is no more virt. ops next_block_range_begin will be set to 0.
Example result set:

{
	"jsonrpc": "2.0",
	"result": {
		"ops": [
			{
				"trx_id": "0000000000000000000000000000000000000000",
				"block": 1,
				"trx_in_block": 0,
				"op_in_trx": 0,
				"virtual_op": 0,
				"timestamp": "2016-03-24T16:05:00",
				"op": [
					"producer_reward",
					{
						"producer": "initminer",
						"vesting_shares": [
							"1000000",
							6,
							"@@000000037"
						]
					}
				]
			}
		],
		"next_block_range_begin": 1093
	},
	"id": 2
}

[vogel76]

@youkaicountry This probably can be closed as this code has been merged by @mvandeberg into develop.