thx, could you explain this a little more?

Can't follow yet, sorry maybe my brain might be too slow. I think security can't be achieved here, bad clients can answer Queryhits on random hashs (like Mandragore) or a client has a bug and gives wrong hashs or wrong partials. So every resume _must _ be overlapped. Something Xolox does right now and therfore Xolox resume is working fine, while for example Bearshares resume is terrible (did not check if its better with 2.30), you get a lot files with artifacts. It might be more important to have a fast & small hash.