|
paladin281978
|
 |
November 10, 2014, 04:21:40 AM
Last edit: November 10, 2014, 05:46:18 AM by paladin281978 |
|
something happens to the network? the connection reset to 1-4 the wallet constantly shows that 49 more blocks have to be loaded but they aren't loaded UPD: 58 blocks  UPD:  Sometimes appear 1-2 connections UPD: after rebooting the blocks are gone over 100 DMD How can this be? wallet in the past, and this month has been synchronized correctly 100% Maybe some sort of a node has been disconnected from the network?Was - Net Hashrate 20,321.50 MH/s Now - Net Hashrate 6,483.44 MH/s Now dmdpool.digsys.bg - Pool Hashrate 4,490.98 MH/s In my opinion it was an attack |
|
|
|
|
|
|
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
|
|
|
Mister1k
|
|
November 10, 2014, 05:04:34 AM
Last edit: November 10, 2014, 05:50:13 AM by Mister1k |
|
Us miningfield is forked. Diff 2
Is there an attack in progress?
160 blocks pending. Oh oh
Smells like july 30 attack.
If i solo mine wallet and miner are synced correct diff.
If i pool mine the diff goes to 2 @ us miningfield.
If i pool mine at Danbis the wallet and diff are correct.
I suspect the Eu.mingfield is forked as well.
I cant confirm but 4 orphans out of 11 doesnt look good.
I only have two active connections,it is usually 4.
|
|
|
|
|
optiplex
Newbie
 Offline
Activity: 17
Merit: 0
|
|
November 10, 2014, 06:07:22 AM |
|
I agree there is a problem. 8 mined and 2 mint blocks pending and no confirms
|
|
|
|
|
|
LTCMAXMYR
|
|
November 10, 2014, 06:25:54 AM |
|
seems we need more node,
my wallet sometimes only has 1 connection,or no connection,miner stopped,
so the network drop 3G hashpower of my rigs
|
Never buy any ICO altcoin.
Never buy any ASIC altcoin.
|
|
|
optiplex
Newbie
Offline
Activity: 17
Merit: 0
|
|
November 10, 2014, 06:41:11 AM |
|
I am also stopptin DMD mining there is a definite problem, diff too low after a few days watching ... forked
|
|
|
|
|
shveicar
Legendary
Offline
Activity: 1414
Merit: 1013
DMD info: https://diamond-info.github.io/
|
|
November 10, 2014, 06:59:29 AM |
|
Need to remove all the old block. All but not wallet.dat and take advantage of a previous backup. Also add the file with the contents diamond.conf listen=1
noirc=0
addnode=193.68.21.19
addnode=54.191.208.14
addnode=54.255.133.30
addnode=54.86.164.216
bantime=600 and then restart the wallet. This procedure has helped me. |
|
|
|
optiplex
Newbie
Offline
Activity: 17
Merit: 0
|
|
November 10, 2014, 07:20:17 AM |
|
yup there was a fork, i restart wallet and those orphans not show now.
Safe to mine again?
|
|
|
|
|
|
|
optiplex
Newbie
Offline
Activity: 17
Merit: 0
|
|
November 10, 2014, 07:59:29 AM |
|
thx for confirm prob miningfield i am mining again
|
|
|
|
|
optiplex
Newbie
Offline
Activity: 17
Merit: 0
|
|
November 10, 2014, 08:10:43 AM |
|
what cause fork |
|
|
|
|
cryptonit
Legendary
Offline
Activity: 3038
Merit: 1053
bit.diamonds | uNiq.diamonds
|
|
November 10, 2014, 08:31:44 AM |
|
can someone confirm his wallet did reorg back into the correct chain without any action needed
this should be the normal behavior
in case u where some time on wrong chain
we still analyzing what happend
normal the selfhealing abilities of wallet
should be able overcome a fork situation and reorg u back into mainchain
without interaction required
(dont make the word fork scare u every mined orphan create a fork
but it normal only lasts one block that wallet reorg back to main blockchain)
|
|
|
|
pallas
Legendary
Offline
Activity: 2716
Merit: 1094
Black Belt Developer
|
|
November 10, 2014, 09:34:18 AM |
|
I'm on the good chain, no action needed.
|
|
|
|
|
|
pokeytex
Legendary
Offline
Activity: 1504
Merit: 1002
|
|
November 10, 2014, 11:41:38 AM
Last edit: November 10, 2014, 12:01:24 PM by pokeytex |
|
How do I fix my wallet. It is showing difficulty 1.7? Also Danbi's pool shows only 640067 blocks found but my wallet shows 640081 blocks? update - nevermind I followed the old instructions and updated my data now wallet seems to match Danbi's pool data. |
|
|
|
|
danbi
|
|
November 10, 2014, 01:12:38 PM |
|
pokeytex, thanks for using my pool as reference  By the way, the pool and the block explorer look at different wallets, so in theory my pool could get forked too. I was offline for few days, having the luxury to be seriously ill and sort of missed this fork. I am glad you guys are back in the main chain, but could we collect some information as to what happened? running the (forked) wallet with debug=1 printjunk=1 (at least) should record some useful information in the debug.log file. We need to find out what caused it -- I was investigating the sudden drop in difficulty, but about the only explanation I could find was large portion of heavy miners dropped off the network (they forked, apparently). If you will remember, few months ago we had more such occurrences. The ultimate cure for this is some discipline in maintaining peer connections, as there are apparently people who like to experiment with other's resources -- no surprise, Diamond has become popular again. There were lots of suggestions earlier in this thread how is better to setup your wallet's connections. In general, if you are block generating node (PoW, PoS) you should refrain from 'fully' participating in the network. In such cases, you should not listen for external connections to you (listen=0) and you should only connect to known good nodes that you are sure run valid software. It is also best to use connect= to these nodes, as to not connect to more nodes than you intend to. We publish a list of nodes that are well dispersed geographically, so should be safe from network outages. If you run larger mining operation, you could set up your own 'master' node and have the actual miner wallets connect to it only/too etc. The reason for all this 'trouble' is that if you have lots of hash power, you are an good target for an attacker, who would trick you to fork out by providing you with 'convincing' block. In a way, they use your own hashing power to fork you away... We continue to investigate possible such cases and will implement more protection in the wallet itself. But it is important to know, that an valid (i.e. not modified) wallet would not relay such blocks. If you are not block generator, you can connect any way you wish, as long as you make sure you are connected to at least one of the 'good' nodes. You will eventually receive the 'cure' from the good node and heal automatically. This should require few hours at most. Hope all this makes sense. I need to get better to be more concise, sorry |
BTC: 15cJkRupKAkGr6sTxj1Uzb6uHbvuRyK1GL
DMD: dJZEqNcjiUiMMd8DKBFS9oMWtArAD2GCHr
|
|
|
lecaillou
Newbie
Offline
Activity: 13
Merit: 0
|
|
November 10, 2014, 01:21:27 PM |
|
can someone confirm his wallet did reorg back into the correct chain without any action needed
this should be the normal behavior
in case u where some time on wrong chain
we still analyzing what happend
normal the selfhealing abilities of wallet
should be able overcome a fork situation and reorg u back into mainchain
without interaction required
(dont make the word fork scare u every mined orphan create a fork
but it normal only lasts one block that wallet reorg back to main blockchain)
Me |
|
|
|
|
|
LTCMAXMYR
|
|
November 10, 2014, 01:58:42 PM |
|
21:55:26

{
"blocks" : 640199,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 201.75285006,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 13853267672,
"pooledtx" : 0,
"stakepower" : 39939,
"testnet" : false
}
am i on the correct chain?
only 2 connections
21:55:55

getpeerinfo
21:55:55

[
{
"addr" : "193.68.21.19",
"services" : "00000001",
"lastsend" : 1415627641,
"lastrecv" : 1415627646,
"conntime" : 1415595829,
"version" : 60006,
"subver" : "/Diamond:2.0.4/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 639675,
"banscore" : 0
},
{
"addr" : "54.255.133.30",
"services" : "00000000",
"lastsend" : 1415627731,
"lastrecv" : 0,
"conntime" : 1415627730,
"version" : 0,
"subver" : "",
"inbound" : false,
"releasetime" : 0,
"startingheight" : -1,
"banscore" : 0
}
]
|
Never buy any ICO altcoin.
Never buy any ASIC altcoin.
|
|
|
cryptonit
Legendary
Offline
Activity: 3038
Merit: 1053
bit.diamonds | uNiq.diamonds
|
|
November 10, 2014, 02:19:36 PM |
|
am i on the correct chain?
only 2 connections
thx for feedback from everyone situation now network recovered cryptsy multipool/cloudmining and the major mining pools (danbies and miningfield) are all on main chain if u wana see if u are on mainchain http://dmdpool.digsys.bg/bc/block_crawler.phpshow the highest block in good chain (refresh with F5 it dont autoupdate screen) analysis will follow but i dont belive in a accident..... looks like a intended attack if u didnt before make sure now u add the line bantime=600 into conf without that line even if our wallet code allow forked wallets to reunite again with mainchain they cant because u block them for 24 hours........ if u dont allow someone talk with u u cant tell him that he is wrong...... |
|
|
|
cryptonit
Legendary
Offline
Activity: 3038
Merit: 1053
bit.diamonds | uNiq.diamonds
|
|
November 10, 2014, 02:35:26 PM |
|
Has the Android wallet been created yet?
no in that area there is a bounty to claim What would the bounty be ? that we will find out when we talk with someone able to provide a android wallet with POS abilities we dont seek a copycode solution with diamond UI but the guys who deliver android wallet must be available for longterm support and upgrades of wallet too all our partners have a longterm relationship with us we dont believe in "fire and forget" jobs sustainable cooperation is the way to success |
|
|
|
stillontop
Member
Offline
Activity: 134
Merit: 12
|
|
November 10, 2014, 02:37:51 PM |
|
Hello miningfield, thank you for polishing your pools around the world! My 290X is already crunshing numbers in EU, just like before I am already considering a donation, if the pool remains stable for some time, I will do it for sure. Keep up the good work guys! My card spits out around 24.x Mh/s, I hope that qualifies for using the 3388 port, I don't want to belong to the lamers on 3387  |
DMD-Address: dQxRzzz1Ae8J46V7KGhvSrbngTodtp5fp7
|
|
|
|
