Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

suggestion: new category field for transactions

See original GitHub issue

I was thinking that it would be helpful to have a little more information in transactions. Going through mine I have not just deposits and withdrawals, but from memory:

forked coins
air drops
refunds
adhoc balance corrections

Perhaps we could either have these as top level types along side deposit and withdrawal, or maybe add an optional category field?

Issue Analytics

State:
Created 4 years ago
Reactions:1
Comments:5 (5 by maintainers)

Top GitHub Comments

1reaction

kroitorcommented, Jun 3, 2019

Basically, most of it is either already documented as a part of fetchLedger or is going to be a part of it )

Transactions are for onchain transfers mostly, whereas the ledger is a superset of transactions+transfers+all other types balance changes…

Let me know if that doesn’t answer it )

0reactions

kroitorcommented, Jun 3, 2019

And is there a way to link together things in the ledger that are related (like the 3 entires for a trade)?

Yes, by referenceId – it contains an id of the event that yielded the ledger entry. The referenceId should be the same for ledger entries generated by the same event. In general it will contain the id of the trade if/where available.