Daemon has downloaded 100.00% of blockchain from 31 peers, never listens on mining ports

[V8por5m1n3R]

Similar to #1374

Issues started with 72.0.1.0 after running successfully for 10 days. Found Issue #1374 today and rebuilt with new pull from GitHub version 73.1.0.0.

LAUCHING MININGCORE.EXE from PowerShell 7.2.6 (PWSH.EXE) not CMD.EXE

System parameters:

WindowsBuildLabEx : 19041.1.amd64fre.vb_release.191206-1406
WindowsCurrentVersion : 6.3
WindowsEditionId : Professional
WindowsInstallationType : Client
WindowsInstallDateFromRegistry : 2/24/2022 12:30:18 PM
WindowsProductName : Windows 10 Pro
WindowsSystemRoot : C:\Windows
WindowsVersion : 2009
WindowsUBR : 2006
BiosCharacteristics : {7, 11, 12, 15…}
BiosBIOSVersion : {ALASKA - 1072009, 0820, American Megatrends - 50013}
BiosBuildNumber :
BiosCaption : 0820
BiosCodeSet :
BiosCurrentLanguage : en|US|iso8859-1
BiosDescription : 0820
BiosEmbeddedControllerMajorVersion : 255
BiosEmbeddedControllerMinorVersion : 255
BiosFirmwareType : Uefi
BiosIdentificationCode :
BiosInstallableLanguages : 9
BiosInstallDate :
BiosLanguageEdition :
BiosListOfLanguages : {en|US|iso8859-1, fr|FR|iso8859-1, zh|TW|unicode, zh|CN|unicode…}
BiosManufacturer : American Megatrends Inc.
BiosName : 0820
BiosOtherTargetOS :
BiosPrimaryBIOS : True
BiosReleaseDate : 4/26/2021 8:00:00 PM
BiosSerialNumber : System Serial Number
BiosSMBIOSBIOSVersion : 0820
BiosSMBIOSMajorVersion : 3
BiosSMBIOSMinorVersion : 3
BiosSMBIOSPresent : True
BiosSoftwareElementState : Running
BiosStatus : OK
BiosSystemBiosMajorVersion : 8
BiosSystemBiosMinorVersion : 20
BiosTargetOperatingSystem : 0
BiosVersion : ALASKA - 1072009
CsAdminPasswordStatus : Unknown
CsAutomaticManagedPagefile : False
CsAutomaticResetBootOption : True
CsAutomaticResetCapability : True
CsBootROMSupported : True
CsBootStatus : {0, 0, 0, 0…}
CsBootupState : Normal boot
CsCaption : USLIT40CCMN5009
CsChassisBootupState : Safe
CsChassisSKUNumber : Default string
CsCurrentTimeZone : -240
CsDaylightInEffect : True
CsDescription : AT/AT COMPATIBLE
CsDomainRole : MemberWorkstation
CsEnableDaylightSavingsTime : True
CsHypervisorPresent : False
CsInfraredSupported : False
CsKeyboardPasswordStatus : Unknown
CsManufacturer : ASUS
CsModel : System Product Name
CsNetworkAdapters : {Ethernet}
CsNetworkServerModeEnabled : True
CsNumberOfLogicalProcessors : 8
CsNumberOfProcessors : 1
CsProcessors : {Intel(R) Core(TM) i3-10105 CPU @ 3.70GHz}
CsOEMStringArray : {Default string, Default string, STEAMER, Default string…}
CsPartOfDomain : True
CsPauseAfterReset : -1
CsPCSystemType : Desktop
CsPCSystemTypeEx : Desktop
CsPowerState : Unknown
CsPowerSupplyState : Safe
CsResetCapability : Other
CsResetCount : -1
CsResetLimit : -1
CsRoles : {LM_Workstation, LM_Server, NT}
CsStatus : OK
CsSystemType : x64-based PC
CsThermalState : Safe
CsTotalPhysicalMemory : 33157529600
CsPhysicallyInstalledMemory : 33554432
CsWakeUpType : PowerSwitch
OsName : Microsoft Windows 10 Pro
OsType : WINNT
OsOperatingSystemSKU : 48
OsVersion : 10.0.19044
OsBuildNumber : 19044
OsHotFixes : {KB5017266, KB5017022, KB4561600, KB4570334…}
OsBootDevice : \Device\HarddiskVolume1
OsSystemDevice : \Device\HarddiskVolume3
OsSystemDirectory : C:\Windows\system32
OsSystemDrive : C:
OsWindowsDirectory : C:\Windows
OsCountryCode : 1
OsCurrentTimeZone : -240
OsLocaleID : 0409
OsLocale : en-US
OsLocalDateTime : 10/6/2022 12:16:17 PM
OsLastBootUpTime : 10/3/2022 11:41:03 AM
OsUptime : 3.00:35:13.6653150
OsBuildType : Multiprocessor Free
OsCodeSet : 1252
OsDataExecutionPreventionAvailable : True
OsDataExecutionPrevention32BitApplications : True
OsDataExecutionPreventionDrivers : True
OsDataExecutionPreventionSupportPolicy : OptIn
OsDebug : False
OsDistributed : False
OsEncryptionLevel : 256
OsForegroundApplicationBoost : Maximum
OsTotalVisibleMemorySize : 32380400
OsFreePhysicalMemory : 18025716
OsTotalVirtualMemorySize : 65934832
OsFreeVirtualMemory : 46627828
OsInUseVirtualMemory : 19307004
OsSizeStoredInPagingFiles : 33554432
OsFreeSpaceInPagingFiles : 33524976
OsPagingFiles : {C:\pagefile.sys}
OsHardwareAbstractionLayer : 10.0.19041.1806
OsInstallDate : 2/24/2022 7:30:18 AM
OsManufacturer : Microsoft Corporation
OsMaxNumberOfProcesses : 4294967295
OsMaxProcessMemorySize : 137438953344
OsMuiLanguages : {en-US}
OsNumberOfLicensedUsers : 0
OsNumberOfProcesses : 202
OsNumberOfUsers : 10
OsArchitecture : 64-bit
OsLanguage : en-US
OsProductSuites : {TerminalServicesSingleSession}
OsPortableOperatingSystem : False
OsPrimary : True
OsProductType : WorkStation
OsSerialNumber : 00330-80000-00000-AA330
OsServicePackMajorVersion : 0
OsServicePackMinorVersion : 0
OsStatus : OK
OsSuites : {TerminalServices, TerminalServicesSingleSession}
KeyboardLayout : en-US
TimeZone : (UTC-05:00) Eastern Time (US & Canada)
PowerPlatformRole : Desktop
HyperVisorPresent : False
HyperVRequirementDataExecutionPreventionAvailable : True
HyperVRequirementSecondLevelAddressTranslation : True
HyperVRequirementVirtualizationFirmwareEnabled : True
HyperVRequirementVMMonitorModeExtensions : True
DeviceGuardSmartStatus : Off

MiningCore config.conf -
{
"logging": {
"level": "info",
"enableConsoleLog": true,
"enableConsoleColors": true,
// Log file name (full log) - can be null in which case log events are written to console (stdout)
"logFile": "core.log",
// Log file name for API-requests - can be null in which case log events are written to either main logFile or console (stdout)
"apiLogFile": "api.log",
// Folder to store log file(s)
"logBaseDirectory": "C:/CCMN/Nodes/ERGO/Miningcore/73.0.1.0/Logs", // or c:\path\to\logs on Windows
// If enabled, separate log file will be stored for each pool as .log
// in the above specific folder.
"perPoolLogFile": true
},
"banning": {
// "integrated" or "iptables" (linux only - not yet implemented)
"manager": "Integrated",
"banOnJunkReceive": true,
"banOnInvalidShares": false
},
"notifications": {
"enabled": false,
"email": {
"host": "smtp.example.com",
"port": 587,
"user": "user",
"password": "password",
"fromAddress": ",
"fromName": "pool support"
},
"admin": {
"enabled": false,
"emailAddress": ",
"notifyBlockFound": true
}
},
// Where to persist shares and blocks to
"persistence": {
// Persist to postgresql database
"postgres": {
"host": "127.0.0.1",
"port": 5432,
"user": "",
"password": "",
"database": ""
}
},
// Generate payouts for recorded shares and blocks
"paymentProcessing": {
"enabled": true,
// How often to process payouts, in milliseconds
"interval": 900000,
// Path to a file used to backup shares under emergency conditions, such as
// database outage
"shareRecoveryFile": "recovered-shares.txt"
},
// API Settings
"api": {
"enabled": true,
// Binding address (Default: 127.0.0.1)
"listenAddress": "127.0.0.1",
// Binding port (Default: 4000)
"port": 35400,
// IP address whitelist for requests to Prometheus Metrics (default 127.0.0.1)
"metricsIpWhitelist": [],
// Limit rate of requests to API on a per-IP basis
"rateLimiting": {
"disabled": false, // disable rate-limiting all-together, be careful
// override default rate-limit rules, refer to https://github.com/stefanprodan/AspNetCoreRateLimit/wiki/IpRateLimitMiddleware#defining-rate-limit-rules
"rules": [
{
"Endpoint": "*",
"Period": "1s",
"Limit": 5
}
],
// List of IP addresses excempt from rate-limiting (default: none)
"ipWhitelist": []
}
},
"pools": [
// Repeat the following section for multiple coins
{
// DON'T change the id after a production pool has begun collecting shares!
"id": "ERGOtls0MN",
"enabled": true,
"coin": "ergo",
// Address to where block rewards are given (pool wallet)
"address": "",
// Block rewards go to the configured pool wallet address to later be paid out
// to miners, except for a percentage that can go to, for examples,
// pool operator(s) as pool fees or or to donations address. Addresses or hashed
// public keys can be used. Here is an example of rewards going to the main pool
// "op"
"rewardRecipients": [
{
// Pool wallet
"address": "",
"percentage": 0.5
}
],
// How often to poll RPC daemons for new blocks, in milliseconds
"blockRefreshInterval": 400,
// Some miner apps will consider the pool dead/offline if it doesn't receive
// anything new jobs for around a minute, so every time we broadcast jobs,
// set a timeout to rebroadcast in this many seconds unless we find a new job.
// Set to zero to disable. (Default: 0)
"jobRebroadcastTimeout": 10,
// Remove workers that haven't been in contact for this many seconds.
// Some attackers will create thousands of workers that use up all available
// socket connections, usually the workers are zombies and don't submit shares
// after connecting. This features detects those and disconnects them.
"clientConnectionTimeout": 600,
// If a worker is submitting a high threshold of invalid shares, we can
// temporarily ban their IP to reduce system/network load.
"banning": {
"enabled": true,
// How many seconds to ban worker for
"time": 900,
// What percent of invalid shares triggers ban
"invalidPercent": 15,
// Check invalid percent when this many shares have been submitted
"checkThreshold": 50
},
// Each pool can have as many ports for your miners to connect to as you wish.
// Each port can be configured to use its own pool difficulty and variable
// difficulty settings. 'varDiff' is optional and will only be used for the ports
// you configure it for.
"ports": {
// Binding port for your miners to connect to
"21133": {
// Binding address (Default: 127.0.0.1)
"listenAddress": "0.0.0.0",
// Pool difficulty
"difficulty": 0.01,
// TLS/SSL configuration
"tls": false,
"tlsPfxFile": "/var/lib/certs/mycert.pfx",
// Variable difficulty is a feature that will automatically adjust difficulty
// for individual miners based on their hash rate in order to lower
// networking overhead
"varDiff": {
// Minimum difficulty
"minDiff": 0.01,
// Maximum difficulty. Network difficulty will be used if it is lower than
// this. Set to null to disable.
"maxDiff": 0.1,
// Try to get 1 share per this many seconds
"targetTime": 5,
// Check to see if we should retarget every this many seconds
"retargetTime": 30,
// Allow time to very this % from target without retargeting
"variancePercent": 15,
// Do not alter difficulty by more than this during a single retarget in
// either direction
"maxDelta": 500
}
}
},
// Recommended to have at least two daemon instances running in case one drops
// out-of-sync or offline. For redundancy, all instances will be polled for
// block/transaction updates and be used for submitting blocks. Creating a backup
// daemon involves spawning a daemon using the "-datadir=/backup" argument which
// creates a new daemon instance with it's own RPC config. For more info on this,
// visit: https:// en.bitcoin.it/wiki/Data_directory and
// https:// en.bitcoin.it/wiki/Running_bitcoind
"daemons": [
{
"host": "127.0.0.1",
"port": 39053,
"apiKey": "",
// "user": "user",
// "password": "",
// Enable streaming Block Notifications via ZeroMQ messaging from Bitcoin
// Family daemons. Using this is highly recommended. The value of this option
// is a string that should match the value of the -zmqpubhashblock parameter
// passed to the coin daemon. If you enable this, you should lower
// 'blockRefreshInterval' to 1000 or 0 to disable polling entirely.
"zmqBlockNotifySocket": "tcp://127.0.0.1:15101",
// Enable streaming Block Notifications via WebSocket messaging from Ethereum
// family Parity daemons. Using this is highly recommended. The value of this
// option is a string that should match the value of the --ws-port parameter
// passed to the parity coin daemon. When using --ws-port, you should also
// specify --ws-interface all and
// --jsonrpc-apis "eth,net,web3,personal,parity,parity_pubsub,rpc"
// If you enable this, you should lower 'blockRefreshInterval' to 1000 or 0
// to disable polling entirely.
"portWs": 18545,
}
],
// Generate payouts for recorded shares
"paymentProcessing": {
"enabled": true,
// Minimum payment in pool-base-currency (ie. Bitcoin, NOT Satoshis)
"minimumPayment": 0.01,
"payoutScheme": "PPLNS",
"payoutSchemeConfig": {
"factor": 2.0
}
}
},
// This section ends here. Add , after } if this is not the last coin section
// Repeat the following section for multiple coins
{
// DON'T change the id after a production pool has begun collecting shares!
"id": "ERGOtls1MN",
"enabled": true,
"coin": "ergo",
// Address to where block rewards are given (pool wallet)
"address": "",
// Block rewards go to the configured pool wallet address to later be paid out
// to miners, except for a percentage that can go to, for examples,
// pool operator(s) as pool fees or or to donations address. Addresses or hashed
// public keys can be used. Here is an example of rewards going to the main pool
// "op"
"rewardRecipients": [
{
// Pool wallet
"address": "",
"percentage": 0.5
}
],
// How often to poll RPC daemons for new blocks, in milliseconds
"blockRefreshInterval": 400,
// Some miner apps will consider the pool dead/offline if it doesn't receive
// anything new jobs for around a minute, so every time we broadcast jobs,
// set a timeout to rebroadcast in this many seconds unless we find a new job.
// Set to zero to disable. (Default: 0)
"jobRebroadcastTimeout": 10,
// Remove workers that haven't been in contact for this many seconds.
// Some attackers will create thousands of workers that use up all available
// socket connections, usually the workers are zombies and don't submit shares
// after connecting. This features detects those and disconnects them.
"clientConnectionTimeout": 600,
// If a worker is submitting a high threshold of invalid shares, we can
// temporarily ban their IP to reduce system/network load.
"banning": {
"enabled": true,
// How many seconds to ban worker for
"time": 900,
// What percent of invalid shares triggers ban
"invalidPercent": 15,
// Check invalid percent when this many shares have been submitted
"checkThreshold": 50
},
// Each pool can have as many ports for your miners to connect to as you wish.
// Each port can be configured to use its own pool difficulty and variable
// difficulty settings. 'varDiff' is optional and will only be used for the ports
// you configure it for.
"ports": {
// Binding port for your miners to connect to
"21134": {
// Binding address (Default: 127.0.0.1)
"listenAddress": "0.0.0.0",
// Pool difficulty
"difficulty": 0.01,
// TLS/SSL configuration
"tls": false,
"tlsPfxFile": "/var/lib/certs/mycert.pfx",
// Variable difficulty is a feature that will automatically adjust difficulty
// for individual miners based on their hash rate in order to lower
// networking overhead
"varDiff": {
// Minimum difficulty
"minDiff": 0.01,
// Maximum difficulty. Network difficulty will be used if it is lower than
// this. Set to null to disable.
"maxDiff": 0.1,
// Try to get 1 share per this many seconds
"targetTime": 15,
// Check to see if we should retarget every this many seconds
"retargetTime": 90,
// Allow time to very this % from target without retargeting
"variancePercent": 30,
// Do not alter difficulty by more than this during a single retarget in
// either direction
"maxDelta": 500
}
}
},
// Recommended to have at least two daemon instances running in case one drops
// out-of-sync or offline. For redundancy, all instances will be polled for
// block/transaction updates and be used for submitting blocks. Creating a backup
// daemon involves spawning a daemon using the "-datadir=/backup" argument which
// creates a new daemon instance with it's own RPC config. For more info on this,
// visit: https:// en.bitcoin.it/wiki/Data_directory and
// https:// en.bitcoin.it/wiki/Running_bitcoind
"daemons": [
{
"host": "127.0.0.1",
"port": 39053,
"apiKey": "",
// "user": "user",
// "password": "",
// Enable streaming Block Notifications via ZeroMQ messaging from Bitcoin
// Family daemons. Using this is highly recommended. The value of this option
// is a string that should match the value of the -zmqpubhashblock parameter
// passed to the coin daemon. If you enable this, you should lower
// 'blockRefreshInterval' to 1000 or 0 to disable polling entirely.
"zmqBlockNotifySocket": "tcp://127.0.0.1:15101",
// Enable streaming Block Notifications via WebSocket messaging from Ethereum
// family Parity daemons. Using this is highly recommended. The value of this
// option is a string that should match the value of the --ws-port parameter
// passed to the parity coin daemon. When using --ws-port, you should also
// specify --ws-interface all and
// --jsonrpc-apis "eth,net,web3,personal,parity,parity_pubsub,rpc"
// If you enable this, you should lower 'blockRefreshInterval' to 1000 or 0
// to disable polling entirely.
"portWs": 18545,
}
],
// Generate payouts for recorded shares
"paymentProcessing": {
"enabled": true,
// Minimum payment in pool-base-currency (ie. Bitcoin, NOT Satoshis)
"minimumPayment": 0.01,
"payoutScheme": "PPLNS",
"payoutSchemeConfig": {
"factor": 2.0
}
}
},
// This section ends here. Add , after } if this is not the last coin section
// Repeat the following section for multiple coins
{
// DON'T change the id after a production pool has begun collecting shares!
"id": "ERGOtls0TN",
"enabled": true,
"coin": "ergo",
// Address to where block rewards are given (pool wallet)
"address": "",
// Block rewards go to the configured pool wallet address to later be paid out
// to miners, except for a percentage that can go to, for examples,
// pool operator(s) as pool fees or or to donations address. Addresses or hashed
// public keys can be used. Here is an example of rewards going to the main pool
// "op"
"rewardRecipients": [
{
// Pool wallet
"address": "",
"percentage": 0.5
}
],
// How often to poll RPC daemons for new blocks, in milliseconds
"blockRefreshInterval": 400,
// Some miner apps will consider the pool dead/offline if it doesn't receive
// anything new jobs for around a minute, so every time we broadcast jobs,
// set a timeout to rebroadcast in this many seconds unless we find a new job.
// Set to zero to disable. (Default: 0)
"jobRebroadcastTimeout": 10,
// Remove workers that haven't been in contact for this many seconds.
// Some attackers will create thousands of workers that use up all available
// socket connections, usually the workers are zombies and don't submit shares
// after connecting. This features detects those and disconnects them.
"clientConnectionTimeout": 600,
// If a worker is submitting a high threshold of invalid shares, we can
// temporarily ban their IP to reduce system/network load.
"banning": {
"enabled": true,
// How many seconds to ban worker for
"time": 900,
// What percent of invalid shares triggers ban
"invalidPercent": 15,
// Check invalid percent when this many shares have been submitted
"checkThreshold": 50
},
// Each pool can have as many ports for your miners to connect to as you wish.
// Each port can be configured to use its own pool difficulty and variable
// difficulty settings. 'varDiff' is optional and will only be used for the ports
// you configure it for.
"ports": {
// Binding port for your miners to connect to
"21135": {
// Binding address (Default: 127.0.0.1)
"listenAddress": "0.0.0.0",
// Pool difficulty
"difficulty": 0.01,
// TLS/SSL configuration
"tls": false,
"tlsPfxFile": "/var/lib/certs/mycert.pfx",
// Variable difficulty is a feature that will automatically adjust difficulty
// for individual miners based on their hash rate in order to lower
// networking overhead
"varDiff": {
// Minimum difficulty
"minDiff": 0.01,
// Maximum difficulty. Network difficulty will be used if it is lower than
// this. Set to null to disable.
"maxDiff": 0.1,
// Try to get 1 share per this many seconds
"targetTime": 15,
// Check to see if we should retarget every this many seconds
"retargetTime": 90,
// Allow time to very this % from target without retargeting
"variancePercent": 30,
// Do not alter difficulty by more than this during a single retarget in
// either direction
"maxDelta": 500
}
}
},
// Recommended to have at least two daemon instances running in case one drops
// out-of-sync or offline. For redundancy, all instances will be polled for
// block/transaction updates and be used for submitting blocks. Creating a backup
// daemon involves spawning a daemon using the "-datadir=/backup" argument which
// creates a new daemon instance with it's own RPC config. For more info on this,
// visit: https:// en.bitcoin.it/wiki/Data_directory and
// https:// en.bitcoin.it/wiki/Running_bitcoind
"daemons": [
{
"host": "127.0.0.1",
"port": 39052,
"apiKey": "",
// "user": "user",
// "password": "",
// Enable streaming Block Notifications via ZeroMQ messaging from Bitcoin
// Family daemons. Using this is highly recommended. The value of this option
// is a string that should match the value of the -zmqpubhashblock parameter
// passed to the coin daemon. If you enable this, you should lower
// 'blockRefreshInterval' to 1000 or 0 to disable polling entirely.
"zmqBlockNotifySocket": "tcp://127.0.0.1:15101",
// Enable streaming Block Notifications via WebSocket messaging from Ethereum
// family Parity daemons. Using this is highly recommended. The value of this
// option is a string that should match the value of the --ws-port parameter
// passed to the parity coin daemon. When using --ws-port, you should also
// specify --ws-interface all and
// --jsonrpc-apis "eth,net,web3,personal,parity,parity_pubsub,rpc"
// If you enable this, you should lower 'blockRefreshInterval' to 1000 or 0
// to disable polling entirely.
"portWs": 18545,
}
],
// Generate payouts for recorded shares
"paymentProcessing": {
"enabled": true,
// Minimum payment in pool-base-currency (ie. Bitcoin, NOT Satoshis)
"minimumPayment": 0.01,
"payoutScheme": "PPLNS",
"payoutSchemeConfig": {
"factor": 2.0
}
}
},
// This section ends here. Add , after } if this is not the last coin section
// Repeat the following section for multiple coins
{
// DON'T change the id after a production pool has begun collecting shares!
"id": "ERGOtls1TN",
"enabled": true,
"coin": "ergo",
// Address to where block rewards are given (pool wallet)
"address": "",
// Block rewards go to the configured pool wallet address to later be paid out
// to miners, except for a percentage that can go to, for examples,
// pool operator(s) as pool fees or or to donations address. Addresses or hashed
// public keys can be used. Here is an example of rewards going to the main pool
// "op"
"rewardRecipients": [
{
// Pool wallet
"address": "",
"percentage": 0.5
}
],
// How often to poll RPC daemons for new blocks, in milliseconds
"blockRefreshInterval": 400,
// Some miner apps will consider the pool dead/offline if it doesn't receive
// anything new jobs for around a minute, so every time we broadcast jobs,
// set a timeout to rebroadcast in this many seconds unless we find a new job.
// Set to zero to disable. (Default: 0)
"jobRebroadcastTimeout": 10,
// Remove workers that haven't been in contact for this many seconds.
// Some attackers will create thousands of workers that use up all available
// socket connections, usually the workers are zombies and don't submit shares
// after connecting. This features detects those and disconnects them.
"clientConnectionTimeout": 600,
// If a worker is submitting a high threshold of invalid shares, we can
// temporarily ban their IP to reduce system/network load.
"banning": {
"enabled": true,
// How many seconds to ban worker for
"time": 900,
// What percent of invalid shares triggers ban
"invalidPercent": 15,
// Check invalid percent when this many shares have been submitted
"checkThreshold": 50
},
// Each pool can have as many ports for your miners to connect to as you wish.
// Each port can be configured to use its own pool difficulty and variable
// difficulty settings. 'varDiff' is optional and will only be used for the ports
// you configure it for.
"ports": {
// Binding port for your miners to connect to
"21136": {
// Binding address (Default: 127.0.0.1)
"listenAddress": "0.0.0.0",
// Pool difficulty
"difficulty": 0.01,
// TLS/SSL configuration
"tls": false,
"tlsPfxFile": "/var/lib/certs/mycert.pfx",
// Variable difficulty is a feature that will automatically adjust difficulty
// for individual miners based on their hash rate in order to lower
// networking overhead
"varDiff": {
// Minimum difficulty
"minDiff": 0.01,
// Maximum difficulty. Network difficulty will be used if it is lower than
// this. Set to null to disable.
"maxDiff": 0.1,
// Try to get 1 share per this many seconds
"targetTime": 15,
// Check to see if we should retarget every this many seconds
"retargetTime": 90,
// Allow time to very this % from target without retargeting
"variancePercent": 30,
// Do not alter difficulty by more than this during a single retarget in
// either direction
"maxDelta": 500
}
}
},
// Recommended to have at least two daemon instances running in case one drops
// out-of-sync or offline. For redundancy, all instances will be polled for
// block/transaction updates and be used for submitting blocks. Creating a backup
// daemon involves spawning a daemon using the "-datadir=/backup" argument which
// creates a new daemon instance with it's own RPC config. For more info on this,
// visit: https:// en.bitcoin.it/wiki/Data_directory and
// https:// en.bitcoin.it/wiki/Running_bitcoind
"daemons": [
{
"host": "127.0.0.1",
"port": 39052,
"apiKey": "",
// "user": "user",
// "password": "",
// Enable streaming Block Notifications via ZeroMQ messaging from Bitcoin
// Family daemons. Using this is highly recommended. The value of this option
// is a string that should match the value of the -zmqpubhashblock parameter
// passed to the coin daemon. If you enable this, you should lower
// 'blockRefreshInterval' to 1000 or 0 to disable polling entirely.
"zmqBlockNotifySocket": "tcp://127.0.0.1:15101",
// Enable streaming Block Notifications via WebSocket messaging from Ethereum
// family Parity daemons. Using this is highly recommended. The value of this
// option is a string that should match the value of the --ws-port parameter
// passed to the parity coin daemon. When using --ws-port, you should also
// specify --ws-interface all and
// --jsonrpc-apis "eth,net,web3,personal,parity,parity_pubsub,rpc"
// If you enable this, you should lower 'blockRefreshInterval' to 1000 or 0
// to disable polling entirely.
"portWs": 18545,
}
],
// Generate payouts for recorded shares
"paymentProcessing": {
"enabled": true,
// Minimum payment in pool-base-currency (ie. Bitcoin, NOT Satoshis)
"minimumPayment": 0.01,
"payoutScheme": "PPLNS",
"payoutSchemeConfig": {
"factor": 2.0
}
}
}
// This section ends here. Add , after } if this is not the last coin section
]
}

[oliverw]

Ergo sometimes misreports its sync progress. There is no known workaround.

Windows is not a supported production environment.

[Sanostee]

same issue

Litecoin 0.21.2.1
Ubuntu 20.04
Miningcore 73

[idanzam]

same for me ...

no solution ?

[snoby]

@Sanostee @idanzam
Your node is not synced,
https://github.com/ergoplatform/ergo/wiki/Set-up-a-full-node

syncing an ergo node has issues. i've faced them as well. I've used this resource to sync my node
https://github.com/mgpai22/ergo-synced-node

[oliverw]

@Sanostee @idanzam Your node is not synced, https://github.com/ergoplatform/ergo/wiki/Set-up-a-full-node

syncing an ergo node has issues. i've faced them as well. I've used this resource to sync my node https://github.com/mgpai22/ergo-synced-node

Yep, Ergo syncing can be a royal pain. I think almost everyone experienced that.

[regtable]

@Sanostee @idanzam Your node is not synced, https://github.com/ergoplatform/ergo/wiki/Set-up-a-full-node

syncing an ergo node has issues. i've faced them as well. I've used this resource to sync my node https://github.com/mgpai22/ergo-synced-node

you do realise sanostee is on about ltc.

i am having the same issue except mine says waiting on daemons coming online. i see it throwing get info req to the wallet no issue. password changed to a wrong password wallet reports there is a password issue. 3 seperate ltc based clones all using legacy daemon setup and ltc using standard and not one of them "comes online" despite running explorers on them no issue. so its not the wallets. and they have been in full sync for 48 hours and miningcore was running for the whole time and still "waiting on daemons coming online" seems this is a common issue and dev and helpers instant is "its not synced" without even noticing its different coins being reported and throw a link to a dead thread/monero issues which isnt the same for ltc/btc based coins and the other "search the issues" brings nothing up other than unanswered issues other than the above multiple answers. its just not working.shame really as i used to like this when i ran it when coin foundary did it it actually worked.

and as a foot note i spent 2 days going in circles roung the "its same as this issue #1241515 that references another one that references the first that circles around. and i looked over all 26 pages of issues and through all discussions, other than monero ones that were user error i think your getting mixed up due to it being the same error message and not the actual error being different as the debug is not verbose enough even on full log. it never reports wrong credentials. or anything thats usefull just "waiting....."

i would open a new issue however answer will be
"dont open issues for your own stupidity" "your wallet isnt synced" and "its not an issue with the code see issue #235235" or lastly "dont make a new thread see this discussion http://nonexistantthread.gone/forever

[MiningCryptoLive]

If it still says waiting on daemons you are either not synced or have the wrong port for the daemon in the config file. Miningcore works fine. I have found that ergo requires a large amount of ram to sync properly. I dedicated 8gb of ram for initial sync. Then dropped it back to 4gb and the pool operates fine. Stays synced and funds blocks

…

On Thu, Nov 17, 2022, 5:51 PM regtable ***@***.***> wrote: @Sanostee <https://github.com/Sanostee> @idanzam <https://github.com/idanzam> Your node is not synced, https://github.com/ergoplatform/ergo/wiki/Set-up-a-full-node syncing an ergo node has issues. i've faced them as well. I've used this resource to sync my node https://github.com/mgpai22/ergo-synced-node you do realise sanostee is on about ltc. i am having the same issue except mine says waiting on daemons coming online. i see it throwing get info req to the wallet no issue. password changed to a wrong password wallet reports there is a password issue. 3 seperate ltc based clones all using legacy daemon setup and ltc using standard and not one of them "comes online" despite running explorers on them no issue. so its not the wallets. and they have been in full sync for 48 hours and miningcore was running for the whole time and still "waiting on daemons coming online" seems this is a common issue and dev and helpers instant is "its not synced" without even noticing its different coins being reported and throw a link to a dead thread/monero issues which isnt the same for ltc/btc based coins and the other "search the issues" brings nothing up other than unanswered issues other than the above multiple answers. its just not working.shame really as i used to like this when i ran it when coin foundary did it it actually worked. — Reply to this email directly, view it on GitHub <#1456 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAIAKRXFQXAAGBVXGMFDG6DWI2ZHRANCNFSM6AAAAAAQ6Z3PDY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[regtable]

sure hope thats not a reply to me. as its doing same with ltc in full sync which i can run coiniumserv mpos nomp and yiimp fine. and as described its throwing things into the log so ports passwords and credentials are fine. this things real finniky for some reason

[idanzam]

my node is full sync bro
I also have coin-qt and its all good and sync ....
also for sync in coind....

so the issue come from some config wrong at minincore.