4 agents across 3 wallets
answeredThe document was fetched and read.
the document
- record hash
- 9b09a1c69f53d242_92
- scheme
- http
- what it answered
- 697 bytes read from http
- asked at
- 2026-11-06 03:38:39Z
- size
- 697 bytes
- name it gives itself
- Seneca
- first registered
- block 55,558,733
check it yourself
curl -sS -o /dev/null -w '%{http_code}\n' 'https://raw.githubusercontent.com/SakshiShah29/The-Agora/main/contracts/metadata/seneca.json'who registered against it
1 of these registrations came from a wallet that registered more than one agent against this same document.
Counted at registration time, not from who holds the token now. An agent is an ERC-721 and ownership moves, so a live aggregate would answer "who holds these today" when the claim being made is about who registered them.
re-derive this
$2 = 9b09a1c69f53d242_92
SELECT owner, "agentCount", "firstSeenBlock" FROM "AgentRecordOwner" WHERE "chainId" = $1 AND record_id = $2 ORDER BY "agentCount" DESC, "firstSeenBlock" ASC LIMIT $3
who funded these wallets, from Nansen
1 of 1 sampled wallets were first funded by 0xab3a…4345. 1 distinct funder across the sample.
one funding tx: 0xe959ed668c…
A shared funder describes how the wallets were set up, not anyone's intent. It does say the wallet count overstates the number of independent operators. Unsampled wallets are unknown, never counted either way.
the agents
4 agents point at this one document.
Brighter means the agent carries at least one feedback. Faint means nothing has ever been said about it.
re-derive this
$2 = 9b09a1c69f53d242_92
SELECT a.id, a."agentId", a.owner, a."agentWallet", a."registeredAtBlock",
coalesce(fb.total, 0) AS feedback_count
FROM "Agent" a
LEFT JOIN (SELECT agent_id, count(*) AS total FROM "Feedback" WHERE "chainId" = $1 GROUP BY agent_id) fb
ON fb.agent_id = a.id
WHERE a."chainId" = $1 AND a."uriHash" = $2
ORDER BY a."agentId" ASC
LIMIT $3 OFFSET $4