PAYANY.LINK

Problem Statement

This project uses tools like ENS and other bridging technologies under LiFi. Fiat settlement by paypal and stablecoin settlement layer by PYUSD. How it works:User visits: vitalik.eth.payany.linkMiddleware detects subdomain: "vitalik.eth"Rewrites to: /sub/vitalik.ethDynamic route handles: /app/sub/[ens_or_address]/page.tsxIf you don't find the ens you are looking for you can still fuzzy search from our own indexing Next thing we enable is payments. Crypto Payments**: Native Web3 wallet integrationFiat Integration: PayPal payments via PYUSD facilitatorCross-Chain: Automatic bridging between networks

Solution

The project uses a typescript convex powered backend, in a turbo monorepo setup. With a next js frontend setup. A shadcn + tailwind UI setup. The "Particularly Hacky" Stuff Worth MentioningThe Subdomain Routing Hack- TThe most innovative part in terms of UX is thesubdomain-to-ENS routing system. This was actually quite tricky to implement correctly: Since we had a issue with DNS allowing wildcard in their top level sub domains.The AI-Powered ENS Search- RAG Implementation The Problem** We had 25,000+ ENS profiles in CSV format and neededsemantic search- not just text matching.The Solution: Custom RAG with Convex + Google AII had to invented a new 402 plus standard in order to open to the possibilities of accepting multiple currencies in both crypto and fiat across any chain.