[ANN] ¤ DMD Diamond 3.0 | Scarce ¤ Valuable ¤ Secure | PoS 3.0 | Masternodes 65%

[pokeytex]

Nice work gentlemen....... I skipped the .conf file from the blockchain download...was this a no-no?

The 2.0.3 wallet is the only/first one I have....apologies if its been answered I read the best I could.

I do have a conf file it just has the OP specs and my settings

I recommend you adding to the .conf file the following line:

noirc=1

If your wallet goes to the wrong chain you will see it as the difficulty will dramatically decrease and you will probably have a crash of your wallet. In that case, delete all files (except wallet.dat and diamond.conf), copy the blockchain from OP again to the folder, and try changing addnode=193.68.21.19 to connect=193.68.21.19 in the .conf file (temporarily). You can then revert to addnode=193.68.21.19 when the situation has stabilised.

Quick question - is the network down?  I cannot connect to Danbi's website nor is my wallet registering any confirmations.  It is stuck at .0157432 difficulty and I have the following settings in my .conf file.
rpcuser=cgar
rpcpassword=x
rpcport=17772
rpcconnect=127.0.0.1
listen=0
noirc=1
connect=193.68.21.19

Is it possible I forked again even though I have the above settings or is Danbi working on the network?

Thanks,
pokeytex

[srcxxx]

I spent about 3 hours today trying to get the pool working. I also think that the network is stuck.
Block explorer http://diamond.danbo.bg:2750/ does not work.

It is not clear what fork is correct and what is not.

[polanskiman]

Sit Tight Boys.

[SRBOOTH]

Sit Tight Boys.

Will do Captain!! I'm sure you will tell us as soon as you can....wish there was something we could do to help...let me know

[digi123]

Cryptsy withdrawals work. I've just checked it.

I haven't checked deposits, but Cryptsy informs that :

Deposits will continue to post for the old addresses, but you should generate a new address for faster deposit processing.

This might have something to do with slow processing time.

With old address and new address the diamond coins are still not depositing into cryptsy. There still seems to be a problem with them.

[utahjohn]

Grrr ... now what is going on my wallet stuck and not syncing from danbi ...  miner not receiving work

[digi123]

The second deposit that I made which was only a while ago has no confirmations and a question mark. So what does this all mean?

[polanskiman]

Seems indeed some people are not yet done targeting DMD for their own benefit. What a bunch of losers.

Looks to me that Danbi's pool is under attack. It comes and goes offline. Perhaps a DDOS?

[utahjohn]

Seems indeed some people are not yet done targeting DMD for their own benefit. What a bunch of losers.

Looks to me that Danbi's pool is under attack. It comes and goes offline. Perhaps a DDOS?

Quite effective if is a DDoS, has completley disabled the correct blockchain sync from Danbi node not happening.

[utahjohn]

ThreadOpenAddedConnections started
trying connection 193.68.21.19:17771 lastseen=363042.4hrs
ThreadMessageHandler started
ipcThread started
connected 193.68.21.19:17771
send version message: version 60006, blocks=484641, us=0.0.0.0:0, them=193.68.21.19:17771, peer=193.68.21.19:17771
0 addresses found from DNS seeds
ThreadDNSAddressSeed exited
GetMyExternalIP() received [65.130.100.203] 65.130.100.203:0
GetMyExternalIP() returned 65.130.100.203
AddLocal(65.130.100.203:17771,5)
socket no message in first 60 seconds, 0 1
disconnecting node 193.68.21.19:17771
Flushed 0 addresses to peers.dat  2ms
trying connection 193.68.21.19:17771 lastseen=363042.5hrs
connected 193.68.21.19:17771
send version message: version 60006, blocks=484641, us=65.130.100.203:17771, them=193.68.21.19:17771, peer=193.68.21.19:17771
socket closed
disconnecting node 193.68.21.19:17771

[danbi]

i love to talk in pictures   :

u can see diamond network as a herd of sheep's with a few shepherd dogs and a shepherd

shepherd is the foundation
shepherd dogs is the network stabilization tool like permanent nodes seed nodes checkpoint wallet filter and so on

from time to times wolves try their luck and create confusion
but soon repelled by shepherd dogs

but some sheep's special if they don't stay close with the shepherd and the shepherd dogs can become victim to the wolves


long story short:

stay with our suggested conf setting and wallet upgrades

some people might suggest:
leave the sheep's on their own they will follow their instincts (base wallet code) and live and prosper
try that with real sheep's and tell me how many left after a year or two

Your description sounds more like a centralized fiat system than a decentralized cryptocurrency. In the United States, your shepherd relates to The Fed, and your shephard's dogs are the Secret Service. And that's not working that well, thus we are all interested in cryptocurrencies.

A new version of diamond needs to be released asap that fixes this genesisblock bug that Danbi and Polanskiman are citing. When a bug causes a blockchain fork, the bug that causes it must be addressed and fixed otherwise it might be hard to get Cryptsy and other exchanges to trust that it won't happen again.
The bitcoin block fork of a year ago. It was caused by a bug and fixed with a patch:
http://www.reddit.com/r/Bitcoin/comments/1a51xx/now_that_its_over_the_blockchain_fork_explained/

Having everyone connect to one host to get the correct block chain is a temporary measure and it will only work if the all miners on that chain hash faster than the other. This may or may not happen, and the latest news according to pallas and Atomicca regarding the falling difficulty level might indicate that danbi's chain is failing.

We need a fix for the bug asap. The longer this goes on the more money is lost.

If you do not want to contradict yourself, you will admit that this is not centralized, publicly developed crypto currency. As such, if you know what the solution is, please either speak up, or if you have the expertise, contribute code to fix it.

Yes, this is a very temporary and very inconvenient measure, mostly for the permanent node operator!

By the way, we already implemented a fix related to the bitcoin bug you described.

[jepistons]

its ok people the devs will figure it out seems I lost 2500 dmd since this attack has happen either I was on the wrong fork or block chain I have faith thing will be fixed soon that only makes dmd  stronger

[jhed]

i love to talk in pictures   :

u can see diamond network as a herd of sheep's with a few shepherd dogs and a shepherd

shepherd is the foundation
shepherd dogs is the network stabilization tool like permanent nodes seed nodes checkpoint wallet filter and so on

from time to times wolves try their luck and create confusion
but soon repelled by shepherd dogs

but some sheep's special if they don't stay close with the shepherd and the shepherd dogs can become victim to the wolves


long story short:

stay with our suggested conf setting and wallet upgrades

some people might suggest:
leave the sheep's on their own they will follow their instincts (base wallet code) and live and prosper
try that with real sheep's and tell me how many left after a year or two

Your description sounds more like a centralized fiat system than a decentralized cryptocurrency. In the United States, your shepherd relates to The Fed, and your shephard's dogs are the Secret Service. And that's not working that well, thus we are all interested in cryptocurrencies.

A new version of diamond needs to be released asap that fixes this genesisblock bug that Danbi and Polanskiman are citing. When a bug causes a blockchain fork, the bug that causes it must be addressed and fixed otherwise it might be hard to get Cryptsy and other exchanges to trust that it won't happen again.
The bitcoin block fork of a year ago. It was caused by a bug and fixed with a patch:
http://www.reddit.com/r/Bitcoin/comments/1a51xx/now_that_its_over_the_blockchain_fork_explained/

Having everyone connect to one host to get the correct block chain is a temporary measure and it will only work if the all miners on that chain hash faster than the other. This may or may not happen, and the latest news according to pallas and Atomicca regarding the falling difficulty level might indicate that danbi's chain is failing.

We need a fix for the bug asap. The longer this goes on the more money is lost.

Yes it is a description of a centralised network, but at the moment this is the only way to ensure Diamonds integrity.
Ideally there would be no time wasters who try to bring us down so we didn't have to resort to this configuration. But this is not an ideal world.

Leave Cryptsy to us, if they really fork we will inform them. It's not the first and the last time we will deal with them and anyone following this thread knows the drill.

Danbis chain is not failing, it's protected well enough to withstand whatever these time wasters throw at us.

Yes we need a fix. But the same bug is present in every percoin/novacoin besed coin. A lot of people reported it but no one came with the solution so it will involve a lot of analytical work to pinpoint the cause, but this takes time.
The link you provided adds nothing to the solution of the problem and it is something different that we're dealing with.  

Jhed - stop being melodramatic as it's not helping anyone, apart from time wasters.
 

According to this page at peercoin, pszTimestamp is supposed to have a max of 91 chars:
https://github.com/Peershares/Peershares/wiki/Genesis-Block-(Starting-a-New-Blockchain-Instance)

But ours is 117 characters:
https://github.com/DMDcoin/Diamond/blob/master/src/main.cpp#L2649

Is that the problem?

[jhed]

Danbi, maybe you could share your list of trusted nodes here? Then we could add them all into our configs with a connect line and stay on the right chain and not need to rely just on your IP.

Or if somebody has a listening node (don't do this) that is able to stay on the correct chain, maybe they could share their getpeerinfo, so that we can add some data for connect lines.

[SRBOOTH]

I believe I am good sync listening.........



02:53:44

[
{
"addr" : "[2001:0:5ef5:79fd:34b5:38b6:c1d3:1ded]:51258",
"services" : "00000001",
"lastsend" : 1406973105,
"lastrecv" : 1406973143,
"conntime" : 1406972800,
"version" : 60006,
"subver" : "/Diamond:2.0.3/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 514028,
"banscore" : 0
},
{
"addr" : "62.44.226.18:17771",
"services" : "00000001",
"lastsend" : 1406973143,
"lastrecv" : 1406973143,
"conntime" : 1406972802,
"version" : 60006,
"subver" : "/Diamond:2.0.3/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 514028,
"banscore" : 0
},
{
"addr" : "193.68.21.19:17771",
"services" : "00000001",
"lastsend" : 1406973144,
"lastrecv" : 1406973143,
"conntime" : 1406972812,
"version" : 60006,
"subver" : "/Diamond:2.0.3.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 514028,
"banscore" : 0
},
{
"addr" : "86.18.76.197:34821",
"services" : "00000001",
"lastsend" : 1406973145,
"lastrecv" : 1406973165,
"conntime" : 1406972939,
"version" : 60006,
"subver" : "/Diamond:2.0.3/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 241142,
"banscore" : 0
},
{
"addr" : "131.191.88.111:17771",
"services" : "00000001",
"lastsend" : 1406973143,
"lastrecv" : 1406973180,
"conntime" : 1406972950,
"version" : 60006,
"subver" : "/Diamond:2.0.2.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 386226,
"banscore" : 0
},
{
"addr" : "178.248.85.73:17771",
"services" : "00000001",
"lastsend" : 1406973143,
"lastrecv" : 1406973143,
"conntime" : 1406972978,
"version" : 60006,
"subver" : "/Diamond:2.0.3/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 514033,
"banscore" : 0
},
{
"addr" : "192.186.133.74:17771",
"services" : "00000001",
"lastsend" : 1406973143,
"lastrecv" : 1406973143,
"conntime" : 1406972979,
"version" : 60006,
"subver" : "/Diamond:2.0.2.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 386226,
"banscore" : 0
},
{
"addr" : "46.242.73.221:17771",
"services" : "00000001",
"lastsend" : 1406973143,
"lastrecv" : 1406973144,
"conntime" : 1406973013,
"version" : 60006,
"subver" : "/Diamond:2.0.3/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 514033,
"banscore" : 0
},
{
"addr" : "122.149.252.123:17771",
"services" : "00000000",
"lastsend" : 1406973223,
"lastrecv" : 0,
"conntime" : 1406973223,
"version" : 0,
"subver" : "",
"inbound" : false,
"releasetime" : 0,
"startingheight" : -1,
"banscore" : 0
}
]

[SRBOOTH]

Current get mininginfo----------



{
"blocks" : 514039,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 39.14637049,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 2741661329,
"pooledtx" : 0,
"stakepower" : 0,
"testnet" : false
}

[pallas]

My node went on a wrong fork again! :-(

[utahjohn]

welcome to the club pallas ... I spent 2 days syncing and then 5 minutes into mining I'm fubar again ....

[cryptonit]

Hello cryptonit,

My wallet is still staying synced with no problems but coins that I sent still haven't arrived at cryptsy.
What can be done?
Should I generate a new address there and try again?
Please explain what needs to be done.

cryptsy does the only right thing at this moment
they dont sync their exchange with their wallet
until everything is sorted

so ur coins there but not visible at exchange

[cryptonit]

last day to earn lotto numbers for the drawing tomorrow
http://multipool.bit.diamonds/
lotto numbers of 3.august cound for september

2.august are last one counting for the drawing on 3.august