ketsuban

alice.ketsuban.eth

sybil signal · reading the graph…

wallet 0xEE48…9F3a

  • References2 of 320/30
  • Humanitynot proved0/25
  • Nameclaimed20/20
  • Accounts1 attested7.5/15
  • Profile0 of 3 filled0/10

Answers

What do you think of Kim Jong Un?
alice.kju-is.ketsuban.eth
not answered

Linked accounts

References received

unsolicited means no invitation from alice 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 alice never asked.

Refer this person

Humanity

not attested

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/alice.ketsuban.eth · GET https://2.ketsuban-api.peeramid.xyz/v1/vouches/alice

Read it yourself, through ENS

The UniversalResolver at 0x4A18…3C70 walked the registry to 0x178f…215e and returned 0xEE48…9F3a.

ketsuban:answer
terrible dictator
ketsuban:expiry
1791450862

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)" \
  0x05616c696365086b6574737562616e0365746800 \
  $(cast calldata "text(bytes32,string)" $(cast namehash alice.ketsuban.eth) "ketsuban:answer")

Share

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