|
xinbinbin
|
 |
March 11, 2015, 12:49:16 AM
Last edit: March 11, 2015, 03:45:58 AM by xinbinbin |
|
What does AMD280X parameter
? How fast?
|
|
|
|
|
|
|
|
"Bitcoin: the cutting edge of begging technology." -- Giraffe.BTC
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
|
|
|
WORE
|
|
March 12, 2015, 12:34:57 AM |
|
What does AMD280X parameter
? How fast?
154k unless you use the --cl-opt-disable in the batch or "cl-opt-disable" : true, in the conf, in that case there is a huge performance gain however you must watch your heat dissipation as it tends to get hot real quick and your VRM's should not be run at or over 120C. |
|
|
|
|
|
xinbinbin
|
|
March 13, 2015, 07:50:16 PM |
|
What does AMD280X parameter
? How fast?
154k unless you use the --cl-opt-disable in the batch or "cl-opt-disable" : true, in the conf, in that case there is a huge performance gain however you must watch your heat dissipation as it tends to get hot real quick and your VRM's should not be run at or over 120C. THX |
|
|
|
|
|
wr104 (OP)
|
|
March 14, 2015, 04:42:02 PM |
|
Guys,
Now that the network is at block 49,0xx I'm detecting lots of connections from older obsolete Wallets version 0.4.x
If you haven't upgraded to version 0.5.0 yet, please do it NOW.
|
|
|
|
|
Videlicet
Legendary
 Offline
Activity: 868
Merit: 1058
Creator of Nexus http://nexus.io
|
|
March 14, 2015, 09:44:27 PM |
|
Bump protocol version, lock out nodes on older protocol if after given time. Then you don't need to worry about the main network forking if they don't update  Thank You,Viz. |
[ Nexus] Created by Viz. [ Videlicet] : "videre licet - it may be seen; evidently; clearly" |
|
|
berbip
Member
Offline
Activity: 143
Merit: 10
|
|
March 15, 2015, 12:01:50 AM |
|
What exactly changes with the updated algorithm ?
|
|
|
|
|
kiwifruit8
Member
Offline
Activity: 61
Merit: 10
|
|
March 15, 2015, 06:14:38 AM |
|
Guys,
Now that the network is at block 49,0xx I'm detecting lots of connections from older obsolete Wallets version 0.4.x
If you haven't upgraded to version 0.5.0 yet, please do it NOW.
That explains why the net hashrate dropped to 4M yesterday. Good job.  |
|
|
|
|
wr104 (OP)
|
|
March 15, 2015, 03:39:27 PM |
|
What exactly changes with the updated algorithm ?
The second and final hash is now calculated using the output of the first hash in reverse order (64Kb per hash). This change doesn't impact the performance on GPUs as the first hash has always been stored in RAM anyway. But, ASIC implementations without RAM to store the first hash, are now forced to do a lot more computations to calculate the second hash. See discussion here: https://bitcointalk.org/index.php?topic=881427.msg10133393#msg10133393 |
|
|
|
|
|
wr104 (OP)
|
|
March 15, 2015, 09:18:31 PM |
|
Bump protocol version, lock out nodes on older protocol if after given time. Then you don't need to worry about the main network forking if they don't update Thank You,Viz.At block 49,000 the Wallet v0.5.0 stopped accepting new connections from older obsolete Wallets version 0.4.x. The problem is with those peers with older Wallet versions that are already connected to you. By design the Wallet cannot disconnect them. I considered adding this disconnect feature to the new Wallet to help with the transition but, I then realized it could have allowed DoS attacks on the network. At block 50,000 the Wallet v0.5.0 will begin sending miners block headers with the version field set to 2. Older obsolete Wallets won't be able to accept these new mined blocks because, the hash in block version 2 isn't compatible with the old block version 1. I'm still detecting few people running the old Wallet 0.4.x. The chance of them causing a fork is small but, I really don't want to take any chances. If you are reading this and you haven't updated the wallet to version 0.5.0 yet, please do it now. On the other hand, if you did update the Wallet to 0.5.0 before block 49,000 was mined yesterday, please restart your Wallet one more time. This is to ensure peers with older Wallet 0.4.x will get further isolated before block 50,000 is mined within the next 24 hours. |
|
|
|
|
dilution007
Member
Offline
Activity: 62
Merit: 10
|
|
March 16, 2015, 11:38:53 AM |
|
Bump protocol version, lock out nodes on older protocol if after given time. Then you don't need to worry about the main network forking if they don't update Thank You,Viz.At block 49,000 the Wallet v0.5.0 stopped accepting new connections from older obsolete Wallets version 0.4.x. The problem is with those peers with older Wallet versions that are already connected to you. By design the Wallet cannot disconnect them. I considered adding this disconnect feature to the new Wallet to help with the transition but, I then realized it could have allowed DoS attacks on the network. At block 50,000 the Wallet v0.5.0 will begin sending miners block headers with the version field set to 2. Older obsolete Wallets won't be able to accept these new mined blocks because, the hash in block version 2 isn't compatible with the old block version 1. I'm still detecting few people running the old Wallet 0.4.x. The chance of them causing a fork is small but, I really don't want to take any chances. If you are reading this and you haven't updated the wallet to version 0.5.0 yet, please do it now. On the other hand, if you did update the Wallet to 0.5.0 before block 49,000 was mined yesterday, please restart your Wallet one more time. This is to ensure peers with older Wallet 0.4.x will get further isolated before block 50,000 is mined within the next 24 hours. Restarted twice |
|
|
|
berbip
Member
Offline
Activity: 143
Merit: 10
|
|
March 16, 2015, 02:33:51 PM |
|
checked with getpeerinfo and only 0.5.0 connected  |
|
|
|
|
berbip
Member
Offline
Activity: 143
Merit: 10
|
|
March 16, 2015, 11:16:28 PM |
|
rejected share above target @ block 49999
|
|
|
|
|
horizontalcareer
Member
Offline
Activity: 93
Merit: 10
|
|
March 16, 2015, 11:26:28 PM |
|
The net hashrate is lower than 4MH/s ,very dangerous!
|
|
|
|
|
wr104 (OP)
|
|
March 16, 2015, 11:57:38 PM |
|
The net hashrate is lower than 4MH/s ,very dangerous!
As long as the Diff remains above 32, we are okay. Besides, this means you and me will be able to mine more coins before the big announcement. |
|
|
|
|
|
E9800
|
|
March 17, 2015, 12:16:03 AM |
|
I have mined in the past with no issue. I have updated the wallet and miner. Just tried to mine on nonce-pool and get all rejects. Any ideas?
|
|
|
|
|
|
wr104 (OP)
|
|
March 17, 2015, 12:16:27 AM |
|
It's been an hour since we crossed the 50,000 block boundary, there has been 12 blocks mined with the new algorithm and I see no problems from my end.
I'm celebrating the success of the network transition with an iced cold Guinness. Cheers!
|
|
|
|
|
|
wr104 (OP)
|
|
March 17, 2015, 12:18:25 AM |
|
I have mined in the past with no issue. I have updated the wallet and miner. Just tried to mine on nonce-pool and get all rejects. Any ideas?
Anybody else having problems with the pool? |
|
|
|
|
|
nonce-pool
|
|
March 17, 2015, 01:53:42 AM |
|
I have mined in the past with no issue. I have updated the wallet and miner. Just tried to mine on nonce-pool and get all rejects. Any ideas?
Anybody else having problems with the pool? Pool is fixed now, to algo v2, somehow we missed a name change. |
|
|
|
|
|
E9800
|
|
March 17, 2015, 01:54:46 AM |
|
I have mined in the past with no issue. I have updated the wallet and miner. Just tried to mine on nonce-pool and get all rejects. Any ideas?
Anybody else having problems with the pool? Pool is fixed now, to algo v2, somehow we missed a name change. Thanks. |
|
|
|
|
|
E9800
|
|
March 17, 2015, 02:05:33 AM |
|
I have mined in the past with no issue. I have updated the wallet and miner. Just tried to mine on nonce-pool and get all rejects. Any ideas?
Anybody else having problems with the pool? Pool is fixed now, to algo v2, somehow we missed a name change. Just tried again and now cannot connect. |
|
|
|
|
|
