Right now it looks like libp2p is optimised for smaller records and less churn (and so less republishing). They operate in the span of days we operate in the span of seconds to minutes (or would like to). Really we want to be doing data republishin on any churn.
So relying on their impl for large chunks etc is a balancing act.
Right now we’ve seen the limits of that approach and how it’s not necessarily optimal.
As @dirvine says, we’re really pushing libp2p and seeing what we can get away with there. I think we’ll be on a hybrid approach for a bit while we see what would make sense for libp2p.
So right now we’re looking at what would be optimal and how that might work into libp2p to see if there’s some PRs we could upstream there 