Works for me 👍🏻

rebase on master

In D16544#378081, @bytesofman wrote:

Not sure what you’re asking there

In D16544#378062, @bytesofman wrote:

update using a dataclass

could you summarize what this does and why this became preferable? I can see the organization change, is it just easier to read and maintain as a class?

rebase to fix build

fix hopefully the last test

fix other tests

fix groups for the error case

move agora.py into ecash-agora (so it becomes part of the npm package), rebase to fix tests, update + fix comments

fix tests in context.rs

minor fixes/cleanup, rebase on D16674

remove unrelated chronik-db change

rebase, update using a dataclass, add sats calculation as requested

fix comments

fix missing =

fix lint length

use djlint to lint explorer templates

Another possible name would be gettransactionstatus; you already say this in the release notes: "retrieve the status of a non-mined transaction". It would (kinda) imply that the RPC should return "mined" for mined txs (which we can't do in the general case because the -txindex can be disabled). So either it looks that up (and returns "unknown" if the txindex is off), or the name could also be gettransactionstatusinmemory, which is I think the most precise, albeit a bit long.

Yes, we wanna make sure we don't crash in this scenario. There might be others too, but I hadn't had the time to cover them yet, we might do so in the future and amend this test.

supposed to be a draft

address review

if you don't like the Object.entries change, fine to ignore

some ideas for better code style

address review

rebase onto master

can't say no to this much removed code 🤷🏼‍♂️

CI failure unrelated, will land anyway

rebase onto D16568

rebase onto D16568 again

fix test

fix test

fix nits

rebase onto D16568