Additional Accelerated Resolvers

[shrugs]

closes #1488

I ran the following query to identify the most popular resolvers, including single-depth wildcards and added the missing resolvers (if static) to the mainnet datasource and the static resolver config

-- Count domains by effective resolver with source breakdown
SELECT 
    COALESCE(r.address, parent_r.address) AS effective_resolver,
    COUNT(*) AS total_count,
    COUNT(r.address) AS direct_count,
    COUNT(*) FILTER (WHERE r.address IS NULL AND parent_r.address IS NOT NULL) AS inherited_count
FROM "alphaSchema1.3.1".subgraph_domains d
LEFT JOIN "alphaSchema1.3.1".subgraph_resolvers r ON d.resolver_id = r.id
LEFT JOIN "alphaSchema1.3.1".subgraph_domains parent ON d.parent_id = parent.id
LEFT JOIN "alphaSchema1.3.1".subgraph_resolvers parent_r ON parent.resolver_id = parent_r.id
WHERE COALESCE(r.address, parent_r.address) IS NOT NULL
GROUP BY COALESCE(r.address, parent_r.address)
ORDER BY total_count DESC;

Summary

• added argent and loopring resolvers to mainnet static resolver acceleration
• added three more historical default public resolvers (0, 1, 2) to mainnet for legacy event handling
• added lineanames default public resolver and threedns resolvers to static acceleration
• renumbered default public resolvers to sequential naming (0-5 instead of 1-3)

---

Why

• accelerates protocol queries for more resolvers

---

Testing

• no runtime behavior changes - only adds additional resolvers to existing acceleration logic
• manually reviewed contracts to confirm static-ness
• naming changes are mechanical renames

---

Checklist

• This PR does not change runtime behavior or semantics
• This PR is low-risk and safe to review quickly

[changeset-bot]

⚠️ No Changeset found

Latest commit: c39b0a9

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
admin.ensnode.io	Ready	Preview, Comment	Jan 7, 2026 11:09pm
ensnode.io	Ready	Preview, Comment	Jan 7, 2026 11:09pm
ensrainbow.io	Ready	Preview, Comment	Jan 7, 2026 11:09pm

[lightwalker-eth]

@shrugs Looks awesome 🚀