nosenothing here is trusted
until it is proven.
Nosepad renders every external claim — the chain, the contract, the socials — from one register. Unverified stays greyed out and dated. Verified gets wired. Nothing is skipped ahead of the proof.
how a claim gets wired in.
Three steps, in order. A claim skips none of them.
State it
A fact enters the register with a source and a timestamp. It starts absent or stated, never assumed.
Verify it
Socials get a logged-out load; the repo gets a headless request without a redirect follow. What comes back decides the status.
Wire it
Only a stated record gets a live link, a click handler, or a number on the page. Everything else stays inert and dated.
the gate, provably.
A gate should be able to fail. Paste something address-shaped that isn't the stated contract and watch it get rejected — the same check runs against the real page.
Try the deployer's own address, a random 0x string, or plain text — none of them should pass while the contract is absent.
| Name | |
| Chain ID | |
| RPC | |
| Source |
| Field | Value | Status |
|---|