On-chain address verification
Verify the
destination.
A wallet address on a page can change. Addrseal checks it against the publisher’s signed record on Robinhood Chain.
On-chain address verification
A wallet address on a page can change. Addrseal checks it against the publisher’s signed record on Robinhood Chain.
01Publish
A publisher deploys a registry from their wallet and records the destination for an HTTPS origin. One registry can hold entries for several origins.
The owner can change a destination or revoke it. Each write leaves a transaction that can be inspected in the chain explorer.
Open publisher tools02Verify
Start with a registry address obtained from the publisher. Enter the website origin and the full wallet address displayed on its page.
Addrseal checks the network and registry code, then reads the owner and destination at the same block. You get a result with links to the evidence.
Open the verifier03Monitor
The browser SDK watches a visible address for text changes or replacement. A change triggers a fresh comparison with the last registry read.
It refreshes the chain record every 15 seconds and when the tab becomes visible again. Your interface receives a match, mismatch, or unverified status.
Explore the browser SDKProduct guide
Use it at the point where a website tells someone which wallet should receive a payment.
Before sharing a payment page, compare its displayed recipient with the finance team’s registered address. Save the registry and block links with the review.
Verify a destinationKeep one on-chain record per website origin. Rotate an address when a treasury wallet changes, or revoke the entry when a page stops accepting payments.
Manage a registryPin the trusted registry in your integration and watch the element that displays the recipient. Use the status callback to show an alert beside the address.
Integrate the SDKReading a result
This example shortens the addresses to make the change visible. The verifier compares all 20 bytes.
0x71a4…C8400x71a4…C841Protocol notes
The supplied destination equals the active entry for that origin in the selected registry at the reported block. You still need a trusted source for the registry address. Anyone can deploy a registry and enter an origin.
Verification and SDK monitoring use public RPC reads. Deploying a registry, setting a destination, or revoking an entry requires a wallet-signed transaction and the network’s ETH fee. You can try the publishing workflow on Robinhood Chain Testnet.
Each HTTPS origin gets its own entry. For example, https://pay.example.com and https://example.com are distinct. Page paths share the record for their origin. Use a separate subdomain for a destination that needs an independent record.
The console reports an unverified result for a missing record, unexpected contract, wrong network, or failed read. The SDK also reports unverified when its selector points to a missing, hidden, or ambiguous element.
The SDK watches the visible text of one configured element. Clipboard contents, QR codes, transaction calldata, and the wallet confirmation are separate surfaces. A script with control of the page can interfere with its alerts. Review the recipient in the wallet before signing.
Addrseal / $ADSL