Cover photo

Scan by Name, Not by Address

Proof of Human now accepts SPACE ID names anywhere you'd type a wallet address. Type vitalik.eth, get a humanness verdict. No address required.

Proof of Human × SPACE ID — Scan by Name, Not by Address

Proof of Human now accepts SPACE ID names anywhere you'd type a wallet address. Type vitalik.eth, get a humanness verdict. No address required.


The problem we solved

Every tool in the humanness-verification space has the same UX assumption: you already have the wallet address.

That's a bad assumption. People share names, not addresses. Communities coordinate around alice.bnb, not 0xb5932a…. Airdrop lists get compiled from handles and domain names that then need a manual lookup step before you can do anything with them.

Proof of Human now skips that step entirely.

post image

How it works

When you enter a value in the Checker input — single address or a row in a bulk CSV — we run a simple check before anything else:

  1. Is it already a wallet address? EVM (0x…) and Solana (base58, 32–44 chars) addresses pass straight through.

  2. Is it a SPACE ID name? Everything else is sent to the SPACE ID resolution API:

GET https://nameapi.space.id/getAddress?domain=vitalik.eth
→ { "address": "0xd8dA6BF…", "code": 0 }

The resolved address is shown in the UI so you can confirm what you're scanning, then the normal verification flow runs — burn 1 POH, query registered methods, return a human/AI verdict.

For bulk scans, the entire CSV is resolved before the POH burn transaction is built. You can upload a file of SPACE ID names, raw addresses, or any mix — all rows are resolved first, then a single transaction covers the full batch.


Why this matters for AI agent detection

This is where it gets interesting.

AI agents are acquiring web3 identities. An autonomous agent can register agent.eth or trading-bot.bnb just as easily as a human can. The domain name says nothing about who — or what — is behind it.

That's precisely the point of Proof of Human. The name is the entry point. What we verify is the on-chain history the address resolves to: transaction patterns, contract interactions, token holdings, behavioural signatures registered by the community through our method voting system.

A bot can have a name. It cannot fake years of organic on-chain behaviour across multiple independent data sources.

The integration with SPACE ID makes humanness checks as easy to run as a Google search — you type what you know, we handle the resolution, we return the signal.


What you can do now

Input

Works?

0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045

EVM address

9WzDXwBbmkg8ZTbNMqUxvQRAyrZzDsGYdLVL9zYtAWWM

Solana address

vitalik.eth

Resolved via SPACE ID

spaceid.bnb

Resolved via SPACE ID

user.arb, name.sol, alice.op

Any SPACE ID TLD

CSV with a mix of names and addresses

Bulk — each row resolved individually


Technical note

Resolution happens on the frontend before the POH burn transaction is constructed. The backend receives only resolved wallet addresses — no changes to the verification engine were needed. If a name cannot be resolved (returns code 1 or network error), the scan is stopped with a clear error message before any tokens are spent.


What's next

  • Reverse lookup in results — show the Space ID name next to each scanned address in the results panel

  • ENS primary name display — surface the primary name on the result card so a human-flagged address shows their identity naturally

  • Agent registry integration — cross-reference resolved addresses against known AI agent registries as an additional method signal


Proof of Human is an open verification network. Community-registered methods, POH-token governance, on-chain dataset for AI training. Built by Assetux