You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm importing my bank transaction logs into my Solid Pod. This is useful in itself, but also a way to get ledger data into my PDS and start dogfooding from there.
The data format will not be the same as for nlt-kit, because that's mainly based on StateTransitions as the base data.
Maybe it makes sense to have a network ledger view in the user's PDS which may also include records of HalfTrades in which the user doesn't participate, as long as the identity relation between HalfTrades in one ledger view and another is bulletproof, to avoid double billing.
Some entries may be speculative (e.g. implying a purchase HalfTrade where there is evidence of a payment HalfTrade in a shop). That's just how bookkeeping works. You can edit your own records to best help your understanding of the world, without affecting reality.
So then maybe I do want to store duplicate entries from the message logs into the ledger-view store.
The text was updated successfully, but these errors were encountered:
I should port the nlt-kit code to solid-logic / money-pane, once I start allowing users of MoneyPane to participate in the LedgerLoops testnet, but for now I can just keep in mind that I want them to use the same data formats. I should document those on https://pdsinterop.org/conventions/.
I'm importing my bank transaction logs into my Solid Pod. This is useful in itself, but also a way to get ledger data into my PDS and start dogfooding from there.
The data format will not be the same as for nlt-kit, because that's mainly based on StateTransitions as the base data.
Maybe it makes sense to have a network ledger view in the user's PDS which may also include records of HalfTrades in which the user doesn't participate, as long as the identity relation between HalfTrades in one ledger view and another is bulletproof, to avoid double billing.
Some entries may be speculative (e.g. implying a purchase HalfTrade where there is evidence of a payment HalfTrade in a shop). That's just how bookkeeping works. You can edit your own records to best help your understanding of the world, without affecting reality.
So then maybe I do want to store duplicate entries from the message logs into the ledger-view store.
The text was updated successfully, but these errors were encountered: