hl.place

What is hl.place?

A bootstrapped public good service for .hl name resolution that enables users to access dApps and web2 content. hl.place is the de facto content resolver for Hyperliquid Names for over 3 months.

What are we trying to solve on this hackathon?

Domain name such as .hl serves more than to simplify your wallet address, we believe that it should also enable people to serve content with ease. Our project aims to simplify content serving while still making decentralization a priority.

In this hackathon, we are launching the hl.place domain, client-side decentralized .hl TLD resolver, and user documentations.

How It Works: The Official "Centralized" Resolver

Stemming from hl.baby, the core idea is to serve content by proxy. Either from a web2 sources via DNS records or IPFS CID hash. We have coordinated with Hyperliquid Names to standardize text records such as A, AAAA, REDIRECT, CNAME, and CID. In this hackathon, we launched hl.place as a more appropriate name after hl.baby. With the following details for the work behind-the-scenes:

Sequence Diagram of The Centralized Name and Content Resolver

For legal reasons, we maintain a network-level blacklist mechanism which is external to the resolver. For the record, we use and regularly maintain our own Bad Bits Denylist. If you were to found any inappropriate content utilizing our service, you can report them to us via any socials.

How It Works: The Client-Side Decentralized Resolver

A client-side resolver comes with many benefits such as being uncensorable, having 0-downtime, and the ability to directly resolve .hl as TLD (instead of using .hl.place). It's like TOR's .onion but users are responsible for their own use and privacy.

Services We Use

• Hyperliquid Names: both on centralized and decentralized resolver as .hl name provider
• Alchemy: on the centralized resolver for direct text records query to HyperEVM (planned after HLnames contracts has been verified)

Demo

You can try our content delivery service here:

• CNAME: https://testooor.hl.baby/
• REDIRECT: https://hanz.hl.place/

Source code for the resolver can be found here: https://github.com/VastlyPage/resolver

Documentation can be read here: https://github.com/VastlyPage/resolver/wiki/

Fund Utilization Plan

• Existing operational cost (gateway server, RPC, and maintenance)
• Extending infrastructure operational capability
• Providing support for users and developers
• Responding to abusive content reports

KPIs

We will be providing monthly report of both funds utilization and KPIs on Twitter complete with TXIDs.

Team

X Page: https://x.com/vastlypage/

Credits

• Background picture