Any update coming for ergo soon #895
Replies: 10 comments 33 replies
-
Look carefully if you are familiar with node ergo, you will understand that only the algorithm is added and that's it. |
Beta Was this translation helpful? Give feedback.
-
|
i am familiar with ergo node... but not sure where you are referring the algo is added.. please clarify |
Beta Was this translation helpful? Give feedback.
-
|
Ergo is fully implemented in a private build for a client that requested a period of semi-exclusive access (means CF can use it as well). The implementation will be merged into the main repository in a couple weeks. |
Beta Was this translation helpful? Give feedback.
-
There isn't really anything special about Ergo. |
Beta Was this translation helpful? Give feedback.
-
Understood, in this case what (which coin) could I use as a reference then for that coin to build? |
Beta Was this translation helpful? Give feedback.
-
I'd say any of the non multi-algo Bitcoin members with
|
Beta Was this translation helpful? Give feedback.
-
Thank you @oliverw again for assistance, I appreciate it. Excuse my ignorance but could you please elaborate "non multi-algo BTC members" for me? Lastly for the sake of this thread, would VTC or BTG be a good sample for ERGO? |
Beta Was this translation helpful? Give feedback.
-
BTC based multi-algo coins are DGB and XVG. VTC should be fine. |
Beta Was this translation helpful? Give feedback.
-
|
So we are building private stuff now??? |
Beta Was this translation helpful? Give feedback.
-
|
Yes. |
Beta Was this translation helpful? Give feedback.
-
|
That's not Kool...... |
Beta Was this translation helpful? Give feedback.
-
|
this is how i started the docker app in the beginning
sudo docker run -d \ -p 9030:9030 \ -p 127.0.0.1:9053:9053 \ -v /home/def/ergo/.ergo \ -v /home/def/ergo/myergo.conf \ -e MAX_HEAP=3G \ ergoplatform/ergo:v4.0.13 --mainnet -c /home/def/ergo/myergo.conf
thanks for reaching outDon Kingdon
On Wednesday, September 22, 2021, 06:22:03 p.m. EDT, Calvin Tam ***@***.***> wrote:
can you share your docker command? it isbl likely you forgot to open the port/misconfig listen ip from miningcore conf
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
|
Beta Was this translation helpful? Give feedback.
-
|
i don’t think you can use 127.0.0.1:9053. it refers to the 127.0.0.1 inside container. you should have reverse proxy to allow open ports (9030) to pass through and block all open ports in firewall. |
Beta Was this translation helpful? Give feedback.
-
|
ok i got the node working and its almost done syncing. miningcore seems to be starting correctly - is there a further frontend that is needed or ? Im not seeing anything familiar for the generation of a webpage. Sorry if its a noob question - i am just starting with miningcore - previous experince with open-ethereum-pool using the full node install - not docker in this build |
Beta Was this translation helpful? Give feedback.
-
|
Any chance to have an example of ergo.conf file ? |
Beta Was this translation helpful? Give feedback.
-
|
Everything is well documented. |
Beta Was this translation helpful? Give feedback.
-
|
thanks so much for the totally useful comment - it helped a lot |
Beta Was this translation helpful? Give feedback.
-
|
ok - im gonna build another vm this weekend and try again. Ill give that a try - but that was a docker startup line i had found in the forum i believe. im starting to feel slightly retarded with this node failing to work over and over. starting to remind me of my first days with open-ethereum-pool
Don Kingdon
On Thursday, September 23, 2021, 12:10:27 a.m. EDT, Calvin Tam ***@***.***> wrote:
i don’t think you can use 127.0.0.1:9053. it refers to the 127.0.0.1 inside container. you should have reverse proxy to allow open ports (9030) to pass through and block all open ports in firewall.
|
Beta Was this translation helpful? Give feedback.
-
|
I have tried this:sudo docker run -d \ -p 9030:9030 \ -p 127.0.0.1:9053:9053 \ -v /home/def/ergo/.ergo \ -v /home/def/ergo/myergo.conf \ -e MAX_HEAP=3G \ ergoplatform/ergo:v4.0.13 --mainnet -c /home/def/ergo/myergo.conf
this successfully starts node and api but i dont know how to adjust the config file after setting the APIkey.
with regular node - this fails:
ergo { directory = ${ergo.directory}"/.ergo" node { mining = false } wallet.secretStorage.secretDir = ${ergo.directory}"/wallet/keystore"}
this also fails with regular node:
ergo { node { mining = true }}
scorex { restApi { # Hex-encoded Blake2b256 hash of an API key. # Should be 64-chars long Base16 string. # below is the hash of the string 'hello' # replace with your actual hash apiKeyHash = "0afa48bb51c2b3c8f9f090922a020a32f244968bda9e7fefeffa68ee3558c584" }}
|
Beta Was this translation helpful? Give feedback.
-
|
Here's an example pool config: {
"id": "ergo",
"enabled": true,
"coin": "ergo",
"address": "9foYU8JkoqWBSDA3ba8VHfduPXV2NaVNPPAFkdYoR9t9cPQGMv4",
"maxActiveJobs": 20,
"blockRefreshInterval": 1000,
"jobRebroadcastTimeout": 50,
"clientConnectionTimeout": 600,
"rewardRecipients": [
{
"address": "9foYU8JkoqWBSDA3ba8VHfduPXV2NaVNPPAFkdYoR9t9cPQGMv4",
"percentage": 0.5
}
],
"banning": {
"enabled": true,
"time": 180,
"invalidPercent": 90,
"checkThreshold": 150
},
"ports": {
"3194": {
"listenAddress": "0.0.0.0",
"difficulty": 0.1,
"name": "GPU Mining",
"varDiff": {
"minDiff": 0.01,
"targetTime": 15,
"retargetTime": 90,
"variancePercent": 30,
"maxDelta": 0.1
}
}
},
"daemons": [
{
"host": "localhost",
"port": 9052,
"apiKey": "foobar"
}
],
"paymentProcessing": {
"enabled": true,
"walletPassword": "barfoo",
"minimumPayment": 0.05,
"payoutScheme": "PPLNS",
"payoutSchemeConfig": {
"factor": 1.0
}
}
}
|
Beta Was this translation helpful? Give feedback.
-
|
@oliverw thank You I appreciate. So it seems that "apikey" and "walletPassword" are the missing pieces or not matching VTC config as it was suggested to use. PS. is the apikey looking for the hash or actual string? I would assume hash since looking at ergo.conf?! |
Beta Was this translation helpful? Give feedback.
-
Actual unhashed value. |
Beta Was this translation helpful? Give feedback.
-
|
@oliverw one more thing, ergo node default mining port is 9030 where 9053 is to access swagger/api. Your example showing 9052 which is closer to the api backend. Can you confirm which port MC requires (swagger or mining)? java 875 ergoadmin 13u IPv6 29094 0t0 TCP *:9030 (LISTEN) |
Beta Was this translation helpful? Give feedback.
-
|
@oliverw may I ask how is the integer in difficulty parameter corresponds to memory size? i.e if you want to allow 4gb and up what would the difficulty look like?! "difficulty": 0.1, |
Beta Was this translation helpful? Give feedback.
-
Anyone knows? |
Beta Was this translation helpful? Give feedback.
-
I would love to see a update for ergo... Any plans in the works?
Beta Was this translation helpful? Give feedback.
All reactions