Hello, and thank you for all the effort you put into the Rosetta API project!
We are wondering if a scenario with transactions spanning multiple blocks (that do not have all their balance-changing operations in a single block) is in the spirit of the Rosetta API.
Block 42: Transaction 0xABBA Operation 1: -50 tokens for Alice, as Transfer Operation 2: -1 token for Alice, as Fee Block 43: Transaction 0xABBA Operation 3: +50 tokens for Bob, as Transfer
Block 52: Transaction 0xFADE Operation 1: -100 tokens for Alice, as Smart Contract call Operation 2: -3 tokens for Alice, as Fee Block 53: Transaction 0xFADE Operation 3: +100 tokens for FooContract Block 54: Transaction 0xFADE Operation 4: +1 tokens for Alice, as FeeRefund
Is this way of splitting the balance-changing operations acceptable for a Rosetta API implementation?