Pages:
Author

Topic: [ANN][ARG] Argentum || A New Begining || UPDATE YOUR WALLET || - page 26. (Read 59759 times)

hero member
Activity: 521
Merit: 500
full member
Activity: 248
Merit: 100
2.2 is now live. Please download asap. The new target for full functionality is 1,840,000. There might be a few issues with things until then, but the blockchain will keep moving.

https://github.com/Cryptcollector/ARG2.0
full member
Activity: 194
Merit: 100
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're running version 2000000.  I can't confirm how SHA-256 works though.
hero member
Activity: 1438
Merit: 574
Always ask questions. #StandWithHongKong
full member
Activity: 126
Merit: 100
Where is pool for sha256?
hero member
Activity: 1438
Merit: 574
Always ask questions. #StandWithHongKong
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.....
full member
Activity: 194
Merit: 100
We are now merge-mining Argentum at the Prohashing scrypt mining pool.  Everything seems to be working great!
full member
Activity: 248
Merit: 100
I've receive confirmation that Cryptopia's Argentum wallet is now fully synced and back online.
hero member
Activity: 1438
Merit: 574
Always ask questions. #StandWithHongKong
If you need any testers for the auxpow release, let me know.
full member
Activity: 248
Merit: 100
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
full member
Activity: 248
Merit: 100
Noted, thank you.
hero member
Activity: 1438
Merit: 574
Always ask questions. #StandWithHongKong
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.
full member
Activity: 248
Merit: 100
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)
hero member
Activity: 1438
Merit: 574
Always ask questions. #StandWithHongKong
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?
full member
Activity: 248
Merit: 100
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.
full member
Activity: 224
Merit: 100
All pools are scrypt at OP. Has this project failed?
full member
Activity: 248
Merit: 100
Hmmm...seems I spoke too soon, I'm still getting all rejected work:

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.
hero member
Activity: 1438
Merit: 574
Always ask questions. #StandWithHongKong
Hmmm...seems I spoke too soon, I'm still getting all rejected work:

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.
full member
Activity: 248
Merit: 100
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!  Tongue

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?
hero member
Activity: 1438
Merit: 574
Always ask questions. #StandWithHongKong
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!  Tongue
Pages:
Jump to: