 Show Posts
|
|
Pages: [1]
|
|
1
|
Bitcoin / Pools / Re: Binance pool dropping payouts too fast.
|
on: November 12, 2021, 02:43:45 PM
|
You know that difficulty has gone up 23% since the beginning of September right?
I checked on Blockchain.com and it went up a 20%, just like the payout drop. Then I guess the calculator on f2pool is inaccurate and BTC miners are not profitable. None is. If the dificulty increases 20% every 2 months all BTC miner existing now will be useless in less than a year unless BTC price catches up, meaning at least 20% every 2 months. Is not a risk, it is sure that the whole insdustry will go bankrupt next year. How is it possible? 23% 17.615t + 23% = 21.66t which is what it is now. And its going to go up another 4%-6% in a few days time. The industry won't go bankrupt. Just people buying overly expensive equipment and using it on overly expensive electric tariffs. BTW for a long time now ROI on most equipment is calculated by the manufacturers to be around a year at least. They raise their prices to keep that ROI figure. Most of the industry is mining on equipment that cost a lot less than it does now, but then bitcoin was worth a lot less then, they took a gamble on that 12 month ROI and it paid off. The hard truth is that around a year ago a 100TH/s S19-Pro cost under $2500.00 and bitcoing was only worth $10-13K but diff was 19.2th ROI was probably around a year. There are people on here who have been mining bitcoin for almost a decade, there have been good and bad times, but people keep on going. Even when you are just breaking even, you keep going on the hope that bitcoin will be worth 10X what its worth today/last year/etc I bet you a year ago no-one really believed that bitcoin would be worth 6x what it was then. But it is. However if the difficulty increase is linear all miners whether are old new or acquired for free will be useless unless they run on free energy, which doesn't exist unless is stolen. And with a steady increase of 10% a month is going to be soon. So the only hope for the industry is a sharp decline in hashrate/price. |
|
|
|
|
2
|
Bitcoin / Pools / Re: Binance pool dropping payouts too fast.
|
on: November 12, 2021, 01:58:01 PM
|
You know that difficulty has gone up 23% since the beginning of September right?
I checked on Blockchain.com and it went up a 20%, just like the payout drop. Then I guess the calculator on f2pool is inaccurate and BTC miners are not profitable. None is. If the dificulty increases 20% every 2 months all BTC miner existing now will be useless in less than a year unless BTC price catches up, meaning at least 20% every 2 months. Is not a risk, it is sure that the whole insdustry will go bankrupt next year. How is it possible? |
|
|
|
|
3
|
Bitcoin / Pools / Binance pool dropping payouts too fast.
|
on: November 12, 2021, 12:49:48 PM
|
|
Dear All
I have been mining for 2 months now and I choosed the miners and the hosting based on what I could find and what was profitable using the f2pool calculator.
What I did I took into account the difficulty increase and I made a thorough search on those hosting services which could make the miners I found ROIable.
However after 2 months on the binance pool I experienced a drop in payouts way faster than expected, something which could potentially make all unROIable.
Does anyone have experience on how payouts work and if there is a pool like f2pool or via btc which doesn't have this dramatic drop?
I went from 0.0000070929 BTC/TH in september to 0.0000057452 BTC/TH now which is a good -20% although the BTC went up a roughly 37% so it is not immediately noticeable.
However I interpolated the function which expresses all payouts daily and the forecast is terrible, I have to say I quickly did it with Excell so probably it interpolates to a linear which could be not the real approximation.
The function presents sudden drops and it doesn't recover with falling prices, although it is kind of inverted of BTC price but not quite.
Can anyone with more experience tell me if it is normal or maybe not all pools work this way?
If the function is linear we will all be in trouble soon, especially those who purchased s19 pro for 10g each.
Probably the future is in altcoins.
|
|
|
|
|
4
|
Bitcoin / Mining support / Re: Avalon 1246 stopped working after 15 days
|
on: September 20, 2021, 09:57:52 AM
|
|
It worked, thank you.
There is another thing I don't understand:
BOOTBY[0x11.00000000]
the docs are giving a value from 0 to 11 but from the logs is something completely different.
Har restarting the miner makes it work again but is very inconsistent, it keeps blocking.
The temperature on the miner is around 50 degrees and chips are reaching 79, the hosting claims it to be normal, is it true?
can that be the reason of this poor performance?
|
|
|
|
|
5
|
Bitcoin / Mining support / Re: Avalon 1246 stopped working after 15 days
|
on: September 19, 2021, 08:23:17 PM
|
this is the hosting: https://www.coinminingsolutions.com/I had an argument with these people I asked if they could lower the temperature and the answer was that thye have many other customers that don't complain and a big waiting queue of new miners. So if I have a problem with how they manage temperature I can take my miners back. Unfortunately there are no other options at the moment, every one seems to be fully booked or they only handle a minimum of 10/20/50 miners. My contact on alibaba said that it has warranty, thechincally the miners were sold as new. |
|
|
|
|
6
|
Bitcoin / Mining support / Avalon 1246 stopped working after 15 days
|
on: September 19, 2021, 07:24:48 PM
|
|
Dear All
I am new to mining, I bought 4 miners from alibaba, all canaan avalon miners.
The first miner is an avalon 1246 83T which worked fine for 15 days and then it stopped hashing, while the second is an 1166 which is still running fine.
They are next to each other in a mining container where miners temperatures (Temp in the log) can rise up to 50 degrees.
The hosting company said that is all fine and they are not going to do anything about it, however my 1246 now stopped hashing but keeps burning kwatts.
I checked the logs and I was wondering if someone with more experience could give some advice:
{'STATUS':[{'STATUS':'S','When':0,'Code':11,'Msg':'Summary','Description':'cgminer 4.11.1'}],'SUMMARY':[{'Elapsed':47,'MHS av':0.00,'MHS 30s':0.00,'MHS 1m':0.00,'MHS 5m':0.00,'MHS 15m':0.00,'Found Blocks':0,'Getworks':7,'Accepted':0,'Rejected':0,'Hardware Errors':0,'Utility':0.00,'Discarded':581429,'Stale':0,'Get Failures':0,'Local Work':4,'Remote Failures':0,'Network Blocks':2,'Total MH':0.0000,'Work Utility':0.00,'Difficulty Accepted':0.00000000,'Difficulty Rejected':0.00000000,'Difficulty Stale':0.00000000,'Best Share':0,'Device Hardware%':0.0000,'Device Rejected%':0.0000,'Pool Rejected%':0.0000,'Pool Stale%':0.0000,'Last getwork':0}
{'STATUS':[{'STATUS':'S','When':0,'Code':70,'Msg':'CGMiner stats','Description':'cgminer 4.11.1'}],'STATS':[{'STATS':0,'ID':'AVA100','Elapsed':47,'Calls':0,'Wait':0.000000,'Max':0.000000,'Min':99999999.000000,'MM ID0':'Ver[1246-83-21042001_4ec6bb0_61407fa] DNA[02010000d66f9d2d] MEMFREE[1221976.0] NETFAIL[0 0 0 0 0 0 0 0] SYSTEMSTATU[Work: In Work, Hash Board: 0 ] Elapsed[57] BOOTBY[0x0A.0000001E] LW[0] MH[0 0 0] HW[0] DH[0.000%] Temp[41] TMax[41] TAvg[41] Fan1[6927] Fan2[6899] Fan3[6619] Fan4[6671] FanR[100%] Vo[2] PS[64 1208 3 0 0 1204] PLL0[0 0 0 0] PLL1[0 0 0 0] PLL2[0 0 0 0] GHSspd[0.00] DHspd[0.000%] GHSmm[0.00] GHSavg[0.00] WU[0.00] Freq[0.00] Led[0] MGHS[0.00 0.00 0.00] MTmax[-273 -273 -273] MTavg[0 0 0] TA[0] Core[A3201] PING[0] POWS[0] HASHS[0 0 0] POOLS[0] SoftOFF[0] ECHU[1 1 1] ECMM[1] SF0[496 516 536 556] SF1[496 516 536 556] SF2[496 516 536 556] PVT_T0[-273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273] PVT_T1[-273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273] PVT_T2[-273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273] PVT_V0[0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0] PVT_V1[0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0] PVT_V2[0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0] MW[0 0 0] MW0[0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0] MW1[0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0] MW2[0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0] ASICCRC0[0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0] ASICCRC1[0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0] ASICCRC2[0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0] CRC[0 0 0] POW_I2C[OK] FACOPTS0[] FACOPTS1[] ATAOPTS0[--avalon10-freq 396:416:436:456 --avalon10-voltage-level 28 ] ATAOPTS1[--avalon10-freq 496:516:536:556 --avalon10-voltage-level 26 ] ADJ[1] COP[0 0 0] MPO[3200] MVL[87] ATABD0[496 516 536 556] ATABD1[496 516 536 556] ATABD2[496 516 536 556] WORKMODE[1]','MM Count':1,'Smart Speed':1,'Voltage Level Offset':0,'Nonce Mask':25}
what I understood to be weird is that the first PS value is 64 which seems to be a "Output over current" issue and the voltage to the hashboards is zero so they are actually idle.
Another strange thing is that the POOLS status is 0 which is bad according to canaan's docs.
All the rest seems to be fine.
I ran both miners on the same worker on Binance and I thought that to be the problem so I made a new worker and set the miner to run on it, however I only rebooted it from the UI and not phisically as I can't do it remotely.
Does anyone have some advice?
|
|
|
|
|
