ETC consecutive shares rejected by the pool #1582

david739 · 2023-01-10T21:40:33Z

hello, I have a problem with ETC, it keeps writing to me on the miner (consecutive shared zamita pool) the coin is displayed and the work goes on, but the hash of the miner is not displayed on the website

pool2mine · 2023-01-22T18:33:20Z

Not 100% sure, but as far as i remember, Miningcore has no support for ETC yet. Remember ETC hardforked and changed algo a couple of years ago to ETCHASH

david739 · 2023-01-23T13:08:13Z

Does anyone know how to set it up to make it work?

Has anyone managed to get it working?

pool2mine · 2023-01-27T02:12:38Z

I never got it working with miningcore... I had to fork the sammy's version that official ETC profile has, then added nicehash support and some other custom stuff i needed. it is easier to start with their repo as they already added ETCHASH support

jon4hz · 2023-01-27T11:55:13Z

#1514 adds support for ETC (not merged yet though)

david739 · 2023-01-29T18:44:35Z

hello, I copied the data and checked the source, it should fit according to the instructions, but I still have something wrong, can someone please help me

Generating DAG for epoch 562

[2023-01-29 19:34:04.3201] [I] [etc1] Broadcasting job 00000073
[2023-01-29 19:34:05.3469] [I] [StatsRecorder] [etc1] Updating Statistics for pool
[2023-01-29 19:34:05.3890] [I] [StatsRecorder] [etc1] Reset performance stats for pool
[2023-01-29 19:34:08.3298] [I] [etc1] [0HMO24O99RQ53] Share rejected: low difficulty share (2.3283064365386963E-10) []
[2023-01-29 19:34:10.3315] [I] [etc1] New work at height 16838286 and header 0xc5b7438db8c4676eae6be51f5219eaa3973bb03bb90648b7b86147af3ff9323b via [POLL]
[2023-01-29 19:34:10.3315] [I] [etc1] Broadcasting job 00000074
[2023-01-29 19:34:11.5124] [I] [etc1] [0HMO24O99RQ53] Share rejected: low difficulty share (4.656612873077393E-10) []
[2023-01-29 19:34:11.5163] [I] [etc1] [0HMO24O99RQ53] Connection closed
[2023-01-29 19:34:16.5339] [I] [etc1] [0HMO24O99RQ54] Accepting connection from ::ffff:192.168.0.1:50232 ...
[2023-01-29 19:34:16.5339] [I] [etc1] [0HMO24O99RQ54] Connection from ::ffff:192.168.0.1:50232 accepted on port 4001

Pool coin Algorithm Miners Pool Hashrate Fee Network Hashrate Network Difficulty
Ethereum Classic (ETC) Ethhash 0 0 H/s 1 % 125.86995 TH/s 1.64834 PGO MINE ETHEREUM CLASSIC

jon4hz · 2023-01-29T18:51:05Z

That's definitely the wrong epoch. What chaintypeoverride did you use in the config.json?

david739 · 2023-01-29T18:51:45Z

david739 · 2023-01-29T18:59:05Z

hello, I didn't change config.json, there is no information in the instructions, what should I change there, please

jon4hz · 2023-01-29T19:03:27Z

try to add "chainTypeOverride": "Classic" in the pool config.

david739 · 2023-01-29T19:28:48Z

hi you mean like this
config.scheme.json

902
"chainTypeOverride": "Classic" {
"type": [
"integer",
"null"
]
},
"equihashMaxThreads": {
"type": [
"integer",
"null"
]
},
"instanceId": {
"type": [
"integer",
"null"
]
},
"logging": {
"$ref": "#/definitions/ClusterLoggingConfig"

jon4hz · 2023-01-29T19:29:48Z

no, your pool config...

david739 · 2023-01-29T19:37:35Z

sorry i got it here is my settings

{
"logging": {
"level": "info",
"enableConsoleLog": true,
"enableConsoleColors": true,
"logFile": "bitcoin-cash.log",
"apiLogFile": "bitcoin-cash_api.log",
"logBaseDirectory": "c:/miningcore/build/logs",
"perPoolLogFile": false
},
"banning": {
"manager": "Integrated",
"banOnJunkReceive": false,
"banOnInvalidShares": false
},
"notifications": {
"enabled": false,
"email": {
"host": "smtp.example.com",
"port": 587,
"user": "user",
"password": "password",
"fromAddress": "info@yourpool.org",
"fromName": "pool support"
},
"admin": {
"enabled": false,
"emailAddress": "user@example.com",
"notifyBlockFound": false
}
},
"persistence": {
"postgres": {
"host": "127.0.0.1",
"port": 5432,
"user": "miningcore",
"password": "xxx",
"database": "xxx"
}
},
"paymentProcessing": {
"enabled": true,
"interval": 900,
"shareRecoveryFile": "recovered-shares.txt"
},
"api": {
"enabled": true,
"listenAddress": "",
"port": 4000,
"metricsIpWhitelist": [],
"rateLimiting": {
"disabled": true,
"rules": [
{
"Endpoint": "",
"Period": "1s",
"Limit": 5
}
],
"ipWhitelist": [
""
]
}
},
"clusterName": "eu1",
"pools": [
{
"id": "etc1",
"enabled": true,
"coin": "ethereumclassic",
"address": "xxx",
"rewardRecipients": [
{
"type": "op",
"address": "xxx",
"percentage": 1.0
}
],
"blockRefreshInterval": 120,
"clientConnectionTimeout": 600,
"banning": {
"enabled": true,
"time": 600,
"invalidPercent": 50,
"checkThreshold": 50
},
"ports": {
"4001": {
"name": "GPU-SMALL",
"listenAddress": "*",
"difficulty": 0.1,
"varDiff": {
"minDiff": 0.1,
"maxDiff": null,
"targetTime": 15,
"retargetTime": 90,
"variancePercent": 30
}
}
},
"chainTypeOverride": "Classic",
"dagDir": "",
"daemons": [
{
"host": "127.0.0.1",
"port": 8545,
"user": "",
"password": ""
}
],
"paymentProcessing": {
"enabled": true,
"minimumPayment": 0.1,
"payoutScheme": "PPLNS",
"payoutSchemeConfig": {
"factor": 0.5
},
"gas": 21000,
"maxFeePerGas": 50000000000,
"BlockSearchOffset": 100,
"keepUncles": false,
"keepTransactionFees": false
}
}
]
}

jon4hz · 2023-01-29T19:39:53Z

Are you running on windows? (looking at the logBaseDirectory)
Not sure if windows is fully supported.

The config looks fine imo.

david739 · 2023-01-29T19:43:52Z

i have ubuntu it's just a bug so what now

jon4hz · 2023-01-29T19:59:12Z

Maybe @blackmennewstyle can help you out. He wrote that code :)

david739 · 2023-01-29T20:04:11Z

ok thank you
and it won't be bad (Generating DAG for epoch 562)

blackmennewstyle · 2023-01-30T05:07:57Z

Hi,

Sorry for the late reply. Generally when i faced the error Share rejected: low difficulty share, it was always related to the DAG. Is your path not filled?

"dagDir": "<Your directory for the dag file>",

Do not hesitate to read that discussion: #1586

On Linux that repository is called .etchash, next to .ethereum and it's always located in the home folder of the user which runs the geth.

david739 · 2023-01-30T06:57:23Z

hi, I'll take a look at it, but I don't have a bad trigger for getg yet

./geth --classic --maxpeers "350" --cache "8192" --allow-insecure-unlock --miner.etherbase "xxx" --unlock "xxx" --password ~/pwd --mine --http --syncmode "fast" --http.api "admin,debug,web3,eth,txpool,personal,ethash,miner,net,trace"

blackmennewstyle · 2023-01-30T07:16:37Z

The POW algorithm etchash needs the DAG files located in that directory in order to work properly and validate the shares it receives from miners. If you does not specify the path for that directory in your config.json, your shares will always be rejected.

Also, what do you mean by bad trigger with geth?

that will be it can you please provide an example in the source code

david739 · 2023-01-30T08:44:36Z

I already put it in there, but the file classic.toml is empty, does anyone know what the source should be in it

"chainTypeOverride": "Classic",
"dagDir": "/home/xxx/.ethereum/classic/geth/classic.toml",
"daemons": [

blackmennewstyle · 2023-01-30T10:12:04Z

Out of curiosity, are you trying to run your ETC pool with the source code currently available on https://github.com/oliverw/miningcore?

blackmennewstyle · 2023-01-30T11:42:51Z

I feel like i misunderstood you since beginning, so my bad.

So like @jon4hz warned about, the source code currently available on https://github.com/oliverw/miningcore does not support ETC with etchash, it has not been merged yet. So if you want to have support for ETC with etchash, you need to use my fork https://github.com/blackmennewstyle/miningcore.

Also, you need clearly to read the geth documentation in order to be more familiar. The .toml file is a configuration file for geth, you need to generate it. It allows you to run the node without the need of specifying one hundreds options.
Once you generated that .toml file, it will contain a line like this one DatasetDir = "/home/ceedii/.etchash". It's the path to the directory which contains all the DAG files, it's the one you can use for "dagDir":.
However, if you are in a situation where miningcore and geth are not running on the same server. You can arbitrarily create a folder on the server which runs miningcore and specify the path to that folder inside "dagDir":. miningcore will automatically generate the necessary DAG files. Just make sure that the user which runs miningcore has read and write access on that folder.

david739 · 2023-01-30T11:47:11Z

ok i will do everything and let you know

david739 · 2023-01-30T12:24:10Z

I would be grateful for the procedure how to generate .toml

jon4hz · 2023-01-30T12:33:19Z

I don't think that is neccessary at all. dagDir is an optional parameter (or at least was until now).

What stands out is that your pool tried to generate the dag for epoch 562 which is wrong. Etc is on epoch 280.
But that should have anything to do with the directoy where the dag is stored.

david739 · 2023-01-30T13:07:03Z

ok, and how should I generate 280, it still generates 562, it wouldn't be possible to fix something

./geth --classic --maxpeers "350" --cache "8192" --allow-insecure-unlock --miner.etherbase "xxx" --unlock "xxx" --password ~/pwd --mine --http --syncmode "fast" --http.api "admin,debug,web3,eth,txpool,personal,ethash,miner,net,trace"

blackmennewstyle · 2023-01-30T13:37:36Z

Please, can you answer which source code you are currently using? https://github.com/oliverw/miningcore or https://github.com/blackmennewstyle/miningcore for running your pool?

david739 · 2023-01-30T13:41:14Z

yeah sorry I'm trying yours now https://github.com/blackmennewstyle/miningcore

david739 · 2023-01-30T13:58:09Z

I got 280 on yours, it's starting up now so we'll see

david739 · 2023-01-30T14:21:40Z

so your system works without a problem thank you thank you and 1 more thank you

blackmennewstyle · 2023-01-30T14:39:14Z

You're welcome. So you were just not using the correct source code. Congratulations :)

david739 · 2023-01-30T14:50:32Z

well, I didn't know about yours, I kept remaking the other system, too bad, but at least I learned something

david739 added the bug label Jan 10, 2023

david739 changed the title ~~hi, can someone please advise me how to get 42coin working~~ ETC consecutive shares rejected by the pool Jan 18, 2023

Copy link

Author

david739 commented Jan 30, 2023

that will be it can you please provide an example in the source code

Repository owner locked and limited conversation to collaborators Jan 31, 2023

oliverw converted this issue into discussion #1596 Jan 31, 2023

Uh oh!

This issue was moved to a discussion.

ETC consecutive shares rejected by the pool #1582

ETC consecutive shares rejected by the pool #1582

Comments

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

This issue was moved to a discussion.