dont forget to change "scantime" and "expiry" in your sgminer conf
What they should be? 
Topic: [ANN] ¤ DMD Diamond 3.0 | Scarce ¤ Valuable ¤ Secure | PoS 3.0 | Masternodes 65% - page 543. (Read 1260677 times)
April 12, 2015, 04:23:38 AM
April 12, 2015, 04:21:28 AM
dont forget to change "scantime" and "expiry" in your sgminer conf
April 12, 2015, 04:19:28 AM
Which chain is the right, AGAIN?
Solo mined 20 dmd, but cryptoid not showing them.
Solo mined 20 dmd, but cryptoid not showing them.
April 12, 2015, 04:19:02 AM
dont be nervous at tests the trigger blocks
the first pow and pos after trigger where always slow found
after first found soon the 100 sec blocktime will establish
the first pow and pos after trigger where always slow found
after first found soon the 100 sec blocktime will establish
April 12, 2015, 04:13:43 AM
Already emailed and PM Davembg to adjust percents, STOP mining on any pools till we can confirm testing ...
April 12, 2015, 04:09:31 AM
Outstanding
1,000,015 DMD
1,000,015 DMD
April 12, 2015, 04:09:13 AM
Woo Hoo we just bumped over 1000000 coins
April 12, 2015, 04:01:50 AM
99 coins to go 
Switching all miners to solo when it gets down to around 25 ...
Will be working with davembg to bring DonkeyPool into line with foundation fee, admin fee, minor adjustments will have to be made.
Switching all miners to solo when it gets down to around 25 ...
Will be working with davembg to bring DonkeyPool into line with foundation fee, admin fee, minor adjustments will have to be made.
April 12, 2015, 03:52:03 AM
cryptsy just confirmed they are with https://chainz.cryptoid.info/dmd/
and monitor the trigger and their dmd wallet
so deposit/withdraw should be soon/already possible
and monitor the trigger and their dmd wallet
so deposit/withdraw should be soon/already possible
April 12, 2015, 03:38:50 AM
blockcount visible there https://chainz.cryptoid.info/dmd/
actual 42 wallets sync with mainchain
just danbi pool and a few attached wallets run in a fork and mine hot air
https://chainz.cryptoid.info/dmd/
(this conf include all mainnodes even that ones who are non on right chain but the lot number of other good nodes outweight that and as soon as alex is alive again he will fix the few backbone nodes who stuck with danbi chain)
for trigger if u not allready on this chain use a backup blockchain and the sync with this conf and u are fine
some guy opened his wallet first time since 10 months and minted a 400 dmd POS block so the trigger is very close
will happen in next 2 hours maybe earlier if someone else mint a big POS block
prepare for warp!
lets see what await us on the other side
actual 42 wallets sync with mainchain
just danbi pool and a few attached wallets run in a fork and mine hot air
https://chainz.cryptoid.info/dmd/
Quote
listen=1
noirc=1
bantime=1800
maxconnections=50
#foundation nodes
addnode=193.68.21.19
addnode=54.191.208.14
addnode=54.255.133.30
addnode=54.86.164.216
#community nodes 2015.04.10
#NineEleven
addnode=193.136.97.30
addnode=193.136.96.30
#temporary for trigger 1MIL:
addnode=83.212.204.1
addnode=46.242.76.211
addnode=198.146.5.4
addnode=213.229.0.41
addnode=195.114.146.253
addnode=95.24.100.97
addnode=5.196.190.82
addnode=82.193.156.120
addnode=190.75.143.144
addnode=72.222.183.237
addnode=5.135.21.225
addnode=184.191.161.130
addnode=99.21.71.124
addnode=54.191.208.14
addnode=62.44.226.18
addnode=193.68.6.1
addnode=24.255.11.244
addnode=50.186.77.84
addnode=50.149.211.203
addnode=54.255.133.30
noirc=1
bantime=1800
maxconnections=50
#foundation nodes
addnode=193.68.21.19
addnode=54.191.208.14
addnode=54.255.133.30
addnode=54.86.164.216
#community nodes 2015.04.10
#NineEleven
addnode=193.136.97.30
addnode=193.136.96.30
#temporary for trigger 1MIL:
addnode=83.212.204.1
addnode=46.242.76.211
addnode=198.146.5.4
addnode=213.229.0.41
addnode=195.114.146.253
addnode=95.24.100.97
addnode=5.196.190.82
addnode=82.193.156.120
addnode=190.75.143.144
addnode=72.222.183.237
addnode=5.135.21.225
addnode=184.191.161.130
addnode=99.21.71.124
addnode=54.191.208.14
addnode=62.44.226.18
addnode=193.68.6.1
addnode=24.255.11.244
addnode=50.186.77.84
addnode=50.149.211.203
addnode=54.255.133.30
(this conf include all mainnodes even that ones who are non on right chain but the lot number of other good nodes outweight that and as soon as alex is alive again he will fix the few backbone nodes who stuck with danbi chain)
for trigger if u not allready on this chain use a backup blockchain and the sync with this conf and u are fine
some guy opened his wallet first time since 10 months and minted a 400 dmd POS block so the trigger is very close
will happen in next 2 hours maybe earlier if someone else mint a big POS block
prepare for warp!
lets see what await us on the other side
April 12, 2015, 03:36:26 AM
Now something very strange is happening. The client get connect and disconnect... when get connect says difficulty 56. What im missing? In the block explorer says difficulty 22, something is wrong
One of the masternodes is misbehaving, specifically the wallet of Danbi's pool, it will get banned by your wallet soon enough ... April 12, 2015, 03:31:19 AM
Now something very strange is happening. The client get connect and disconnect... when get connect says difficulty 56. What im missing? In the block explorer says difficulty 22, something is wrong
April 12, 2015, 03:23:10 AM
Hi
as i see we need to change the conf file. How will be this time? Im not a programmer just a proud owner of some Diamonds
Thanks in advance
as i see we need to change the conf file. How will be this time? Im not a programmer just a proud owner of some Diamonds
Thanks in advance
See https://bitcointalksearch.org/topic/m.11060015
Thanks for the fast answer
"Changed .conf to addnode= and listen=1" means
listen=1
noirc=1
addnode=193.68.21.19
addnode=54.191.208.14
addnode=54.255.133.30
addnode=54.86.164.216
bantime=600
Is that correct?
Yes. It has also been recommended to increase bantime to 3600 (1 hour) or even 10800 (3 hours).
With upcoming reward reduction and increase in blocktime to 100s I would suggest 20000 at that time, allowing blocks time to mature ...
Done, thanks a lot for ur help
April 12, 2015, 03:13:20 AM
Hi
as i see we need to change the conf file. How will be this time? Im not a programmer just a proud owner of some Diamonds
Thanks in advance
as i see we need to change the conf file. How will be this time? Im not a programmer just a proud owner of some Diamonds
Thanks in advance
See https://bitcointalksearch.org/topic/m.11060015
Thanks for the fast answer
"Changed .conf to addnode= and listen=1" means
listen=1
noirc=1
addnode=193.68.21.19
addnode=54.191.208.14
addnode=54.255.133.30
addnode=54.86.164.216
bantime=600
Is that correct?
Yes. It has also been recommended to increase bantime to 3600 (1 hour) or even 10800 (3 hours).
With upcoming reward reduction and increase in blocktime to 100s I would suggest 20000 at that time, allowing blocks in disputed fork time to mature ...
April 12, 2015, 03:06:25 AM
Hi
as i see we need to change the conf file. How will be this time? Im not a programmer just a proud owner of some Diamonds
Thanks in advance
as i see we need to change the conf file. How will be this time? Im not a programmer just a proud owner of some Diamonds
Thanks in advance
See https://bitcointalksearch.org/topic/m.11060015
Thanks for the fast answer
"Changed .conf to addnode= and listen=1" means
listen=1
noirc=1
addnode=193.68.21.19
addnode=54.191.208.14
addnode=54.255.133.30
addnode=54.86.164.216
bantime=600
Is that correct?
April 12, 2015, 02:59:29 AM
Hi
as i see we need to change the conf file. How will be this time? Im not a programmer just a proud owner of some Diamonds
Thanks in advance
as i see we need to change the conf file. How will be this time? Im not a programmer just a proud owner of some Diamonds
Thanks in advance
See https://bitcointalksearch.org/topic/m.11060015
April 12, 2015, 02:51:35 AM
Hi
as i see we need to change the conf file. How will be this time? Im not a programmer just a proud owner of some Diamonds
Thanks in advance
as i see we need to change the conf file. How will be this time? Im not a programmer just a proud owner of some Diamonds
Thanks in advance
April 12, 2015, 02:11:38 AM
I think the BIG mistake was allowing a pool to gain 51%+ hashrate, complacency on miner's part by allowing this to happen. spread the hashrate to prevent this. Also centralized network was a point of failure, the blockchain is stable again now that de-centralization of network is being done by many wallet holders and miners using addnode= and listen=1 thereby allowing the network to heal itself rather than forcing connect= on miners which allows a point of failure, the centralized masternodes ...
April 12, 2015, 01:57:12 AM
These attacks only show DMD s got bright future. Why would anyone attack DMD if they do not think it s valuable.
Also, we re reaching 1 mil in about 12-16 hours. I hope at that point this problem should go away cause the new code will kick in.
Also, we re reaching 1 mil in about 12-16 hours. I hope at that point this problem should go away cause the new code will kick in.
What makes you certain this is an attack and not some kind of flaw?
Cause we ve been using the same code for months and everything was fine just until few days before the reward reduction. Also, take a look at some earlier posts by Cryptonit.
I have no proof for this but I am 100% sure this is not a mistake on our side. Dev team has spent hours during the last few days to fend off this attack and I think all we need to do is to wait till tonight. The new code should resolve these issues.
DMD Diamond s NOT dead. There are a lot of good people working behind the scene so we can all sit back and relax once the price starts going up. Have a little faith, this coins is not Paycoin.
Jump to: