It's only a test, nud has been on exchange , it's not a test, you are waste our time and money.
The former support like a monkey, dev is Monkey man，lol.
1:1 ratio is appropriate .
Even worse. Ever thought about how hard it will be now to convince an exchange to trust NUD, considering that alcurex will sooner or later find out that the NUD update leaves them with all their customers' NUD deposits being lost? Blockchain restarts are simply a no-go for any serious altcoin dev who cares about the coin's reputation.
I didn't give any exchange permission to add NUD, that is why I ignore all the PMs from exchanges willing to add support to NUD.
Of course I am not the dictator of the network, exchanges may still add NUD without my permission, just don't be surprised when inconveniences occur.
Unfortunately we are bound to have many updates within the first weeks. I don't think that it's wise to add support for NUD so early for most exchanges.
Hello from alcurEX exchange. We got support message about your coin NUD:
Hi,
I need you to comment on the NUD blockchain re-start. I had no idea that you were adding coins without the permission of the dev. What will happen with the NUD that is deposited with you? This is a serious trust issue.
First of all. If you clone and publish opensource coins, there is no"dev permissions".
We inform your community in your thread and PM dev, so everyone know there is exchange for NUD.
Ofcourse we expect dev inform all exchanges and pools how to keep NUD coin alive.
If your dev will not inform pools and exchanges, and want to keep this private, do not make ANN. Use like PREANN and inform you coin is not published yet.
I will freeze NUD market untill we know if we have dev support... and "permission".
Any way. Good luck with your coin. We will not leave you if there is solution to keep your coin on the market.
alcurEX support
-halibit-
I am fully with you. I think it is a huge step forward to have exchanges which pick up new cryptocurrencies, and the invention of open source software as you say, together with the security gained through cryptographic blockchain networks, can be seen as the basis for allowing this. I can't imagine what potential the cryptocurrency economy would have if exchanges could pick up new cryptocurrencies easily and without fearing damaging actions from rogue altcoin devs. For example:
* Real mining profit from day one
* Possibility to compare different altcoins on their exchange performance from the beginning
So what can be done? One thing would be to better educate people about the ethics of creating a cryptocurrency. As you correctly stated, PREANN would be at the very least appropriate if the dev plans to make blockchain restarts for no reason. But even then: Blockchain restarts should be only an ultimate resort. This becomes clear when thinking about how the blockchains are computed. No matter if it's a CPU, GPU or ASIC coin: People invest computing power into verifying the blocks and computing the hashes. So, even when policies like the hash being used change, it could be considered an environmental crime to just throw away the old data, considering that it doesn't take much development effort to make such changes to a blockchain client without a restart.
But even more can be done, thanks to the blockchain cryptography:
For this, it must be understood that the dev's attack against the old blockchain and its exchanger, miner and user community was very simple: He replaced the software on the advertised seed nodes to be incompatible with the old blockchain, and stopped to distribute the software compatible with the old blockchain.
So, to recover the funds on the exchange, the following steps can be taken:
* Advise people to use the known-to-work software release 0.0.0.1
* Put it on accessible servers and provide their hostnames for people to "addnode" them
* Notify the miners - they will be needed at least to let the difficulty adapt downwards. But they cannot mine on the new blockchain anyway
So, by appropriate usage of the potential of open source and of blockchain networks, it should even be possible to limit the power of rogue devs.
As future steps, I would recommend to make the change to bcrypt from the old blockchain - in a proper way without invalidating blocks. This way, the community NUD and the dictator-dev NUD stay maximally compatible (think CentOS and the product of a certain North American software vendor
). Maybe we can then even convince the dev to join forces. A cryptocurrency with a healthy community is even more valuable after all.
