ketsuban

test-account-123456.ketsuban.eth

sybil signal · reading the graph…

wallet 0x14fc…291E

  • References1 of 310/30
  • Humanitynot proved0/25
  • Nameclaimed20/20
  • Accounts2 attested15/15
  • Profile0 of 3 filled0/10

Answers

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

Linked accounts

  • google verified, masked — needs a view code
  • email verified, masked — needs a view code

References received

unsolicited means no invitation from test-account-123456 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 test-account-123456 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/test-account-123456.ketsuban.eth · GET https://2.ketsuban-api.peeramid.xyz/v1/vouches/test-account-123456

Read it yourself, through ENS

The UniversalResolver at 0x4A18…3C70 walked the registry to 0x178f…215e and returned 0x14fc…291E.

ketsuban:expiry
1791557109

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)" \
  0x13746573742d6163636f756e742d313233343536086b6574737562616e0365746800 \
  $(cast calldata "text(bytes32,string)" $(cast namehash test-account-123456.ketsuban.eth) "ketsuban:expiry")

Share

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