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

Very strange indeed ... Danbi's pool shows Pool hashrate 2262.8MHs and Network hashrate 1142.28 diff ~18
(and no i didn't mix up the numbers LOL)

My wallet was good. Since last night
connect=193.68.21.19
listen=0
I added those nodes one at a time to the config.
listen 1. It synced no problem.
At least an hour running getting block data.
Closed the wallet.
added the Singapore:  54.255.133.30
And I got that assertion error.
upon restart.Like last month.
I went back to:
connect=193.68.21.19
listen=0
sync, closed and restarted.
fully synced everything is good.
I have no idea.I had 15 connections.
Did I pick up a bad node after listen=1
or addnodes?
I suspect connect on those nodes is good.
With listen=0
addnodes and listen=1 might not be a good thing right now.JMHO

if I add connect = 54.191.208.14, and then after synchronization addnode = 54.191.208.14, then the difficulty is not correct
with 193.68.21.19 difficulty correct

Of course it fell due to the synchronization problem.
It will go up, once the problem is resolved.

Try to connect to utahjohn.ddns.net (currently 65.130.100.203) for US-West node ... I don't have any way to test connectivity but it is port forwarded on my router to my main wallet server ...

New permanent nodes:

US West:   54.191.208.14
US East:    54.86.164.216
Singapore:  54.255.133.30

Added to the instructions in the OP.

That's the version I have, plus the latest blockchain zip - but I still can't get it to sync fully

due to of synchronization problems the price fell?

v. 2.0.3 - Yes: https://github.com/DMDcoin/Diamond

Guys, is the latest wallet updated in GitHub?

So far all is good on my miners now but I am still getting connections from 2.0.2.1 nodes

The second lot of coins I sent had no confirmations and a question mark.

And now my wallet seems frozen as it opens fine and has many connections but does nothing.

everyone use wallet 2.0.3 its mandatory now!
http://bit.diamonds/download.html
and a good start for sync is the blockchain
http://diamond.danbo.bg/downloads/dmdchain20140731-fast.zip


regarding conf
u delete peers.dat
and u sync with this:

listen=0
noirc=1
connect=193.68.21.19
bantime=600

once synced u stop wallet make a copy of the diamond appdata folder (in case things go wrong in future u have a nice fallback point)

then u change in ur conf

listen=1
noirc=1
addnode=193.68.21.19
bantime=600

and restart wallet

the full diamond.conf i use after full synced:

replace rpcallowip=192.168.1.* with 127.0.0.1 or first 3 numbers of ur  local lan if u as example allow solo minting of another rig towards this wallet

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

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

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

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

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
}

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
}
]

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.