Frontend Verification: Checks whether retrieved content matches the expected version Contract Verification: Examines onchain execution logic and associated risks As the BNB Chain ecosystem explores more application mechanisms, understanding these distinct verification layers becomes increasingly important

Frontends should not depend on Web2 black boxes forever HashPort is building a new publishing model Websites enter TapeOut Containers Files have on chain paths Content has SHA 256 hashes Users can verify the frontend source This is only the beginning

Frontend security should not be checked only on launch day After every dependency update configuration change domain change or NFT transfer verify again Container ownership DNS records Entry files External dependencies File hashes A verifiable frontend also requires verifiable operational habits

Frontend Identity in HashPort is not simply a wallet address It is made up of three parts Chain ID Store Site Chain ID identifies which chain the frontend belongs to Store identifies which Onchain File Store provides the frontend files Site identifies the Site Account associated with those files So the identity of a frontend can be understood as A specific Site Inside a specific Store On a specific chain This is also why HashPort does not use a Domain as the identity of a frontend A Domain is only the entry point used to access a website It does not fully describe the identity of the onchain frontend The combination of Chain ID Store and Site tells the wallet exactly which set of files the current frontend corresponds to on chain Both Hash Verification and Contract Frontend Declaration are built on top of this identity

HashPort frontend verification actually has two different layers The first layer is Published The wallet takes the HTML JavaScript Worker WASM and other executable resources actually loaded by the current page and calculates their SHA-256 hashes, then compares them with the file hashes recorded by the on-chain Store Only when everything matches can the wallet confirm that the current page is identical to the version published on chain But this still does not prove that it is the official website Anyone can publish a frontend on chain, including an attacker publishing a phishing website That is why there is a second layer called Official The target contract can declare its official frontend through the Frontend Declaration Registry When the user is about to sign a transaction, the wallet can compare the Frontend Identity of the current page with the frontend declared by the contract Published proves that the files have not been secretly modified Official proves that the frontend has been recognized by the target contract These two checks solve two completely different problems

The frontend page may depend on CDN scripts, DNS resolution, npm packages, build dependencies, and server permissions If any one of these links is hijacked, it may lead to a situation where the domain is correct and the contract is correct, but the page is no longer the original page

Morpho Frontend and API Partially Disrupted by AWS Outage, Now Restored Morpho principal engineer Julien said app morpho org and api morpho org experienced a partial outage about three hours ago, likely due to an issue with AWS CloudFront. All Morpho services have since been restored and are operating normally. YEET co-founder Mando also said the project's website is offline due to the same AWS CloudFront outage, stressing that the incident has no impact on user assets or funds. The team is actively working on a fix and expects services to resume shortly.

Another frontend phishing story is a reminder: the page can look normal while the signature is the trap. 🧩 Wallet safety cannot live only inside a pop-up. Browsers need context, risk signals, and clearer signing before users tap approve. 🛡️ #HootArk# #Web3Security# #WalletUX#

HashPort deploys website frontends onchain and connects users to onchain websites through domain names The TapWeb DeWEB Viewer makes these websites easier to discover and access From circuits to frontends to real users, a complete ecosystem loop is taking shape