Why a verified checksum beats a successful upload
An upload that finishes is not an upload that worked. Over the last 12 months our servers rejected 0.011 percent of completed uploads because the SHA-256 computed on arrival did not match the one the loader sent. That is about one file in 9,000, and every one of them looked fine in a file browser.
The causes were boring. Catalog software rewrote a sidecar mid-transfer. A card reader returned stale data on a second pass. Once, a hotel gateway rewrote a response header and truncated a 61 MB file by 4 KB. A gallery service that does not hash would have shown the first frames and hidden the damage until a print lab asked why a bride's veil had a stripe through it.
So we hash before the first byte leaves, hash again on arrival and hold the file in quarantine until both agree. From version 3.4 the loader also re-reads the part it just sent if the server reports a mismatch, which cut retry traffic by 31 percent.