Fluidkey ENS

PROJECT NAME

Fluidkey ENS

DESCRIPTION OF THE PROJECT (2 lines)

Start receiving private payments the simple way with an offchain ENS resolving your stealth addresses. Users get a free fkey.eth ENS subdomain when connecting to the app and can use it to receive stealth payments from it, which can all be accessed via our app.

DISCORD AND TELEGRAM USER NAME (team contact to share the judging details)

Discord: 0xmetony

Telegram: t0nit

REPOSITORY WITH PROJECT'S CODE (should be open and public)

https://github.com/fluidkey/eth-rome-23

VIDEO DEMO (3 min max) - NO SLIDES ONLY PROJECT DEMO SHOWCASE

https://www.loom.com/share/9b2fd873ecd94b819c0f5e20131377f4

The contract address(es) or website URLs of your deployed application, either on a testnet of your choice or mainnet of a platform of choice. 📂📂 (NOT mandatory)

ethrome.fluidkey.com

Bounties (provide a description or explanation on how you integrated any bounty sponsors technology - add them also on categories)

ENS: our innovation lies in using user-specific ENS subdomains connected to an offchain resolver to receive private payments while keeping a static, widely compatible and human readable identity. Every time the ENS is queried, a new stealth address owned by the user is generated and returned.

Base: we are bringing privacy to Base in a user-friendly way - users can keep sending payments to a single ENS per recipient, while benefiting from increased privacy for both the sender and the recipient. 

If your project was started before the ETHRome hackathon, please link here a PUBLIC Google Doc describing all the previous iterations in details (make sure to check the hackathon rules around pre-existing projects)

The app created during the hackathon was created from scratch and brings an innovation we haven't worked on before. We have had some experience working with stealth addresses over the past weeks but have not reused any code except for open source repositories like noble-secp256k1.