Hacker Newsnew | past | comments | ask | show | jobs | submit | evbots's commentslogin

coinbase is to namebase

as bitcoin is to handshake


the context for that comment is that handshake took a snapshot of the icann namespace. so any names icann adds or changes after the fact will conflict with the HNS namespace.


The comment is the start of a longer thread that is one data point in understanding how HNS would rather be adversarial than cooperative, from my perspective and others. Much of the crypto public speak is about replacing rather than enhancing existing systems. There is no join, only beat. They would likely become the very thing they desire to replace. It's human nature


There are factions within crypto, some think the "end of history" looks like crypto replacing centralized systems. others (like myself) think those systems are complements and simply alternatives in the marketplace.

As to being adversarial... ICANN was allocated 1.2% of the total HNS supply, and all existing TLD owners (at the time of the snapshot) can claim their TLDs on chain. The icann allocation is 5.8% of the current circulating supply.

i suppose there could have been a way to give ICANN a blank check to modify the handshake namespace in perpetuity, but i suspect that might either be technically unworkable or just made the whole venture pointless.


I use it, and own a small portfolio of names on chain. "base" and "faq" are a couple of them. It's been pretty interesting to watch the ecosystem mature.

Just recently a small dev team released a desktop app that syncs name data to your local device and lets you browse sites with lookups to the handshake root before falling back to icann root https://impervious.com/fingertip.html


So name squatting will still be a thing? Any solutions for that?


the way handshake addresses this problem is putting a cap on the total number of names that can be registered, and then users compete on fees in order to get their transaction mined to renew the name


Can't I make a few million accounts (or "wallets") programmatically, since it's a blockchain?


total number of names "total", not total number per wallet


So there is an ongoing cost to owning a name and the cost increases as the global number of names registered/owned increases?


yeah. right now it's ~$0 since there's no fee competition, but as soon as the total names registered gets close to the limit (66 million) then the cost of renewall will go up and it will be costly to squat. there are 1.85 million names registered currently.


There are a few blockchain based solutions to this problem.

- Handshake

- ENS

- Namecoin

My favorite so far is Handshake - a fork of the bitcoin protocol with added support for covenants, which is how arbitrary names can be registered and associated with some 512 bytes of data. Example: https://hnsnetwork.com/names/proofofconcept which shows TXT and other records. ENS was previously my favorite, but the root protocol is secured by only a 7 person multisig. Namecoin is old and poorly designed in my opinion.


It was via Handshake that I came across this concept (though I heard it as "Zooko's Trilemma") a few months ago! Handshake indeed looks pretty cool and interesting. I bought-in enough to register both my real name (firstnamelastname) and commonest online handle, but I haven't found time to actually do anything with them. I should make a personal web site. I should do a lot of things.


you only need hns.to if you haven't set up your system to resolve handshake names directly, or (theoretically) use a browser that has support baked in.

It's on Brave Browser's roadmap to resolve handshake DNS directly.


The true cost of any product is the project lifecycle cost. There are many cases where a serverless architecture would cut down on that.


Can you go into a little more detail about who owns the bank account that users are depositing into when they use sparkswap?


AnchorUSD is our payment partner who operates the API we interact with (it's a custom API that they built for us).

The escrow account is held with a trust company in AnchorUSD's name, but is designed so that only the users they onboard can access the funds. Funds cannot be legally used for any other purpose.


> The escrow account is held with a trust company in AnchorUSD's name,

That means the total FDIC insurance on all the money in all accounts is capped at $250K between all the users of your platform. One Bitcoin quoting at $10,288, means that at most money needed to buy 24.3 bitcoins are insured across the entire platform.


Personally, I don't expect FDIC insurance on swap space used for trading, or generally anything except my bank account.


It is not about trading - customer's funds are deposited into a bank account of a US financial institution partner under under a name of a trust created by their service provider. Until those funds are "spent" they sit in that account. That account is FDIC ensured to $250k.

Compare this to you depositing money with your brokerage to trade stocks. The account is opened at clearing broker in your name, which means that the SPIC coverage limit is just yours.


Our partner has clarified that FDIC insurance is per user (per Tax ID) rather than for the whole platform


I'm sorry, but your response is a strong indicator that anyone and everyone needs to stay as far away as humanly possible from your company in its current form because:

1) company's leadership does not understand how FDIC insurance works -- trusts have their own tax ID which are not customer's tax id. Trusts cannot currently be created in real time.

2) company's leadership does not know what they are getting from a "partner" -- some random person who ran a couple of companies and consulted for some financial institutions should not know more about what is and what is not possible than a leadership of a company in a space

3) there's a lack of understanding among the leadership what are the implications of customer account being insured by FDIC.

4) leadership does not understand that ACH credit has a liability attached to it which needs to be managed very carefully ( especially with points 1-3 )

5) In no even should the points 1-4 stand should a company ever trade from its own inventory to satisfy customer's order.

Drop whatever you are currently doing and immediately hire a compliance person from a large commercial bank that does not have any reason to leave his or her position i.e. overpay for one of 100-200 experts that exist in this field so you can at least ensure that you don't blow up in the most spectacular fashion with a potential criminal prosecution.

This is not an Uber or AirBnB. If you mess up you will create potentially criminal problems not just for yourselves but for your customers.


thank you for making this public, even though it may not be perfect.


It depends on how you interpret your jurisdiction's tax laws. in the united states there are some tax professionals that would count airdrops as taxable, and others that wouldn't if you never plan to claim the airdrop.


This is why anyone trading digital assets should use a tax tracker to understand the implications of each trade before they make it. I've spent some time building software for exactly this (https://cryptotax.tools).


I actually disagree with this. As someone who uses linux as the primary build OS for my software projects, i need to know just enough to make things work but I don't necessarily want to be an uber linux expert. This results in me constantly googling "command for <XYZ> ubuntu", which usually lands me on a stackoverflow page with something that points me in the right direction. Now, i'm not saying a linux example commands website will be successful for my anecdotal reason, but i have to imagine there are many more devs just like me.


yes, but do the numbers....

how many of you are there? People in that stage of learning Linux where they google the 5 most common things people get wrong?

Let's be generous and say 1 million. That seems reasonable. It's certainly more than 100,000 and less than 10 million.

Let's be more generous and say that all these people search for this once a week.

At $1 per 1000 pageviews (the generous estimate) that caps income at $1K/week maximum.

That's a nice side-project, if it captures 100% of all the traffic and manage to monetise it (I'd like to see the percentages of Linux users/admins who also install an adblocker; I suspect it's high).

I do this all the time... "I want a service that does X". But I'm not typical, so the market always ends up being small. The standard startup advice of "solve a problem you have yourself" doesn't work for me. I call it my "Kardashian Problem": I don't understand why anyone would ever spend any time paying the Kardashians any attention whatsoever. This is clearly my problem, because the Kardashians are very popular, and the bajillions of people who do pay them attention seem very OK with it. So I am clearly not a very good judge of the market and should not trust my instincts about what will sell well.


This is where you upsell into ebooks, video courses and paid training. Also if you build an email list you can build partnerships which will lead to a much higher CPM.


yeah, but then your business model is selling ebooks, video courses and paid training, and this just becomes one of a number of avenues to reach your market. Which is all totally fine, of course, but the business is no longer "a website with the 5 answers to the most commonly asked Linux questions" :)


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: