ETC consecutive shares rejected by the pool #1596

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

david739
Jan 10, 2023

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

pool2mine
Jan 22, 2023

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

0 replies

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

david739
Jan 23, 2023
Author

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

Has anyone managed to get it working?

0 replies

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

pool2mine
Jan 27, 2023

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

0 replies

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

jon4hz
Jan 27, 2023

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

0 replies

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

david739
Jan 29, 2023
Author

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

0 replies

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

jon4hz
Jan 29, 2023

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

0 replies

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

david739
Jan 29, 2023
Author

0 replies

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

david739
Jan 29, 2023
Author

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

0 replies

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

jon4hz
Jan 29, 2023

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

0 replies

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

david739
Jan 29, 2023
Author

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"

0 replies

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

jon4hz
Jan 29, 2023

no, your pool config...

0 replies

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

david739
Jan 29, 2023
Author

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
}
}
]
}

0 replies

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

jon4hz
Jan 29, 2023

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

The config looks fine imo.

0 replies

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

david739
Jan 29, 2023
Author

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

0 replies

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

jon4hz
Jan 29, 2023

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

0 replies

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

blackmennewstyle
Jan 30, 2023

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?

0 replies

david739 · 2023-01-30T07:49:49Z

david739
Jan 30, 2023
Author

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

0 replies

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

david739
Jan 30, 2023
Author

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": [

0 replies

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

blackmennewstyle
Jan 30, 2023

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

0 replies

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

blackmennewstyle
Jan 30, 2023

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.

0 replies

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

david739
Jan 30, 2023
Author

ok i will do everything and let you know

0 replies

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

david739
Jan 30, 2023
Author

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

0 replies

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

jon4hz
Jan 30, 2023

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.

0 replies

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

david739
Jan 30, 2023
Author

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"

0 replies

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

blackmennewstyle
Jan 30, 2023

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?

0 replies

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

david739
Jan 30, 2023
Author

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

C95D

0 replies

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

david739
Jan 30, 2023
Author

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

0 replies

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

david739
Jan 30, 2023
Author

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

0 replies

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

blackmennewstyle
Jan 30, 2023

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

0 replies

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

david739
Jan 30, 2023
Author

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

0 replies

Uh oh!

ETC consecutive shares rejected by the pool #1596

Uh oh!

Uh oh!

Replies: 33 comments

Uh oh!

Uh oh!

Uh oh!

david739 Jan 23, 2023 Author

Uh oh!

Uh oh!

Uh oh!

david739 Jan 29, 2023 Author

Uh oh!

Uh oh!

david739 Jan 29, 2023 Author

Uh oh!

david739 Jan 29, 2023 Author

Uh oh!

Uh oh!

Uh oh!

david739 Jan 29, 2023 Author

Uh oh!

Uh oh!

Uh oh!

david739 Jan 29, 2023 Author

Uh oh!

Uh oh!

Uh oh!

david739 Jan 29, 2023 Author

Uh oh!

Uh oh!

Uh oh!

Uh oh!

david739 Jan 30, 2023 Author

Uh oh!

david739 Jan 30, 2023 Author

Uh oh!

Uh oh!

Uh oh!

Uh oh!

david739 Jan 30, 2023 Author

Uh oh!

david739 Jan 30, 2023 Author

Uh oh!

Uh oh!

david739 Jan 30, 2023 Author

Uh oh!

Uh oh!

david739 Jan 30, 2023 Author

Uh oh!

Uh oh!

david739
Jan 23, 2023
Author

david739
Jan 29, 2023
Author

david739
Jan 29, 2023
Author

david739
Jan 29, 2023
Author

david739
Jan 29, 2023
Author

david739
Jan 29, 2023
Author

david739
Jan 29, 2023
Author

david739
Jan 30, 2023
Author

david739
Jan 30, 2023
Author

david739
Jan 30, 2023
Author

david739
Jan 30, 2023
Author

david739
Jan 30, 2023
Author

david739
Jan 30, 2023
Author