Service Provider Stream Nomination Thread

💬 General Discussion
6

2947×648 138 KB

NAME AND WEBSITE:

namesys.eth (namesys.eth.limo | namesys.xyz)

POINT OF CONTACT:

dev.namesys.eth (== sshmatrix.eth)

WHAT DO YOU WANT TO BUILD ON ENS?

NameSys is a Research & Development Cooperative dedicated to creating cost-efficient, open-source and accessible cryptonative products, helping scale ENS adoption through immediate and tangible benefits to end users. High gas fees have been a burden on the accessibility of Ethereum and ENS for a while now. NameSys attempts to resolve these gas issues by developing secure off-chain infrastructures that can replace some of the on-chain functionailties of ENS domains, in particular the Resolver. This on-chain to off-chain offloading has massive impact on the overall gas overhead for managing and truly utilising an ENS name. CCIP-Read (EIP-3668) and ENS Wildcard Resolution (ENSIP-10) form the backbone of most of the NameSys infrastructure.

The on-chain to off-chain offloading of the Resolver has several beneficial features other than the cost efficiency. For instance, no-cost dynamic off-chain content can now be injected in ENS Records to replace the static and expensive on-chain content. This feature is most impactful in the ENS Contenthash Field (ENSIP-07) responsible for decentralised web content. NameSys infrastructure makes it possible to render dynamic web-content in Contenthash at zero cost! This development has the potential to drastically expand the usecases emerging from ENS Contenthash.

Our approximate projected development path consists of the following throughout 2024:

CORE INFRASTRUCTURE

  • NameSys.eth : ENS Off-Chain Records Manager

    Off-Chain Records are NameSys’s core premise. NameSys’s Record Manager infrastructure (including the on-chain Resolver) could be much more efficient and upgradeable than its current form. In particular, work is well underway for a permanent migration to Universal v2 Resolver employing carbon-wrapping (EIP-2535) and proxying for upgradeability.

  • dAppSys.eth : dApp Store for ENS Domains

    NameSys’s Off-Chain infrastructure can be bootstrapped to provide a dApp Store-like feature where users can ‘install’ a dApp by posting a signed ENS Record, and then access the installed dApp at dapp.domain.eth. On-chain codebase for this feature is already deployed in CCIP2.eth v1.

  • notAPI.eth : Serverless GET-Only JSON API using ENS Wildcard Resolution & On-Chain Data.

    Work is in progress on a fully on-chain API (a contract) that returns JSON responses to queries formatted as subdomains, e.g. https://erc20.dai.balanceof.<0xaddress>.notapi.eth.limo shall return the DAI (ERC20) balance of an arbitrary <0xaddress>.

  • htmx3.eth : On-Chain HTMX Generator using ENS Wildcard Resolution and On-Chain Data.

    HTMX Generator contract forms the infrastructural core to rendering dynamic dwebsite content in ENS Contanthash in data:uri format using only on-chain data. Discussion of a generic implementation is available here.

  • namesys.js : Open-Source Library for implementing NameSys Infrastructure.

    End-to-end library to simplify native integration of NameSys infrastructure into marketplace clients, registrars and domain managers.

IPFS + ENS SERVICES

  • ipns.eth : Public and free-to-use IPFS & IPNS Hosting, Publishing and Pinning Service with Keyless Record Management for ENS Domains. To this effect, NameSys has deployed its own fork of w3name API and re-publisher service on Cloudflare for IPNS (re)broadcasting. This service will be developed with the ability to sync to IPFS Network and/or L2 Events or Data.

    4775×4353 660 KB

OTHER SIDE PROJECTS

  • ENS & Lightning Bitcoin Compatibility. See the prototype implementation here.
  • IPLD Integration in ENS Contenthash and other relevant fields. See example implementation here.
  • Research & Standards work for ENS. See an example here.

†FUTURISTIC STUFF

  • ZK Proofs as ENS Records
  • Off-Chain 2PC and MPC using ENS
  • ENS & Secure NFC Hardware Stack for RWA

† not covered by this stream

PAST EXPERIENCE WORKING ON ENS

The team behind NameSys has been part of the Ethereum & ENS ecosystem for several years, and have already built useful infrastructure benefitting ENS, Ethereum and in some cases even generic crypto users. While NameSys is mostly known for its Off-Chain Records infrastructure, the team behind it has created an array of protocols and products in the past. Here goes:

NameSys.eth STACK

ENS Off-Chain Records Manager stack (Web Client + Support Services) with support for web3 IPFS and traditional web2 server for storage. Web Client can be accessed here.

CCIP2.eth RESOLVER

Gasless Resolver for Off-Chain Records which functions adjacent to the Web Client

DOSTR.eth ADAPTOR

DOSTR is an ENS-aware Ethereum Adaptor for NOSTR Network which allows it to function with Ethereum wallets. At its heart lies a seamless Key Generation Algorithm that interfaces the Bitcoin-native Schnorr Signature scheme and the Ethereum-native secp256k1 scheme.

IPFS2.eth GATEWAY

Web3 IPFS Gateway IPFS2.eth.limo that uses ENS Wildcard Resolution (ENSIP-10) to resolve IPFS, IPNS or IPLD content.

isTest.eth BRIDGE

Testnet-to-Mainnet Resolver (or vice-versa) for ENS Contenthash. Simply render your Testnet (Goerli) Contenthash for domain.eth on Mainnet as a subdomain domain.istest.eth

Helix2.eth ABSTRACTION

ENS-compatible Link Service Protocol that allows for multi-party linking in configurable spaces.

ed25519-keygen/ipns LIBRARY

Contributed IPNS base36 CID support in paulmillr/ed25519-keygen library

SIZE OF TEAM AND COMMITMENT

  • Two full-time Cryptographers & Engineers (sshmatrix.eth & freetib.eth)
  • One Social & Public Relations Manager (part-time)
  • One Frontend Web Developer (full-time)†
  • One Backend & SRE Developer (full-time)†
  • One Media Developer & Designer (part-time)†

† to be hired when or if funds are available

FURTHER INFORMATION AND LINKS:

CONFLICT OF INTEREST STATEMENT:

There is no conflict since none of the NameSys team members are part of the ENS DAO admininstration or ENS delegates. In the past, NameSys has received

  • $10,000 USD through a systematic grant from ENS DAO Ecosystem WG in Term 4, and
  • 0.7 ETH in Small Grants Ecosystem WG Round 10.

10k ENDORSEMENT LINK:

https://snapshot.org/#/nominations.ens.eth/proposal/0x64fbc81a7ab8b57deea798df03141fa1b7d1f2fce6f1051b580e568ca89e8070

BUGDET REQUESTED:

We are requesting $200,000 USD/year for a team of 3-4 full-time individuals and 1-2 part-time contractors. Open Grants are the sole source of revenue for NameSys and all related development work.

SUMMARY FOR SNAPSHOT

NameSys is a Research & Development Cooperative dedicated to creating cost-efficient, open-source and accessible cryptosystems, helping scale ENS adoption through immediate and tangible benefits to end users. NameSys in particular attempts to lower or eliminate gas costs by developing secure off-chain infrastructures that can securely replace some of the on-chain functionalities of ENS domains such as the Resolver. This significantly reduces the gas overhead for managing and utilising your ENS names. NameSys framework consists of remarkable gas-free features such as Bulk Records (v1), Stealth(iest) Payments to ENS domains (v1), Dynamic dWebsites (v2), Dynamic Records (v2) and more! Our requested stream of $200,000 per year for 3-4 full-time engineers & 1-2 part-time support staff will allow us to continue our work on NameSys upgrade from v1 to v2 while also focusing on integrating NameSys infrastructure into ENS-dedicated services such as marketplaces, registrars and domain managers.

Link to full proposal: t/service-provider-stream-nomination-thread/6

ALIGNMENT MATRIX

Nominee Open-source?* VC-funded?** Project Launched Already? ENS-dedicated?† Amount Requested Prior ENS DAO Grants? (total amount)
NameSys :white_check_mark: :x: :white_check_mark: :white_check_mark: $200,000 :white_check_mark: $10,000 + 0.7 ETH
10 Likes