PageKey
“This address belongs to whoever runs that page” is usually a badge somebody hands out. Here it is a fact other contracts can read. You publish a token on a page you control, and the binding exists only when validators agree the page itself says so — not a visitor comment, not a quote, not a token copied from someone else. The network looks again on a fixed interval, and a page that stops saying so loses the binding.
Contract 0x909151ae02…F95d · no owner, no issuer · contract source · this console
1 · Bind a page to your wallet
Enter a page you can edit. The token below is derived from the page and from your address, so it is useless to anyone else. Put it in the page's own content, then claim.
Connect a wallet and enter an https page to see the token.
Both numbers are fixed by this claim and have no setter. With these values a page that drops the token stays bound for at most 10 min of rechecks. A refused claim binds nothing; you can try again after a minute.
2 · What a check decides
- absent the token is not on the page. Counted in code over the whole page; no model is asked.
- own validators agree the token is part of the page's own content: a bio, a profile field, a statement by the author.
- not own the token is there, but in a visitor comment, a quote, a list of other people's tokens or a code sample. Doubt resolves here.
- unchanged on a recheck, a page byte-identical to the one already verified is confirmed without a model.
- unreachable the first outage is only noted; a second in a row is a miss. An outage never refreshes a binding.
- reverts a malformed model answer or a consensus failure records nothing.
Another contract reads is_bound(url, address, max_age) and chooses its own max_age: a binding nobody has rechecked lately is not a binding.
Pages on chain
Recent events
No events yet.