In get_obt_data fio_request_id is set to 0 when it was empty, but 0 is an actual fio_request about fio

[edrotthoff]

there are several tactics that can be employed to solve this, the first is to change the value of the return id to be a signed int and return a negative value when there is not a FIO Request id, this may have impact on the fio sdks, and wallet integrations as each may need to have logic added to interpret this correctly. the next is to permit id 0 (though valid) to have the meaning that there is not a request id, this will eliminate the impact on the sdks, but will affect the maintenance of the protocol. For development purposes we will need to always ensure that a 0 request is made and on the chain...wallets will need to be coordinated to ensure they are filtering the 0 value correctly...

[ericbutz]

It was determined that it is acceptable to have fio_request_id = 0 when it is an OBT record with now associated Request.

Closing