This subgraph indexes Fenine Name Service contracts on the fenine network. It tracks the Fenine registry, base registrar, FEN registrar controller, name wrapper, and resolver events so ens-metadata-service can resolve domain metadata, registrations, wrapped names, and resolver text records.
The repo now includes a complete local stack for subgraph indexing:
postgresipfsgraph-node
Environment variables are defined in .env.example. Create .env from it and adjust values as needed.
Main variables:
POSTGRES_DBPOSTGRES_USERPOSTGRES_PASSWORDPOSTGRES_PORT=5433(host port; container tetap listen di5432)GRAPH_NODE_ETHEREUM=fenine:https://rpc.fene.appGRAPH_NODE_QUERY_PORT=8000GRAPH_NODE_ADMIN_PORT=8020IPFS_API_PORT=5001
Boot the stack:
docker compose up -dCreate and deploy the Fenine subgraph locally:
yarn create-local
yarn deploy-localThe deployed local endpoint used by ens-metadata-service is:
http://127.0.0.1:8000/subgraphs/name/fenine/fns
Here we have example queries, so that you don't have to type them in yourself eachtime in the graphiql playground:
{
domains {
id
labelName
labelhash
parent {
id
}
subdomains {
id
}
owner {
id
}
resolver {
id
}
ttl
}
resolvers {
id
address
domain {
id
}
events {
id
node
... on AddrChanged {
a
}
... on NameChanged {
name
}
... on AbiChanged {
contentType
}
... on PubkeyChanged {
x
y
}
... on TextChanged {
indexedKey
key
}
... on ContenthashChanged {
hash
}
... on InterfaceChanged {
interfaceID
implementer
}
... on AuthorisationChanged {
owner
target
isAuthorized
}
}
}
registrations(where: { labelName_not: null }, orderBy: expiryDate, orderDirection: asc, first: 10, skip: 0) {
expiryDate
labelName
domain{
name
labelName
}
}
}