[ANN][ARG] Argentum || A New Begining || UPDATE YOUR WALLET ||

[mrbodz]

Whats the argentum chain id? 0?

Ahmed

EDIT: nvm

[1715221698]

1715221698

[1715221698]

1715221698

[1715221698]

1715221698

[1715221698]

1715221698

[protonn]

Less than 24 hours until the fork.

Last chance to upgrade to 2.0, please do it if you haven't already.

Be sure to vote at Slushpool https://slushpool.com/proposal/detail/572/

http://www.litecoinpool.org is set to merge mine.

I believe http://www.clevermining.com is as well, but I haven't received confirmation.

[cryptcollector]

almost there...

[protonn]

I've received correspondence from Multipool.us stating they will add Argentum at a future date, during their next round of additions.

Cryptopia.co.nz is still having issues

Coinexchange.io is working fine.

Let's hope for a smooth transition @1,825,000

[protonn]

I believe the correct switch for sha is algo=sha256d

Is anyone having trouble with sha?

[IconFirm]

I'm struggling with merge mining ARG with p2pool, all merged work is rejected with the following error:

Code:

2016-07-10 18:00:30 ERROR: AUX POW parent hash f42eaa0baaeeaf27df2f30bdfacaf8e8b04ecf2db0caadb96037b16c403a8a9d is not under target 000000002fe70400000000000000000000000000000000000000000000000000
2016-07-10 18:00:30 ERROR: AUX POW parent hash 65bdf98bae5978e3521407449255b6324c99c6093dd9665bf1f12252ff71be6a is not under target 000000002fe70400000000000000000000000000000000000000000000000000
2016-07-10 18:00:30 ERROR: AUX POW parent hash 2e1da9f5ebc0cf163eae74afe836d2e51f083a6c24a422ec8cc16a0aed583808 is not under target 000000002fe70400000000000000000000000000000000000000000000000000
2016-07-10 18:00:30 ERROR: AUX POW parent hash c0ddb3cd6a28e4804cf752124e93ee77dac9d573572ba3bd7df5b27422b8d14c is not under target 000000002fe70400000000000000000000000000000000000000000000000000
2016-07-10 18:00:30 ERROR: AUX POW parent hash 92289598e81d5af2ecc50173b870c25469d92a64c4a96c37526768cbbf90a20c is not under target 000000002fe70400000000000000000000000000000000000000000000000000
2016-07-10 18:00:30 ERROR: AUX POW parent hash 49d5f051ef7d65596333720732be2e5bbbf316d4dc8210f5b1d44d39fd7e628e is not under target 000000002fe70400000000000000000000000000000000000000000000000000
2016-07-10 18:00:30 ERROR: AUX POW parent hash 0561f9cfa8ebc47c2a5fd438c80d203f6639c9ea1e85235ae1cf814790cdef35 is not under target 000000002fe70400000000000000000000000000000000000000000000000000
2016-07-10 18:00:30 ERROR: AUX POW parent hash 66f7f05af520f843c41e18d230f73c4f97a4e48cd2b778c554cb6581d64bec2d is not under target 000000002fe70400000000000000000000000000000000000000000000000000
2016-07-10 18:00:30 ERROR: AUX POW parent hash f7defb1a9359c1ea292d1c3f065ca0ef48d5687c6539ecb04ba0d91b8e280e02 is not under target 000000002fe70400000000000000000000000000000000000000000000000000
2016-07-10 18:00:30 ERROR: AUX POW parent hash 31f9e83fdadfc7ab0b7c2ad8a9a9a839fe9368b23a70dbb90764eda834538655 is not under target 000000002fe70400000000000000000000000000000000000000000000000000
2016-07-10 18:00:30 ERROR: AUX POW parent hash 40aa8ca7e0be6393d9186eaaac71fde13779c99973cbc8bda43ae6e45057355c is not under target 000000002fe70400000000000000000000000000000000000000000000000000
2016-07-10 18:00:30 ERROR: AUX POW parent hash 1b2bf6ff21f4e4513935d4febeac81dfb6c8e7d9413d747927972589c54dfaf5 is not under target 000000002fe70400000000000000000000000000000000000000000000000000
2016-07-10 18:00:30 ERROR: AUX POW parent hash bc71689d2d7c888eb8b0273b8e5affa0f7034994703e94a4472224a10222c2ca is not under target 000000002fe70400000000000000000000000000000000000000000000000000
2016-07-10 18:00:30 ERROR: AUX POW parent hash d1952c19441daed1bdc7de6e2b5e0ee1dff4c309e7864a55b5fee6edddb1cb4a is not under target 000000002fe70400000000000000000000000000000000000000000000000000
2016-07-10 18:00:31 ERROR: AUX POW parent hash e6a0fcad27c40934f82a4dbfeeab3483fe99bc3c70be948d362b548374ba3b15 is not under target 000000002fe70400000000000000000000000000000000000000000000000000
2016-07-10 18:00:31 ERROR: AUX POW parent hash b6b4e3aba3cca7baafe1ddb0a63a3789e1a7b5be202beb207563357d2c781ddb is not under target 000000002fe70400000000000000000000000000000000000000000000000000
2016-07-10 18:00:31 ERROR: AUX POW parent hash fa1855530f729a0ac163669dcf5eaee7399a5ba9144732ef9f763f8193d20bcc is not under target 000000002fe70400000000000000000000000000000000000000000000000000
2016-07-10 18:00:31 ERROR: AUX POW parent hash 3472a5820f42b6fb66f82b4799fae95f7f01c29784f008b357f911fd709e8371 is not under target 000000002fe70400000000000000000000000000000000000000000000000000
2016-07-10 18:00:31 ERROR: AUX POW parent hash 306bac01c08eca0889076adaba7851cbbf92f4f0b7e48337a089c0eaf888194f is not under target 000000002fe70400000000000000000000000000000000000000000000000000
2016-07-10 18:00:31 ERROR: AUX POW parent hash 6586b64912370027f44d32342615367a25e147f0995d0aecebb8b2fca2125967 is not under target 000000002fe70400000000000000000000000000000000000000000000000000
2016-07-10 18:00:31 ERROR: AUX POW parent hash 6d82ffd6f5e90e85defc012a02c036dec13f8d6926e7d4000d2adf0a5df400df is not under target 000000002fe70400000000000000000000000000000000000000000000000000
2016-07-10 18:00:31 ERROR: AUX POW parent hash bc1467477db009459f8bfd9e2c24ca8f0bbed02a5ace3131d725cb98910ebb4b is not under target 000000002fe70400000000000000000000000000000000000000000000000000
2016-07-10 18:00:31 ERROR: AUX POW parent hash 1dce2b4b754537f3bd4ee5b17998de94e9574d62fa5e2ff46a5a197dc5fd2e8c is not under target 000000002fe70400000000000000000000000000000000000000000000000000
2016-07-10 18:00:31 ERROR: AUX POW parent hash 5623acb298c8a1abce9d2474460c12d75d05820e30b15d3bd7ccb6c82cad9b0b is not under target 000000002fe70400000000000000000000000000000000000000000000000000
2016-07-10 18:00:31 ERROR: AUX POW parent hash 0f0798e364fc932cef0988933026ddcb3b164f62abf06822b74b4df5d743a077 is not under target 000000002fe70400000000000000000000000000000000000000000000000000
2016-07-10 18:00:31 ERROR: AUX POW parent hash a7b891b3a758b3de16ac3fad853a2022aef92f16eb8e5096f7bdae9df6cd3078 is not under target 000000002fe70400000000000000000000000000000000000000000000000000
2016-07-10 18:00:31 ERROR: AUX POW parent hash 884a49d1a7049275313d607e2d01a3720e5ad4e6925a49eb9c5da3efc40b7b14 is not under target 000000002fe70400000000000000000000000000000000000000000000000000
2016-07-10 18:00:31 ERROR: AUX POW parent hash 60879918ad65ac7df37a905a196d2e7d8adce782fd8b18b5b7e79af0c026a248 is not under target 000000002fe70400000000000000000000000000000000000000000000000000
2016-07-10 18:00:31 ERROR: AUX POW parent hash 8d93ad706e146a863381a91f8e04bfde3843198702b5a50fdae3a748f202ecc1 is not under target 000000002fe70400000000000000000000000000000000000000000000000000
2016-07-10 18:00:31 ERROR: AUX POW parent hash 953ec6f987abe56d39f5781d097109f8e9be34136724595625ad2cbdfcb9d19a is not under target 000000002fe70400000000000000000000000000000000000000000000000000

...difficulty does not seem to be rising either, which tells me merge mining doesn't seem to be working correctly?

Edit: From my p2pool console:

Code:

2016-07-10 19:30:59.478912 > Merged block submittal result: False Expected: True
2016-07-10 19:30:59.535919 > Merged block submittal result: False Expected: True
2016-07-10 19:30:59.591851 > Merged block submittal result: False Expected: True
2016-07-10 19:30:59.646016 > Merged block submittal result: False Expected: True
2016-07-10 19:30:59.794424 > Merged block submittal result: False Expected: True
2016-07-10 19:30:59.853775 > Merged block submittal result: False Expected: True
2016-07-10 19:30:59.909303 > Merged block submittal result: False Expected: True
2016-07-10 19:30:59.981168 > Merged block submittal result: False Expected: True
2016-07-10 19:31:00.203761 > Merged block submittal result: False Expected: True
2016-07-10 19:31:00.328549 > Merged block submittal result: False Expected: True
2016-07-10 19:31:00.557721 > Merged block submittal result: False Expected: True
2016-07-10 19:31:00.615623 > Merged block submittal result: False Expected: True
2016-07-10 19:31:00.667747 > Merged block submittal result: False Expected: True
2016-07-10 19:31:00.754704 > Merged block submittal result: False Expected: True
2016-07-10 19:31:00.812586 > Merged block submittal result: False Expected: True
2016-07-10 19:31:00.868804 > Merged block submittal result: False Expected: True
2016-07-10 19:31:00.952767 > Merged block submittal result: False Expected: True
2016-07-10 19:31:01.012157 > Merged block submittal result: False Expected: True
2016-07-10 19:31:01.067966 > Merged block submittal result: False Expected: True
2016-07-10 19:31:01.330743 > Merged block submittal result: False Expected: True
2016-07-10 19:31:01.388443 > Merged block submittal result: False Expected: True
2016-07-10 19:31:01.449058 > Merged block submittal result: False Expected: True
2016-07-10 19:31:01.504785 > Merged block submittal result: False Expected: True
2016-07-10 19:31:01.563900 > Merged block submittal result: False Expected: True
2016-07-10 19:31:01.618328 > Merged block submittal result: False Expected: True
2016-07-10 19:31:01.701129 > Merged block submittal result: False Expected: True
2016-07-10 19:31:01.707837 > Merged block submittal result: False Expected: True
2016-07-10 19:31:01.758415 > Merged block submittal result: False Expected: True
2016-07-10 19:31:01.817245 > Merged block submittal result: False Expected: True
2016-07-10 19:31:01.876255 > Merged block submittal result: False Expected: True
2016-07-10 19:31:01.934541 > Merged block submittal result: False Expected: True

All ARG work rejected.

[IconFirm]

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")

[protonn]

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

[protonn]

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.)

[IconFirm]

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! 

[protonn]

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?

[IconFirm]

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.

[protonn]

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.

[Mohareb]

All pools are scrypt at OP. Has this project failed?

[protonn]

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.

[IconFirm]

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?

[protonn]

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)

[IconFirm]

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.

[protonn]

Noted, thank you.

[protonn]

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