Where is pool for sha256?
https://bitcointalksearch.org/topic/m.15541111
Topic: [ANN][ARG] Argentum || A New Begining || UPDATE YOUR WALLET || - page 26. (Read 59642 times)
Where is pool for sha256?
We are now merge-mining Argentum at the Prohashing scrypt mining pool. Everything seems to be working great!
What version are they using? I tried with v2.1 but still had the same auxpow errors with sha256d.....
We are now merge-mining Argentum at the Prohashing scrypt mining pool. Everything seems to be working great!
I've receive confirmation that Cryptopia's Argentum wallet is now fully synced and back online.
If you need any testers for the auxpow release, let me know.
We've push a minor update to fix the Blockchain getting stuck while syncing. It should also speed up the initial download of the Blockchain significantly. Just do a simple clone and build and you'll be good to go. This version is marked 2.1 and is not mandatory, unless of course, you cannot download the Blockchain. There is not currently a windows qt wallet for this version.
Expect a windows QT wallet update to 2.2 once the difficulty and AUXPOW problem is fixed. The fix is currently under peer review and testing. It is believed to be an RPC issue, and not a core issue. Thanks for your patience all.
https://github.com/Cryptcollector/ARG2.0
Expect a windows QT wallet update to 2.2 once the difficulty and AUXPOW problem is fixed. The fix is currently under peer review and testing. It is believed to be an RPC issue, and not a core issue. Thanks for your patience all.
https://github.com/Cryptcollector/ARG2.0
Noted, thank you.
All pools are scrypt at OP. Has this project failed?
We're in the process of figuring out what is wrong with the difficulty adjustment and an AUXPOW error IconFirm is getting. The SHA256 pool will be back up once it is sorted out.
Any progress on this problem?
Do you have logs you can provide (aside from what you already posted)
Nothing any different from the ones I've posted, reams & reams of those though. I had to stop the client because it was flooding my logs & console with the same error & causing rejects on my node I'm afraid.
All pools are scrypt at OP. Has this project failed?
We're in the process of figuring out what is wrong with the difficulty adjustment and an AUXPOW error IconFirm is getting. The SHA256 pool will be back up once it is sorted out.
Any progress on this problem?
Do you have logs you can provide (aside from what you already posted)
All pools are scrypt at OP. Has this project failed?
We're in the process of figuring out what is wrong with the difficulty adjustment and an AUXPOW error IconFirm is getting. The SHA256 pool will be back up once it is sorted out.
Any progress on this problem?
All pools are scrypt at OP. Has this project failed?
We're in the process of figuring out what is wrong with the difficulty adjustment and an AUXPOW error IconFirm is getting. The SHA256 pool will be back up once it is sorted out.
All pools are scrypt at OP. Has this project failed?
Hmmm...seems I spoke too soon, I'm still getting all rejected work:
I'm running a private p2pool node.
Code:
2016-07-10 19:33:39 ERROR: AUX POW parent hash f5a6e007ebd8c8646b73f73f267bcf700805044970686b9686969f69838ff2ce is not under target 00000000000511bf000000000000000000000000000000000000000000000000
2016-07-10 19:33:46 ERROR: AUX POW parent hash 381f4b8a55cd93dd25e6f8c40727f5fad08fb2f058580c6688fb1bcf1176e45b is not under target 00000000000511bf000000000000000000000000000000000000000000000000
I'm running a private p2pool node.
Our dev is investigating.
Hmmm...seems I spoke too soon, I'm still getting all rejected work:
I'm running a private p2pool node.
Code:
2016-07-10 19:33:39 ERROR: AUX POW parent hash f5a6e007ebd8c8646b73f73f267bcf700805044970686b9686969f69838ff2ce is not under target 00000000000511bf000000000000000000000000000000000000000000000000
2016-07-10 19:33:46 ERROR: AUX POW parent hash 381f4b8a55cd93dd25e6f8c40727f5fad08fb2f058580c6688fb1bcf1176e45b is not under target 00000000000511bf000000000000000000000000000000000000000000000000
I'm running a private p2pool node.
I believe the correct switch for sha is algo=sha256d
According to the readme here:
https://github.com/Cryptcollector/ARG2.0/blob/849ea4b82f2db6442f899305f26225c966760fdd/README.md
..the correct syntax for the conf file is "algo=sha256" (without the "d")
I checked my debug file, when I use algo=sha256d I get this message "Deviating from Scrypt, now on SHA256d"
So I think it's sha256d
I take it you got it working? (The difficulty is way up now.)
Yes - success!!
If dev could correct the error on the github readme asap, that would save others having the same problems as me.
Thanks for that info - thought I was going mad!
Sorry about that :\
Do you have a pool you would like to post here?
Are you mining sha only, or both? I'm seeing issues with difficulty. Looks like sha and scrypt are the same. Anyone else?
I believe the correct switch for sha is algo=sha256d
According to the readme here:
https://github.com/Cryptcollector/ARG2.0/blob/849ea4b82f2db6442f899305f26225c966760fdd/README.md
..the correct syntax for the conf file is "algo=sha256" (without the "d")
I checked my debug file, when I use algo=sha256d I get this message "Deviating from Scrypt, now on SHA256d"
So I think it's sha256d
I take it you got it working? (The difficulty is way up now.)
Yes - success!!
If dev could correct the error on the github readme asap, that would save others having the same problems as me.
Thanks for that info - thought I was going mad!
I believe the correct switch for sha is algo=sha256d
According to the readme here:
https://github.com/Cryptcollector/ARG2.0/blob/849ea4b82f2db6442f899305f26225c966760fdd/README.md
..the correct syntax for the conf file is "algo=sha256" (without the "d")
I checked my debug file, when I use algo=sha256d I get this message "Deviating from Scrypt, now on SHA256d"
So I think it's sha256d
I take it you got it working? (The difficulty is way up now.)
I believe the correct switch for sha is algo=sha256d
According to the readme here:
https://github.com/Cryptcollector/ARG2.0/blob/849ea4b82f2db6442f899305f26225c966760fdd/README.md
..the correct syntax for the conf file is "algo=sha256" (without the "d")
I checked my debug file, when I use algo=sha256d I get this message "Deviating from Scrypt, now on SHA256d"
So I think it's sha256d
I believe the correct switch for sha is algo=sha256d
According to the readme here:
https://github.com/Cryptcollector/ARG2.0/blob/849ea4b82f2db6442f899305f26225c966760fdd/README.md
..the correct syntax for the conf file is "algo=sha256" (without the "d")
Jump to: