Cached Bundlr Txs about arkb

[xloem]

This may not be an issue if there is something relevant I'm not understanding well.

[xloem]

Thanks for organising my issue. I'd love to know what I'm missing that it got closed without comment, although I haven't been using arkb recently.

When I made this, I was planning to review the caching code and modify the checks, but instead I've been using the subsidized 100KB upload deal so that duplicate transmissions don't cost me.

[fuadop]

Hi @xloem 👋🏾 ,

Arkb only caches transactions on the main gateway (https://arweave.net) currently. bundlr nodes are more than one and is always evovling. from https://bundlr.arweave.net to (https://node1.bundlr.network and https://node2.bundlr.network).

[xloem]

Thanks, I was actually a little confused on that, but are you kind of implying that arkb would need a pull request contributed in order to be concerned with caching txs sent to bundlr nodes?

[fuadop]

Bundlr is similar to a micro gateway, and they cache data before sending it to arweave.net, if I'm correct, that data is after deleted, so we cannot rely on bundlr.

[xloem]

Sorry, I mean to prevent retransmission. If the bundlr cache is not checked, then the same file can be funded and confirmed twice. Does that sound right?

EDIT: I'm thinking arkb might be intentionally refunding files that haven't confirmed yet. I don't remember. Maybe that would be a different issue.