Well done lucky miner! Now come on little bitaxe.. wen block. "workers": 4, "shares": 284999958384, "bestshare": 3219734.943005498, "bestever": 268266973098,
|
|
|
Good luck to you Willi and to the whole group! I wish you guys find a block (or two)!
Would be great if you have at least one before the halving..
thanks, but unfortunately over and no block found Unlucky guys that was some best share too!
|
|
|
Well my small private 10ph double runs is over. Back to just the old bitaxe boards. Wishing the 1000ph run luck smash it guys! "hashrate1m": "1.32T", "hashrate5m": "1.72T", "hashrate1hr": "70.9T", "hashrate1d": "1.36P", "hashrate7d": "1.01P", "lastshare": 1713391241, "workers": 3, "shares": 223749457214, "bestshare": 268266973098.5093, "bestever": 268266973098, "authorised": 1710841905,
|
|
|
{ "hashrate1m": "120T", "hashrate5m": "121T", "hashrate1hr": "117T", "hashrate1d": "1.06P", "hashrate7d": "546T", "lastshare": 1713090148, "workers": 6, "shares": 103791851192, "bestshare": 268266973098.5093, "bestever": 268266973098,
Also on a small hunt 50 hours left. On the ramp down from 10ph. Good luck hunters may the hash gods be with us all! Bitaxe's still chopping away. FREQ 485 (Default) CoreV 1200 (Default) "workername": ".bitaxe1", "hashrate1m": "388G", "hashrate5m": "442G", "hashrate1hr": "440G", "hashrate1d": "476G", "hashrate7d": "472G", "lastshare": 1713090143, "shares": 243859969, "bestshare": 32687206.42865465, "bestever": 256103050 FREQ 500 CoreV 1250 "workername": ".bitaxe2", "hashrate1m": "608G", "hashrate5m": "549G", "hashrate1hr": "470G", "hashrate1d": "456G", "hashrate7d": "441G", "lastshare": 1713090136, "shares": 231166842, "bestshare": 87946178.57762636, "bestever": 87946178 FREQ 535 CoreV 1300 "workername": ".bitaxe3", "hashrate1m": "295G", "hashrate5m": "338G", "hashrate1hr": "392G", "hashrate1d": "369G", "hashrate7d": "376G", "lastshare": 1713090143, "shares": 214391130, "bestshare": 160822501.7945735, "bestever": 160822501
|
|
|
Date: 2/1/2022 Address: bc1q2pr99p75skdzyqdg0hnpd7hf56tge6h9x4wyet Hashrate: 1.14P Solved after: 5,496,218,477,727 shares Network difficulty: 26.6432 trillion Shares solved / Network difficulty (%): 20.63% Link: https://bitcointalk.org/index.php?topic=5237323.msg59129443#msg59129443
Date: 2/3/2022 Address: 1ADwc721c1KuqhHy2vuL8b96G6DEDAhSUX Hashrate: 13T Solved after: 10,38,303,277,333 shares Network difficulty: 26.6432 trillion Shares solved / Network difficulty (%): 38.97%
Date: 4/27/2022 Address: bc1q0pd359kfxh93esgntxa6esxtjy3s9rhuqdn02m Hashrate: 61.3T Solved after: 47,330,132,229,632 shares Network difficulty: 28.7703 trillion Shares solved / Network difficulty (%): 164.51%
Date: 9/6/2022 Address: 15Hgp1dLmdNfZCYVysikTsJXoEL3kMpPz3 Hashrate: 269T Solved after: 69,526,501,463,599 shares Network difficulty: 30.9771 trillion Shares solved / Network difficulty (%): 224.44%
Date: 1/20/2023 Address: 1CEmkQkgiCMx6DHSDkHi53mL8oEthCZSw Hashrate: 10.5T Solved after: 69,815,559,814,517 shares Network difficulty: 37.5905 trillion Shares solved / Network difficulty (%): 185.73%
Date 2/23/2023 Address: 14MooZUhqu3gXPDGC4aUh3AQFKDs3SZ1MW Hashrate: 733T Solved after: 18,302,096,290,838 shares Network difficulty: 39.1564 trillion Shares solved / Network difficulty (%): 46.74%
Date: 3/10/2023 Address: 39nDQ9BexEBXpRdkHY1z95CaMDEwh6muPW Hashrate: 6.7P Solved after: 9,160,686,932,609 shares Network difficulty: 43.1271 trillion Shares solved / Network difficulty (%): 21.24%
Date: 3/28/2023 Address:bc1q97xwgr64c9hykuu99ur3qva9k37f776fx76yl8 Hashrate: 978P Solved after: 41,109,244,715,384 shares Network difficulty: 46.8434 trillion Shares solved / Network difficulty (%): 87.76%
Date: 3/28/2023 Address: bc1q97xwgr64c9hykuu99ur3qva9k37f776fx76yl8 Hashrate: 665P Solved after: 2,521,484,426,673 shares Network difficulty: 46.8434 trillion Shares solved / Network difficulty (%): 5.38%
Date: 3/31/2023 Address: bc1q8xs6ehy98se88k6nk0axlahnkwyytua0wa8umu (BlockParty) Hashrate: 17.7P Solved after: 1,973,798,317,311 shares Network difficulty: 46.8434 trillion Shares solved / Network difficulty (%): 4.21%
Date: 5/23/2023 Address: c1q0ftg0p7ljsj3m32e22ned92536gr5tafctr7mp Hashrate: 722T Solved after: 55,827,554,693,516 shares Network difficulty: 49.5497 trillion Shares solved / Network difficulty (%): 112.67%
Date: 6/9/2023 Address: 151XTfHBfaDqoNWGGeYobNX2YzFFWuB5YD Hashrate: 17T Solved after: 15,306,888,081,924 shares Network difficulty: 51.2343 trillion Shares solved / Network difficulty (%): 29.88%
Date: 6/21/2023 Address: 3EHpvbs5ar7DWiux1AQ5JMB2zTBE6wzX7d Hashrate: 42T Solved after: 17,167,552,901,929 shares Network difficulty: 52.3504 trillion Shares solved / Network difficulty (%): 32.79%
Date: 10/29/2023 Address: 3KCykmdpBpNKTtZJAvp3u2N2EQjGzbUF7c Hashrate: 11.2P Solved after: 85,396,736,583,039 shares Network difficulty: 61.0307 trillion Shares solved / Network difficulty (%): 139.92%
Date: 11/26/2023 Address: 15VYcdhWXB2tpKmFHKT9DcGLWDQJQ2XMJW Hashrate: 1.98P Solved after: 28,288,508,859,013 shares Network difficulty: 67.9129 trillion Shares solved / Network difficulty (%): 41.65%
Date: 2/4/2024 Address: 32hZXGyQ1SJV1wYiSA5dE52duoLvkYRiv1 Hashrate: 45.3P Solved after: 121,610,801,791,457 shares Network difficulty: 75.5022 trillion Shares solved / Network difficulty (%): 161.07%
Date: 4/5/2024 (Block: 837814) Address: 33uUaKyRDWFoKAFPJNp3gjXSd9FRa4Z2GW Hashrate: 7.42P Solved after: 66,741,581,025,506 shares Network difficulty: 83.127 trillion Shares solved / Network difficulty (%): 80.29%Overall insightsMedian days between blocks mined: 34 days Median hashrate: 1.14P Average 'Shares solved / Network Difficulty' when block mined: 82.23% Median 'Shares solved / Network Difficulty' when block mined: 46.74% Nice data there interesting to see how many weres actully solved by smaller miners is incredible. Just goes to show only takes that 1 hash. My run didn't even hit a new bestshare with 10ph { "hashrate1m": "808T", "hashrate5m": "1.37P", "hashrate1hr": "1.41P", "hashrate1d": "2.03P", "hashrate7d": "533T", "lastshare": 1713002604, "workers": 18, "shares": 90516238870, "bestshare": 77309508876.16481, "bestever": 77309508876, "authorised": 1710841905, "worker": [
|
|
|
Seems kind of pointless puzzle if when you do find a solution someone else can just rob the coins off you by spam attacking and kangaroo attack.
So really the whole point of the "weak" keys puzzle is flawed as many people will just be waiting for the TX to hit the network then just go after that.
In essence unless your conneced to some mining pool or have connections there is zero chance your going to get a pool to include this actually you may find they try steal it from you.
And yes there are people running this stuff on crazy crazy machines so there is a good chance once broadcast before it gets picked up someone else then it's fee race and yea before in the past this happened someone ended up paying a massive fee just to get what little coins they could.
So don't participate unless your well linked up and know exactly how to do this stuff or you will get mugged for your find on broadcast.
|
|
|
Good luck lads was rooting for y'all Won't lie I'm also trying for one before halving solo fingers crossed. "bestshare": 77309508876.16481, Miles off.
|
|
|
Wow cannot believe that 1.2EH didn't hit.
|
|
|
Is it not supposed to be a . at the end of the address "workername": "bc1qprzt4ks2ne8s7pfazgwxu59kgxj9j6j6ekful7_megarun", "workername": "bc1qprzt4ks2ne8s7pfazgwxu59kgxj9j6j6ekful7.megarun", Good luck guys! I'm also rolling with some power no where near your chad hashrate! "hashrate1m": "293T", "hashrate5m": "432T", "hashrate1hr": "676T", "hashrate1d": "181T", "hashrate7d": "30.2T", "lastshare": 1712696471, "workers": 9, "shares": 4728834846, "bestshare": 77309508876.16481,
|
|
|
Well done miner a stong effort right before halving too! There was me thinking boss moves with a 256m best share on one of the Bitaxe's Thought the Satoshi gods were with me when I saw 256! "hashrate1m": "1.45T", "hashrate5m": "1.4T", "hashrate1hr": "1.35T", "hashrate1d": "1.35T", "hashrate7d": "1.23T", "lastshare": 1712336095, "workers": 3, "shares": 458212215, "bestshare": 4111717.675488911, "bestever": 256103050, Onward.
|
|
|
Love the Bitaxe so far. Been playing about with interface designs and possible updates for additional information in the dashboard. 1. Possible to add a realtime bestshare value I noticed it shows the overall bestshare this is good to know but if I restart the miner it would be good to see a rolling best share from restart below the overall best. 2. Further peak and min voltage values on the dash would be nice. 3. Debug mode (show more information in the log window when debug mode is active (possible?)
|
|
|
With the release of the Satoshi emails over the last few weeks I believe Litecoin has it's merits not to mention Bitpay transactions soaring merchants seeing more payments in LTC than BTC for the first time in history.
It's great to see the Litecoin development pushing forward too. For a long time there was not much going on but now we are really seeing interest be taken in the Litecoin network.
One thing we really missed out on was the doge hype doge that was a big mistake we needed to be party to that hype train as the security behind the doge!
I always wondered what would occur if we see a market reversal where people switch there doge for LTC.
I really do think now we should be trying to convince markets to list LTC as a base pair like BTC has pairs against most alts.
This would drive trading and liquidity into the LTC pair.
At this point for trading alt markets the BTC pairs make no sense anymore. The logical choice would be LTC base pairs.
Raccoon Out.
|
|
|
You could try encode the input. input_string = "<provided if you can help>".encode('utf-8')
Since the ord function returns the unicode point for the given charater though if your outside the range for ASCII then it might not fit in a single byte. What you can do is try encode the string like UTF-8 before processing it. Keep in mind if you modify the encode decode function to accpet the unicode points you may need to transform the scheme.
|
|
|
Is there a possibility that market makers (MMs) are manipulating the Bitcoin SV (BSV)/Bitcoin (BTC) pairs on the OKX exchange? It appears unusual that the BSV/BTC pair on OKX is experiencing movements that result in selling pressure. Could it be that MMs are extracting BTC from these transactions and then 'burning' it? My hypothesis is that this activity originates from within the exchange. The pattern seems to be: the market is artificially pumped, which excites MMs. These MMs then add BTC to their trading pairs. Subsequently, the manipulators withdraw the BTC from these market makers and deliberately decrease the price. Intriguingly, this BTC doesn't seem to re-enter the market. Instead, it might be destroyed or used for other purposes, such as spamming the network with low-value transactions, referred to as 'shitpegs.' I think there is more to this than meets the eye.
|
|
|
Miners must be loving it right now!
Yeah, the miners are getting huge rewards in the form of those high fees miners dont see transactions miners dont choose transactions miners are just given whatever cut of reward the POOL decides. dont point fingers at miners. realise who is making transaction decisions look at the devs that refuse to fix the exploits they create asic owners were not in poverty when the bitcoin price was $17k so dont even pretend miners deserve fee's now.. also the spot market will take care of miners when the reward halves so fees are not essential realise its all about dev politics thats causing the issues we see. it has absolutely nothing to do with asic economics whomever is telling you to look at miners is the guy that doesnt want you to scrutinise the core devs indecision and sponsored deals Relax.. Was a simple comment on the block fees atm. wow.
|
|
|
Yay more fees just what everyone wants around the holiday season!
With the block count being ahead small transactions users going to feel the pain the most.
Miners must be loving it right now!
|
|
|
You can use https://www.breadcrumbs.app/ to track your transaction. Enter the address you send the coins to into the site and you can follow where the coins have gone. Without sharing some info on your transaction cannot advise further.
|
|
|
|