Bitcorn labs presents: a url for daos/dapp on Icp: ic0.io

we all know and love ic0.app as the main tool of Icp, so why don’t we mate our dapps to an ic0 url?

ic0.io will be maintained by Bitcorn labs and we will forward prefix’s of daos and known dapps upon request. Currently we have redirected via team request:

@KongSwap: dex.ic0.io, kong.ic0.io
@rem.codes: toolkit.ic0.io
@icsneed: sneed.ic0.io, lock.ic0.io
@WaterNeuron: wtn.ic0.io
@baolongt: pacapump.ic0.io, paca.ic0.io

For non utility projects we have created by request:
clouds.ic0.io
chicken.ic0.io
wumbo.ic0.io

ic0.io points to the nns.ic0.app

We welcome requests for prefix forwarding and if you want a prefix please post your prefix and link to your dapp/dao homepage.

5 Likes

We now have

@bobdotfun : bob.ic0.io
@ICPSwap : swap.ic0.io
@skilesare : icdevs.ic0.io

1 Like

We now have

Oisy wallet: wallet.ic0.io, oisy.ic0.io

So here’s what we are thinking:
Sns/developer projects get their URLs

Longterm known non sns projects can get URLs by request

We will accept bids for the following URLs from legitimate parties:
btc.ic0. io
ai.ic0. io
bitcoin.ic0. io
forum.ic0. io
game.ic0. io
cloud.ic0. io
Ic0.ai

A dapp will be published soon with a directory of the URLs.

If anybody has thoughts or opinions we would love to here it as this is all very new

We now have

Openchat: oc.ic0.io, Openchat.ic0.io

We now have

Msq wallet: msq.ic0.io

Openchat has been removed from url forwarding.

Oc.ic0. io
Openchat.ic0.io are available for purchase.

We now have

@wpb : codegov.ic0.io, synapse.ic0.io

1 Like

We now have

@radudaniel : taggr.ic0.io

A repository has been published where users can submit pull request for url forwarding.

As this grows, we will commit the marketplace/dapp here.

This is going to take a considerable amount of work and we are looking at implementing some existing ICRC standards as well as custom web2 infra to do this correctly.

The repo is here

The first pull request has been made:

Welcome

@PonziBuddy : Ponzi.ic0.io

This is a highly risky practice:

  1. Similarity to Official Domains: The domain ic0.io closely resembles DFINITY’s official domain ic0.app. Users might mistakenly trust it, assuming it is officially managed by DFINITY.
  2. Lack of Control: Projects cannot control the behavior of these domain resolutions, such as wallet.ic0.io or oisy.ic0.io, which are not managed by the Oisy wallet team.
  3. Potential for Malicious Redirection: If such domains become widely adopted, they could be redirected to malicious data sources, leading to unforeseen consequences. For example, an AI Agent might use swap.ic0.io/xxxxxx to fetch incorrect token prices and execute transactions based on faulty data.

If you like this approach, feel free to disregard my comments—but always do your own research.

Hi there!

Home page for ic_dns is icdns.app

So we are currently building out a method for a used to

-claim a url prefix xyz.ic0.io
-deploy a canister
-bind their chosen url to their canister
-control their url

This is gonna take ALOT of work but if you don’t want to use a prefix for your dapp don’t feel required.

The above git is where we will be publishing all the code/info

Most likely going to start with this as some framework

For the record, we spoke to 99% of the people before we made these redirected URLs. It’s voluntary and fun. We 100% will not just randomly assign urls and advertise them. The goal is to make a simple (permissionless) way to obfuscate the usual aaaaa-aaaaa-cai etc of canisters.