SoloPool.com - First Ever Miner Set Hybrid / Solo + Solo Split + Prop + Pool

[philipma1957]

Or set the primary as ny.solopool.com and the backup to stratum.solopool.com and it will automatically pick our closest live pool to you.

Either way should work!

SO the Apollo III miner is set off solo.

1st back up is ny solo pool
2nd back up is eu solo pool

And this seems to work.

Or set the primary as ny.solopool.com and the backup to stratum.solopool.com and it will automatically pick our closest live pool to you.

Either way should work!

with the Apollo III

solo on the included node is primary.

then backup 1
then backup 2


I looked at logs and it rotates out of back up 1 every once in a while to check if solo was made active.


once this new 2 bm1373 chip  hammer miner arrives I will set 1 and 2 to you with 3 to ck

https://altairtech.io/product/thor-p2-bitcoin-miner/

and set the apollo back to solo node.






I dropped out again not sure why it is happening  .

do not know if the Apollo has an issue
or the pool has an issue or
the internet service has an issue

I am going to put a different miner here for a while to see what happens

stratum+tcp://ny.solopool.com:3333
bc1q7ss6pzzj6y459tvc4lz8llkwxly7zhps6l2esm.T21one
75


stratum+tcp://eu.solopool.com:3333
bc1q7ss6pzzj6y459tvc4lz8llkwxly7zhps6l2esm.T21one
75



stratum+tcp://btc.viabtc.io:3333
worker
password



on a 1 board down clocked t21


https://www.solopool.com/user.html?addr=bc1q7ss6pzzj6y459tvc4lz8llkwxly7zhps6l2esm

so I set the Apollo III to solo on its own node

and I am only running the 1 board t21 here.


so the settings are above two to this pool and 1 to via btc.



if this runs well I will assume the Apollo does not like the solo node option shut off.

I will continue to check on this.

note the Apollo no longer running here just the 1 board t21

[philipma1957]

Or set the primary as ny.solopool.com and the backup to stratum.solopool.com and it will automatically pick our closest live pool to you.

Either way should work!

SO the Apollo III miner is set off solo.

1st back up is ny solo pool
2nd back up is eu solo pool

And this seems to work.

Or set the primary as ny.solopool.com and the backup to stratum.solopool.com and it will automatically pick our closest live pool to you.

Either way should work!

with the Apollo III

solo on the included node is primary.

then backup 1
then backup 2


I looked at logs and it rotates out of back up 1 every once in a while to check if solo was made active.


once this new 2 bm1373 chip  hammer miner arrives I will set 1 and 2 to you with 3 to ck

https://altairtech.io/product/thor-p2-bitcoin-miner/

and set the apollo back to solo node.






I dropped out again not sure why it is happening  .

do not know if the Apollo has an issue
or the pool has an issue or
the internet service has an issue

I am going to put a different miner here for a while to see what happens

stratum+tcp://ny.solopool.com:3333
bc1q7ss6pzzj6y459tvc4lz8llkwxly7zhps6l2esm.T21one
75


stratum+tcp://eu.solopool.com:3333
bc1q7ss6pzzj6y459tvc4lz8llkwxly7zhps6l2esm.T21one
75



stratum+tcp://btc.viabtc.io:3333
worker
password



on a 1 board down clocked t21


https://www.solopool.com/user.html?addr=bc1q7ss6pzzj6y459tvc4lz8llkwxly7zhps6l2esm

so I set the Apollo III to solo on its own node

and I am only running the 1 board t21 here.


so the settings are above two to this pool and 1 to via btc.



if this runs well I will assume the Apollo does not like the solo node option shut off.

I will continue to check on this.

note the Apollo no longer running here just the 1 board t21

so the t21 says I am mining and the pool say I am offline.

so this means it is not the gear. as two totally different machines gave me the same issue

a reboot fixes it

it could be an internet issue
it could be a pool issue

[philipma1957]

I did a double entry.

I understand the issue.

and the pool is wrong .

machine a   8th I shut it down the Apollo III
machine b 33th I added this

and I get a penalty

even with the hash increase

not good.

I can work around by simply doing a new addy with the second machine.

but it appears that if you run 2 machines at the pool both at 75-25

and decide to remove a machine

you get a penalty.

kind of makes mining with 2 machines a high risk if you want to split one off.

and these are 33+8th

I will add back the Apollo and see if penalty leaves.

well I went a different method to test this issue .  new btc addy here is the miner a t21 1 board set to 33th

https://www.solopool.com/user.html?addr=bc1q696ugy8fuygc3vlhycrwv7zqwv9fs9hgws235l

I will post later.

[Sledge0001]

The penalty will certainly apply if the miner goes offline. If you have 2 miners and then take one offline there will be a hashrate penalty enforced as you cut your hashrate!

[philipma1957]

The penalty will certainly apply if the miner goes offline. If you have 2 miners and then take one offline there will be a hashrate penalty enforced as you cut your hashrate!

No I understand what you are trying to do. But

The 8-10tb Apollo seems to not like your pool.

I added the 33tb t21.

So for about ten minutes both ran and 8+33=41

The 8tb drops out again and the penalty shows.

I pull it and run the 33tb

So at 8 in the   Morning I was running a flakey 8tb unit

And by the end of the day I was running a 33tb unit

And was punished with a penalty for not maintaining the two units

So the 70+30 split

Or 75+25 split should only be done if you run one machine.

And even though I began the day with 8-10tb

And ended the day with 33tb

Creates a penalty.

It’s a flaw.

But I do understand what you are trying to stop.

If you do not do it abuse is easy.

But to penalize 8-10th hash going to 33th with a brief amount of time at 41th shows a design flaw.

Although it does end large core  abuse.

Still do not understand why the Apollo does not drop out but the modded t21 seems good.

I get the Thor hammer next week which is a 10th unit.

The way I will go is put it on the same address as the 33th unit.


Bringing me to 43 th.

I will then drop the 33th unit

Bringing me to 10th and triggering the penalty


So next question is.

I keep the 10th unit say at 70-30 and it is perfect. When does the penalty go away.

Look I am not trying to game your system but I am trying to understand how to run a 70-30 setup and not worry about penalty’s.

And starting at 8/10 going to 41 dropping and staying at 33 losing on a penalty is flawed.

Well next week the Thor p2 comes.

[Sledge0001]

Philip,
This is exactly the kind of feedback I want, and I think I can clear up the main misunderstanding.

THE PENALTY IS PER MACHINE, NOT PER ADDRESS

Every worker is scored on its own. The pool never adds your machines together and then punishes you because the total dropped. Going 8 → 41 → 33 TH did not create a penalty on the 33 TH machine. Only the Apollo's own contribution was penalized, for the hours it wasn't hashing. The T21 carried nothing from that.

THE TWO CHECKS

Both look at one machine at a time and compare it only to its own history:

Offline check   — hours since that worker's last share.

Hashrate check  — that worker's current rate vs its own average this round.
Anything within 15% of normal is ignored. Nothing happens for the first 5 hours below that.

Whichever is higher applies. Adding a second machine cannot trigger either one.

HOW THE PENALTY GROWS (a machine that stops hashing completely)

Hours dark   Offline check   Hashrate check   Applied (higher wins)
  ----------   -------------   --------------   ---------------------
   4               0%                0%                   0%
   5              0.2%              0%                  0.2%
   6              0.5%              3%                   3%
   8              1.7%             12%                 12%
  10             3.4%             23%                 23%
  12             5.5%             43%                 43%
  14             9%                69%                 69%
  16             12%             100%               100%  ("excluded")
  24             26%             100%               100%
  48             100%            100%               100%

The hashrate check is the one that bites on a fully dark machine — it reaches 100% at 16 hours.
The offline check only matters on its own for a machine that's still trickling a few shares. A machine that keeps hashing at a lower rate ramps more gently, and never past what the drop justifies.

WHAT'S PERMANENT AND WHAT ISN'T

  When the machine comes back...
  ----------------------------------------------------------------------
  The "excluded" / penalty badge clears within minutes
  Contribution written down while STAYS gone for the rest of the round it was dark
  New shares from that point on count at 100%, immediately
  Your other machines never affected
  Your 70/30 split setting unchanged — has nothing to do with this

So the penalty is real, but it's bounded: it only ever touches what that one machine had built up before it went quiet, and only in proportion to how long it was quiet.

WHAT YOU'RE LOOKING AT RIGHT NOW

Both rows show "excluded" because neither machine has sent a share in over a day (T21 ~48 h, Apollo ~66 h). That's 100% in the table above. The moment either one reconnects, its badge clears and it starts fresh.

THE THOR PLAN — ONE THING TO GET RIGHT

Give the Thor its own worker name (address.thor, or whatever you like). Then:

Thor as its own worker   → clean record, no penalty, starts at 0 and builds
T21 unplugged            → ramps off on its own contribution, nothing carries
Thor under the T21's     → pool sees "that worker" drop 33 → 10 TH and, after old worker name 5h, starts penalizing it. Avoid this.

The pool can't tell a hardware swap from a rental walking away, so separate names is the whole trick. Do that and a 70/30 setup runs with no surprises.

On the Apollo dropping while the T21 holds — I'd like to figure that out. I've seen the firmware version and what its log says at the disconnect, and I'll dig in.

Thanks again for taking the time to try us out.