mortelli

> i don't think its possible to do a clean implementation of this with the current stack. For now we should just drop in the accounting hook if the other...

Also: look into possibly merging this API with the `swap` API.

look into the `bitvector` package for this one

this one should **not** be tackled before solving #2157

> what will happen if we retrieve 2 different chunks with the same addr field? this was a very silly question on my part. chunks are not _sent_ to an...

> what should be the correct return type of `Send`? this question no longer applies as #2159 has updated the signature for this function.

few questions here: - is there a size limit to each store? - would we be able to tell if the data we need is archived? how?

maybe i'm not following here, but: suppose i want a cheque for peer `p`. how do i know if this is stored in the regular store or the archived one?...

> I think it might make sense to store (in swap or the cashout processor) extra information for every peer: > the last cumulativeAmount that was scheduled to be cashed...

even though this is most likely a temporary solution: should this be implemented as a function, or as a hard-coded mapping? meaning: with a bzz network ID as an input,...