We started using content hash addressing with our assets build system (i.e. combining CSS & JS into a single URL), so that we'd get maximum cache life without needing to artificially manage cache busting query strings.
The more substantial use now though, is for the "content" of the site (purchasable ebooks/etc and associated artwork) which is constantly growing and occasionally old content gets updated with newer editions/revisions. We use content hashing to actually store the files (free de-duplication) and obviously it then gives us the same caching benefits.