search

onemorebsmith / kaspa-stratum-bridge

Bridge/Adapter between the stratum-based miners and a kaspad node
MIT License
67 stars 102 forks source link

digging to the exbitron.com exchange, payments do not come for blocks #46

Open seoseo29 opened 2 years ago

seoseo29 commented 2 years ago

digging to the exbitron.com exchange, payments do not come for blocks

onemorebsmith commented 2 years ago

Don't mine to an exchange wallet. Never do that for any miner.

seoseo29 commented 2 years ago

IT DOES NOT COME TO THE LOCAL WALLET EITHER

myntfarm commented 2 years ago

Author

seoseo29 commented 2 minutes ago

I have been using this to mine to a web wallet for more than a week. make sure your kaspad is updated and use the new v1.1.4 version.

rpringst commented 2 years ago

I never got the block that I found and I was using ghost-pool, and am not using an exchange based wallet, so something is amiss. :(

myntfarm commented 2 years ago

I never got the block that I found and I was using ghost-pool, and am not using an exchange based wallet, so something is amiss. :(

yes there was a bug and v1.1.4 fixed it

rpringst commented 2 years ago

I never got the block that I found and I was using ghost-pool, and am not using an exchange based wallet, so something is amiss. :(

yes there was a bug and v1.1.4 fixed it

@Myntfarm https://github.com/onemorebsmith/kaspa-stratum-bridge/releases/tag/v1.1.4

Nothing in release notes regarding a bug outright causing a mined block not to exist. I was on the dev's pool, not running my own instance...

myntfarm commented 2 years ago

the bug was involved issues with the submitted blocks i believe. We had many many people report issues of suddenly days with out blocks or invalid blocks being submitted. Issue was resolved. sorry about the block but if it helps its not like the pool owner got anything. The stratum has no mechanism to collect fees or for pay out control. It just sends that data to the node. The mining software where you input your address is credited from the kaspa coinbase itself. not from the node or the stratum.

rpringst commented 2 years ago

@Myntfarm If it was an invalid block, or rejected by the network, the dashboard shouldn't have reported a block was mined. I have gone through the code base, there are error codes for such scenarios, but none were reported. Without a block hash from a log to go off of, with a reason why that hash was invalid, one's faith completely evaporates.

Why are you saying 'We'? Are you an active contributor to this repo as well?

myntfarm commented 2 years ago

@Myntfarm If it was an invalid block, or rejected by the network, the dashboard shouldn't have reported a block was mined. I have gone through the code base, there are error codes for such scenarios, but none were reported. Without a block hash from a log to go off of, with a reason why that hash was invalid, one's faith completely evaporates.

Why are you saying 'We'? Are you an active contributor to this repo as well?

i am not a contributor yet. just active in the community. also a user. i experienced this same issue.

myntfarm commented 2 years ago

@rpringst heres the thing. There ARE logs from the bridge about errors. Did you have it save logs anywhere?

Errors like this "error unknown error during check stales: blueScore 26538515 vs 26538554: stale share {"component": "stratum", "address": ":5555", "client": "x.x.x.x"}."

Once again. There was a bug. It affected MANY people. It was fixed by the amazing dev who does this FOR FREE on their own time. No one is trying to con you out of your coins... if you are very worried just make your own node and use BZminer to miner directly to it.

rpringst commented 2 years ago

@Myntfarm I was using the developer's instance of the bridge, 'ghost pool', not my own. I said this multiple times... The dev would be the one with the logs.