Reduce Ergo confirmations

[hjonathan2019]

hello... I found an answer from @oliverw that said the following:

"pools": [
{
"id": "ergo",
"paymentprocessing": {
"minimumConfirmations": 70
}
}
]

so... should my json stay like this? (check if the { } placed are correct)

"pools": [
// Repeat the following section for multiple coins
{
// DON'T change the id after a production pool has begun collecting shares!
"id": "MYIDHERE",
"paymentprocessing": {
"minimumConfirmations": 70
}
"enabled": true,
"coin": "ergo",
// Address to where block rewards are given (pool wallet)
"address": "MY WALLET",
// Max Active Jobs
"maxActiveJobs": 20,
// 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": [

[jvxis]

Hi, @hjonathan2019 I'm using "minimunConfimations": 720

[hjonathan2019]

ok, but How many people entered miningcore for being free and then went to pro? github has a lot to do with it. (i think)

[hjonathan2019]

well.. i put it here

hope it works

[hjonathan2019]

well.. i put it here

hope it works

anyone can confirm this?

[oliverw]

That looks fine.

[hjonathan2019]

That looks fine.

awesome @oliverw . thank you very very much for your time