Arvin
> @vindard, I will like to work on this issue. Can I get assigned to it. Sure done. Let me know if you'd like to have a [chat](https://chat.galoy.io) or anything...
Adding some context here from off-github chats. --- @rxbryan asks: I would like a few clarification. 1. What is the new TxSummaryStatus type supposed to include. successful, failed, confirmation times...
> @vindard : "I'll double-check that cron deletes these from lnd" It does, all good
> I don't see a way to fix it on our end — we seem to be passing through everything correctly. This is still an issue, but it's an lnd...
> Could you be a bit more specific? I don't understand the "when sending from wallet". If I go to my LNBits shown below and I click scan in the...
> please run codegen too > > ``` > buck2 clean #required to avoid cache issues in update schemas > buck2 run //dev:update-schemas > ./dev/bin/codegen.sh > ``` We have `buck2...
> first pass... does this require a migration? I'm thinking no to migration so far based on the use-case. This change is a cosmetic one that doesn't affect any of...
> This doesn't expose any new fields from GQL - just uses a different mapping of tx state -> `Status` correct? Yup that's right
> However this introduces the possibility that a question is completed but a reward was not paid. Should we consider adding `rewardPaid` to persistence as well?
Agree with @nicolasburtey, there might be easier issues to tackle. If we want to do this properly we'd likely need multiple "memo" fields on a single entry, some of which...