support_search and transaction_search (purchase_search?)

[tzarebczan]

• [x] should be able to pass a filter for your purchases vs someone purchasing your content
• [ ] show which content was purchased in txo list - both incoming and outgoing purchases

[tzarebczan]

Per Lex's findings, purchase list only handles outgoing purchases and not incoming. What API do we want to use for incoming ones? If it's txo list, we need details added to the purchase.

[kauffj]

Yes, it should be txo_list. Ideally I could pass a claim id of a stream or channel and get the results accordingly.

[tzarebczan]

Also consider https://github.com/lbryio/lbry-sdk/issues/2939 as part of this. Not sure if this should be a new API or just part of resolve - probably the latter with a flag similar to other examples.

[kauffj]

Also for supports that are signed

[kauffj]

First call to develop is support_xxx, which will:

• Take a URL or claim id
• Report on the amounts, aggregated by identities (as well as anonymous), sortable by total amount

[kauffj]

Second is to develop APIs that would allow the creation of UIs that let me see my supports aggregated by claim and use support_abandon to manage the amounts.

[kauffj]

Summing supports historically has some challenges with regards to unlocking and history, @jackrobison will propose specific design. First step will be to get signing information into txo_list

[kauffj]

@lyoshenka wants to be involved in this, will discuss with you