Website only has this one. Can I get an older version? 6 hours on autotune set at blance and still going. Guy I got it from says it takes 3 days to settle....
3 days to autotune the miner is just way too long and I don't think I would believe that, assuming the miner tunes every chip individually (which needs the most time) it shouldn't be move than 24hrs to do that, in fact even half that is way too long. This might be caused by a bad chip that forces the autotune to keep dropping its frequency down to the specified minimum number which could be for example 100 while the tuner starts at 700, but unless the firmware is really stupid that shouldn't take forever, could you post the logs here? |
|
|
|
... a little sketchy that Zuesbtc is trying to sell it when you can read it yourself with the tools needed to program the chip.
Not sure if I agree with this logic, that is a "know-how" that they utilize just like most other businesses. If members of this forum were not generous enough to share such knowledge for free, most people would not know about using pickit to accomplish the same result, plus, they make the process simpler/faster, you don't need a pc or any extra software to copy-paste and confirm the hex. Of course, if you know how to do that it makes no sense to pay $300+ for that tool, but the average joe would probably not touch a pickit at its basic level, but I don't think it's "sketchy" by any means, and that is just my opinion. I haven't actually programmed a chip with the firmware I read out, so maybe there is some issue with doing that that I'm not seeing. Or maybe some boards do have the read protection bit set and I got lucky.
Nop they don't, you can read and write using MPLAB without an issue. |
|
|
|
|
Sounds like a control board issue to me, of course going with the assumption that the new fan is good, try to Sdcard the miner using the recovery firmware, if that does not solve it you might need a new control board.
|
|
|
|
check_asic_number_with_power_on: Chain[1]: find 0 asic, times 0
check_asic_number_with_power_on: Chain[2]: find 0 asic, times 0
check_asic_number_with_power_on: Chain[3]: find 0 asic, times 0
Usually, I'd suspect the PSU when all 3 hash boards show 0 asics, but I saw you mention ... stopped working one by one.
In that case, I would say with at least a probability of =>90% that all hash boards have actually diead, Bitmain makes these gears terrible enough in the production phase, I would not be surprised if the repaired once come out even worse, that repair guy is in a bad mood and he rushes to fix the 100 hash boards he has in the basket next to him before 5 pm because he doesn't want to stay late, he quickly solders those chips and heatsinks using the terrible med-temp adhesive, assemble the miner and off he goes, and we all know there is probably no quality-control unit there, the "at best" just plug-in the fixture tool and count the number of chips and that's all about it. If you have tried a different control board, a different PSU there is nothing else you can do, you will need to send the boards for repair, but since your first experience with Bitmain wasn't so great, you might want to find someone else to fix them. |
|
|
|
I have real-time production/consumption data available via API that I would use as input for controlling the miner's performance. The preferred way would be to directly interact with the miner's API, or even calling a script via SSH that will apply the most appropriate (pre-defined) performance profile. But for this script approach I again don't know if this profile/config change would be applied on the fly or rather only when the bmmminer process gets restarted.
The program has to restart that's for sure, there is probably no way to change those parameters without restarting, so if you plan on changing those constantly your miner will be offline most of the time, but if say this happens once an hour or so - the total downtime won't be huge, and then mining to a PPS pool would be the best approach. So the biggest question still is, whether such freq/voltage control API commands are available and which makes/models/firmwares (original or custom) do support that. For me this is the most crucial part to clarify before setting this up.
Yes, most of the old stock firmware versions have SSH enabled by default, some of the recent ones can be unclocked, and the latest 1-2 versions are locked and I am not aware of an easy way to unlock them, but you really can work just fine with one of the old firmware versions. You can find the list here > https://service.bitmain.com/support/download?product=Antminer%20S9. Basically, anything prior to any of the 2019 releases is going to have SSH enabled, if so happen that you find it locked you can use this free tool to unlock it, but by all means, you should avoid the 2020 versions. You could also use one of thierry4wd free mods, he basically takes the original firmware and modifies the signature/lock aspect, so you have the same firmware with no locks on it, he also knows a lot about the firmware, so moving forward I believe he will be the best person to ask for support. |
|
|
|
|
65m3/min is (2275 CFM) which should be enough for these 4 miners, but you know you can't exhaust more air than you intake, so even installing 2 or fans might not solve the problem, 400m tube is pretty small especially if the spacing between these miners isn't enough. So until you figure out a way to get rid of that heat, I would suggest you underclock all 4 gears, if it was S9s I would not even bother with 90c, but these 17 series are pretty sensitive to heat and they could die faster than you think if you keep running them this hot.
|
|
|
|
I can't answer in regards to the latest bitmain firmware, but my guess would be no, I highly doubt that you will have access to the voltage and frequency by any means with the latest sets of bitmain firmware. But to answer this part but rather adaptively controlling the hashrate (frequency/voltage) via API (is that possible?) so that I can throttle or max up as appropriate during the day. The answer would be yes if you use Vnish and AwesomeMiner you can basically set different voltage and/or frequency throughout the day/night, and you can even automate that, for example, 10v and 500mhz between 1 am and 5 am and all that kind of schedule, and since you have full access to those parameters with custom firmware, you could probably use something like Arduino or a R-PI to acquire data from your PV system and adjust the miner's setting accordingly. Old versions of stock firmware allow you to play with the voltage and frequency ( I am sure about the latter but not the former) so I guess you could use the Bmminer API miner on that, BraiinOS, not the + version is also free and open-source so you can eventually find a way to achieve what you want, but if you want the easy way, you will need to pay 3% of your hashrate to AwoesomeMiner and get the license included version of the firmware, you end up with monitoring software that allows you to achieve what you need at little efforts, but of course, you will learn nothing about the API and you pay a fee. |
|
|
|
Even if you're running your S9s in normal mode at 90W/TH, and you're paying 10c/kWh for power, the price would need to fall below $37,000 at the current diff to be unprofitable. So I don't think anyone is turning off gear because it is not profitable anymore.
People are buying S9s even in Europe, which means they are running them at way higher power rates than just 10 cents. Kwh cost Minimum Price 5c 25k 6c 25k 7c 30k 8c 35k 9c 35k 10c 40k 11c 45k 12c 50k 13c 50k 14c 55k 15c 55k 16c 60k 17c 65k That is quick math, ignoring everything between those numbers, so for example, 16 cents could still make a tiny profit between 60k and 55k, but the profit would be too small anyway, and I used 1250w to 14th which is about 89w/th, so when the price goes below 50k everything above 13 cents becomes unprofitable, I can only imagine that there are a good amount of gears that run at above 10 cents khw, of course we can't be certain that they will shut down right after the price crosses their profit-line, and they could just mine at a lose hopping that coin prices will go higher soon. But I could see people taking gear offline to sell it.
You are right, selling is another factor, but judging by the listing I see on the telegram, there does not seem to be any major re-allocation of gears, a few months back we see WTS/WTB orders of 20,000S9s for example every once in a while, things like 3,000 T71 were every day's usual, the past couple weeks have been really quiet, today's listing is all about fans and some used PSUs.  One of my Malaysian friends said he can't source any reasonable quantity of S9 in China, they say some Russian whales took everything a few weeks ago, to me, it seems like the selling was over, and the majority of people who now have a mining gear that's generating these instance profits will not likely going to sell, I mean at least the whales that make the difference not the average joe with his 5 S9s, although I do believe that pretty soon they will start to unload. But again, we don't know what we don't know, we are just throwing some speculations around and all that matters is the fact that difficulty is staying flat. |
|
|
|
|
I spoke to one of Vnish devs (Marc) and he also believes what you think is true, in other words, the voltage settings are stored on the e-prom, he also said that Vnish ignores the e-prom completely in that regards, which means (in theory) you can mix hash boards with different e-prom stored values, but since that isn't the case, I am still trying to investigate the matter.
|
|
|
|
الحمد لله انك استطعت الحصول على اموالك, خبر مفرح. ولكنهم طلبو مني اخذ سكرين شوت...الذي لا يمكنني أخذه الا في حال تمكني من الدخول للحساب و الذي يكون أيضا عن طريق البريد الالكتروني و تطبيق غوغل..  هدا يعني ان اي شخص يمتلك الوصول الى الايميل و 2FA يمكنه سحب اموالك, مما يعني ان طلب كلمة مرور التداول لاقيمة له من الناحية "الامنية" وهدا يدل على 1 من 2 1- الشخص الذي صمم بروتوكول الامان للمنصة شخص "متخلف عقليا". 2- المنصة تعول على ان البعض او الكثير من المستخدمين لن يقومو بطلب اموالهم بعد قراءة كلمة KYC وسوف يتركون اموالهم لكي يتسنى للمنصة اخدها بعد مرور عدة سنوات. |
|
|
|
Well, of course, this wouldn't be easy, it says: While that’s preheating, start removing the heatsink and any other plastic parts on your video card. You essentially want the card naked, with nothing but the PCB and rear bracket While that is obvious, I seem to have ignored that when I thought about baking those hash boards, many components on the hashboard will melt at 198c, so this isn't a simple operation, removing the plastic 18pin data ribbon cable alone is going to take me a long time (I have shaky hands when I deal with things like that). With that being said, if someone trusted here tries that and it works, I could hire someone to remove all those components that need removing and try the trick out, but without any reviews from other miners, this would be a waste of time, efforts, probably an oven, and a wife. |
|
|
|
2021-02-23 17:05:52 thread.c:968:asic_status_monitor_thread: ERROR: chain 2 get hashrate_reg_counter 0, require 65, failed times 1
2021-02-23 17:05:53 temperature.c:838:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 0
2021-02-23 17:05:53 temperature.c:838:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2021-02-23 17:05:53 temperature.c:838:get_temp_info: read temp sensor failed: chain = 2, sensor = 1, chip = 10, reg = 0
2021-02-23 17:05:54 thread.c:996:asic_status_monitor_thread: chain 2 can't get enough hashrate reg val for 0 times.
2021-02-23 17:05:54 temperature.c:838:get_temp_info: read temp sensor failed: chain = 2, sensor = 1, chip = 10, reg = 1
2021-02-23 17:05:54 thread.c:968:asic_status_monitor_thread: ERROR: chain 2 get hashrate_reg_counter 0, require 65, failed times 1
2021-02-23 17:05:54 temperature.c:838:get_temp_info: read temp sensor failed: chain = 2, sensor = 2, chip = 54, reg = 0
2021-02-23 17:05:54 temperature.c:838:get_temp_info: read temp sensor failed: chain = 2, sensor = 2, chip = 54, reg = 1
2021-02-23 17:05:55 temperature.c:838:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 50, reg = 0
2021-02-23 17:05:55 temperature.c:838:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 50, reg = 1
I have a similar issue which I posted about just a few minutes ago, mind you the board that gives me this error was a dead board which I froze in the freezer, worked fine for a while, and then started to throw these temp sensors errors, so in other words, chances are this is a dead hashboard. We know that a loose heatsink causes temp sensors not to read, but that usually comes along with some missing asic chips, but the overall temp sensor issues do not mean the sensor is bad, it means the hash board is dying or otherwise, dead. You could get lucky with custom firmware, I want to try that on the miner I was testing but for some stupid reason when I removed BraiinOS it flashed the latest Bitmain firmware instead of the MP test so now I need to go get that miner and Sdcard my way into it, but I would without a doubt test Vnish when I have the time for that. Should I just install a new firmware and change the max temp for the chips? Because it can't rly be that high when the other boards are fine?
The other boards are not fine, the nearest sensors to the exhaust fan are reporting 86c, I wouldn't be surprised if the middle board is at or above 90 or hot enough to trigger the firmware to shut it down, so this could be more than just a temp sensor glitch, it could be that chain is actually running too hot, so I would fix that part first, and once you are certain the board isn't getting hot and it's just a bad sensor, maybe you could increase the max temp by a little, but be careful, if the board does indeed run way too hot it could melt and set the whole place on fire. |
|
|
|
Here are some plots for the last 3 epochs I made using the data from LoyceV's file...
Nice analysis, I wish the source of the data was more accurate, I believe Kano and/or CK would have such data since they both have mining nodes running, I suppose they keep a record of when they received every block regardless of the timestamp on the block itself. If someone was shutting down 6EH of S17s at 5c power, they'd only be giving up $69,700 per hour.... lol.
What's 70k between fellow miners? 
Ok price dropped a nice 23%, many things have changed from the last 2 epochs, hard to assume why didn't phill theory apply this time, anyway, I am happy to see us cool down and with some potential of a drop in difficulty which is massive. Latest Block: 671863 (11 minutes ago)
Current Pace: 94.0643% (536 / 569.82 expected, 33.82 behind)
Previous Difficulty: 21434395961348.92
Current Difficulty: 21724134900047.27
Next Difficulty: between 20450514442221 and 21117763283211
Next Difficulty Change: between -5.8627% and -2.7912%
Previous Retarget: last Friday at 11:56 PM (+1.3517%)
Next Retarget (earliest): March 6, 2021 at 9:42 AM (in 10d 10h 48m 18s)
Next Retarget (latest): March 6, 2021 at 9:08 PM (in 10d 22h 13m 54s)
Projected Epoch Length: between 14d 9h 46m 31s and 14d 21h 12m 8s
Going with the assumption that this is accurate, 5% of the total hashrate from the last epoch is 8EH, since this can't be the 19 series since those are still profitable even with high rates of power, let's assume those are old S9s and T17s, so maybe in the range of 70w/t per miner on average, so anywhere between 25-30th per miner in respect to w/th, this means at least 266,666 (quarter of a million) are not profitable below 50k. The above is far from accurate obviously, but it's an indication that the majority of the hashrate does not come from the new generation miners, or else, 20% in price shouldn't shake anybody, but to shake out those many gears, well. maybe this explains why I failed to source any S9i for one of my clients the past couple of days in China. |
|
|
|
Has anyone considered putting their bad hash board to oven as some people do for GPUs? In hopes of re-soldering it.
I have plenty of dead hash boards to test, give me the oven receipie and I'll cook the hell out of them. The science behind it as explained to me years ago.
Things shrink when cooled. The boards shrink at one rate, the wire traces in the board shrink at another. The chips shrink at one rate the solder connections at another.
We are talking about fractions of a % of a mm. BUT, something that was just on the edge at room temperature will at times start to work.
That explains it very well.
Update: The 2 hash boards are working just fine still, I also noticed one of the boards that came back to life and then died now shows full Asics (65 asics) but it has a temp sensor error 2021-02-23 19:04:14 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[0]: find 65 asic, times 0
2021-02-23 19:04:25 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[2]: find 65 asic, times 0
2021-02-23 19:04:30 driver-hash-chip.c:266:set_uart_relay: set uart relay to 0x330003
2021-02-23 19:04:30 driver-btm-api.c:435:set_order_clock: chain[0]: set order clock, stragegy 3
2021-02-23 19:04:30 driver-btm-api.c:435:set_order_clock: chain[2]: set order clock, stragegy 3
2021-02-23 19:04:31 driver-hash-chip.c:502:set_clock_delay_control: core_data = 0x34
2021-02-23 19:04:31 driver-btm-api.c:1892:check_clock_counter: freq 50 clock_counter_limit 6
2021-02-23 19:04:31 voltage[0] = 1980
2021-02-23 19:04:31 voltage[2] = 1980
2021-02-23 19:04:31 power_api.c:226:set_working_voltage_raw: working_voltage_raw = 1980
2021-02-23 19:04:32 temperature.c:340:calibrate_temp_sensor_one_chain: chain 0 temp sensor NCT218
2021-02-23 19:04:33 temperature.c:340:calibrate_temp_sensor_one_chain: chain 2 temp sensor NCT218
2021-02-23 19:04:33 uart.c:72:set_baud: set fpga_baud to 12000000
2021-02-23 19:04:34 driver-btm-api.c:293:check_bringup_temp: Bring up temperature is 21
2021-02-23 19:04:34 thread.c:1378:create_check_miner_status_thread: create thread
2021-02-23 19:04:34 thread.c:1368:create_show_miner_status_thread: create thread
2021-02-23 19:04:34 thread.c:1348:create_temperature_monitor_thread: create thread
2021-02-23 19:04:34 frequency.c:514:check_bringup_temp_dec_freq: dec freq = 0 when bringup temp = 21 dec_freq_index=0
2021-02-23 19:04:34 freq_tuning.c:183:freq_tuning_get_max_freq: Max freq of tuning is 650
2021-02-23 19:04:34 driver-btm-api.c:1765:send_null_work: [DEBUG] Send null work.
2021-02-23 19:04:34 thread.c:1338:create_asic_status_monitor_thread: create thread
2021-02-23 19:04:34 frequency.c:1110:inc_freq_with_fixed_vco: chain = 255, freq = 500, is_higher_voltage = true
2021-02-23 19:05:58 power_api.c:352:set_to_voltage_by_steps: Set to voltage raw 2090, step by step.
2021-02-23 19:05:59 power_api.c:85:check_voltage_multi: retry time: 0
2021-02-23 19:06:01 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 20.817602
2021-02-23 19:06:02 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.720663
2021-02-23 19:06:02 power_api.c:53:_get_avg_voltage: average_voltage = 20.769132
2021-02-23 19:06:02 power_api.c:71:check_voltage: target_vol = 20.90, actural_vol = 20.77, check voltage passed.
2021-02-23 19:09:27 frequency.c:1152:inc_freq_with_fixed_step: chain = 2, freq_start = 500, freq_end = 520, freq_step = 5, is_higher_voltage = true
2021-02-23 19:09:35 frequency.c:1181:inc_asic_diff_freq_by_steps: chain = 0, start = 500, freq_step = 5
2021-02-23 19:09:41 frequency.c:1181:inc_asic_diff_freq_by_steps: chain = 2, start = 520, freq_step = 5
2021-02-23 19:09:44 driver-btm-api.c:765:set_timeout: freq = 550, percent = 90, hcn = 44236, timeout = 80
2021-02-23 19:09:44 power_api.c:310:set_to_working_voltage_by_steps: Set to voltage raw 1980, step by step.
2021-02-23 19:09:49 power_api.c:85:check_voltage_multi: retry time: 0
2021-02-23 19:09:50 power_api.c:40:_get_avg_voltage: chain = 0, voltage = 19.727040
2021-02-23 19:09:51 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 19.630102
2021-02-23 19:09:51 power_api.c:53:_get_avg_voltage: average_voltage = 19.678571
2021-02-23 19:09:51 power_api.c:71:check_voltage: target_vol = 19.80, actural_vol = 19.68, check voltage passed.
2021-02-23 19:09:51 thread.c:1373:create_check_system_status_thread: create thread
2021-02-23 19:09:52 driver-btm-api.c:2618:bitmain_soc_init: Init done!
2021-02-23 19:09:52 driver-btm-api.c:222:set_miner_status: STATUS_INIT
2021-02-23 19:09:56 driver-btm-api.c:222:set_miner_status: STATUS_OKAY
2021-02-23 19:09:57 frequency.c:205:get_ideal_hash_rate_GH: ideal_hash_rate = 45227
2021-02-23 19:09:57 frequency.c:223:get_sale_hash_rate_GH: sale_hash_rate = 43000
2021-02-23 19:10:00 driver-btm-api.c:1496:dhash_chip_send_job: Version num 4.
2021-02-23 19:10:00 driver-btm-api.c:1644:dhash_chip_send_job: stime.tv_sec 1614107400, block_ntime 1614107373
2021-02-23 19:10:04 thread.c:1273:asic_status_monitor_thread: ERROR: chain 2 get hashrate_reg_counter 63, require 65, failed times 1: xxooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo ooooo
2021-02-23 19:10:05 thread.c:1293:asic_status_monitor_thread: chain 2 can't get enough hashrate reg val for 0 times.
2021-02-23 19:10:23 thread.c:1273:asic_status_monitor_thread: ERROR: chain 2 get hashrate_reg_counter 5, require 65, failed times 1: ooooo xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx
2021-02-23 19:10:24 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 0
2021-02-23 19:10:24 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 0, chip = 14, reg = 1
2021-02-23 19:10:24 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 1, chip = 10, reg = 0
2021-02-23 19:10:24 thread.c:1293:asic_status_monitor_thread: chain 2 can't get enough hashrate reg val for 0 times.
2021-02-23 19:10:25 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 1, chip = 10, reg = 1
2021-02-23 19:10:25 thread.c:1273:asic_status_monitor_thread: ERROR: chain 2 get hashrate_reg_counter 5, require 65, failed times 1: ooooo xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx xxxxx
2021-02-23 19:10:25 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 2, chip = 54, reg = 0
2021-02-23 19:10:25 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 2, chip = 54, reg = 1
2021-02-23 19:10:26 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 50, reg = 0
2021-02-23 19:10:26 temperature.c:843:get_temp_info: read temp sensor failed: chain = 2, sensor = 3, chip = 50, reg = 1
2021-02-23 19:10:26 temperature.c:875:get_temp_info: ERROR: chain 2 can get NONE temp info or temp value abnormal, power it off
2021-02-23 19:10:26 thread.c:1293:asic_status_monitor_thread: chain 2 can't get enough hashrate reg val for 1 times.
2021-02-23 19:10:27 thread.c:1265:asic_status_monitor_thread: ERROR: chain 2 get hashrate_reg_counter 0, require 65, failed times 1
2021-02-23 19:10:28 frequency.c:205:get_ideal_hash_rate_GH: ideal_hash_rate = 22656
2021-02-23 19:10:28 frequency.c:223:get_sale_hash_rate_GH: sale_hash_rate = 22000
2021-02-23 19:40:00 thread.c:259:calc_hashrate_avg: avg rate is 23083.64 in 30 mins
2021-02-23 19:40:00 temperature.c:516:temp_statistics_show: pcb temp 49~65 chip temp 72~80
2021-02-23 20:10:01 thread.c:259:calc_hashrate_avg: avg rate is 22760.07 in 30 mins
2021-02-23 20:10:01 temperature.c:516:temp_statistics_show: pcb temp 50~65 chip temp 71~79
Maybe i froze those temp sensors more than I should, or, it could just be a loose heatsink somewhere, but nonetheless, showing full asic count after the freezer visit is a good sign. |
|
|
|
هل تقصد أننى عندما أستبدل التوكن AWC لن احصل على أيثيريوم و لكن سأحصل على WETH  هل هذه العملات أمنة ويمكن أستبدالها أيضا ؟؟ [/b][/right] لا اخي ستحصل على ايثيريوم لان الايثريوم موجودة على بلوك تشين الايثيريوم, يمكن تصور ان البتكوين مثل الذهب, او البصل! هل يمكنك وضع البصل داخل بلوك تشين الايثيريوم ؟ طبعا لا, لكن يمكن وضع عملة مربوطة بالبصل اسمها W-Onion تكون قيمتها مربوطة بالبصل ولكن عندما تريد ان تأخد البصلة لتأكلها لن يكون هدا ممكن, بل يجب عليك استبدالها بعملة موجودة على البلوك تشين الخاص بالايثيريوم مثل عملة ETH وارسالها لمنصة اخرى مثلا, واستبدالها ب USDC وشراء البصل مجددا من السوق. يعني الملخص اي عملة موجودة في الاصل على البلوكتشين الخاص بالايثيريوم اي عملة erc20 يمكن مقايضتها مباشرة, اي عملة غير موجودة مثل البتكوين يمكن مقايضة عملة مرتبطة بها فقط, اتمنى ان يكون الشرح واضح. تفضل اخي اسئل ماتريد لا تخجل من السؤال. |
|
|
|
أفهم الأن أنه يمكننى أستخدام هذه المنصة ولكن أردت أن أسأل بخصوص التكلفة من تحويل التوكن الى ايثيريوم عن طريق هذه المنصة فى ظل أرتفاع مصاريف التحويل ... هل هى عالية ؟؟؟ وماذا اذا أردت أن أحول التوكن الى بيتكوين وليس أيثيريوم فهل أستطيع عن طريق هذه المنصة و أذا كانت الأجابة نعم فكيف سيرسلون البيتكوين الى حسابى و انا قد دخلت بحساب ERC20؟؟؟؟ رسوم البيع والشراء مرتبطة ارتباط مباشر بتكلفة تحويل الايثيريوم, وهي الان مرتفعة وغير منطقية للتحويلات الصغيرة, وهدا ماجعل من عملة باينانس تعانق السحاب لانها حلت مشكلة التكاليف العالية للعقوذ الذكية, واعتقد انه مع توجه بعض المشاريع الى باينانس (عملة مركزية 100% لا اتمنى لها النجاح) وايضا الشهر المقبل مع اطلاق عملة كاردانو للعقود الذكية سوف نلاحظ انخفاض حجم التداول على الايثيريوم ولربما انخفاض في تكاليف التحويل. بخصوص البتكوين فهي على بلوك تشين مختلف تماما, ولكن يمكن ان تستلم "بتكوين افتراضية" ان صح التعبير على عنوان ايثيريوم ولكنها لن تكون بتكوين حقيقية بل Wrapped Bitcoin يعني عملة WBTC وهي تحتفط بقيمة البتكوين وسعرها ولكنها موجودة على بلوك تشين الايثيريوم. |
|
|
|
الخيار الاخر هوا الاحتفاظ دائما بعملة بديلة قليلة التكلفة خارج المنصة في محفظة موبايل, دائما احتفط ببعض LTC و Doge في محفظة CoinOmi على الموبايل, المبالغ تكون قليلة ومعدة فقط لمثل هده الاستخدامات الصغيرة ولا اكترث لصعود او نزول سعرها, في المقابل حالفني الحظ في الارتفاع الجنوني لعملة دوجي حيت ارتفع سعرها تقريبا 1500% وصدمت عندما شادهت رصيدي تحول الى رقم لاباس به (خارج سياق الموضوع الموضوع), ولكن اعتقد الفكرة وصلت. |
|
|
|
|
We all have heard this old "freeze" your electronic stuff to fix them, some say it works, some say it does not, I have always thought it was a complete B.S, until one of the members here whom I believe was "Favebook" reported some sucssess.
As some of you already know, I have a lot of dead 17 series hash boards, so I decided to give it a try.
I got myself 10 plastic bags and put 10 hash boards in those bags and buried them in the fridge for about 40 hours or so, I don't recall the exact duration but it was 2 nights and a bit less than 2 days.
I took the plastic bags out of the freezer but I didn't open them because the water condensed on them, I left them to dry overnight and the next day, I tested the 10 boards which were a combination of S17+ and T17 ( the T17s are a pain in the ass to disassemble and reassemble compared to the + and E versions).
The initial test brought 4 boards to life, reporting full asic numbers, I went ahead and flash a custom firmware to see if I get better results, sadly nothing.
After 10 hours when I checked the miners again two out of the four have died again (tears), I think one died after 30 mins or so (judging the hashrate on the pool) the other one lasted for a little under 10 hours.
The other two boards I managed to revive are still hashing after 2 days, it was one T17 hash board and one S17+, all the boards I have tested have no physical damage, I applied a good amount of pressure on all the heatsinks and nothing fell, I also noticed the 2 hash boards that came back to life for a while before resting in piece again show more than 0 asic but not all Asics for an example one of the T17 boards shows 20 Asics.
The T17 board that is still mining on does seem to have an issue with the 4th temp sensor reading, it's showing 0 on both the PCB and Chip but hashing at a modest 12.6TH.
Again, I would like to give credit to Favebook, and encourage you all to try this simple and free trick, I also think my success rate isn't realistic and far from sustainable when the sample size is larger, so don't expect to get 2 out of 10 every time, but really, given how easy and free this is, even with 1 in 20 you are a winner.
|
|
|
|
What kind of performance can I reasonably expect on S9 and S9i, assuming I set powerlimit to 1500. For some reason autotuning is giving me 16+th on one..and only 14th on the other, even though both have all chips active? I’ve heard of people getting as high as 18th+?
Some chips are just bad and can't be tuned above their average, of course, assuming you are doing everything right and your PSU is in great shape, so don't expect that all gears will perform the same, that won't happen. as far as the 18th claim goes, it's possible but most likely not without liquid cooling, I am pretty sure most gears will collapse when you start pushing past 16th, overclocking your gears to 16th is already a bit risky, attempting to go higher is a toast recipe. |
|
|
|
You sure its not $0.074?
Thank you for asking the question, I wanted to ask the same question but then I remembered he mentioned he works for some electricity supplier and he probably wouldn't make such a mistake, it would be easier to say that he has free power. Thanks for your advice, I left a message. 😉
Nice, I see you got a reply already, please be careful, given that your rank is a newbie, many scammers will be attempting to scam you. if you don't manage to find a seller in Europe - check with grace from Miner Expert https://bitcointalk.org/index.php?action=profile;u=2706610, they are based in China but they might help you source something nearby. |
|
|
|
|
Show Posts
