15:12 <stellar-slack> <fredolafritte> anyone know how to decode the column txresult in the txhistory table of the stellar database

15:12 <stellar-slack> <jed> scott ^

15:13 <stellar-slack> <fredolafritte> i've tried *StellarBase.xdr.TransactionResult.fromXDR* without success

15:15 <stellar-slack> <fredolafritte> that's related to creating an offer

15:16 <stellar-slack> <jed> It gets stuck in here: TransactionFrame::storeTransaction

15:16 <stellar-slack> <jed> looks like it is xdr that has been base64 encoded

15:16 <stellar-slack> <fredolafritte> var errorXdr = 't1qpS2SGmIWfZXnpmlFsZBt6JYb2+YIUC5RcngrmvCoAAAAAAAAD6P////8AAAABAAAAAAAAAAP////5AAAAAA=='; var errorMessage = StellarBase.xdr.TransactionResult.fromXDR(new Buffer(errorXdr, "base64"));

15:18 <stellar-slack> <jed> scott should be online in a bit. I'm not sure what the state of his xdr decoder is. maybe that is the issue?

15:19 <stellar-slack> <fredolafritte> the transaction is in the txhistory table but go-horizon replies 404 when trying the transaction through its hash

15:34 <stellar-slack> <sacarlson> I only know that AAAAAAAAAAD////7AAAAAA==` is a bad sequence error, so I guess you don't have my original problem

15:53 <stellar-slack> <scott> @fredolafritte: the txresult should be a base64 encoded `TransactionResultPair`

15:58 <stellar-slack> <fredolafritte> perfect

16:43 <stellar-slack> <sacarlson> not sure this is it or not

16:44 <stellar-slack> <sacarlson> so I guess that indicates you have no account?

17:00 <stellar-slack> <scott> @sacarlson: the .x files (https://github.com/stellar/stellar-core/tree/master/src/xdr) are the source of truth for all the xdr encoded data structures throughout the stellar network.

17:00 <stellar-slack> <scott> The snippet you posted is generated from https://github.com/stellar/stellar-core/blob/master/src/xdr/Stellar-transaction.x#L628

17:03 <stellar-slack> <sacarlson> so I take it in in the right place but don't know how to decode base64

17:03 <stellar-slack> <sacarlson> as the error codes here are in decimal

17:08 <stellar-slack> <scott> sacarlson: All of the base64-encoded values are byte streams that contain an XDR-encoded data structures. https://tools.ietf.org/html/rfc4506 is the specification for how you go from a byte stream to in-memory structures

17:09 <stellar-slack> <scott> the actual structure encoded in any given value is not very well documented, as shown by fredolafritte’s question

17:10 <stellar-slack> <scott> for example, the value in the `txresult` column is a `TransactionResultPair` strucut, or the `txmeta` column is the `TransactionMeta` struct.

17:11 <stellar-slack> <scott> So, the procedure to get to that decimal value is 1) decode the base64 value to a raw byte stream 2) decode that byte stream to an in-memory XDR struct of the appropriate type 3) access the in-memory field to retrieve the decimal value

17:11 <stellar-slack> <scott> make sense?

17:12 <stellar-slack> <sacarlson> ya makes sense but I think it's out of my pay grade ha ha

17:13 <stellar-slack> <sacarlson> I'll await the released utility that converts it to a more readable format

17:14 <stellar-slack> <sacarlson> or force known errors and see what results I see and maybe the results will show a pattern

17:15 <stellar-slack> <scott> so, luckily we have that utility for ruby, javascript, and go. That’s what ruby-stellar-base is: https://github.com/stellar/ruby-stellar-base for example

17:16 <stellar-slack> <scott> We convert those .x files into c++, ruby, etc. to make it easier to go into the in-memory representation.

17:16 <stellar-slack> <scott> Let me explain how you would go from "AAAAAAAAAAD////7AAAAAA==“ to the error code:

17:17 <stellar-slack> <sacarlson> ok

17:21 <stellar-slack> <scott> That script will output `Stellar::TransactionResultCode.tx_bad_seq(-5)`

17:21 <stellar-slack> <sacarlson> cool in ruby I love it

17:21 <stellar-slack> <scott> :)

17:54 <stellar-slack> <sacarlson> so from this then I am guessing fredolafritte's code 't1qpS2SGmIWfZXnpmlFsZBt6JYb2+YIUC5RcngrmvCoAAAAAAAAD6P////8AAAABAAAAAAAAAAP////5AAAAAA==' is .tx_insufficient_balance(-7)

17:58 <stellar-slack> <scott> That’s incorrect… the -7 in that data structure is a member of the `ManageOfferResultCode` enum, which is `manage_offer_underfunded`

17:58 <stellar-slack> <scott> If you inspect the whole data structure:

18:01 <stellar-slack> <sacarlson> ok