Trader.ListAccounts OutPoint txid not reverse byte order

[cwispp]

when using grpc ListAccounts, the account outPoint txid is not reverse byte order

[guggero]

That's kind of an implicit API level design Pool shares with lnd. If a TXID is of type bytes in the proto, then it means the TXID is in the internal (non-reversed) representation that corresponds to the transaction hash. That is the case everywhere the Outpoint RPC message is used. The CLI explicitly converts this representation to the human-readable (reversed) form when presenting it to the user.

If an outpoint or TXID has the type string on the RPC it means it is hex encoded in the human-readable (reversed) format.

I guess this should just be documented better.