1

Inside the Stellar core history archive there are these folders:

bucket  history  ledger  results  scp  transactions

So inside of the transaction folder:

└── transactions
└── 00
    └── 72
        ├── 69
        │   ├── transactions-007269bf.xdr.gz

I can now unzip this file and get "transactions-007269bf.xdr"

My question is how do I unpack this file?

I managed to use Stellar-archivist's command 'dumpxdr' that unpacks the XDR file to JSON format.

How can I do it programmatically? (preferably python, but I'm open to suggestions) I can execute the stellar-archivist program from code, but I want to do it without being dependent on an external program.

Improve this question

1 Answer 1

Reset to default
1

Those files are streams of XDR objects, you can simply pick up any of the "base" SDK packages that include the generated code to (un)marshal objects (all generated from the .x files that are the specification).

A stream is written as a concatenation of pairs (XDR encoded size, XDR encoded object). The XDR encoded size is ORed with 0x80000000 and written byte by byte with the high order byte first. You can mimic what archivist XDRStream does to decode.

Most languages are supported, for example the javascript one is js-stellar-base

You can find a list of some of the existing SDKs on the developers reference page

Improve this answer
2
  • Sorry if im missing something obvious, but the stellar history docs say that "The file contains a sequence of XDR structures of the type TransactionHistoryEntry" All sdks I have seen allow you to unpack a TransactionHistoryEntry, but not a sequence of them. How can I do that?
    – Ron Serruya
    Feb 28, 2018 at 18:12
  • I see, let me add some details in my answer. those are "streams"
    – MonsieurNicolas
    Mar 1, 2018 at 22:46

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.