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. |
|
|
|
True, the recent batches are of better quality; also the ones that ship from Malaysia are worse according to what most people reported, however, the overall quality of all batches is combined is terrible, I bought those gears throughout the time of their release, as early as the second batch of the S17 (most of them for my clients), and nobody is really happy with any of them except for the s17 pro version which seems to be an expectation, not all great but a lot better than the rest. On the other hand, we have some Whatsminers from the same bitmain 17 series era that my clients reported 0 failure rate on, some are over 2 years old, imagine for 2 years, sounds like S9 all over again. With that being said, if you have a low failure rate, you should be thankful really as this is the unusual of how they are, you guys have decent luck I envy you.  Even if you do have the tools and skills to repair them, many times there are just too many issues to make it worth the effort. Many of these miners have flaky connections everywhere.. so you fix one issue and it runs for a few days until another issue springs up. Not worth the repair when it becomes a full time job to keep a single miner going...
Couldn't agree more, especially when you see Avalon and Whatsminer's owners be like "What does repair mean" , I know everyone has a different view on the subject, given what I think is a large enough sample size I find it very risky to buy any of the 17 series especially when other options are around, so far people are reporting good results with their S19s and T19s, some minor issues with their PSUs but nothing all that serious, my plan is to migrate to Whatsminer, selling my Bitmain gears for premium during this bull cycle and rebuying cheap M20s and M30s when things cool off little sounds like a great plan for the following years. I wish I could keep all the S9s I have because nothing comes close to their stability, but these gears are getting too old, I just realized some of them are as old as 4 years. |
|
|
|
They basically told me that these were the worse units that bitmain produced and has had a ton of issues.
I have been saying this for months or perhaps years on this forum, I kept mentioning how bad the 17 series mining gears are on every occasion I saw possible, I did that to the extreme that someone accused me of "fud", I can't blame them, it did sound like I own a Bitmain competitor company. Phill is probably the only one I know who didn't have a high failure rate, the vast majority of people I know had well over 30% failure rate, some are above 50% in less than a year, this is so unfortunate given that most of us bought those gears when BTC price was at or below 10k. It's a lesson learned, I hope more people become aware of that, if you don't have the tools and skills needed to fix these gears DO NOT buy them. |
|
|
|
Is there a flash upgrade for the S9's to take them to +3 th/s?
This should be in the mining support board instead. Short answer: NO Long answer: This is probably a glitch in btcTool, the multi-option firmware has an option to underclock the miner by 3 terahash but a maximum of 2 terahash for the overclock, you should NOT attempt a firmware upgrade, the latest version has no tuning options and you probably can't revert to the 2019 firmware which has the drop-down options for tuning, I also believe +2th is already good enough to sustain your miners anyway, don't push them hard. |
|
|
|
If I had to count the cost of importing from a country outside the European Union I think we would easily have to add 30%.
Then you should try to source them locally, make a WTB in the market place/hardware section https://bitcointalk.org/index.php?board=75.0. Make sure you either have a F2F meeting with the seller or ask for escrow, phill would escrow that I believe. If I wanted to start small, would it be a good idea to buy a revised or even a new used Bitmain S9?
With your low power rate, you can make a decent profit with an S9 and most importantly get the hang of how mining actually works, all of that while risking well below 1k instead of 14k. |
|
|
|
Imagine someone would turn off 6EH just to mess with someone.  I wanted to take screenshots of 250, 500, 750, and 1000 blocks but I missed 250 and I got the 285. Latest Block: 671612 (8 minutes ago)
Current Pace: 101.6779% (285 / 280.30 expected, 4.7 ahead)
Previous Difficulty: 21434395961348.92
Current Difficulty: 21724134900047.27
Next Difficulty: between 21827669607849 and 22123513877023
Next Difficulty Change: between +0.4766% and +1.8384%
Previous Retarget: last Friday at 11:56 PM (+1.3517%)
Next Retarget (earliest): March 5, 2021 at 6:23 PM (in 11d 19h 44m 20s)
Next Retarget (latest): March 5, 2021 at 10:28 PM (in 11d 23h 49m 37s)
Projected Epoch Length: between 13d 18h 27m 18s and 13d 22h 32m 35s
I also got the 5 blocks status earlier on. Latest Block: 671332 (3 minutes ago)
Current Pace: 83.0581% (5 / 6.02 expected, 1.02 behind)
Previous Difficulty: 21434395961348.92
Current Difficulty: 21724134900047.27
Next Difficulty: between 19472305559050 and 21711695987187
Next Difficulty Change: between -10.3656% and -0.0573%
Previous Retarget: Yesterday at 11:56 PM (+1.3517%)
Next Retarget (earliest): March 6, 2021 at 12:16 AM (in 13d 23h 20m 10s)
Next Retarget (latest): March 8, 2021 at 8:28 PM (in 16d 19h 31m 57s)
Projected Epoch Length: between 14d 0h 20m 22s and 16d 20h 32m 9s
|
|
|
|
For those who know, are the S19 Pro that can be found at reputable sellers on Alibaba the same as ordering on the Bitmain site?
Avoid Alibaba like the plague, you can find other trusted sellers on this forum, but do you really want to pay close to 14k for a miner? what about tax, how much do you have to pay to import a miner like that? Do you think this information sounds realistic?
They don't, this is based on static difficulty and price which we all know is impossible, it all depends on your luck, let's assume difficulty is going to be same if bitcoin price goes to 150k the S19 pro at your power cost will make you about 3k a month, so for 14k investment, you would need a little under 6 months to ROI, if however, bitcoin price drops to 27k, your miner will make you $500 a month, and that will be over two years to ROI. To put this in a simple and yet somehow accurate way, when you buy bitcoin mining gear you are essentially betting on the price to go up if you believe that will be case until you hit ROI, then go ahead, if not - don't. The point here is not to get your hopes so high, know that the difficulty is only going to go up and the price can't go up forever, if you understand the risk and the dark side of mining then mining is a great business, if you don't, you will end up losing money just the like the majority of people who invest in something they don't quite understand. |
|
|
|
[...]
Keep in mind only the repair shops located in China are actually certified by them, the rest are not, and they state that clearly on their website, however, I'd imagine they do some basic due diligence before listing anyone, still, deal with cautious. If they don't reply you let me know, I have quite a solid relationship with Kevin, and I am trying to get him to treat bitcointalk members with a bit of a priority and offer them some discount, I believe sometime in the future I may get him to sign up to the forum or put one of his staff here for the forum members to interact with Zeusbtc directly on the forum. |
|
|
|
I have a quick question, I live in France and the delivery of the first Bitmain Antminer S19 Pro 110 TH / s is expected around the month of August. If I understand correctly from the posts I have seen in the forum there are in some countries people who have already received their Bitmain Antminer S19 Pro 110 TH / s, is this possible? Are there priority countries? There are no priority countries except for China, and the Chinese buy from the Chinese website, not the English one. I also don't understand on what bases do you think this is the 1st batch of Antminer S19 pro, it isn't, it has been out there for months (close to a year), so yes, some people who ordered early have already received their S19 pro, the rest are waiting. On a side but related note, the August batch is for those who ordered last month or the month before IIRC. Right now, everything is out of stock, and would IMO continue to be the case for months to come, I believe the spot price for S19 pro now is $13-14k, I have not checked it today but the S19 non-pro is 10.5k. |
|
|
|
I almost forgot I made this bitcoin bottom analysis more than 2 years ago, It has been a wild journey ever since, I believe in a few months I shall be posting another analysis on how bitcoin has likely topped, interesting times ahead, I take this chance to praise everyone (myself included ) for staying strong when the majority of people were in panic mode, it's easy now to look back and say, oh, it was obvious and simple! since 2 years have passed and the price moved from 3k to over 50k, but it was certainly not easy then. Those who were strong enough to enter when all the media and 90% of everyone around them was telling them BTC was going to zero, congratulations you deserve to own bitcoin when everyone wants to buy it for 50k. |
|
|
|
If you look at a the chances of being ahead or behind at each block of an epoch, you are more likely to be equal to or ahead than behind through the whole epoch, but getting closer and closer to 50/50 as you get to the end.
Aha, exactly what I mean, of course by 700 blocks we get close to 1/3 of the epoch lifespan which would get as closer to the mean, unlike when we view the results at say block no.100 or so. Well, the data is available, so maybe if I get ambitious I'll look at the blocks from the last couple epochs to see what we might be able infer. All you need are the timestamps of the blocks to re-create the % ahead/behind.
The timestamp is inaccurate, you will see blocks mined in the past or way ahead into the future, the most accurate would be the actual time a block was submitted, not sure if any of the explorers out there keep track of that, but if you want just the timestamps LoyceV has it here in a single file. |
|
|
|
Given who they are my guess is host their own pool at their datacenters for their customers.
Makes sense, I didn't even bother reading their username, anyway I just wanted to confirm they actually do know what setting up your own pool means, I know some newbies would want to do that to evade mining pool fees. Yes the post was deleted. I don't know why. I am testing different open source softwares. Thanks for your answer I will check db record and will get back to you.
Probably the admin thought it was spam or something, I hope they won't delete this one too, anyway, check and let me know, if you didn't find it I'll take another look into the backend code on Github. |
|
|
|
|
Was your other post deleted? I answered your question on that topic, not sure what happened!!
You need to use a username and not a wallet address, that user name needs to be in your db, I looked into the table name and I forgot it, but there will be user/worker database table, the worker name needs to match with one of the rows in there, only then it will show alive.
As far as connecting that to your wallet, you have to know that you are now running your own pool, so you need to find a block to get any rewards, search the code and you will find "genesis transaction" that's where your wallet address goes to.
May I ask what are you trying to achieve by running your own copy of btc.com?
|
|
|
|
Um, no. If the hashrate was 100% flat, over long enough time scale the average diff would be flat.
By long enough I suppose you mean infinity? I believe we are on the same boat but with a little bit of confusion, let's "for fun" work with the time between blocks which follows the exponential distribution as it's a lot easier to understand than the Poisson distribution which is the number of blocks found in x time follows. Using the cumulative distribution function we get this nice and simple result.  Notice how almost 40% of blocks come after less than 5 mins from the previous one, we will just assume the epoch just started and we are now at block 10, based on the CDF Block 0 > =<5 mins > block 1 Block 1 > =<5 mins > block 2 Block 2 > =<5 mins > block 3 BLock3 >=<5 mins > block 4 Block 5 >=<10 mins > block 6 Block 6 >=<10 mins > block 7 Block 7 >=<15 mins >block 8 Block 8 >=<15mins > block 9 Block 9 >=<20 mins >block 10 The order does not matter, and this isn't really how it works by the way , but without a doubt finding the first 10 blocks will in theory (based on static hashrate) take less than 100 mins, let's just assume it takes 95 mins, this will automatically set the cryptdiff to a base of +5% which would indicate that we have 5% more hashrate when we are not even close to that. The deviation from the mean will eventually drop closer to zero as we move further, but when the sample is too small the slightest deviation makes a large impact, Back to my earlier post about the chances of being 10% ahead after 700 blocks when the hashrate was actually flat, that is the chance of getting 700 blocks or more when on average we would expect 636 (not 770 vs 700 like I said before), that would be 0.649% (1 in 154 times). So you might expect that to happen once every 6 or so years... doing that 3 times consecutively is 1 in 3.6 million.... so once in 140,000 years... lol.
It was indeed not flat or else it can't go to 10%, chances are slim to nothing as you have explained since we are now only 4 blocks away and now the number shows 1.3% we can safely assume that this is going to be accurate, and we can for the sake of argument say this has been it since the beginning of this epoch. In 20 mins or so we will hit a new diff epoch, let's try to take as many screenshots/copy-paste the data so we can discuss it further when we actually get to 700 blocks. |
|
|
|
|
Show Posts
