Question about solo mining with Phoenix

[maciekish]

So, when running phoenix against bitcoinpool.com, it would show something like

Code:

[xxx Mhash/sec [23 Accepted] [1 Rejected] [RPC (+LP)]

However if i run the same phoenix command against my local bitcoin.exe -server, i get the following output instead

Code:

[xxx Mhash/sec [0 Accepted] [0 Rejected] [RPC]

Is that normal? Is everything working like it should? I do have all the blocks (126000+)

When do i know if i solved a block? Any way to see progress to that or "it just happens"?

Thank you for your time!

[1714986627]

1714986627

[1714986627]

1714986627

[1714986627]

1714986627

[1714986627]

1714986627

[1714986627]

1714986627

[kjj]

Yes, totally normal.

The standard node client isn't impressed unless you've got a valid hash that meets the current difficulty target.  For most people, this will be never.

The pools, however, accept hashes that only meet a much easier target, so that they can allocate shares to the miners.

[maciekish]

So that means with 333MH/s i should probably go to a pool then?

[dikidera]

Yes, totally normal.

The standard node client isn't impressed unless you've got a valid hash that meets the current difficulty target.  For most people, this will be never.

The pools, however, accept hashes that only meet a much easier target, so that they can allocate shares to the miners.

The pool does not allocate shares. You do them. If they meet the needed criteria they get inserted in the database as a valid share(bit might not meet the target).

[kjj]

Yes, totally normal.

The standard node client isn't impressed unless you've got a valid hash that meets the current difficulty target.  For most people, this will be never.

The pools, however, accept hashes that only meet a much easier target, so that they can allocate shares to the miners.

The pool does not allocate shares. You do them. If they meet the needed criteria they get inserted in the database as a valid share(bit might not meet the target).

No, you do hashes.  The pool does shares, and I'm pretty sure the right word for that process is allocation.