Сделали ставку 15 в личку.
Отписал что продано. Если сделка не состоится, продолжим.
|
|
|
Форк это само собой. Но это настолько ваще фундаментальный косяк, что я думаю уже в сторону BitDNS или че там задумывалось ОТЦАМИ биткоина?
Косяк заключается в том, что сеть НЕ самостоятельна. Она по своей природе стремится к хаосу, при чем довольно шустро. И девелоперы вынуждены вмешиваться в работу сети (устанавливая корректное значение NetFee), чтобы не наступил армагедец. Т.е. это сеть контролируемая девелоперами. Ну типа как ФРС США контролирует экономику базовой процентной ставкой.
Это неприемлемо в принципе.
|
|
|
Короче, GetNetworkFee() - функция, взятая пальцем с неба. Она возвращает текущую стоимость домена, которая уничтожается при регистрации. int64 GetNetworkFee(int nHeight) { // Speed up network fee decrease 4x starting at 24000 if (nHeight >= 24000) nHeight += (nHeight - 24000) * 3; if ((nHeight >> 13) >= 60) return 0; int64 nStart = 50 * 100000000; int64 nRes = nStart >> (nHeight >> 13); nRes -= (nRes >> 14) * (nHeight % 8192); return nRes; }
У меня чуть мозг не взорвался, когда я пытался посчитать что девелоперы этим хотели сказать. Но получается в текущем виде до 80000 блока Fee уйдет в ноль и сеть будет полна спама. Чтобы этого избежать, девелоперы вынуждены постоянно корректировать эту функцию, при этом просить всех клиентов обновиться. Девелоперы - центральная точка сбоя системы. От их произвола зависит как вообще система будет себя вести. Следовательно, НеймКоин - система с непредсказуемым поведением и единой точкой сбоя. И в текущем виде ни к черту не годится. В пользу моего вывода так же говорит то, что khal и doublec методично обходят стороной неугодные вопросы. И вообще полностью игнорят это обсуждение. В морг. Мне жаль. Пошел искать другую систему.
|
|
|
Anyway,
GetNetworkFee() is a function which taken from the sky, and returns a current network fee which is guessed by developers. GetNetworkFee() -> 0 @ block 80000 first_update destroys GetNetworkFee() coins, increasing deflation
when GetNetworkFee will be zero, namecoin will be full of spam. To avoid it, developers should watch and update this fee with relevant values and ask all network members to update their clients.
developers is the central point of failure in this system. The system is controlled by developers intrusion by changing network fee for name registration, like US economics controlled by Federal Reserve intrusion by changing discount rate.
Also i noticed that this question is uncomfortable for developers. They don't try to go deep into problem, but giving common answers.
The problem with destroyed coins exists from beginning and still not resolved and ignored by developers.
NameCoin is a system with unpredicted behavior. It is not suitable for usage in i2p with a current design.
I am sorry.
|
|
|
I've parsed a block chain to know the dynamic grow of registered domains and dynamic grow of lost coins. I tried to look in the future by mathcad predict() function. And got a lulz Left graph - number of registered domains Right graph - number of lost coins Red line - current data Dot line - mathcad's prediction (this not the correct prediction, just lulz)
|
|
|
Прикол. Взял распарсил цепь блоков, чтобы узнать сколько когда было потеряно коинов и сколько когда доменов зарегано. Чтобы узнать что будет в будущем, использовал маткадовскую функцию predict() и вот что она мне показала Левый граф - количество доменов Правый - количество потерянных коинов Красным - текущая динамика, точками - предсказание Это ни о чем не говорит, просто маткад пророчит неймкоину смерть
|
|
|
Ok. I think I got it.
If system will pass netfee to miners, it will inflate to spamhell If system will have a zero netfee, it will be a spamhell
So it is doomed for controlled self-killing by destroying netfee coins, and amount of this netfee is assigned by some central person in patches. He have to monitor the network and keep netfee in reasonable range. Like federal reserve with its Discount rate.
In sysadmins sociaty this method is called "spike-nail".
Good night.
|
|
|
After 500k blocks fee will be 0 if I don't mistake. What about squaters? )) int64 GetNetworkFee(int nHeight) { // Speed up network fee decrease 4x starting at 24000 if (nHeight >= 24000) nHeight += (nHeight - 24000) * 3; if ((nHeight >> 13) >= 60) return 0; int64 nStart = 50 * COIN; if (fTestNet) nStart = 10 * CENT; int64 nRes = nStart >> (nHeight >> 13); nRes -= (nRes >> 14) * (nHeight % 8192); return nRes; }
People ask me, what do I dont like. This all smells like the central person will decide what fee will be, because it doesn't have its algo, I don't see any documents explaining effects of this code in future. What will be in a future? What is the diagram of number of lost namecoins versus number of mined? Where is the intersection? Very, very many questions.
|
|
|
Actually khal's explanations confused me. He said the problem in squaters, but the real problem is in money from nothing. That is why they destroy coins.
Squaters are not a problem.
The problem that system by current design is DEAD in a future. And my programmer expirence says that future becomes much quickly than expected.
|
|
|
I don't see real reason to limit coins in existence (especially when system is systematically destroying them).
This is also a point!
|
|
|
afaik there's some algorithm which calculates price for domain from last x blocks. So yes, those coins are destroyed, but when namecoin gets some popularity and namecoins will be more expensive, then domain will cost maybe eve 1 satoshi, which means we can still have bazilion of domains.
I am programmist (not in c++ unfortunately), and one of programmist rule says: The future comes much quicker than expected. So if the future will bring a collapse, im worried. Worried because namecoin may become a basis of I2P naming structure.
|
|
|
Основания конечно есть, но лучше поискать выход.
Зачем писать клиента под потенциально мертвую сеть.
|
|
|
Actually this is not from empty place. There is some logic in that.
Miner has a 1Ghash/s mining power.
With a difficulty 518525.94130231 he will get 1.94 NMC per day.
Day left, he mined 1.94 NMC and bought 194 domains.
If system pass that 1.94 NMC as reward for block solving, miners' total daily revenue will be increased by 1.94*(his_power/network_power).
Actually this is the "money from nothing". And devs still didnt find any suitable method to resolve this except to destroy these coins.
So my proposal is: may be is it possible to hold domain associated coins util it will be expired.
|
|
|
Стоит там обычный вордпресс, автоматизация лишь в подсчете актуального курса. Ценен посещаемостью с поисковиков. Скрины статсы Начальная цена - 10 BTC. Кто больше, тому и домен. Трансфер за ваш счет. Если акк на namecheap, то перенос бесплатный. Обменники - не мое
|
|
|
namecoin has identical emission behavior to bitcoin. 21M of max "coins" (each coin is 1E8 (if not mistake) integer). So the total possible number of namecoins is the same as bitcoins = 21E6 * 1E8 = 21E14. It is deflated in value by default.
Additionally, namecoin has special transactions which contain key=value pair (i.e. domain => ip). When first registering such key (domain), the fee for registering is actually destroyed (to fight squaters). So every domain registered decreases total possible number of NMC currently by 0.01 (1E6 = 1 million integers). 81k namecoins (81E12 integers) are already destroyed by this way.
So namecoin is doomed for death with this behavior someday.
|
|
|
==cut out=== Purpose of this thread to find a way to build censorship resistant authoritative key=value storage (Distributed DNS) based on Satoshi ideas. Please scroll down for design improvement proposals to namecoin. Also here http://dot-bit.org/forum/viewtopic.php?f=5&t=58&start=40And russian discussion is here: https://bitcointalk.org/index.php?topic=61486.80Current namecoin design has several errors which are: 0. Coins are destroyed Proof1. NetworkFee descreasing for 50 to zero and will be zero in ~80000 block Proof and has no feedback with network activity like difficulty has. 2. Namecoin was designed for free domains and this is its future Proof3. Developers have to do system intrusion from time to time to avoid collapse or spam hell Proof Proof
|
|
|
|