Term 2 Grants - Summary

This thread is an ongoing summary of grants by Ecosystem Working Group for the second term.

This is not the place to request grants. To request a grant please reach out to @slobo.eth on the forum or on twitter (https://twitter.com/AlexSlobodnik). Discussion of any items in this thread will also occur on the weekly ecosystem calls (cal link).

Below is a sample post that is required of every project receiving a grant, it will evolve over time. The working group or a subgroup sets the amount of fund disbursed.

Grants are giving for work completed. The vast majority of grants will be given retroactively with proof of value added to the ENS ecosystem as in the example post below.

Nimi

Author: @dave-nimi
Date: August 2022

Project: nimi.eth.limo

About:

What is Nimi.eth?

Nimi.eth started as a hackathon project at ETH Amsterdam 2022. The basic idea behind Nimi was to make it easier for users to host content on their ENS domain! Currently Nimi could be thought of as a “Linktree for web3”. But that’s just the beginning! We want to act as your web3 connector - aggregating all your favourite parts of web3 and hosting them on your ENS domain!

Nimi presentation (includes latest release notes): https://nimi.mypinata.cloud/ipfs/QmbS4uqbuaoT5DmoA2kwJ3EQd7cELJL7gj6EPabffCZsUz

Rationale

Currently just 0.65% of ENS domains have a content hash set: Dune of those that have a content hash set 5% are Nimi pages - demonstrating a strong user interest in hosting on their ENS. The spike in July was in large part due to folks registering on Nimi.

Our goal is to get users to use their ENS for hosting content and allowing them to use it as a regular domain. With the grant we want to expand functionality and features to attract more users to setup their Nimi page as well as increasing user engagement.

Steward Commentary: A grant of 15,000 USDC + 100 ENS has been approved, with the payment split into two parts. After conversations with @neiman of .eth subgroup, we determined that the first payment will amount to 8,000 USDC + 100 ENS. The remaining 7,000 USDC will be distributed at the discretion of the ecosystem stewards, with the intention of the remainder being distributed after a mid term update.

15 Likes

Slobo.eth requested we post here.

What is ENSAcademy.eth?

ENSA aims to accelerate the adoption of ENS worldwide.

We bring ENS experts and web3 entrepreneurs to share their knowledge with the global community. Our goal is to educate, support, and empower anyone who can benefit from this technology.

We built a platform where we can all learn the fundamentals, skills, and possibilities of ENS. We currently provide focused interviews in the form of Twitter spaces/podcasts and educational content through our ENSA forum, which adds value to the community.

What we do:

  • Recurring Twitter spaces on focused topics with Q&A sessions.
  • All our interviews are uploaded to our podcast (iTunes, Spotify).
  • Publish daily threads/posts covering all ENS-related topics and categories on our Twitter and forum.
  • List verified ENS resources, best practices, and FAQs.
  • Create a network with ENS experts, entrepreneurs, and builders.

Topics we cover:

  • ENS Fundamentals:
    • Best Practices
    • How-to Content
    • ENS Use Cases
    • Integrations
  • Industry News
  • ENS Tools
  • Subdomains
  • ENS Website Building & Deployment
  • ENS Security & Legal
  • ENS Sales & Brokering

Since launching in June, here is what we accomplished:

  • 21 interviews on a variety of topics via Twitter spaces that are now uploaded to our podcast.
    • Over 6k tuned in to Twitter spaces with our latest episode having over 500 listeners.
    • 600+ podcast downloads.
    • Backlog of interviews schedule weeks in advance
  • Over 60 forum posts collecting 11k+ page views.

We need funding to pay for the following:

  • The monthly cost for hosting our podcast, forum, and website. This costs us over 200$/month currently.
  • Content writers to create educational long-form ENS content.
  • Forum moderators to ensure quality content and eliminate any fraudulent posts or scams.
  • Dev resources.
    • To migrate the forum to be self-hosted and integrate sign-in with Ethereum (SIWE).
    • Add new features and upgrades to the forum experience, such as chat and other UX improvements.
  • New equipment to improve our podcast quality and introduce video podcast to publish on YouTube and other platforms.
  • A budget for marketing and promoting our platform.

Links:

Website:

Forum:

iTunes:

Spotify:

Steward Commentary: A grant of 20,000 USDC + 100 ENS has been approved, with the payment split into two parts. The first payment will amount to 8,000 USDC + 100 ENS. The remaining 12,000 USDC will be distributed at the discretion of the ecosystem stewards, with the intention of the remainder being distributed after a mid term update.

Update December 2022: After further consideration, we decided to not disburse the discretionary 12,000 USDC part of the grant.

ENS Academy multi channel (forum, twitter, podcasts) content is a boon to the ecosystem. The content educates existing members and on-board new ones. We are happy to support this effort.

6 Likes

About:

What is ETH.LIMO (LIMO)?

LIMO is an ENS enabled IPFS gateway with a strong focus on user privacy and security. LIMO represents a shift in dweb adoption by providing an alternative means of accessing ENS resolvable domains. Prior to LIMO, Cloudflare’s eth.link service was the only public service for bridging web2 and web3. LIMO takes public gateway services a step further by enforcing strong privacy guarantees such as never logging IP addresses or engaging in TCP fingerprinting. Limo now actively blocks FLoC (Federated Learning of Cohorts). This is a Google developed algorithm that tracks and correlates users based on their browsing history. FLoC enables advanced fingerprinting capabilities and greatly undermines online privacy and anonymity.

On average at any given moment there are 300+ concurrent connections to the gateway with traffic occasionally spiking to over 2000+ connections if Vitalik or another popular personality tweets an eth.limo URL.

Rationale:

  1. As it stands, there was a single ENS/IPFS gateway operator: Cloudflare. Uptime and availability were plaguing dweb adoption. The spirit and ethos of decentralization had ironically been compromised by relying upon a single corporate entity to provide critical transitional infrastructure from web2 to web3. In addition to the threats posed by centralization, there was no accountability or public influence when it came to governing the eth.link service.

  2. Web3 provides new challenges and opportunities for safely and reliably testing dweb deployments in a cost effective manner. Existing web2 tooling is inadequate and fails to provide the same experience and functionality for the web3 ecosystem.

  3. Modern browser integrations still rely on Infura RPC calls by default which leaves a lot to be desired in regards to user privacy.

The LIMO project is organized around the following founding principles:
1. Operate ETH.LIMO as a public good.
2. Establish community governance and oversight.
a. Provide support and technical guidance for builders and users.
3. Work towards building a truly decentralized ENS/IPFS gateway service and global CDN.
4. Build a world-class developer platform for dweb sites, including integrated analytics reporting and traffic management deployment tooling for commonly used web2 patterns such as A/B testing, canary and blue/green deployments.
5. A commitment to open source software and the advancement of web3 through education, best practices, evangelism, and public accessibility.

Contenthash growth is moving at a rapid pace!

Recent Updates:

We have been working hard to improve the performance and reliability of our service while adding new features based on community feedback. We are happy to announce that we now support the following enhancements.

  • Cross Chain Interoperability Protocol (CCIP) and ENSIP-10 wildcards. CCIP is an important advancement for ENS resolution across chains. The eth.limo service is now able to resolve names on any L2 or chain that properly implements the CCIP gateway resolver service. Test it out with https://offchainexample.eth.limo.
  • Automated, on-demand certificates for ENS subdomains. Once you submit an HTTPS request for your name (i.e. https://foo.bar.eth.limo), we’ll attempt to issue the certificate in the background. Usually this process takes 1-2m and during that time you might need to keep refreshing the page in your browser. This is a one-time process and once the certificate has been issued you’ll be able to visit your subdomain on eth.limo.
  • Skynet storage support - In addition to IPFS and IPNS, Skynet accessible content can now be resolved. More information can be found here.
  • IPv6 support - All eth.limo loadbalancers now support both IPv4 and IPv6. This greatly reduces latency for mobile devices.
  • IPFS peering with all major content providers (Fleek, Web3 Storage, Cloudflare, etc…).
  • Accelerated DHT (Distributed Hash Table) support for IPFS. This results in faster retrieval times and a better user experience.
  • Nimi profiles - anyone with an ENS domain can simply append .limo in their browser to resolve a personalized Nimi profile. This pulls in your ENS avatar, text records and even displays POAPS. Learn more about the Nimi implementation here.
  • DNS over HTTPS (DoH) resolver. We now offer an easy to use DNS resolver for ENS domains. The DoH resolver can be integrated with applications for native ENS resolution, or even your browser! We feature both JSON and DNS wire format responses with DNSLink support.
    Consult our documentation for implementation details.

Privacy:
The eth.limo team respects our end users’ privacy. We never log your IP address (IPv4 or IPv6) or X-Forwarded-For HTTP headers (this header is used when your request is forwarded from an upstream proxy), which means all request data is completely anonymized. Additionally we terminate all HTTPS connections at the application layer, which prevents cloud providers from inspecting the contents of each request/response.

Website: https://eth.limo/

Discord: https://discord.gg/zf8NxW94rB

Twitter: https://twitter.com/eth_limo

Steward Commentary: A grant of 60,000 USDC, 10 ETH, and 3,000 ENS has been approved for the eth.limo team. This is the largest retroactive grant approved by the Ecosystem Working Group to date.

LIMO is foundational infrastructure for the decentralized web, built on top of ENS. Infrastructure like air is ever present, but rarely noticed, that is until it’s gone.

ENS notices, respects, and funds critical infrastructure. Next time you type vitalik.eth.limo and it “just works” remember that happens because of limo’s builders, who make that happen. Every time. Thousand times a day.

Thank you @ethlimo.eth. Keep building.

7 Likes

Author: @hodl.esf.eth
Date: September 2022

Project: esf.tools (Generic NFT Controller/Resolver)

About:

The generic ENS mapper contract will allow NFT projects to easily allow their communities to claim subdomains that dynamically link to NFTs. This concept is based around a custom controller contract I wrote last year for Purrnelopes Country Club, this has over 800 subdomains currently registered. You can read more about that implementation here:

Rationale:

There is a lot of ERC-721 NFT collections and adding subdomains that link is good utility and will allow holders to represent their “brand” with web3 name and profile picture. It can also be used as proof of ownership for the assets.

Current Status:

I deployed the contract and after 3 days we currently have 5 ENS domains and 600 subdomains registered through the contract. We’re currently working on a generic UI so that projects can utilise this and have a number of projects showing interest. The contracts have been written to be compatible with NameWrapper and can provide additional functionality/security to the subdomains when this is deployed to mainnet.


Links

Web UI: TBA

Github

Smart contract
https://etherscan.io/address/0x64fa880b224b112d371948914e9e667e22bddc46#code

Dune Dashboard

Steward Commentary: A grant of 20,000 USDC and 250 ENS has been approved for Generic NFT Controller/Resolver. This project is an excellent example of the type of project the ecosystem is proud to support. The project not only adds utility, but also broadens ENS’s reach. This is the first major project to utilize the name wrapper. The open source nature of the code will allow others to learn and expand its capabilities.

4 Likes

stevegachau.eth - Full time dao contributor : Ongoing Projects

1: Optinames

Link: https://optinames.eth.limo

Summary:

Register a free ENS Subdomain on Optimism L2 and use it everywhere including L1 Ethereum.

What are Optinames?

Optinames are tradable and transferable sub-domains wrapped as ERC721s & fully integrated with the Ethereum Name Service (ENS). They can be resolved on L1 Ethereum by utilizing an off-chain resolver.

Important Links:

Off-chain Resolver on L1 - Etherscan

Subdomain NFTs on Optimism - Optimism Etherscan

Subdomain Example on ENS App - ENS App

Subdomain Example on Etherscan - Etherscan Resolution

Subdomain Example on Rainbow Wallet - Rainbow Wallet

What We Do:

This project is leading the charge in making it easier & cheaper to acquire and utilize ens domains. We are implementing the latest technologies released by the ENS team (CCIP Read & Off-chain resolution) to make it possible for users to register subdomains on Optimism while making them available & resolvable on L1 Ethereum.

In addition to providing free ENS subdomain on Optimism (currently ecc.eth), OptiNames is partnering with gaming communities building their games on any Layer 2. Gaming communities will be utilizing our tech and smart contracts to provide free usernames & gamer-tags that double up as ENS subdomains.

Adoption:

The first project utilizing Optinames to issue subdomains to their community is ECC Name Service (Optimism). ECC Name Service has since grown to become the Number 1 domain collection on Optimism surpassing Punk Domains.

Registrations: 1.6K

Activity:

What Next?:

  • We are working on a generic smart contract and a simple to use UI to allow anyone to wrap their names on any EVM L2 and provide cheaper subdomains to their community. Communities will have an option of using our off-chain CCIP gateway or deploy their own serverless gateway.
  • We will open-source the entire implementation on Github (MIT License) and provide documentation.

2. EnsRegistry | ENS Registrations Bot :robot:

Link: https://twitter.com/ensregistry

What is @EnsRegistry?

@ensregistry is a community-run bot that tracks new .eth $ENS domain registrations. The service runs in realtime and posts all new ENS domains as they are registered. (293,000 tweets total / 1440 tweets per day / up-to 18 names per tweet during peak times)

Value to the Ecosystem/DAO

The real-time visibility of domains (& ENS clubs) being registered & posted by the bot has helped drive new ENS registrations. This in turn has led to a noticeable increase in DAO revenue thus improving its financial sustainability.

What Next?

  • Upgrading the service to handle 100% of the domains being registered especially during peak periods.
  • Improving moderation (both human and algorithmic).
  • Adding support for subdomains created via the ENS Name Wrapper.

Check out the twitter bot in action. https://twitter.com/ensregistry

3. MintBot

Link: https://mintbot.io/

What is MintBot?

Mintbot started out as a service that allows ENS Domain holders to create collections for free and mint NFTs directly from their Telegram account.

The NFTs are minted on Polygon (an Ethereum layer 2 network) and the bot covers the gas costs.

On successful minting, your NFTs are visible and trade-able on marketplaces (which support Polygon) such as Opensea. All users mint NFTs under their own contract/collection (tied to their telegram username)

The service has since expanded to provide free & gas-less ENS subdomains via Twitter. Gas-less registrations are achieved through CCIP Read and Off-chain resolution (same technology utilized by coinbase with their free cb .id subdomains). The names can be resolved via rainbow wallet, coinbase wallet & trust wallet with metamask integration coming soon.

Links:

Minting Example on Twitter - Twitter Minting

Subdomain Example on Rainbow Wallet - Rainbow Wallet

Off-chain Subdomains Registered: 688

How to Use:

NB: Only letters & digits are supported at the moment.

Steward Commentary: A grant of 8,000 USDC has been approved for @stevegachau.eth. Steve continues to build and improve the ecosystem. The projects outlined above are used daily by a variety of people across the ecosystem. We are happy to provide this grant retroactively for all that has been accomplished so far. We are looking forward to Steve’s future contributions.

5 Likes

Posting about dWeb Services per Slobo’s request.

What is dWeb Services?

dWebservices.xyz is a pinning service for ENS+IPNS .eth websites. DWeb Services aims to support the .eth web community in updating and pinning their websites faster, and easier, with no gas costs. All of this is made possible with IPNS technology.

Currently, there are slightly over 4000 .eth websites indexed by esteroids.eth, out of which almost 1100 .eth websites already use dWeb Services, meaning we provide infrastructure for around 25% of the .eth web. This includes some of the most prominent projects of the .eth web, such as Nimi.eth, Planetable.xyz, and predomain.eth.

dWeb Services offers an easy-to-use UX, making it possible even for non-technical people to update their websites for free. For big projects like the ones mentioned above, dWeb Services provides an API tailored to the needs of the .eth web.

Rationale

One main rationale for building dWeb Services is to make it easy to have gasless updates of .eth websites. Before dWeb Services, when someone wanted to update a .eth website, they had to either do that on-chain, which is expensive due to gas costs, or run their own server for IPNS, which is difficult to set up, configure and maintain. With dWeb Services, they can now easily update .eth websites off-chain with zero costs.

A second rationale is that the community needed an IPNS pinning service tailored to the needs of ENS and the .eth web. dWeb Services nodes are paired with the main nodes of the .eth web, like the nodes of eth.limo. We provide features such as “Sign-in with ENS”, and support auto-import of your ENS names. Our API supports using ENS as ID instead of IPNS keys, making it easier for projects to manage the content of their .eth websites.

Last, but not least, there was a need for a pinning service that is easy to use for anyone, without a need for technical knowledge. dWeb Services UX is easy-to-use, intuitive, and as proof, there are plenty of non-technical in the community using it without any assistance or guidance.

Recent Updates

We keep on improving dWeb Services every week, mostly based on requests arriving from users. Some of our latest updates are:

  1. Provided an API to dynamically update .eth websites programmatically.
  2. Peered dWeb Services nodes with those of eth.limo for a faster resolution using eth.limo gateway.
  3. Added Sign-in with ENS. It is a variation of Sign-in with Ethereum (SIWE), for users that own at least one ENS name.
  4. Added an easy widget for creating records of ENS names using The Graph.
  5. Keep the IPNS record alive in the IPFS network by automatic republishing.
  6. Extended the EOL of our IPNS records to 1 year.
  7. Added the ability to auto-convert CID V0 to V1 upon publishing.

We have plenty of other updates waiting in line, see the roadmap below.

Roadmap

When a user has a request from dWeb Services, we try to implement it immediately. However, some of the requests require more time to implement, which is why we created a roadmap.

Our current roadmap consists of the following items.

  1. Better user documentation for both the UX and the API.
  2. Add more infrastructure to have redundancy and more stable service.
  3. Export option for IPNS keys. The export option allows users to keep a backup of the keys we create for them in our service. This makes it easier for them to migrate later on, or easier to recover in case of unexpected issues we may face.
  4. Import option for IPNS keys. This makes it easier for users to migrate from other services to dWeb Services.
  5. Integrate IPFS pinning (of other services) in the UX.
  6. Monitoring services to spot and react to issues faster. The end goal is to minimize our downtime to almost zero.
  7. Usage report for users to be able to track their activities. Currently, users are required to track on their own how they use dWeb Services, which is difficult to do both for private users, and for big projects like Nimi.

Links

Website: https://dwebservices.xyz/
Discord: Discord
Twitter: https://twitter.com/dweb_services

Steward Commentary: In consultation with .eth website subgroup, we have agreed on a grant of 5,000 USDC for dwebservices. This is becoming foundational infrastructure of the decentralized web with projects such as planetable.xyz, nimi.eth.limo, and predomain.eth.limo utilizing them. The grant is made to support dwebservices primary builder @tomlightning. Thank you for your continued efforts.

5 Likes

We post here per @slobo.eth and @neiman

Author: @planetable.eth
Date: October 2022

Project: Planetable.xyz

What is Planetable.xyz?

Planet is a native macOS app for building, browsing, and following dWeb content on IPFS + ENS. It’s a GUI consisting of a dWeb content reader, a two-column markdown editor, a static website generator, and a built-in IPFS node.

Rationale

  1. Among all the methods to host a website for ENS, IPFS is the current most popular one. But to use IPFS for ENS, users will need to learn commands of IPFS or use a centralized service like Fleek. Planet provides a native macOS app for users to build and host websites for ENS, all from their Mac. It is an all-GUI experience with no CLI involved. Websites built with Planet are hosted with a local built-in IPFS node. Third-party services like Filebase.com or Crust Network can be utilized for better availability and performance but are optional.
  2. Planet also can be used as a reader to follow content updates of ENS. For example, you can use Planet to follow the latest updates from vitalik.eth. When following, Planet pin the IPFS CID locally. Thus it makes the content available offline, and it also makes the content more reachable to other users. Since it uses IPFS peer-to-peer communication for fetching ENS website content, it is resistant to many censorship efforts on HTTP and DNS.

With the self-hosted local-first architecture outlined above, Planet is a fully decentralized solution to build and host websites for ENS.

Recent Updates

Since the initial launch in June, we have kept shipping new features every month. Here are some latest:

  • Video and audio content support. Generate a podcast.xml that can be subscribed to by Podcast clients like Castro, Overcast, and Apple’s Podcast app.
  • Two-column Markdown editor with live preview. Easily attach or drag-n-drop pictures, video, audio, or any useful attachments like PDF.
  • Integration with Filebase.com IPFS pinning service for better performance and availability.
  • Publish any local folder as IPNS. Hence the app can work with static website generators like Jekyll, Hugo, Zola, etc. Making it easier to link static sites to ENS.
  • Integrations with various ecosystem projects: dWebServices.xyz for hosted IPNS records. Plausible.io for privacy-focused traffic analytics. WorldWideWeb, a macOS web server from the Iconfactory, for quickly previewing template changes.
  • Template engine and two built-in templates.
  • ENSKit: A Swift library for reading addr, contenthash, and text records from the ENS contract. When we started this project, we needed a Swift library for ENS, but most of the existing tooling was in JS/TS. So we built a Swift library for ENS.
  • A tutorial website about creating and linking websites for ENS: Planet

Roadmap

  • Add WalletConnect to enable tipping for content on ENS.
  • Implement more interactions between ENS dWeb: likes, emoji reactions, and comments.
  • Create more tutorials on how to build a richer dWeb on ENS.
  • Build more beautifully designed site templates.
  • Integrate with more pinning services. People who tried IPFS usually thought it was slow, but a ubiquitous pinning network would eliminate that slowness. That would also make ENS websites faster.
  • iOS version for creating and following ENS dWeb on mobile devices.

Links

Steward Commentary: In consultation with the .eth website subgroup, we have agreed on a grant of 10,000 USDC for @planetable.eth. Planetable brings ENS to MacOS users and to the blogging community, with hundreds of blogs already created by their tool. Planetable continuing efforts to integrate with as many tools as possible, tie the ENS ecosystem together. We’re looking forward to seeing what Planetable will do next.

3 Likes

gm :slight_smile:

here is a brief year-end recap and things we were able to achieve thanks to this grant:

  • Grew to a total of over 2500 Nimi Profiles with over 10k deploys (i.e. includes users updating their Nimi page) ~15% of all ENS content hashes set
  • Onboarded new part-time dev to help work on Nimi
  • Rebuilt Nimi page-builder interface, with more social links, multiple links and more customization for the users
  • Extended our POAP integration to allow users to select their favourite POAPs to show
  • Improved UX with connecting wallet, domain pagination, domain search etc.
  • We managed to attend devcon and released a custom Nimi theme just for devcon attendees - by making it POAP gated!

Overall content hash records have seen strong growth and we want to keep that trend going!

A big thanks to the ENS community for all the support and we hope to continue working closely together in the future :rocket:

7 Likes

Posting here as guided by @alisha.eth and @slobo.eth

What is dra.gd?
dra.gd is a decentralised website builder. Our vision is to build Wordpress for Web3, with the goal of simplifying the site building experience for users while using decentralised architecture.

Figma-stye editor

dra.gd offers a simple drag-and-drop editor with various blocks for users to design a site. Blocks range from simple units like text, button and links, and also include more complex blocks like smart-contract integration and an AI-based image generator.

All sites and assets used on dra.gd are deployed to IPFS and linked to your ENS domain, allowing you to set up a fully customisable blog or profile page, and link it to yourname.eth in just a few steps.

Over 300 users have created sites with dragd so far. We recently won $3000 in grants at ETHIndia, and we’re looking to work closely with the ENS community to build a website builder we all love to use!

Rationale
Products like Wix and Webflow that provide easy-to-use site builders usually involve hosting the site on their centralised service. Export is a premium feature and further requires users to figure out deployment to dWeb as an additional step.

Further, support for Web3 integrations is poor. Plugin support is usually limited to whatever integrations they offer. With Ethereum serving as shared data-infrastructure, projects can simply connect their existing smart contract address to connect data to other plugins on the site. (Eg. a private analytics dashboard for your community, or a private group chat)

Recent Updates

  • Started in May 2022, as a hobby project and was conceived at a hackathon.
  • We started out with building an intuitive editor that lets people build a website with a figma-like experience.
  • Responsive by default - pages designed in dragd effortlessly resize to fit on smaller screens, making the design process much easier.
  • The page editor has seen tons of upgrades, including multi-select, new blocks, keyboard shortcuts, a ‘help’ screen, and much more.
  • When a new site is created, we immediately deploy a redirect to your dragd site on IPFS which can then be linked to your domain. (not ideal, see roadmap)
  • Smart contract support - connect smart contracts to your page and using on-chain data to control actions, like private pages for NFT holders or defi dashboards.

Roadmap
We’ve had a lot of ideas for cool features to add to the editor, but we’d like many of our features to be driven by community feedback. Here is some of the stuff we have planned for the coming months:

  • Link ENS button: For the ETHIndia hack, our demo just linked the site to your primary ENS, but we would like to build a better UI to connect sites and domains.

  • More plugins: Our new plugin system is ready and we’ll be adding new blocks to try out on your site.

  • Static build and deploy: Currently sites are still hosted on our centralised server, with just a redirect deployed to IPFS. This also makes our sites indexable on Esteroids.

With this change, dra.gd will no longer require a centralised server, as the editor itself can be hosted on IPFS, with just a build service run on some decentralised compute provider.

  • Better flows for creating blogs and profile pages, with good defaults and a fun user experience to set it up.

  • Delegation support: Currently we just update the content hash. We’d like to look into delegation support as a part of the roadmap for subdomains and making updates on user’s behalf.

  • Subdomain support: we envision this as a feature for communities to express themselves under a shared identity, where every member gets a personal space under a subdomain.

  • Analytics: we’d love to help users understand more about the kind of traffic and journey their visitors exhibit. Of course, we want to implement this in a privacy-protecting manner.

  • Polish the editor: We built the editor from scratch to feel like Figma but for actual functional sites. We wrote a lot of vanilla JS to handle behaviour on different platforms, and there are some UI bugs around that we’ll be hammering out.

Links
dra.gd homepage
Discord
Twitter
Demo video

Steward Commentary: A grant of 10,000 USDC has been approved. This project adds utility to the ENS ecosystem. The project is live and is being used by the ENS community, which supplies the rationale for this grant. Additionally, the roadmap clearly demonstrates that ENS is a key part of the future of dra.gd. The future plans around subdomains and progressive decentralization are particularly noteworthy.

4 Likes

Just curious, is Optinames going to be compatible with the namewrapper coming out?

The namewrapper contracts are on mainnet while Optinames’ wrappers are on L2. Both will co-exist fine.