I build tools that put naming ownership back in users' hands. No cloud gatekeepers. Self-hosted infrastructure.
|
|
The real challenge: handling providers that silently fail (returning
nullinstead of an error) while keeping response times acceptable for the user.Multiple providers · Multiple blockchains · Different failure modes · One search bar
More Web2 & Web3 domain utilities are in the works. Everything a domain owner needs, in one place.
🔍 Audit methodology / I audit my own code before shipping
| Axe | What I check | |
|---|---|---|
| 🛡️ | Reliability | Retry, fallback, circuit breaker, cache. Every failure path covered? |
| ⚡ | Performance | Time budget per resolution path, redundant RPC calls, timeout calibration |
| 🔒 | Security | XSS via on-chain records, input validation, no client-side secrets, CSP |
| ⚙️ | Maintainability | Coupling with third-party libs, technical debt, error handling consistency |
| ✅ | Correctness | Owner vs manager vs resolved address, stale cache, race conditions |
| 🔬 | Edge cases | Expired domains, 100+ domain wallets, ad-blockers, empty records |
| 🎨 | UX under constraint | Progressive feedback during 3-10s waits, skeleton loading, typed errors |
| 📊 | Observability | Sentry breadcrumbs, error rates by provider, Discord user feedback |
| 🖥️ | Browser compat | Ad-blocker vs RPCs, neutral URL choices, no wallet extension needed |