ENSplit

ENSplit is a DeFi payment-splitting protocol that transforms ENS names into programmable payment routers. Instead of locking payout logic into immutable smart contracts—which require expensive redeployments whenever a team member changes—ENSplit reads payment rules directly from live ENS text records.

The Problem It Solves Managing on-chain payroll and treasury splits is currently rigid and operationally intensive. Organizations often rely on manual multi-sends or static splitter contracts that become obsolete the moment a contributor creates a new wallet or leaves the project.

How It Works Organizations configure their payout splits as standard text records on their ENS name (e.g., split.dev=40%, split.dao=60%). When a payer sends funds to that ENS name through the ENSplit interface, the protocol:

Resolves the ENS name in real-time. Parses the text records to determine recipients and percentages. Executes the split automatically in a single transaction. Key Innovations

Dynamic Operations: Change your entire payment structure instantly by updating ENS records—no code required. Zero-Contract Ops: Eliminates the need to write or audit new payment splitter contracts for every organizational change. Human-Readable Configuration: Treasurers and signers can audit payment flows by simply reading the ENS record, making crypto payments more transparent and accessible. Built with a focus on UX and operational efficiency, ENSplit makes complex payment routing as simple as updating a domain record.

Step Id: 181 ENSplit was architected as a lightweight, frontend-first solution to enable dynamic payment routing without complex smart contract management.

Core Architecture & Technologies

Frontend Logic: Built with vanilla JavaScript managed by Vite for a highly optimized, dependency-minimal build. I avoided heavy frameworks to keep the interaction layer fast and auditable. ENS Integration: The core innovation lies in treating ENS text records as a configuration database. I implemented a custom parsing engine that queries specific keys (e.g., split.engineer, split.designer.percent) directly from the ENS resolver contract. Simulated Testnet Environment: For this hackathon demo, I built a TestENSProvider class that mocks the Ethereum Name Service resolution process. This allows users to experience the entire flow—configuring splits, resolving names, and executing payments—instantaneously on a local testnet-like environment without needing Mainnet ETH or waiting for transaction confirmations. Notable Implementation Details The most "hacky" yet effective part of the build is the live reconfiguration system. Instead of storing state in a database or local storage, the application state is derived purely from the "on-chain" (simulated) ENS records. When a user updates a split configuration in the UI, it writes directly to the mock ENS registry. The next payment transaction then reads from this updated registry in real-time. This perfectly mimics how the production version would work: relying on ENS as the single source of truth for organizational structure.

Design System I implemented a custom styling system using CSS variables and modern layout techniques (Grid/Flexbox) to achieve a high-performance, glassmorphism-inspired UI. This ensures the application feels premium and responsive while maintained in a single, clean stylesheet.