[ANN][ANC] Anoncoin (anoncoin.net) | Privacy-centric currency | I2P darknet

[Cryptoslave]

Running the latest wallet synced to the same block as https://prohashing.com/explorer/Anoncoin but my wallet is reporting 0.00000135 difficulty?

Since I update to v0.9.6.11-eaf7af2 I am seeing the same thing for all the blocks.

getmininginfo
{
"blocks" : 538434,
"currentblocksize" : 0,
"currentblocktx" : 0,
"difficulty" : 0.00000135,
"errors" : "This is a HARDFORK build for block 555555",
"genproclimit" : -1,
"networkhashps" : 3302921396,
"pooledtx" : 1,
"chain" : "main",
"generate" : false
}

Hi,

Yes that is right. The difficulty displayed is a difficulty number between 0 and 1, relative to the minimum difficulty equal to 1, which becomes more difficult the smaller it is.

Code:

00:28:14

help getdifficulty


00:28:14

getdifficulty

Returns the proof-of-work required difficulty now at the tip of the block chain.

Result:
n.nnn (numeric) The minimum difficulty is defined as 1 and this result is linear relative to that value.
Smaller values indicate harder, larger an easier difficulty and all blocks will have a value < 1.

Examples:
> anoncoin-cli getdifficulty 
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getdifficulty", "params": [] }' -H 'content-type: text/plain;' http://127.0.0.1:9376/

You can see it changing from block to block too, obviously.

Code:

00:09:03

getchaintips


00:09:04

[
{
"height" : 538504,
"hash" : "0000000000d929ff1592eb4adecb1d1e9d733510a3e984c995be35108903ab7e",
"shad" : "b0201d1fe8e462f6a6ed56090d9974435357bc14d79149065b623a3eba12a266",
"branchlen" : 0,
"status" : "active"
}
]


00:09:06

getdifficulty


00:09:06

0.00000135



00:17:59

getdifficulty


00:17:59

0.00000139

If you run cgminer against anoncoin you will see the difficulty moving in the reverse way, in this case the higher it is the more difficult it is. Cgminer made his own interpretation of the block difficulty, which did not change between the wallet version.

Code:

Connected to 127.0.0.1 diff 11.8M without LP as user Cryptoslave
Block: b381edee13ef64ef...  Diff:11.8M Started: [00:13:58]  Best share: 13

 [2016-06-01 00:22:53] Network diff set to 11.5M
 [2016-06-01 00:22:53] New block detected on network
 [2016-06-01 00:23:21] Network diff set to 11.8M
 [2016-06-01 00:23:21] New block detected on network

The old wallet displayed the difficulty as a number which was a multiple of the minimum difficulty. That is why you cannot directly tell what difficulty relates to the old wallet difficulty for the user, as they are displayed differently, but the difficulty algorithms (Kimoto Gravity Well v2 and GroundRod Retarget PID) understand the difficulty very well, as the proof-of-work required difficulty algorithm did not change between KGW v1 and KGW v2. But after block 555555 with the change of the difficulty algorithm to GroundRod PID, the way the proof-of-work required is calculated will change and this is the reason why this is an hardfork.
In truth the PID Difficulty is a number of 256 bits such as 0x00000000010a2d19999999999999999999999999999999999999999999999999, and the PID use this number as it is, but the displayed number by getdifficulty was simplified as shown above.

[Conqueror]

New wallet is great, thanks for all the work on it!

[hananl1styo]

translation for indonesian

https://bitcointalk.org/index.php?topic=1500646.0

[Tommo_Aus]

Running the latest wallet synced to the same block as https://prohashing.com/explorer/Anoncoin but my wallet is reporting 0.00000135 difficulty?

Since I update to v0.9.6.11-eaf7af2 I am seeing the same thing for all the blocks.

getmininginfo
{
"blocks" : 538434,
"currentblocksize" : 0,
"currentblocktx" : 0,
"difficulty" : 0.00000135,
"errors" : "This is a HARDFORK build for block 555555",
"genproclimit" : -1,
"networkhashps" : 3302921396,
"pooledtx" : 1,
"chain" : "main",
"generate" : false
}

Hi,

Yes that is right. The difficulty displayed is a difficulty number between 0 and 1, relative to the minimum difficulty equal to 1, which becomes more difficult the smaller it is.

So after block 555 555 we'll see the standard difficulty number or will it still be between 0 and 1? How do we get a comparable scrypt difficulty?

[shojayxt]

People need to learn how to read the ANN.  It really isn't that hard and the answers to these questions are there.

supply? wallet? ico?

ICO?

[MickyCOB]

New wallet looks great   

[Cryptoslave]

So after block 555 555 we'll see the standard difficulty number or will it still be between 0 and 1? How do we get a comparable scrypt difficulty?

The standard difficulty will from now on be always between 1 and 0. This is what the PID is programmed to use, and is the target requested by the block at the tip.
1 is the lowest difficulty.
The more leading zero there is after the decimal separator, the more difficult it is to find a block.
The lower the significant figure, at constant number of leading zero, the more difficult it is.
Difficulty zero will never happen, but could be displayed if hashrate reach thousands of GH/s, because in fact the difficulty as displayed by getdifficulty is just a troncated representation of the minimum hexadecimal target to find the block at the tip of the chain, which is a 256 bit number.

I am sure people will get habituated, meanwhile just use the reciprocal, ie 1/difficulty to get an idea.

Otherwise, your miner program will display the difficulty in the reciprocal format.

[Tommo_Aus]

So after block 555 555 we'll see the standard difficulty number or will it still be between 0 and 1? How do we get a comparable scrypt difficulty?

The standard difficulty will from now on be always between 1 and 0. This is what the PID is programmed to use, and is the target requested by the block at the tip.
1 is the lowest difficulty.
The more leading zero there is after the decimal separator, the more difficult it is to find a block.
The lower the significant figure, at constant number of leading zero, the more difficult it is.
Difficulty zero will never happen, but could be displayed if hashrate reach thousands of GH/s, because in fact the difficulty as displayed by getdifficulty is just a troncated representation of the minimum hexadecimal target to find the block at the tip of the chain, which is a 256 bit number.

I am sure people will get habituated, meanwhile just use the reciprocal, ie 1/difficulty to get an idea.

Otherwise, your miner program will display the difficulty in the reciprocal format.

Ok... so to compare ANC difficulty to other scrypt coins?

[Cryptoslave]

This is a Scrypt coin, obviously nothing was changed has to how much the hashrate and proof of work target are related to maintain the targetspacing for a typical average network hashrate.

If you want to use a value for your Scrypt multipool automatic switching to the most profitable coin, I leave it to yourself to calculate the best profitability vs other coin. All the difficulty values are in fact not comparable already, being different for different target spacing, and to use the reciprocal of anoncoin difficulty in your jumping script is not difficult. I will not help you further for that as we prefer to support the long term miner over multipools, and also because I do not see what issue you have in this.

So after block 555 555 we'll see the standard difficulty number or will it still be between 0 and 1? How do we get a comparable scrypt difficulty?

The standard difficulty will from now on be always between 1 and 0. This is what the PID is programmed to use, and is the target requested by the block at the tip.
1 is the lowest difficulty.
The more leading zero there is after the decimal separator, the more difficult it is to find a block.
The lower the significant figure, at constant number of leading zero, the more difficult it is.
Difficulty zero will never happen, but could be displayed if hashrate reach thousands of GH/s, because in fact the difficulty as displayed by getdifficulty is just a troncated representation of the minimum hexadecimal target to find the block at the tip of the chain, which is a 256 bit number.

I am sure people will get habituated, meanwhile just use the reciprocal, ie 1/difficulty to get an idea.

Otherwise, your miner program will display the difficulty in the reciprocal format.

Ok... so to compare ANC difficulty to other scrypt coins?

[Cryptoslave]

This is a Scrypt coin, obviously nothing was changed has to how much the hashrate and proof of work target are related to maintain the targetspacing for a typical average network hashrate.

If you want to use a value for your Scrypt multipool automatic switching to the most profitable coin, I leave it to yourself to calculate the best profitability vs other coin. All the difficulty values are in fact not comparable already, being different for different target spacing, and to use the reciprocal of anoncoin difficulty in your jumping script is not difficult. I will not help you further for that as we prefer to support the long term miner over multipools, and also because I do not see what issue you have in this.

So after block 555 555 we'll see the standard difficulty number or will it still be between 0 and 1? How do we get a comparable scrypt difficulty?

The standard difficulty will from now on be always between 1 and 0. This is what the PID is programmed to use, and is the target requested by the block at the tip.
1 is the lowest difficulty.
The more leading zero there is after the decimal separator, the more difficult it is to find a block.
The lower the significant figure, at constant number of leading zero, the more difficult it is.
Difficulty zero will never happen, but could be displayed if hashrate reach thousands of GH/s, because in fact the difficulty as displayed by getdifficulty is just a troncated representation of the minimum hexadecimal target to find the block at the tip of the chain, which is a 256 bit number.

I am sure people will get habituated, meanwhile just use the reciprocal, ie 1/difficulty to get an idea.

Otherwise, your miner program will display the difficulty in the reciprocal format.

Ok... so to compare ANC difficulty to other scrypt coins?

OK I understood your question, which indeed was a meaningful question! Thank you to have asked it. 

The new command 'getnetworkhashps' is what you need to get the most accurate approximation.

Code:

02:59:18

help getnetworkhashps


02:59:18

getnetworkhashps [blocks] [height]

Returns the estimated network hashes per second, optionally for a given height and based on the last n blocks.

Arguments:
1. blocks (numeric, optional, default='tipfiltersize') Hint: The 'getretargetpid 1' query tells you the tip filters size.
2. height (numeric, optional, default=0) Default to current chain tip, or specify at what height the calculation is to be made.

NOTES: Block spacing is measured, so at least 2 blocks are needed to calculate one spacing interval, the more the better.
Pass in [height] to estimate the network speed at the time when a certain block was mined. Pass in [blocks] to override the # of
blocks used in the calculation, any value < 2 sets the min of 2 blocks. Expect a poor estimate, with so few.

Result:
(numeric) Estimated hashes per second, the calculation made is the chain work proofs (latest - oldest) / time delta.

Examples:
> anoncoin-cli getnetworkhashps 
> anoncoin-cli getnetworkhashps 200 350000
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getnetworkhashps", "params": [] }' -H 'content-type: text/plain;' http://127.0.0.1:9376/
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getnetworkhashps", "params": [5000,390000] }' -H 'content-type: text/plain;' http://127.0.0.1:9376/

By default, it use the tipfilter size which is 21 block, but then the value will fluctuate according to the time it took to find those 21 blocks as given by the TipsAvg. If you want to know on a broader timescale, you shall use at least 120 blocks, which is the last 6 hours average. You can see from the GroundRod PID graphs that both the TipsAvg and Difficulty value will be then precise enough for the calculation of the getnetworkhashps.

Code:

03:15:02

getnetworkhashps


03:15:02

3268971239


03:15:04

getnetworkhashps 21


03:15:04

3268971239


03:15:06

getnetworkhashps 2


03:15:06

393059443


03:15:10

getnetworkhashps 120


03:15:10

4120719633


03:15:16

getnetworkhashps 480


03:15:16

3780644272

The value of your hashrate, divided by the 'getnetworkhashps' value will be the most precise to know how much percentage blocks you shall get on a time period, especially after the PID is activated which shall render the mining much more stable on a several blocks time period than KGW.

[HPt]

Is there a working blockchain explorer for Anoncoin? (The blockchain explorers listed at https://wiki.anoncoin.net/Block_chain_explorers are either out of date or not available at all.)

[jwinterm]

Is there a working blockchain explorer for Anoncoin? (The blockchain explorers listed at https://wiki.anoncoin.net/Block_chain_explorers are either out of date or not available at all.)

There's at least a crappy one here:
https://www.cryptopia.co.nz/BlockExplorer?id=190

[Cryptoslave]

Is there a working blockchain explorer for Anoncoin? (The blockchain explorers listed at https://wiki.anoncoin.net/Block_chain_explorers are either out of date or not available at all.)

There's at least a crappy one here:
https://www.cryptopia.co.nz/BlockExplorer?id=190

We have updated the https://wiki.anoncoin.net/Block_chain_explorers page and have three working explorer now.

[geometric_series]

Great to see the new version wallet ,that means the dev is still working on this coin.

[smarterhash]

nodes please?

[CartmanSPC]

Thank you for putting the fork at least a month out...I don't follow every coin closely and only just now realized ANC was forking by chance from another thread (myriad). Hate it when coins decide to fork and only give a couple weeks notice. Now I got to get to work compiling the new version in Linux...tomorrow.

Edit: Compiled with no issues.

[manfred87]

so cryptopia is still on chain v0.8.5.1-132-g73a4219-beta, did you contact them?

The old wallet displayed the difficulty as a number which was a multiple of the minimum difficulty. That is why you cannot directly tell what difficulty relates to the old wallet difficulty for the user, as they are displayed differently, but the difficulty algorithms (Kimoto Gravity Well v2 and GroundRod Retarget PID) understand the difficulty very well, as the proof-of-work required difficulty algorithm did not change between KGW v1 and KGW v2. But after block 555555 with the change of the difficulty algorithm to GroundRod PID, the way the proof-of-work required is calculated will change and this is the reason why this is an hardfork.
In truth the PID Difficulty is a number of 256 bits such as 0x00000000010a2d19999999999999999999999999999999999999999999999999, and the PID use this number as it is, but the displayed number by getdifficulty was simplified as shown above.

so will pools have to change something after block 555555? ( will stratum difficulty change etc? )

nodes please?

-addnode=109.133.156.15:49362
-addnode=211.149.175.37:52736
-addnode=84.55.23.199:55863
-addnode=211.149.175.37:51950
-addnode=192.99.13.67:54869
-addnode=108.61.10.90:56562

[Cryptoslave]

so cryptopia is still on chain v0.8.5.1-132-g73a4219-beta, did you contact them?

Thank you for noticing, yes I contacted them again today and they are upgrading now.

The old wallet displayed the difficulty as a number which was a multiple of the minimum difficulty. That is why you cannot directly tell what difficulty relates to the old wallet difficulty for the user, as they are displayed differently, but the difficulty algorithms (Kimoto Gravity Well v2 and GroundRod Retarget PID) understand the difficulty very well, as the proof-of-work required difficulty algorithm did not change between KGW v1 and KGW v2. But after block 555555 with the change of the difficulty algorithm to GroundRod PID, the way the proof-of-work required is calculated will change and this is the reason why this is an hardfork.
In truth the PID Difficulty is a number of 256 bits such as 0x00000000010a2d19999999999999999999999999999999999999999999999999, and the PID use this number as it is, but the displayed number by getdifficulty was simplified as shown above.

so will pools have to change something after block 555555? ( will stratum difficulty change etc? )

Normally not, indeed as already stated the difficulty for miners is calculated on the nBits target. So no change has to be made.

A bit more info on the difficulty... You can see the new target by typing "getretargetpid" in the console

Code:

15:57:37

getretargetpid


15:57:37

{
"retargetheight" : 546970,
"allowmintime" : 1466256114,
"retargettime" : 1466258267,
"adjustedtime" : 1466258267,
"prevdiff" : "1c0240e1(231)",
"spacingerror" : "+52.7429(210)",
"rateofchange" : "-14.4158(190)",
"integratorheight" : 546969,
"integrationtime" : 172794,
"integratorblocks" : 974,
"proportionterm" : 89.66285966,
"integratorterm" : 167.94450154,
"derivativeterm" : -0.00000000,
"pidoutputtime" : 257.60736120,
"prevdiffx256" : "000000000240e1e32fa7578cbe9d5e32fa7578cbe9d5e32fa7578cbe9d5e32fa",
"hitlimits" : false,
"nextdiffbits" : "1c033add",
"nextdifflog2" : 38.30849247,
"nextdiffx256" : "00000000033add5f3bc530b02247f5f3bc530b02247f5f3bc530b02247f5f3bb",
"tipspacing" : 215.95000000,
"blkspacing" : 87,
"prevshad" : "4d2392a5d6d13d9b5580fabf5f3dc9ea4b246d0400c583f1b1b3e647fd696eaa"
}

The new difficulty target is given by "nextdiffbits" or "nextdiffx256". The pools software will use this number as described in https://en.bitcoin.it/wiki/Difficulty

The profitability of mining for the casual user when the PID will engage at block 555555, when there will be quite variation in difficulty block to block to maintain the targetspacing to 180, shall best be known on an averaged value. The difficulty value returned by "getdifficulty" is only for next block, and not an average. Two values can thus be used to assess an recent average of difficulty.

First is "prevdiff" or "prevdiffx256" which is the smoothed average of difficulty on the last 21 blocks (tipfilter). Once again the smaller the more difficult. "Prevdiff" is the blue line in the next chart, "Newdiff" is the red line in the chart and the actual difficulty, the limits down (green) and up (purple) of the PID are seen too.

The second way to know indirectly the difficulty on average was stated in a post above, and it is by typing 'getnetworkhashps #'. With # being the number of blocks, 21 (Tipfilter) or 120 (6 hours) are good numbers.

Code:

16:27:04

getnetworkhashps 120


16:27:04

2877270143


16:28:37

getnetworkhashps 21


16:28:37

2184023236

With the getnetworkhashps value and your own hashrate it is easy to know how much blocks you shall receive in an interval of time. There are 480 blocks a day in anoncoin, 2.5 ANC per block right now, knowing your hashrate and net hashrate and doing the math you can calculate profitability in ANC per day.

Code:

My hashrate = 100 MH/s = 100000000
getnetworkhashps 120 = 2877270143
Proportion of hashrate = 100000000/2877270143 = 0.035
ANC per day = 2.5 * 480 * 0.035 = 42

But to answer your question, both BFGminer and cgminer interpret nBits correctly on 0.9.6.11 with GR RetargetPID enabled, so Stratum shall works similarly.

nodes please?

-addnode=109.133.156.15:49362
-addnode=211.149.175.37:52736
-addnode=84.55.23.199:55863
-addnode=211.149.175.37:51950
-addnode=192.99.13.67:54869
-addnode=108.61.10.90:56562

There are hardcoded DNSseednodes (https://github.com/Anoncoin/anoncoin/blob/master/src/chainparams.cpp#L124) and hardcoded seednodes (https://github.com/Anoncoin/anoncoin/blob/master/src/chainparams.cpp#L29) and hardcoded I2P nodes (https://github.com/Anoncoin/anoncoin/blob/master/src/chainparams.cpp#L36). There is no need to add other nodes.

[CartmanSPC]

Crash on launch with the win64 version of anoncoin-qtc.exe. Anyone else?

Edit: Same with the win32 version.
Edit2: Had to delete everything except wallet.dat and rebuild blockchain from scratch.

[Cryptoslave]

Crash on launch with the win64 version of anoncoin-qtc.exe. Anyone else?

Edit: Same with the win32 version.
Edit2: Had to delete everything except wallet.dat and rebuild blockchain from scratch.

Yes, you have to empty the data directory but not and rebuild from scratch, with or without bootstrap.dat

Also the old anoncoin.conf is not compatible with the new one, use the anoncoin.conf.sample or anoncoin.conf.txt provided in anoncoin/doc directory.

see https://wiki.anoncoin.net/How_to_setup_your_Anoncoin_wallet#Setting_up_your_client_to_use_I2P_.289.6.11.29
and https://wiki.anoncoin.net/How_to_install_Anoncoin

Thank you, I updated The Guide to install Anoncoin

CS