1
00:00:00,000 --> 00:00:05,860
This time I'm back with another focus episode where we want to dive into what shares are.

2
00:00:06,300 --> 00:00:10,360
HashrateUp. Hardware sales, advisory, hosting, and side brokerage.

3
00:00:10,780 --> 00:00:14,820
Find new and use basic deals through the website and the Telegram channel below.

4
00:00:15,380 --> 00:00:17,500
Make smarter decisions with HashrateUp.

5
00:00:18,300 --> 00:00:25,480
All right, before we get started, I recently added a little free course to my website that you can sign up for.

6
00:00:25,480 --> 00:00:30,440
feel free to visit my website or the link in the description below to sign up for that

7
00:00:30,440 --> 00:00:37,300
and then you'll just get emails five emails and then another two into your inbox explaining sort

8
00:00:37,300 --> 00:00:42,660
of core concepts if you're interested in that feel free to visit the link below all right so

9
00:00:42,660 --> 00:00:49,160
what are shares to put it very simply right if all the miners in the world are hashing trillions of

10
00:00:49,160 --> 00:00:53,760
times a second who are sending them their hash rate to pools it's going to be very difficult for

11
00:00:53,760 --> 00:00:59,040
pools to verify all of the hash rate and all of the hashes that are being sent to the pool

12
00:00:59,600 --> 00:01:08,560
so the way pools work is that they set a lower difficulty to the actual difficulty that you would

13
00:01:08,560 --> 00:01:14,640
need to hit a block and that's what they count as a share all right so if the actual difficulty

14
00:01:14,640 --> 00:01:22,160
of the bitcoin blockchain is x the pool difficulty will be set below that and it's obviously going to

15
00:01:22,160 --> 00:01:26,540
to be way easier for to reach that number so this is a way for the pools to make sure that you're

16
00:01:26,540 --> 00:01:43,447
actually working and depending on how many shares you are sending to the pool and you also get paid out right so instead of validating all of the hashes that your miner produces or that your fleet produces and having to do all of that work to verify each individual

17
00:01:43,447 --> 00:01:52,007
hash in real time the pools just verify if your hash is meeting the their minimum requirement and

18
00:01:52,007 --> 00:01:57,287
so while you're not actually finding blocks you're finding shares which happens below that

19
00:01:57,287 --> 00:02:02,407
if you look into and i've shared my screen here if you look into your dashboard this is the luxa

20
00:02:02,407 --> 00:02:08,087
dashboard it looks something like this over here you've got the share efficiency in a hundred percent

21
00:02:08,087 --> 00:02:13,207
you will see the active miners this is just some hash rate i bought on on wrigley but what this

22
00:02:13,207 --> 00:02:20,887
means basically is how many of the shares that you are sending are actually being counted and rewarded

23
00:02:20,887 --> 00:02:28,287
because there are also shares that you could send that are stale or invalid shares that the pool

24
00:02:28,287 --> 00:02:35,467
receives but doesn't pay you for one example of a stale share could be one that you send when the

25
00:02:35,467 --> 00:02:41,667
block was already found right so the the pool creates the template that your miner is working

26
00:02:41,667 --> 00:02:46,827
on all right your miner is working on the pool sending shares to the pool the block is found

27
00:02:46,827 --> 00:02:59,207
And then your miner still sends shares that are related to the previous block, which the pool obviously cannot reward you for because it's, quote unquote, useless work.

28
00:02:59,667 --> 00:02:59,787
Yeah.

29
00:02:59,847 --> 00:03:06,687
If you peek down below in the bottom half of the screen, you will see rejected shares, stale shares and shares efficiency.

30
00:03:07,047 --> 00:03:17,895
Right Ideally you want the share efficiency to be 100 which means all of the shares that you sending are valid and being rewarded stale shares you don want those right if you see many of

31
00:03:17,895 --> 00:03:24,775
these that's a problem and then rejected shares are just straight up rejections that the pool makes

32
00:03:24,775 --> 00:03:31,175
buying bitcoin miners should be simple safe and fast alter ear technology delivers exactly that

33
00:03:31,175 --> 00:03:36,695
Based in the US and shipping directly from St. Louis, AltaEar eliminates all the shady

34
00:03:36,695 --> 00:03:41,815
messaging groups, customs and tariffs issues and makes sure Bitcoin miners get to you on

35
00:03:41,815 --> 00:03:42,815
time.

36
00:03:42,815 --> 00:03:46,575
AltaEar stocks leading commercial ASIC miners, efficient home units and all the critical

37
00:03:46,575 --> 00:03:52,355
parts you need, backed by real inventory, real support and a team of people that you

38
00:03:52,355 --> 00:03:55,255
can rely on and actually mines Bitcoin.

39
00:03:55,255 --> 00:03:58,035
Thank you so much, AltaEar Technology, for supporting the show.

40
00:03:58,035 --> 00:04:00,675
And without further ado, let's get back to it.

41
00:04:00,675 --> 00:04:06,415
So the question beckons, what's the difference between a stale share and an invalid share

42
00:04:06,415 --> 00:04:07,895
or a rejected share?

43
00:04:08,415 --> 00:04:10,335
Rejected shares are exactly that.

44
00:04:10,875 --> 00:04:15,615
They are invalid and stale shares are shares that are sent too late.

45
00:04:15,895 --> 00:04:19,595
Now, the next question is, okay, what causes these rejected shares?

46
00:04:19,995 --> 00:04:22,235
One problem could be firmware issues, right?

47
00:04:22,235 --> 00:04:27,475
If the firmware on the device is not working properly, it can lead to shares that are for

48
00:04:27,475 --> 00:04:34,395
some reason not valid and don't have a chance to be a valid answer to finding a block or

49
00:04:34,395 --> 00:04:36,055
a valid hash.

50
00:04:36,055 --> 00:04:38,855
With some ASIC models, you will find this as well, right?

51
00:04:38,855 --> 00:04:55,742
If they come out of the box and some ASIC models just end up producing faulty shares or faulty hashes that can then not be counted to the pool Because again the pool can only pay you for shares that could have been a valid solution to a block

52
00:04:55,742 --> 00:04:59,982
or a valid block solution that then the pool gets paid out for.

53
00:05:00,382 --> 00:05:01,602
Latency can also be an issue.

54
00:05:01,702 --> 00:05:05,942
There's a lot of data being sent between your mine and the pool server.

55
00:05:05,942 --> 00:05:10,922
And if the latency is too big or too long in that sense,

56
00:05:10,922 --> 00:05:15,582
then that means you're more likely to send work that is invalid and therefore rejected.

57
00:05:15,942 --> 00:05:20,742
Temperature also works. So it's all within the ASIC, right? If the firmware is not working

58
00:05:20,742 --> 00:05:25,962
properly, or there's some fault in the device configuration or in the model type, if the ASICs

59
00:05:25,962 --> 00:05:33,042
are running too hot, they can calculate invalid shares as well, or invalid hashes turn into shares

60
00:05:33,042 --> 00:05:39,062
that are then being rejected by the pool. So that's why it's important to keep your ASICs cool

61
00:05:39,062 --> 00:05:44,742
for a long long time and so overall you want to make sure that you run a very clean smooth operation

62
00:05:44,742 --> 00:05:51,942
to make sure that the number of invalid shares and therefore rejected shares stays as close to zero

63
00:05:51,942 --> 00:05:58,582
as possible currently in the new year i'm heavily advocating for hydro hosting to improve the

64
00:05:58,582 --> 00:06:05,622
financial and physical lifespan of the machine this also has to do with keeping a machine cool

65
00:06:05,622 --> 00:06:10,342
and running it smoothly in a well-maintained data center if you want to learn more about that or

66
00:06:10,342 --> 00:06:15,302
interested in hosting a hydro miner feel free to reach out i hope you learned something new

67
00:06:15,302 --> 00:06:23,222
all the best for 2026 see you next time