Author

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

sr. member
Activity: 393
Merit: 250
As announced previously, the http://dmdpool.digsys.bg pool has now introduced 1% fee from 1st of August 2014.

Let's hope this change, by eliminating "unfair competition" will encourage more Diamond mining pols to be created.
legendary
Activity: 3052
Merit: 1053
bit.diamonds | uNiq.diamonds
diff raise again sign situation solved miners found their way home

time for me move my miners again to http://multipool.bit.diamonds/

we made over 1100 DMD there already in a few days

join us and earn not only DMD but also a chance to win 100DMD in multipool lotto

with ur average daily hashrate u earn there lotto tickets (numbers) more hashrate more tickets (up to 6 max each day)

next drawing of winner is sunday 3rd august

the winner will be choosen by austrian officicial lotto jackpotnumber from 3.august
(will be visible there after around 21:00 europe time on 3rd august http://www.win2day.at/gaming/RundenPlakat_wai.jsp)

our lotto number which is closest to it wins

close in mathematical sence not how many numbers are the same

so example

123456 joker number
923456 not closest number
187654 closest number
sr. member
Activity: 393
Merit: 250

And my Diamond.conf is this on both machines

listen=0
server=1
daemon=1
rpcuser=username
rpcpassword=passowrd
rpcport=1444
rpcallowip=*
rpcthreads=8182
connect=193.68.21.19
noirc=1
 

and today this is the second time that the mining server get's on the wrong fork


This is pretty much not possible. You cannot get on the wrong fork when connected to only 193.68.21.19. There is no way you can get a wrong block.

What does 'getpeerinfo' return? If your setup is correct, you should have only one peer, 193.68.21.19.

Also, rpcallow=* is a very bad idea. rpcthreads=8182 possibly too...
legendary
Activity: 3052
Merit: 1053
bit.diamonds | uNiq.diamonds
as an investor i dont like new wallets every week , it makes me nervous .
Another problem, my wallet evrey time it shut-down , i have to resync from scratch whit loadblok=blk0001.dat, that issue must be fixed asap ( again this is POS fault)
Please , focus on stability, we don’t need a fancy wallet , or fancy features , as an investor i want reliable block chain, HIGH HASHRATE  nothing more.
sory for my bad inglish
Regards
Porfirio from sunny  portugal Smiley

hi porfirio

we take ur feedback very serious thx for posting
still one or two new wallets will come in this stabilisation phase but not for fancy features
we want exact same as u a stable network and stable wallet

but later on most wallet releases will be optional so fancy stuff for people who want but noone forced to update

regarding ur resync after each shut down please tell us what wallet version u run
i strong suggest upgrade to 2.0.3 to everyone
it will be soon mandatory to have at least this version

legendary
Activity: 2716
Merit: 1094
Black Belt Developer
I've experienced this error:

diamondd: /usr/include/boost/thread/pthread/recursive_mutex.hpp:101: void boost::recursive_mutex::lock(): Assertion `!pthread_mutex_lock(&m)' failed.

A couple times when stopping the daemon.
legendary
Activity: 1414
Merit: 1013
DMD info: https://diamond-info.github.io/
There is still a lot of work to strengthen the security of the network of Diamond and prevent such attacks in the future. Such methods are available and should be used .. The Diamond should be one of the most stable coins to such attacks. Only then will success.
full member
Activity: 274
Merit: 100
Still having blockchain problems ... re-indexed from beginning and diff was 35-45 for several hours and then dropped to 9.  This is frustrating Huh

yep that what’s happened to me again  Undecided
full member
Activity: 274
Merit: 100
I would suggest those suffering from this issue follow this checklist:

1. Upgrade to the latest wallet version (2.0.3) -- as a bonus you are getting the fast index feature, which besides being.. fast, helps great deal with the block index corruption (does not resolve it 100% yet).
2. Delete your peers.dat file!
3. Then make sure you have noirc=1 in the Diamond.conf file.
4. Make sure you have connect=193.68.21.19 in your configuration file. (or, later switch it to addnode=193.68.21.19)
5. If you do not run your wallet all the time (thus acting as a node for others), it might be helpful to have listen=0 in the configuration file as well.
6. Download the posted recent block chain (or sync from scratch).

So in summary, you need this in the config file:

listen=0
noirc=1
connect=193.68.21.19

The later might be addnode= instead so you get more peers from that node and be connected when it is down or unreachable. Unfortunately, that node might be banning you... because of your past behavior. We are working to make the ban duration shorter.

PS: We want to get rid of wallets version 2.0.2.1. Unfortunately, this also means we need to get rid of 2.0.2.2 as due to some error that shows itself as 2.0.2.1 too... So if you have one of these versions, *please* upgrade.

PPS: Re-arranged the steps appropriately.

Hello all from Portugal
this is my first post here
I have never write here but i read it every day, and i'm am a DMD miner / investor

But today this is getting very hard

I have two servers one for solo mining where my miners connect at  150 mhs and another machine just for staking  

And my Diamond.conf is this on both machines

listen=0
server=1
daemon=1
rpcuser=username
rpcpassword=passowrd
rpcport=1444
rpcallowip=*
rpcthreads=8182
connect=193.68.21.19
noirc=1
 

and today this is the second time that the mining server get's on the wrong fork
this is very bad for the reputation

A situation like this kill atheistcoin, almost kill fluttercoin

Of course my  wallets are always updated

I think the most important feature for any type of currency ( crypto or flat ) is stability and the last months every week some coin got forked, it happen to me in flut , DMD , ATH , STR  and so on

As an investor i already dumped 5M flut , and I'm start thinking in dump my  3000 DMD, and begin to miner and dump .

I really like DMD , the small reward , make it difficult and interesting , and the sloow adition of coin's to the network is a huge advantage .

By the way , and this is just my opinion  , POS was a huge mistake it bring more problems to the blockchain than advantages , POW and high hash rate is what makes a coin secure , look a dogecoin, since the hashrate drops, people star concerning about network security price drops and i think that doge will eventualy die .

And the reason i love DMD was the groestl algo and a fixed reward of 1 DMD , POS sucks .


Since de POS switch , this coin have had many problems, and as an investor i dont like new wallets every week , it makes me nervous .

Another problem, my wallet evrey time it shut-down , i have to resync from scratch whit loadblok=blk0001.dat, that issue must be fixed asap ( again this is POS fault)

Please , focus on stability, we don’t need a fancy wallet , or fancy features , as an investor i want reliable block chain, HIGH HASHRATE  nothing more.

sory for my bad inglish


Regards
Porfirio from sunny  portugal Smiley
 
hero member
Activity: 630
Merit: 500
Still having blockchain problems ... re-indexed from beginning and diff was 35-45 for several hours and then dropped to 9.  This is frustrating Huh
legendary
Activity: 3696
Merit: 2219
💲🏎️💨🚓
legendary
Activity: 3052
Merit: 1053
bit.diamonds | uNiq.diamonds
Vote for Diamond DMD on

click pic or this link https://www.mintpal.com/voting#DMD

place #115  now

paying 1 DMD to everyone who reached a new rank

so first one reporting #114 and walletaddress
@ http://bit.diamonds/community/index.php/topic,16.0.html
gets 1 DMD
IMPORTANT only claim rewards on
http://bit.diamonds/community/index.php/topic,16.0.html[/b][/color]

Dont forget our Design Contest!

we wont change the coin as main logo itself
(or just in a very similar improved version)

so if u think u can do better
and stay with design and color scheme that fit to our coin logo and our website
http://bit.diamonds/promo.html

please show us ur skills

we will pay some DMD for each serious attempt and at least 200 DMD for the great winner!
(required is logo (have to be very close to original) buttons and icons for ANN thread
and some examples of promo banners where we get all the used art modules to create more similar looking banners)
(if there is nothing that fullfil requirements we can also choose no winner..)


contest will run over a month we will select winner in first week of september

DMD Multipool Lotto
next drawing 3.august 100 DMD
http://multipool.bit.diamonds/
full member
Activity: 266
Merit: 100
Here's are some stubborn people:

{
"addr" : "72.200.68.98:61887",
"services" : "00000001",
"lastsend" : 1406800492,
"lastrecv" : 1406800419,
"conntime" : 1406800418,
"version" : 60006,
"subver" : "/Diamond:2.0.2.1/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 511431,
"banscore" : 0
},

{
"addr" : "131.191.88.111:17771",
"services" : "00000001",
"lastsend" : 1406800608,
"lastrecv" : 1406800577,
"conntime" : 1406800564,
"version" : 60006,
"subver" : "/Diamond:2.0.2.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 386226,
"banscore" : 0
}
full member
Activity: 266
Merit: 100
Current checkpoint:

{
"synccheckpoint" : "00000000011c6943555847f7a7c701cb21d6c1e33a56e4a3be2593424dc7f80d",
"height" : 511430,
"timestamp" : "2014-07-31 09:51:11 UTC"
}
legendary
Activity: 3052
Merit: 1053
bit.diamonds | uNiq.diamonds
a crew of a sailing ship can prove their skills only in a storm

we just had hard weather and high waves

thx to all crewmen special danbi who show that our crew and our ship is no easy target
for those who play with wind and weather and feel like gods

they think "we make em - we break em"

but we dont need their pumps and we dont die to their attacks

we might be a playball of elements
but not of intended manipulation by self declared crypto gods......



thx for all the support of our loyal community
u are the real backbone of our coin

hero member
Activity: 742
Merit: 500

danbi

after your council all in norm.
sr. member
Activity: 393
Merit: 250
I would suggest those suffering from this issue follow this checklist:

1. Upgrade to the latest wallet version (2.0.3) -- as a bonus you are getting the fast index feature, which besides being.. fast, helps great deal with the block index corruption (does not resolve it 100% yet).
2. Delete your peers.dat file!
3. Then make sure you have noirc=1 in the Diamond.conf file.
4. Make sure you have connect=193.68.21.19 in your configuration file. (or, later switch it to addnode=193.68.21.19)
5. If you do not run your wallet all the time (thus acting as a node for others), it might be helpful to have listen=0 in the configuration file as well.
6. Download the posted recent block chain (or sync from scratch).

So in summary, you need this in the config file:

listen=0
noirc=1
connect=193.68.21.19

The later might be addnode= instead so you get more peers from that node and be connected when it is down or unreachable. Unfortunately, that node might be banning you... because of your past behavior. We are working to make the ban duration shorter.

PS: We want to get rid of wallets version 2.0.2.1. Unfortunately, this also means we need to get rid of 2.0.2.2 as due to some error that shows itself as 2.0.2.1 too... So if you have one of these versions, *please* upgrade.

PPS: Re-arranged the steps appropriately.
hero member
Activity: 630
Merit: 500
I resynced from latest blockchain that Danbi provided.  And already forked again with diff = 7 ... shutting down my DMD solo mining for now Sad and closing wallet Sad  Fortunately I have no DMD on exchanges right now ...
member
Activity: 134
Merit: 12
From my observations following nodes are doing unusual things:

173.246.103.92:17771
192.75.207.148:17771

I am getting warnings for outgoing connections from Diamond-Qt.exe to 98.142.248.233 as well.

I also had to rebuild the blockchain today.

Btw. what are the exact needs for the Design Contest?
sr. member
Activity: 393
Merit: 250
Quote
I am still trying to pinpoint the exact cause of it, and will appreciate any ideas someone might have...
Maybe just someone checks the network Diamond strength, because even half a year ago a lot of coins were split (ftc, trc, and others) some unknown with large computing power.

Diamond network is protected from such an attack, but the individual nodes are not. As it turns out, they may be disconnected from the network for up to 24 hours.
sr. member
Activity: 393
Merit: 250
An current block chain for fast syncing is available at http://diamond.danbo.bg/downloads/dmdchain20140731-fast.7z
Also with .zip extension. Please note this is for the v2.0.3 and later wallets, that support fast index.
Jump to: