@fulltimegeek So you are directly interacting with the RPC node and creating the operations on your own? Then I'm pretty sure that your need to handle the order also on your own. The RPC API needs an array of parameters, and not an object. But normally the RPC node wrappers are handling this. What are you using? Is there a java implementation for steem?
Otherwise checkout my other comment, I've described my theory there.
That is correct.
Order should only matter in serialization I believe. Json have maps with keys so order shouldn't be that critical. I'm not 100% sure tho on that. But, I'll play around with it.
I wish STINC had a utility or website that allowed anyone to construct operations and then spit out the raw buffer for one to sign. That would help A LOT ...
This the json that is getting send to the RPC node. Please adapt it and it will work. :)
{"id":2,"jsonrpc":"2.0","method":"call","params":["network_broadcast_api","claim_reward_balance",[account, steem, sbd, vests]]}in case it does not work, I'll have a look in a couple of hours.