sipa: it's not clear to me how it's possible to implement the policy to remove floods sent by the far side. You can tell that you already have the txn when you recieve the flood, so presumably you would have put it to be recon .. but it might have already been reconed and not part of your current recon set?
gmaxwell: in that case you don't remove it?
i believe the set is kept explicitly, not just in sketch form
[bitcoin] jonatack closed pull request #21855: fuzz: enable passing a max value to FuzzedDataProvider::ConsumeEnum() (master...ConsumeEnum-enable-passing-max-value) https://github.com/bitcoin/bitcoin/pull/21855