The Scenario
A researcher in your team built a validator attribution study and left the company before finishing the cleanup pass. The handoff note says there are 60 rows in the sheet — some are ENS names like vitalik.eth, some are raw hex addresses — and all of them need to be resolved to their canonical form before the study can proceed. Nobody on the remaining team wants to touch it because the manual resolution process through beaconcha.in requires looking up each entry one at a time in a search box.
The bad version:
- Paste the first ENS name into the beaconcha.in search, copy the resolved address from the result page, paste into column B
- Move to the next row — except this one is a raw address, so the resolution direction is reversed and the search result looks different
- Hit row 31 and realize one of the ENS names resolves to multiple addresses, and you have no documented rule for which one to pick
Sixty lookups. Two different input formats. No clear resolution rule for edge cases. The study can't move until this is done.
The Easy Way: One Prompt in SheetXAI
SheetXAI is an AI agent that lives inside your Google Sheet. It reads each entry from column A, determines whether it's an ENS name or an address, calls Beaconchain's resolution endpoint in the right direction, and writes the resolved output to column B — for all 60 rows at once.
Resolve each ENS name or Ethereum address in column A of my sheet using Beaconchain and write the resolved address or ENS name to column B — process all 60 rows
What You Get
- Column B populated with the resolved canonical form for each input
- ENS names resolved to their primary Ethereum address
- Raw addresses resolved to their associated ENS name where one exists, or returned as-is if no ENS is registered
- Any entry that fails resolution gets a note in column C so you can investigate without losing the rest of the batch
What If the Data Is Not Quite Ready
Some entries in column A have extra whitespace or mixed case that might break resolution
Resolve ENS names and Ethereum addresses from column A using Beaconchain — trim whitespace and normalize to lowercase before resolution — write resolved output to column B and flag any entries that failed resolution in column C
You need to keep the original input in column A and put the resolved form alongside it without overwriting
Read ENS names and Ethereum addresses from column A — resolve each via Beaconchain — write the resolved form to column B, keeping the original in column A intact — mark rows where the resolved form differs from the input with CHANGED in column C
Some rows have entries that are neither valid ENS names nor valid Ethereum addresses
Resolve entries from column A via Beaconchain — write resolved form to column B — for any row where the entry is not a valid ENS name or Ethereum address, write INVALID INPUT to column B and skip the Beaconchain call
Pull the resolved addresses and then enrich each one with its current ETH balance in a single pass
Resolve all entries in column A via Beaconchain and write resolved form to column B — then for each resolved Ethereum address, fetch the current ETH balance from Beaconchain and write to column C, denominated in ETH
Combining resolution and enrichment in one instruction means the study gets a complete attribution table without a second round of lookups.
Try It
Get the 7-day free trial of SheetXAI and open the validator attribution sheet with your mixed ENS and address list in column A, then ask SheetXAI to resolve all 60 rows. You might also want the spoke on mapping ERC-20 holdings per address once the resolution step is done, and the hub page covers all Beaconchain workflows.