Indexing Mirror.xyz
If you read content online you’ve probably at least heard of publishing services like Medium and Substack. These are centralized, web2 companies that make money with views; subscriptions, ads, etc. Thankfully, as we transition into the web3 space we are already seeing some promising alternatives. The largest of these web3 publishers is Mirror. The beauty of protocols like Mirror is that they don’t own any of the data. They still have a login, a clean text editor, and shareable links just like...
Devcon VI and the State of EVM Data
By all measures, Devcon VI was a huge success. Over 6000 participants from around the world met in Bogota, Colombia to build, network, and celebrate together in the official Ethereum conference. This is coming about a month after The Merge in which Ethereum switched from Proof of Work (PoW) to Proof of Stake (PoS). That transition worked far better than any could have hoped and has lead to ETH even being deflationary at times 🔥https://ultrasound.money/So what’s next for Ethereum and its ecos...

Accessing Data 3.0: Indexing 101
This is an entry in our long running series, “Accessing Data 3.0”, where we talk about the “whats” and the “hows” of working with data in web3. Enjoy! Remember libraries? The walls of books and the fearless librarians somehow always knowing exactly where everything is. Well, two things: 1) libraries still exist, 2) those libraries are each indexed. Librarians around the world categorize all of the books under their purview into what are known as a “library catalogs”. These catalogs serve as a...
Paving the road to Data 3.0 one index at a time
Indexing Mirror.xyz
If you read content online you’ve probably at least heard of publishing services like Medium and Substack. These are centralized, web2 companies that make money with views; subscriptions, ads, etc. Thankfully, as we transition into the web3 space we are already seeing some promising alternatives. The largest of these web3 publishers is Mirror. The beauty of protocols like Mirror is that they don’t own any of the data. They still have a login, a clean text editor, and shareable links just like...
Devcon VI and the State of EVM Data
By all measures, Devcon VI was a huge success. Over 6000 participants from around the world met in Bogota, Colombia to build, network, and celebrate together in the official Ethereum conference. This is coming about a month after The Merge in which Ethereum switched from Proof of Work (PoW) to Proof of Stake (PoS). That transition worked far better than any could have hoped and has lead to ETH even being deflationary at times 🔥https://ultrasound.money/So what’s next for Ethereum and its ecos...

Accessing Data 3.0: Indexing 101
This is an entry in our long running series, “Accessing Data 3.0”, where we talk about the “whats” and the “hows” of working with data in web3. Enjoy! Remember libraries? The walls of books and the fearless librarians somehow always knowing exactly where everything is. Well, two things: 1) libraries still exist, 2) those libraries are each indexed. Librarians around the world categorize all of the books under their purview into what are known as a “library catalogs”. These catalogs serve as a...
Paving the road to Data 3.0 one index at a time

Subscribe to The Indexing Company

Subscribe to The Indexing Company
Share Dialog
Share Dialog
Here at Indexing Co we’ve been spending the holiday season onboarding our first customers and getting our infrastructure into production 🎉 And as a holiday gift for web3 builders, we’re releasing our ENS Profile API to the public. No sign up required, no tracking, and completely free. Seriously!

This is the same API that powers our ENS Profile search tool, What’s my name again, and is backed by our real-time indexing engine. You can access it via GraphQL at https://query.indexing.co/graphql with the following schema:
type ENSProfileAddresses {
address: String
coinType: Int
}
type ENSProfileAttributes {
textKey: String
textValue: String
}
type ENSProfile {
addresses: [ENSProfileAddresses!]
attributes: [ENSProfileAttributes!]
contenthash: String
name: String
node: String
owner: String
tokenId: String
}
input ENSProfileFilter {
name: String
node: String
owner: String
textValue: String
tokenId: String
}
type Query {
ensProfiles(filters: ENSProfileFilter): [ENSProfile!]!
}
For example, to grab the current profile for vitalik.eth you could simply do:
query {
ensProfiles(
filters: {
name: "vitalik.eth"
}
) {
addresses {
address
coinType
}
attributes {
textKey
textValue
}
contenthash
name
owner
}
}
Which would return:
{
"data": {
"ensProfiles": [
{
"addresses": [
{
"address": "0xd8da6bf26964af9d7eed9e03e53415d37aa96045",
"coinType": 60
}
],
"attributes": [
{
"textKey": "avatar",
"textValue": "eip155:1/erc1155:0xb32979486938aa9694bfc898f35dbed459f44424/10063"
},
{
"textKey": "url",
"textValue": "https://vitalik.ca"
}
],
"contenthash": "0xe3010170122081e99109634060bae2c1e3f359cda33b2232152b0e010baf6f592a39ca228850",
"name": "vitalik.eth",
"owner": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"
}
]
}
}
Give it a try and let us know how it goes! And if you find yourself needing anything extra / different, don’t hesitate to reach out - we’re always looking for ways to improve our offerings and empower the builders in web3.
Here at Indexing Co we’ve been spending the holiday season onboarding our first customers and getting our infrastructure into production 🎉 And as a holiday gift for web3 builders, we’re releasing our ENS Profile API to the public. No sign up required, no tracking, and completely free. Seriously!

This is the same API that powers our ENS Profile search tool, What’s my name again, and is backed by our real-time indexing engine. You can access it via GraphQL at https://query.indexing.co/graphql with the following schema:
type ENSProfileAddresses {
address: String
coinType: Int
}
type ENSProfileAttributes {
textKey: String
textValue: String
}
type ENSProfile {
addresses: [ENSProfileAddresses!]
attributes: [ENSProfileAttributes!]
contenthash: String
name: String
node: String
owner: String
tokenId: String
}
input ENSProfileFilter {
name: String
node: String
owner: String
textValue: String
tokenId: String
}
type Query {
ensProfiles(filters: ENSProfileFilter): [ENSProfile!]!
}
For example, to grab the current profile for vitalik.eth you could simply do:
query {
ensProfiles(
filters: {
name: "vitalik.eth"
}
) {
addresses {
address
coinType
}
attributes {
textKey
textValue
}
contenthash
name
owner
}
}
Which would return:
{
"data": {
"ensProfiles": [
{
"addresses": [
{
"address": "0xd8da6bf26964af9d7eed9e03e53415d37aa96045",
"coinType": 60
}
],
"attributes": [
{
"textKey": "avatar",
"textValue": "eip155:1/erc1155:0xb32979486938aa9694bfc898f35dbed459f44424/10063"
},
{
"textKey": "url",
"textValue": "https://vitalik.ca"
}
],
"contenthash": "0xe3010170122081e99109634060bae2c1e3f359cda33b2232152b0e010baf6f592a39ca228850",
"name": "vitalik.eth",
"owner": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"
}
]
}
}
Give it a try and let us know how it goes! And if you find yourself needing anything extra / different, don’t hesitate to reach out - we’re always looking for ways to improve our offerings and empower the builders in web3.
<100 subscribers
<100 subscribers
No activity yet