-
-
Notifications
You must be signed in to change notification settings - Fork 760
Mining on the pool by myself, not getting full reward. #1689
-
As title suggests; I'm mining on the pool, and no one else is mining there. I've confirmed in the database that my miner is the only one connected. When a block is hit, my miner is getting less than 40% of the reward, but it doing 100% of the work. The rest is sent to a random wallet address; it seems that the pool is generating a new address each time the block is hit. So far, I've hit 4 blocks and now I have 5 addresses.
I have no reward recipients configured, and I've tried to set one at 0%. Nothing changed.
Beta Was this translation helpful? Give feedback.
All reactions
Replies: 4 comments 7 replies
-
We need more information. What coin are you mining?
Beta Was this translation helpful? Give feedback.
All reactions
-
We need more information. What coin are you mining?
I’m mining Bitoreum, and using the standard Core wallet for RPC. I used a brand new wallet, with a single address. Once a block was hit, a new address was automatically generated.
Am I incorrect in my thinking that a single miner in PPLNS system should receive the whole reward, minus pool fee and TX cost?
Beta Was this translation helpful? Give feedback.
All reactions
-
Beta Was this translation helpful? Give feedback.
All reactions
-
If you look through the threads on here it has been explained before. A true pplns pool will pay proportionally for the amount of shares submitted by the miner.
Beta Was this translation helpful? Give feedback.
All reactions
-
For the payments to work properly you also need to setup the wallet as a legacy wallet
Beta Was this translation helpful? Give feedback.
All reactions
-
Ahhh okay, I’ll look up how that’s done and will circle back here for an update. Thanks for the suggestion.
Beta Was this translation helpful? Give feedback.
All reactions
-
Circling back. I'm not seeing anything in the daemon or CLI help documentation about enabling "legacy" mode. From Bitcoin Core's legacy mode, you'd typically need to set descriptors to false, but I'm not seeing that as an option for this coin. Any advice on that?
Beta Was this translation helpful? Give feedback.
All reactions
-
Bitoreum - How to Setup your Wallet and Mine - BTRM - YouTube https://m.youtube.com/watch?v=Frr01iVwRyw
Beta Was this translation helpful? Give feedback.
All reactions
-
Please. I can't tell if you're trolling, being an ass, or really trying to be helpful. I'm not meaning disrespect here, but at least give me some credit. I am not an idiot. Not to mention, you suggested that the wallet needs to be setup as some "legacy" type, but the video - which I watched prior to circling back a while ago - mentions nothing about.
Here is my start script, which is called by a systemd unit file. Of course, some data is scrubbed.
/opt/crypto/wallets/bitoreum/bitoreumd -datadir="<path>" -rpcuser=user -rpcpassword=pass -daemon
I've ran this command to generate a wallet:
/opt/crypto/wallets/bitoreum/bitoreum-cli -datadir="<path>" -rpcuser=user -rpcpassword=pass createwallet "test_wallet"
That's it. The output of the createwallet command is simply the hash of the wallet. I configured the pool to use that hash for block rewards and have no fees configured.
The host running the MiningCore installation is a Ubuntu 22.04.
I should also point out that NOMP does not have these issues while mining similar bitcoin-family coins.
Beta Was this translation helpful? Give feedback.
All reactions
-
if you hit rewards before the miner's PPLNS window is saturated, the pool keeps more than you expect in this scenario
it's really only a "problem" for new pools - but it's functioning as expected, strictly speaking
this thread should be helpful:
https://bitcointalk.org/index.php?topic=39832
Beta Was this translation helpful? Give feedback.