The HashPort Gateway is not another trust center A normal browser cannot directly read website files from the blockchain, so a Gateway is needed to read the onchain content and serve it to the browser through HTTP But the Gateway itself does not decide whether a file is authentic After retrieving the file, it should verify the content against the SHA-256 recorded on chain If the returned file does not match the onchain hash, that file should not be treated as a verified frontend This means the Gateway itself can be replaced There can be multiple Gateways, and different teams can operate them The final verification does not depend on any single Gateway It depends on the files stored on chain and the hashes recorded on chain This is an important part of DeWEB Users can access the same onchain frontend through different gateways But the verification result should always come from the same onchain source of truth