Future Fee System for Names - step 1 : minimal requirements
-
- Posts: 801
- Joined: Sun Aug 18, 2013 8:26 pm
- os: mac
Re: Future Fee System for Names - step 1 : minimal requireme
We could also implement critical functions (such as what counts as a well-formed field, weighted domain name pricing, etc) using Haxe. Presumably, the unit tests would be translated into all of the languages it supports (C++, C#, Java, JavaScript, PHP and experimental Python 3). Using PEG's for parsing fields would be more cross platform compatible too.
DNS is much more than a key->value datastore.
-
- Posts: 801
- Joined: Sun Aug 18, 2013 8:26 pm
- os: mac
Re: Future Fee System for Names - step 1 : minimal requireme
Domob,
After conferring with a friend, it sounds like you might be right. He had tried resolving all of the names in the root zone file and some 50% were parked. That was a rough estimate, it certainly wasn't domains for sale so it's not exactly squatting but (at the very least) it sounds like a lot of names are just sitting around.
After conferring with a friend, it sounds like you might be right. He had tried resolving all of the names in the root zone file and some 50% were parked. That was a rough estimate, it certainly wasn't domains for sale so it's not exactly squatting but (at the very least) it sounds like a lot of names are just sitting around.
DNS is much more than a key->value datastore.
-
- Posts: 2001
- Joined: Tue Jun 05, 2012 6:25 am
- os: linux
Re: Future Fee System for Names - step 1 : minimal requireme
Just for reference, the name fee must be able to decrease down to around 0.000875 NMC (21 million NMC / 8 billion world population / (1 id/ + 1 d/ + 1 dd/ name per person) ) without a hardfork. Otherwise mass adoption would make some users unable to use NMC. That also assumes no squatters, no people who own multiple domains or ID's, and no name expiration... any of those would push the price even lower.