why are the encodings not "the same" as results we could expect from chronik-client?

Seems like this makes it harder to generate mocks.

update: ok after reviewing i see what's going on, so in this way you can mock the actual endpoint responses, works well with cy intercept

this is still pretty complicated; what was your procedure for generating these mocks?

A possible alt approach would be to use MockChronikClient and set it as it is usually set before tests. But depending on architecture, this can be quite difficult to drop in / inject in place of chronik in the tests.

The intercept approach is probably a better pure API reflection. Maybe add scripts / tools to generate these into modules/mock-chronik-client?

update: ok I see how these are generated, nice. For now, cypress is only being used in marlin, so it makes sense to keep the scripts here vs in mock-chronik-client. As the stubbing system matures / if it becomes more complex and starts getting more endpoints, could consider adding these scripts to their own dir in the monorepo, or perhaps to mock-chronik-client.

Chronik's strongly-typed responses are super helpful for creating detailed real world tests. But the mock creation across various testing libs is a huge headache (see Cashtab, here). Now that AI is commonly available, even some MD files or context where prompts like "please create appropriate mocks for a wallet with this balance including this token balance and this kind of tx history" would be ideal.

these are different encodings vs normal hex?

why?