Verification is consistency, not endorsement
D17 separates metadata agreement from canonical economic rules.
The terminal can show that public records agree without claiming that a project is valuable or honest.
The metadata check compares token name, symbol, description, SVG, links, stored metadata hashes, the factory publication event, and token contractURI. A checkmark means those records are consistent.
The rules check is separate. A locker validates the launch's contract identity, WETH, exact rulesHash, and canonical factory registration before commitment and settlement-sensitive paths.
These checks reduce two different forms of drift:
- identity content that changes between a page and the deployed token; and
- economic configuration that does not belong to the canonical launch the locker was asked to use.
Neither is an audit, reputation score, or prediction. A correctly identified canonical launch may still represent a poor idea, misleading promotion, volatile token, or software risk. Verification answers “do these records match?” and nothing more.