Search content
Sort by
Showing 20 of 325 results by faraway
Re: [ANN][FLO] Florin | 0.10 Upgrade | The original tx msg coin | Project Alexandria
Sounds great and price follows hashrate sooner or later. Look at Dash for example! I am buying the dips and promoting it to my friends. 2018 will be great for florincoin for sure! Lets promote it together on facebook, twitter and real life people! 
Indeed Florin is still a solid coin and well supported by exchanges.
Wallet - This is a pre-release test build - use at your own risk - do not use for mining or merchant applications
what does this mean? I thought the official bitcoin gold client was all we needed?
I tried checking out version 0.15 instead of master from the github source, and that took the pre-relase message away. However I'm still not syncing any blocks (ubuntu 14.04)
The last release of the branch 'master' seems to be the good one.
If you have trouble getting peers; opening the port: 8338 is helpful.
This nodes not work!
This one is OK:
addnode=78.193.221.106
Full chain
Bad news :/ How can you sync faster? Is there a way to download the blockchain until the hard fork?
You can use the -bootstrap option, and use the 'connect=' option pointing to your regular bitcoin client.
Wallet not sync? 0 nodes!
addnode=109.192.23.101
addnode=88.99.5.24
addnode=164.132.164.49
addnode=91.224.140.216
addnode=178.63.11.246
addnode=176.12.32.153
addnode=93.88.74.26
addnode=213.148.176.232
addnode=109.201.133.93
addnode=195.42.181.134
addnode=72.65.232.4
addnode=154.16.63.17
addnode=213.154.230.106
addnode=178.238.228.83
addnode=213.154.229.126
addnode=91.222.17.86
addnode=45.77.62.72
addnode=213.154.230.107
addnode=98.114.91.222
addnode=35.196.226.49
addnode=66.70.247.151
addnode=89.18.27.165
addnode=89.18.27.165
addnode=45.32.234.160
addnode=217.182.199.21
addnode=185.139.2.140
addnode=31.214.157.104
addnode=149.154.71.96
addnode=109.252.108.223
addnode=67.170.52.226
addnode=188.75.128.27
addnode=199.229.248.218
addnode=81.218.148.131
addnode=36.78.96.92
addnode=212.47.236.104
addnode=89.110.53.186
addnode=145.239.0.50
addnode=100.1.157.185
addnode=172.113.91.211
addnode=54.153.140.202
addnode=188.120.223.153
addnode=45.76.136.149
addnode=46.22.7.74
addnode=91.50.219.221
addnode=85.253.172.161
addnode=31.128.109.238
addnode=159.89.192.119
addnode=92.51.61.81
addnode=95.235.32.196
addnode=37.113.31.187
addnode=176.107.192.240
addnode=93.85.135.35
addnode=46.188.16.96
addnode=178.130.45.210
addnode=213.154.229.50
addnode=46.39.249.143
addnode=31.131.99.98
addnode=83.99.172.208
addnode=219.89.122.82
addnode=46.53.217.127
addnode=217.15.136.205
addnode=79.220.108.12
addnode=35.200.168.155
addnode=128.71.176.116
addnode=95.83.189.23
addnode=93.185.18.90
addnode=145.255.184.109
addnode=31.128.187.194
addnode=5.18.232.205
addnode=37.232.180.232
addnode=82.209.92.252
addnode=176.120.61.207
addnode=59.44.59.39
addnode=95.158.227.162
addnode=91.247.153.10
addnode=67.68.226.130
addnode=76.16.12.81
addnode=37.113.183.76
addnode=149.172.240.141
addnode=178.158.247.119
addnode=94.25.167.53
addnode=91.97.19.163
addnode=159.224.111.200
addnode=176.59.116.246
addnode=5.79.211.1
addnode=94.29.97.194
addnode=92.112.175.122
addnode=64.251.97.144
addnode=173.176.95.92
addnode=84.234.52.190
addnode=194.88.107.212
addnode=193.165.126.22
addnode=178.137.150.156
addnode=35.189.127.200
addnode=176.15.109.97
addnode=94.140.241.96
addnode=37.147.131.69
addnode=188.17.149.51
addnode=75.83.89.98
addnode=72.39.197.234
addnode=94.50.4.238
addnode=79.66.239.82
addnode=178.44.31.26
addnode=146.241.19.216
addnode=14.231.241.123
addnode=93.78.122.48
addnode=80.77.163.221
addnode=79.191.221.201
addnode=86.245.221.65
addnode=95.107.22.142
addnode=189.165.103.35
addnode=88.206.10.31
addnode=178.130.42.86
addnode=178.78.32.112
addnode=212.56.120.203
addnode=162.213.254.102
addnode=95.26.135.119
addnode=91.227.197.0
addnode=172.90.200.135
addnode=77.29.64.33
addnode=35.200.126.199
addnode=143.207.67.209
Build problems...
In file included from ./uint256.h:15:0,
from consensus/params.h:9,
from chainparams.h:10,
from bitcoind.cpp:10:
./crypto/common.h:16:10: fatal error: sodium.h: No such file or directory
In file included from ./uint256.h:15:0,
from consensus/params.h:9,
from chainparams.h:10,
from bitcoind.cpp:10:
./crypto/common.h:16:10: fatal error: sodium.h: No such file or directory
'libsodium' is required.
Indeed my client is now synchronized - And the mining started at 13h30 today. A lot of instamine/premine...
what do you mean. the real mining started at 13.30???
2017-11-12 20:09:11 UpdateTip: new best=00069578d7a76f82b2c7117c1334c7efa0ee308c7b848cf37e1e6d948dbf5140 height=491407 version=0x20000000 log2_work=87.340668 tx=265017498 date='2017-11-12 13:34:01' progress=0.999723 cache=0.0MiB(1txo) warning='2 of last 100 blocks have unexpected version'
2017-11-12 20:09:11 UpdateTip: new best=0005df4cfdcaba340b50f59eb2d434739b1447f716b4a877e99fea082b8a4842 height=491408 version=0x20000000 log2_work=87.340668 tx=265017499 date='2017-11-12 13:34:37' progress=0.999723 cache=0.0MiB(2txo) warning='2 of last 100 blocks have unexpected version'
2017-11-12 20:09:11 UpdateTip: new best=0001a74ae7bbe99dada6698246ee3a592f58aab189740e8138061a7ced61e0ab height=491409 version=0x20000000 log2_work=87.340668 tx=265017500 date='2017-11-12 13:34:40' progress=0.999723 cache=0.0MiB(3txo) warning='2 of last 100 blocks have unexpected version'
2017-11-12 20:09:11 UpdateTip: new best=00012ba27086f7a2cc682399f2897f73eb2140069705322b710070d6b57f3ce0 height=491410 version=0x20000000 log2_work=87.340668 tx=265017501 date='2017-11-12 13:34:46' progress=0.999723 cache=0.0MiB(4txo) warning='2 of last 100 blocks have unexpected version'
2017-11-12 20:09:11 UpdateTip: new best=00004ec454950417352d79bae02faa85d8cd1209bdf44364f0ad0bed77245d48 height=491411 version=0x20000000 log2_work=87.340668 tx=265017502 date='2017-11-12 13:34:49' progress=0.999723 cache=0.0MiB(5txo) warning='2 of last 100 blocks have unexpected version'
2017-11-12 20:09:11 UpdateTip: new best=0001dbb981e728fe402afc65f2dddcac0d6663ba716bea014dfaaeae345703ef height=491412 version=0x20000000 log2_work=87.340668 tx=265017503 date='2017-11-12 13:34:55' progress=0.999723 cache=0.0MiB(6txo) warning='2 of last 100 blocks have unexpected version'
2017-11-12 20:09:11 UpdateTip: new best=00015a66b584ca046578b404e080a3d4670b0591f7d8601d34996bd7d8e19b89 height=491413 version=0x20000000 log2_work=87.340668 tx=265017504 date='2017-11-12 13:35:04' progress=0.999723 cache=0.0MiB(7txo) warning='2 of last 100 blocks have unexpected version'
2017-11-12 20:09:11 UpdateTip: new best=00027e3bddf3b4deac1aba1d78a0944d76909c762d6a6612ae4d906dccfcf24d height=491414 version=0x20000000 log2_work=87.340668 tx=265017505 date='2017-11-12 13:35:38' progress=0.999724 cache=0.0MiB(8txo) warning='1 of last 100 blocks have unexpected version'
2017-11-12 20:09:11 UpdateTip: new best=00022717cb3cd4c17a9624098a36f9be5a550889a63d447bca612ba163667309 height=491415 version=0x20000000 log2_work=87.340668 tx=265017506 date='2017-11-12 13:35:43' progress=0.999724 cache=0.0MiB(9txo) warning='1 of last 100 blocks have unexpected version'
2017-11-12 20:09:11 UpdateTip: new best=0001154042cbe55d6bc35d7f1d7e3d989e2f480eb92f44e90f9c06fce83654f9 height=491416 version=0x20000000 log2_work=87.340668 tx=265017507 date='2017-11-12 13:35:45' progress=0.999724 cache=0.0MiB(10txo) warning='1 of last 100 blocks have unexpected version'
2017-11-12 20:09:12 UpdateTip: new best=00013811d40a5edceb256510341e39bc1402aa887997f6340d60e65ac3e44c06 height=491417 version=0x20000000 log2_work=87.340668 tx=265017508 date='2017-11-12 13:35:58' progress=0.999724 cache=0.0MiB(11txo) warning='1 of last 100 blocks have unexpected version'
2017-11-12 20:09:12 UpdateTip: new best=00015ca6edb3dcc1ea0edbb61e57a30887ec88a480d23ac422593f632c741045 height=491418 version=0x20000000 log2_work=87.340668 tx=265017509 date='2017-11-12 13:36:19' progress=0.999724 cache=0.0MiB(12txo) warning='1 of last 100 blocks have unexpected version'
2017-11-12 20:09:12 UpdateTip: new best=00008fb2f5d85d4bb027b2cd4561c2f2087634c2cd169ee9f1f77f3aaff18f1f height=491419 version=0x20000000 log2_work=87.340668 tx=265017510 date='2017-11-12 13:36:22' progress=0.999724 cache=0.0MiB(13txo) warning='1 of last 100 blocks have unexpected version'
2017-11-12 20:09:12 UpdateTip: new best=0000f2e794a3914c08223dace25d22cf6ad4e7a39469c17338351371dcc00c2f height=491420 version=0x20000000 log2_work=87.340668 tx=265017511 date='2017-11-12 13:36:26' progress=0.999724 cache=0.0MiB(14txo) warning='1 of last 100 blocks have unexpected version'
hashrate on supanova is 0 right now
The sight states they are syncing to the blockchain. How long is that going to take? There is a way to use a bootstrap for this coin, right?
Option -bootstrap is implemented to 'sync' on the classical bitcoin nodes.
But my 'getpeerinfo' is still empty right now...
Re: [ANN] Spondoolies-Tech - carrier grade, data center ready mining rigs
A function that is still missing with the last firmwares; is a proper 'start' of the ASICs that failed tests below a known temperature.
With the last firmwares the 3 ASICs of the same loop are disabled, and they are never turned on; We must disable the troublesome one, and wait for the temperature to rise.
We are in winter; Have you a fix for this issue?
With the last firmwares the 3 ASICs of the same loop are disabled, and they are never turned on; We must disable the troublesome one, and wait for the temperature to rise.
We are in winter; Have you a fix for this issue?
Re: [ANN] Spondoolies-Tech - carrier grade, data center ready mining rigs
It's looking more certain that what we've been seeing in our DC is a poor reaction of SP30s to temperatures below about 6°C. We haven't seen any issues with SP10s yet at these temperatures.
Some machines work fine at low temperatures. I've seen a few operate just dandy at intake temperatures as low as 2°C. However, others will show problems at intake temperatures as high as 8°C. When a machine has trouble at low temperatures, it's often specific ASICs that show the problem (often #2 and #17). It's not always the ASICs in the front that have issues, though it seems more common to be those. Once an ASIC has trouble at low temperatures, it sometimes has trouble even when warmed up. Sometimes it has to be disabled permanently; other times it can be enabled once the machine is warmer.
Indeed, but a hardware to be reliable, must handle 25°C variation without too much trouble.Here at low temperature some ASICs can't start. It will be a good idea to add a 'delay' option for the troublesome ASICs where they are turn off during the cold start and enabled later. Adding an option to change the Fan speed according to the intake temperature, will be a good too idea too. (I suspect this issue to trigger some machines crashes when minergate restart).
Have you an update about this issue? Anyway, outside a software fix, if a decoupling capacitor fix (or modification) is helpful; it will ease running the machines, and will be welcome; An idea?
Re: [ANN] Spondoolies-Tech - carrier grade, data center ready mining rigs
It's looking more certain that what we've been seeing in our DC is a poor reaction of SP30s to temperatures below about 6°C. We haven't seen any issues with SP10s yet at these temperatures.
Some machines work fine at low temperatures. I've seen a few operate just dandy at intake temperatures as low as 2°C. However, others will show problems at intake temperatures as high as 8°C. When a machine has trouble at low temperatures, it's often specific ASICs that show the problem (often #2 and #17). It's not always the ASICs in the front that have issues, though it seems more common to be those. Once an ASIC has trouble at low temperatures, it sometimes has trouble even when warmed up. Sometimes it has to be disabled permanently; other times it can be enabled once the machine is warmer.
Indeed, but a hardware to be reliable, must handle 25°C variation without too much trouble.Here at low temperature some ASICs can't start. It will be a good idea to add a 'delay' option for the troublesome ASICs where they are turn off during the cold start and enabled later. Adding an option to change the Fan speed according to the intake temperature, will be a good too idea too. (I suspect this issue to trigger some machines crashes when minergate restart).
Re: [ANN] Spondoolies-Tech - carrier grade, data center ready mining rigs
I have had 39 SP30s running 2.5.12 so far for about 12 hours 16 minutes with no apparent issues. If I see no problems with 2.5.12 by next morning, I will probably move the rest of our machines over to it. Otherwise, I will probably move everything back to 2.4.23.
I've had a plethora of "disabled (bist cant start, stuck X)" errors on the remaining 100 or so SP30s we have running 2.5.6 in the mean time. It seems every few hours, I have to restart cgminer on 5% or 10% of our machines to get them back to full hashrate. Very annoying, but so far the issue has always been resolved by restarting minergate.
I've also had several reports of machines on 2.5.6 showing half hashrate at the pool even though I see full hashrate. These issues have always been restarted by a minergate restart.
I saw some much more serious problems on 2.5.7 during the 36 hours we had machines using that version. We saw about 10 machines get "Loop serial failed x" error messages (where x is a loop number, between 0 and 9 inclusive) and fail to start until one or sometimes two ASICs on that loop were disabled. After a few hours, many of these ASICs could be enabled again, but about 25% of the ones that failed are still non-operational. Currently, I think there are 9 ASICs which we lost on 2.5.7 which have not recovered.
It's possible that the potential ASIC-damaging bug in 2.5.7 might still be present in 2.5.12. I haven't seen any indications of it yet, but I also haven't had enough machines running on it for long enough to be certain. On 2.5.7, I saw the loop serial failed ASIC damage thing with about 5% of our machines per day. At that rate, there's only about a 63% chance that I would have seen it if it were present at the same rate in 2.5.12 with 39 machines running half a day.
It is now looking like the issues we've been seeing in our datacenter with the potential ASIC-damaging bug was not related to version 2.5.7 per se, but is instead temperature-related, and we only noticed it now because the temperatures in our DC only recently started getting really close to 0°C. Version 2.5.13 does not appear to fix these issues. Zvi is looking into it further.I've had a plethora of "disabled (bist cant start, stuck X)" errors on the remaining 100 or so SP30s we have running 2.5.6 in the mean time. It seems every few hours, I have to restart cgminer on 5% or 10% of our machines to get them back to full hashrate. Very annoying, but so far the issue has always been resolved by restarting minergate.
I've also had several reports of machines on 2.5.6 showing half hashrate at the pool even though I see full hashrate. These issues have always been restarted by a minergate restart.
I saw some much more serious problems on 2.5.7 during the 36 hours we had machines using that version. We saw about 10 machines get "Loop serial failed x" error messages (where x is a loop number, between 0 and 9 inclusive) and fail to start until one or sometimes two ASICs on that loop were disabled. After a few hours, many of these ASICs could be enabled again, but about 25% of the ones that failed are still non-operational. Currently, I think there are 9 ASICs which we lost on 2.5.7 which have not recovered.
It's possible that the potential ASIC-damaging bug in 2.5.7 might still be present in 2.5.12. I haven't seen any indications of it yet, but I also haven't had enough machines running on it for long enough to be certain. On 2.5.7, I saw the loop serial failed ASIC damage thing with about 5% of our machines per day. At that rate, there's only about a 63% chance that I would have seen it if it were present at the same rate in 2.5.12 with 39 machines running half a day.
The other two bugs were definitely firmware related, so you should still avoid 2.5.6 and 2.5.7.
Findings are still tentative and provisional, and investigation is ongoing.
Also for keeping the miners in top condition.
Guy
The issue seems to be really temperature dependent; Indeed at low temperature (e.g. 5°C intake) some ASICs can't start and must be disabled. This is an hardware issue; anyway a good software fix may be to add an option to delay the activation of the problematic ASICs at the time, when the machine is at an acceptable temperature; And turn off these ASICs again when minergate restart to avoid machines crashes.
Re: [ANN] Spondoolies-Tech - carrier grade, data center ready mining rigs
To continue on the disabled ASIC issue topic (following the 2.5.7 upgrade).
I've still two ASICs in a 'stuck' state; They operated again, for some time, a few hours ago; But, after a reboot the issue is back on the same ASICs.
If we consider there is no hardware damage (I hope so). Do you know, a reliable method, to get them in a deterministic and operational state?
I've still two ASICs in a 'stuck' state; They operated again, for some time, a few hours ago; But, after a reboot the issue is back on the same ASICs.
If we consider there is no hardware damage (I hope so). Do you know, a reliable method, to get them in a deterministic and operational state?
Re: [ANN] Spondoolies-Tech - carrier grade, data center ready mining rigs
5 out of 10 SP30's seem to have failed after about 10 hours with the new firmware 2.5.6
any suggestions?
any suggestions?
Look in the Events tab. Post what you find.
Try disabling ASICs. First, disable all but one ASIC. See if it starts up. If it does, then try enabling a few more ASICs, then a few more, etc. Eventually, you may be able to isolate one or two ASICs that are causing the trouble.
If you see "Loop serial failed X" messages, then you can start by disabling loop X, then re-enabling those ASICs one by one. If you see that message, you should also let Zvi know (and preferably also me by Skype; my Skype ID is jtoomim).
You're welcome to contact me on Skype if you want more advice. Zvi's rather busy, and I'd be happy to help if I can until he can get his workload under control again.
Some ASICs can't be activated again. Is this the main sha256 chip that is affected, or a different hardware failure?
One of my ASIC came back to life. I suspect now, a chip undefined state, unaffected by the RESET signal. If this is really the case have you a trick (software, etc..) to set the chip in the proper state, and enforce the RESET sequence? May you fix this bug?
Re: [ANN] Spondoolies-Tech - carrier grade, data center ready mining rigs
5 out of 10 SP30's seem to have failed after about 10 hours with the new firmware 2.5.6
any suggestions?
any suggestions?
Look in the Events tab. Post what you find.
Try disabling ASICs. First, disable all but one ASIC. See if it starts up. If it does, then try enabling a few more ASICs, then a few more, etc. Eventually, you may be able to isolate one or two ASICs that are causing the trouble.
If you see "Loop serial failed X" messages, then you can start by disabling loop X, then re-enabling those ASICs one by one. If you see that message, you should also let Zvi know (and preferably also me by Skype; my Skype ID is jtoomim).
You're welcome to contact me on Skype if you want more advice. Zvi's rather busy, and I'd be happy to help if I can until he can get his workload under control again.
Some ASICs can't be activated again. Is this the main sha256 chip that is affected, or a different hardware failure?
Re: [ANN] Spondoolies-Tech - carrier grade, data center ready mining rigs
HELLO - October 28th 2014.
When are we expecting SP31 to ship? Was one of the first orders (or close to) of October batch 1 - Still no email notification. Please advise. Thank You.
When are we expecting SP31 to ship? Was one of the first orders (or close to) of October batch 1 - Still no email notification. Please advise. Thank You.
Same issue; I've no email notification yet.