Inspiration

The Nostr and Lightning Network communities overlap heavily, but there's no easy way to bridge the two — to search a Lightning node and see who's behind it on Nostr, or to look up a Nostr identity and see their node's standing on the network. We wanted to build a tool the wider Nostr community could actually use, and one that's genuinely built for the agent-native web this hackathon is exploring — not just a human-facing dashboard, but a site AI agents can query and act on directly.

What it does

Lightning Network Explorer lets you:

  • Search Lightning nodes by pubkey or alias, with capacity, channel count, and network scoring pulled from Amboss
  • View detailed node stats on a per-node basis
  • See network-wide stats — total nodes, channels, and capacity
  • Match a Nostr identity (npub or NIP-05) to its associated Lightning address and node data, resolved live against our own relay (wss://hasky.chat)

With WebMCP support, an AI agent can call these same lookups directly — searching a node, pulling network stats, or resolving a Nostr identity's Lightning presence — without needing a human to click through the UI first.

How we built it

Built with Next.js, TypeScript, and Tailwind. Node and network data comes from the Amboss GraphQL API; Nostr profile resolution runs against our own relay at wss://hasky.chat. WebMCP tools are registered via document.modelContext.register(), exposing node search, node detail, and network stats directly to agents.

Challenges we ran into

Getting clean fallback behavior for malformed or unknown pubkeys (Amboss returns a GraphQL error rather than a clean "not found," which we had to handle gracefully), and designing the Nostr × Lightning matcher so it degrades sensibly when no match is found rather than treating that as an error state.

What's next

Deeper zap/wallet interactions via Alby Hub and NWC, historical trend charts for network growth, and expanding node scoring with more data sources.

Built With

Share this project:

Updates

Submission history