Search results

I'm ready for this, from the start my MN are running on private servers with a good configuration in the perspective of an evolution.

Firewall setting ?

I will stop to "disrupt" your thread, but before that a small reminder from the documentation for all users (advanced like the OP or not) : "Backup wallet.dat. Frequently backup after, this is BETA software." PS : Don't try to copy wallet.dat while the client is running

That was kind of ironic. Some long-time supporters started to troll the coin for money not so long ago...

lol case closed !

blackempress and his/her emphasis of "closed source", see what you are trying to do.

Not a good strategy IMO if it's officially announced like that it could be misinterpreted (focused on the value of the coin). Instead it can be announced or implied that the source will be released the xx.xx.xxxx to let the coin have a fair headstart (focused on the coin).

Each masternode can check the others to create a common list of valid MN.

Maybe a MN owner can tamper with the port check (if it's done locally).

You have my vote.

Cool, but IMO no need for a specific date, end of June, beginning of July is good. Thanks to flare the code will be stronger :) !

That why I said that they can be hosted by every MN and that the hash have to be checked by the wallet. The reference being in the blockchain. If the hash is different it means that the executable has been altered.

The 8th idea is IMO of the highest priority for a wider adoption. A lot of people don't keep track of updates, are surprised when their wallet doesn't sync , may stay in a wrong fork or endanger the network. A notification when a new version is available and an update button would be a good...

Of course, there was a hard fork weeks ago. Delete everything in the Darkcoin folder except wallet.dat, then run the wallet.

C'est bien ça ! D'ailleurs le lien est présent ici : https://www.darkcoin.io/getstarted.html

In that case we must find a way to prove the ownership of that address. Otherwise, what keeps somebody to use any address with 1000+ DRK to a setup a MN. (sorry for the off topic)

That's like the actual procedure, but for the cold storage ? The masternode must check the amount in the "cold" address and it must be proved that this address belongs to the MN owner. if address checked amount < 1000 { The MN is invalid and can't start } else if address doesn't belong to MN...

Authorizing the cold storage for a MN is, in my opinion, a big can of worms. Using a remote setup server---->server instead of local----->server seems to be, for me, the best solution. What prevents somebody to move around the funds, and create 10 MN with the same 1000 DRK. If the address is...

How does the new version deal with MN using (intentionally or not) an old version ?

Listed with a or a ?