IPFS is content-addressed. That means that it's trivial to discard tampered content. Lying majority, sure, will impact your content retrieval speed — but dealin

IPFS is content-addressed. That means that it's trivial to discard tampered content. Lying majority, sure, will impact your content retrieval speed — but dealing with cheaters seems to be as simple as adding their addresses in some ignore list (which can itself be IPFS-shared, if needed). I'm not sure of this blacklisting is implemented in current go-ipfs out js-ipfs codebase — but hash verification itself certainly is.