Verifier
Verify a destination.
Compare the wallet address on a website with the destination in its publisher’s on-chain registry.
Address check
Read-onlyWhat the verifier checks
- Chain identityChecks that the RPC endpoint reports the selected chain ID and obtains a block number.
- Contract codeCompares the deployed code hash with the compiled Addrseal registry.
- Origin and recipientReads the owner and origin entry at that block. A successful read includes explorer links to the registry and block.
Where do I get the publisher registry?
Obtain it through a channel you already trust. The code check identifies the contract implementation. The registry address identifies which publisher’s records you are choosing to trust.
Publisher
Manage a registry.
Bind a website origin to its intended destination, rotate the address, or revoke the entry using your publisher wallet.
Registry transaction
Wallet signaturePublisher permissions
The deploying account becomes the registry owner. Only that account can set or clear entries. A registry can serve multiple origins, each with one active destination. Updating an entry applies to all pages on that origin that use this registry.
How should I test and distribute a registry?
Choose Testnet and use testnet ETH for network fees. After publishing, verify the intended recipient in the same network. Distribute the registry address through an official channel and pin it in the SDK configuration. Mainnet and testnet maintain separate records.
Browser integration
Monitor a page.
Embed a read-only address monitor on your HTTPS site. It watches the rendered recipient and reports changes to your interface.
Install the browser SDK
Download SDK ↓- Self-host
addrseal.jsalongside your integration page. - Set
registryto the trusted publisher contract and use the network selected above. - Point
selectorat one visible element containing the full destination as plain text.
Handle all three states
matchThe displayed address equals the registered destination. The callback includes the record and block number.
mismatchThe text differs or is malformed. Show the registered destination so the visitor can review the discrepancy.
unverifiedA record is unavailable or the target is missing, hidden, or ambiguous. Display an explicit pending or unavailable state.
API options and cleanup
watchAddress({ network, registry, selector, rpcUrl, onStatus }) returns a cleanup function. Call it when a component unmounts. The optional rpcUrl accepts an HTTPS endpoint for the selected network. Use an endpoint suitable for browser access.
For a single read, call readRecord({ network, registry, origin, rpcUrl }). The returned object includes the normalized origin, publisher, destination, registry, network, and block number.
Integration boundaries
The SDK runs in the page alongside other scripts. It observes a single visible text element. QR codes, copied text, links, and wallet transaction data need their own checks. Keep the final wallet confirmation available for review.