ketsuban

peersky.ketsuban.eth

sybil signal · reading the graph…

wallet 0xD70B…94a0

  • References2 of 320/30
  • Humanityproved25/25
  • Nameclaimed20/20
  • Accounts4 attested15/15
  • Profile1 of 3 filled3/10

Answers

What do you think of Kim Jong Un?
peersky.kju-is.ketsuban.eth
dictatorvalid until 2026-10-10 08:31Z

Linked accounts

References received

unsolicited means no invitation from peersky came with that reference. Anyone may refer anyone here, so it is a fact about how the reference arrived — not a judgement of it, and not proof that peersky never asked.

Refer this person

Humanity

attested (selfie)

Who stands behind them

reading the graph…

Read it without this app

Every field above is a resolver read. Any ENS client resolves the same names; the API only formats them.

The same page as JSON, conservative and bounded — never authorisation to execute anything:

GET https://2.ketsuban-api.peeramid.xyz/v1/verify/peersky.ketsuban.eth · GET https://2.ketsuban-api.peeramid.xyz/v1/vouches/peersky

Read it yourself, through ENS

The UniversalResolver at 0x4A18…3C70 walked the registry to 0x178f…215e and returned 0xD70B…94a0.

ketsuban:expiry
1791552223
ketsuban:humanity
selfie
avatar
http://ketsuban-api.peeramid.xyz/v1/avatar/ca60ac079a13158583b128f80fcce4e79a3612370b69ac79c213f9bc40423410.gif

Point ETH_RPC_URL at Sepolia (chain 11155111), which is where these records live.

cast call --rpc-url "$ETH_RPC_URL" 0x4A1817d13E9cF196f471725176355C1234b63C70 \
  "resolve(bytes,bytes)(bytes,address)" \
  0x0770656572736b79086b6574737562616e0365746800 \
  $(cast calldata "text(bytes32,string)" $(cast namehash peersky.ketsuban.eth) "ketsuban:expiry")

Share

Verify me at Ketsuban: https://2.ketsuban.peeramid.xyz/p/peersky — on-chain name peersky.ketsuban.eth