Author

Topic: [ANN] ¤ DMD Diamond 3.0 | Scarce ¤ Valuable ¤ Secure | PoS 3.0 | Masternodes 65% - page 741. (Read 1260636 times)

newbie
Activity: 26
Merit: 0
i love to talk in pictures  Cool :

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 Wink

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?
sr. member
Activity: 252
Merit: 250
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 Smiley
sr. member
Activity: 393
Merit: 250
i love to talk in pictures  Cool :

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 Wink

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.
hero member
Activity: 630
Merit: 500
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
hero member
Activity: 630
Merit: 500
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 Sad sync from Danbi node not happening.
full member
Activity: 266
Merit: 100
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?
full member
Activity: 236
Merit: 100

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?

hero member
Activity: 630
Merit: 500
Grrr ... now what is going on Huh my wallet stuck and not syncing from danbi ...  miner not receiving work Huh
full member
Activity: 236
Merit: 100
Cryptsy withdrawals work. I've just checked it.

I haven't checked deposits, but Cryptsy informs that :
Quote
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.

sr. member
Activity: 309
Merit: 250
Sit Tight Boys. Smiley

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
full member
Activity: 266
Merit: 100
sr. member
Activity: 266
Merit: 250
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.
legendary
Activity: 1504
Merit: 1002
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
full member
Activity: 266
Merit: 100
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.

VERY IMPORTANT: Please update to version 2.0.3 of the wallet if you have a lower version.

sr. member
Activity: 309
Merit: 250
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



Also, may I ask how to check wallet is correct, once it syncs?
full member
Activity: 266
Merit: 100
Got one wallet on correct chain and now minting Smiley
Syncing miner wallet from this one and danbi's ... will be mining again soon enough with 2 local nodes connected to each other and danbi node Smiley
Will bring another local node on another box just to keep my local node net sane LOL

Good then. Mine as well since last night.
sr. member
Activity: 309
Merit: 250
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

full member
Activity: 266
Merit: 100

Hello, anyone that can help

After downloading the blockchain+data file and replacing relevant files and restarting the wallet it seems to be in sinc and working fine.  However I tried sending a few coins to cryptsy as a test and they are not getting there, the wallet says over 50 confirmations but no coins at cryptsy.
Does anyone know what is happening, why the coins aren't making it to cryptsy?


check if transaction id is visible here
http://diamond.danbo.bg:2750/chain/Diamond

if not u are on wrong chain
please update us if coins arrived a cryptsy so its ckear they on right chain too


I checked the transaction id and found a match. It was there with the amount of coins I sent.
The coins still haven't turned up at cryptsy with over 150 confirmations on my wallet.



Nobody should be trying to send money into Cryptsy right now. There was previous claims by cryptonit that cryptsy was on danbi's chain, but as you've noticed, they are not.

In your case, your money will show up when Cryptsy gets on danbi's chain. Maybe it already has? But in any case Cryptsy is not going to be happy when they learn the bug is not fixed yet.

Your recommendations are useless and creating unnecessary FUD.
full member
Activity: 266
Merit: 100
i love to talk in pictures  Cool :

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 Wink

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.

Do you think we are all sitting here doing nothing. Your FUD is starting to be annoying specially coming from a new comers who doesn't seem to like to read and look for the proper information before jumping on people's neck.

I recommend you to chill and follow the recommendations.
full member
Activity: 266
Merit: 100
Please note you can no longer connect to 193.68.21.19 if you are using any pre 2.0.3 Diamond wallet.
Cool, will it help the forking situation?
connected subver /Diamond:2.0.3.1/

Yes that's the next version coming along. If I understood correctly, it will ban anything below 2.0.3
Jump to: