tims-friend-test.ketsuban.eth
Friend of Tims
https://Friends.comsybil signal · reading the graph…
wallet 0x686F…9203
67/100
- References0 of 30/30
- Humanityproved25/25
- Nameclaimed20/20
- Accounts3 attested15/15
- Profile2 of 3 filled7/10
Answers
- What do you think of Kim Jong Un?
tims-friend-test.kju-is.ketsuban.eth - “Very bad bad person” valid until 2026-10-12 09:54Z
Linked accounts
x.comverified, masked — needs a view code ·tims-friend-test.com.x.private-www.ketsuban.ethgithub.comverified, masked — needs a view code ·tims-friend-test.com.github.private-www.ketsuban.ethgmail.comverified, masked — needs a view code ·tims-friend-test.com.gmail.private@.ketsuban.eth
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/tims-friend-test.ketsuban.eth · GET https://2.ketsuban-api.peeramid.xyz/v1/vouches/tims-friend-test
Read it yourself, through ENS
The UniversalResolver at 0x4A18…3C70 walked the registry to 0x178f…215e and returned 0x686F…9203.
ketsuban:expiry- 1791798255
ketsuban:humanity- selfie
description- Friend of Tims
url- https://Friends.com
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)" \
0x1074696d732d667269656e642d74657374086b6574737562616e0365746800 \
$(cast calldata "text(bytes32,string)" $(cast namehash tims-friend-test.ketsuban.eth) "ketsuban:expiry")Share
Verify me at Ketsuban: https://2.ketsuban.peeramid.xyz/p/tims-friend-test — on-chain name tims-friend-test.ketsuban.eth