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

[danbi]

Please note you can no longer connect to 193.68.21.19 if you are using any pre 2.0.3 Diamond wallet.

[1714863054]

1714863054

[1714863054]

1714863054

[1714863054]

1714863054

[1714863054]

1714863054

[utahjohn]

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/

[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.

[digi123]

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.

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.

[jhed]

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.

[utahjohn]

Will someone on correct blockchain verify this checkpoint with getblock

17:37:59

getcheckpoint
17:37:59

{
"synccheckpoint" : "0000000000d3e4e307ce32201bf226a5e7f2c0ebbae5b48d528397f923686aec",
"height" : 513570,
"timestamp" : "2014-08-01 23:36:11 UTC"
}

17:38:29

getinfo


17:38:29

{
"version" : "v2.0.3.0",
"protocolversion" : 60006,
"walletversion" : 60000,
"balance" : 514.51305200,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 513570,
"moneysupply" : 519518.77674200,
"connections" : 1,
"proxy" : "",
"ip" : "65.130.98.156",
"difficulty" : 33.30559349,
"testnet" : false,
"keypoololdest" : 1404277506,
"keypoolsize" : 102,
"paytxfee" : 0.00000000,
"unlocked_until" : 0,
"errors" : ""
}

[digi123]

my latest checkpoint,


09:48:12

{
"synccheckpoint" : "00000000010726cf2ceea3fe6d0e955aae12cb51cd8db7d3547e7e04c77e45cf",
"height" : 513578,
"timestamp" : "2014-08-01 23:41:37 UTC"
}

[utahjohn]

my latest checkpoint,


09:48:12

{
"synccheckpoint" : "00000000010726cf2ceea3fe6d0e955aae12cb51cd8db7d3547e7e04c77e45cf",
"height" : 513578,
"timestamp" : "2014-08-01 23:41:37 UTC"
}

Mine agrees

17:45:33

getblock 00000000010726cf2ceea3fe6d0e955aae12cb51cd8db7d3547e7e04c77e45cf


17:45:33

{
"hash" : "00000000010726cf2ceea3fe6d0e955aae12cb51cd8db7d3547e7e04c77e45cf",
"confirmations" : 3,
"size" : 324,
"height" : 513578,
"version" : 4,
"merkleroot" : "34af8e153185e322ec07b77dcd400a807deba73899184cf6222eef26617e2624",
"mint" : 1.05000000,
"time" : 1406936497,
"nonce" : 96976403,
"bits" : "1c0678ad",
"difficulty" : 39.55813246,
"previousblockhash" : "0000000002ef87373426070899bc932ce28e94048c9601fc559ce11eb12f5cf6",
"nextblockhash" : "0000000002b064232d06b74b2a736c64a72bf6bb369860c52e732ac1c37627a9",
"flags" : "proof-of-work",
"proofhash" : "00000000010726cf2ceea3fe6d0e955aae12cb51cd8db7d3547e7e04c77e45cf",
"entropybit" : 1,
"modifier" : "98414c7b3a6a2094",
"modifierchecksum" : "4610ed08",
"tx" : [
"34af8e153185e322ec07b77dcd400a807deba73899184cf6222eef26617e2624"
],
"signature" : "3044022025af3740de7d292f40ca379c03624358dbf2588b04ad8ec3cf0aaa347837fcb8022040c f457c34f0fb926f05a952ca34fffa740d12f5238a127e0101e831e3087d7b"
}

[digi123]

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.

Is someone contacting cryptsy and sorting things out with them so people can start using the exchange again?

[popshot]

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.

[popshot]

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.
 

[polanskiman]

http://www.liveipmap.com/193.68.6.1
Is on same ISP as Danbi's pool ... dcave.digsys.bg

Calm down. This thing sits on my desk and guaranteed does not have any open proxy service running. It is also not located where "they" identified it, but.. that's fine

The "/Diamond-seeder:0.01/"  is a new secret Diamond weapon I was prototyping today. Figured people will spot it, but it was too late to masquerade. Good catch. Only if we can identify the abusers instead (unfortunately the wallet does not log where the blocks come from).

ahaha Utahjohn got carried away here. Relax is the word.

[utahjohn]

http://www.liveipmap.com/193.68.6.1
Is on same ISP as Danbi's pool ... dcave.digsys.bg

Calm down. This thing sits on my desk and guaranteed does not have any open proxy service running. It is also not located where "they" identified it, but.. that's fine

The "/Diamond-seeder:0.01/"  is a new secret Diamond weapon I was prototyping today. Figured people will spot it, but it was too late to masquerade. Good catch. Only if we can identify the abusers instead (unfortunately the wallet does not log where the blocks come from).

ahaha Utahjohn got carried away here. Relax is the word.

Got one wallet on correct chain and now minting
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
Will bring another local node on another box just to keep my local node net sane LOL

[polanskiman]

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

[polanskiman]

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.

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.

[polanskiman]

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.

[SRBOOTH]

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

[polanskiman]

Got one wallet on correct chain and now minting
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
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.

[SRBOOTH]

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?

[polanskiman]

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.