(...)
Ok, so the problem will be the anoncoin.net link, why is it contacting anoncoin.net for libboost?
Our wallet servers are locked down and cannot contact external sites, is this a custom build of libboost?
if this is a custom build can you please direct me to the source code so we can review it? I am not keen to download unreview code onto our wallet server.
Thanks
Sorry I had mistaken... I did build the dependencies using the toolchain (first make) and here is the libraries it download: 2016-06-27 22:25:18 URL:http://heanet.dl.sourceforge.net/project/boost/boost/1.57.0/boost_1_57_0.tar.bz2 [60821561/60821561] -> "/home/yo/anoncoin/depends/work/download/boost-1_57_0/boost_1_57_0.tar.bz2.temp" [1]
2016-06-27 22:26:36 URL:https://www.openssl.org/source/openssl-1.0.1j.tar.gz [4432964/4432964] -> "/home/yo/anoncoin/depends/work/download/openssl-1.0.1j/openssl-1.0.1j.tar.gz.temp" [1]
2016-06-27 22:27:30 URL:https://fukuchi.org/works/qrencode//qrencode-3.4.3.tar.bz2 [370709/370709] -> "/home/yo/anoncoin/depends/work/download/qrencode-3.4.3/qrencode-3.4.3.tar.bz2.temp" [1]
2016-06-27 22:28:15 URL:http://heanet.dl.sourceforge.net/project/freetype/freetype2/2.5.3/freetype-2.5.3.tar.bz2 [1703842/1703842] -> "/home/yo/anoncoin/depends/work/download/freetype-2.5.3/freetype-2.5.3.tar.bz2.temp" [1]
2016-06-27 22:28:34 URL:http://tenet.dl.sourceforge.net/project/expat/expat/2.1.0/expat-2.1.0.tar.gz [562616/562616] -> "/home/yo/anoncoin/depends/work/download/expat-2.1.0/expat-2.1.0.tar.gz.temp" [1]
2016-06-27 22:28:42 URL:https://dbus.freedesktop.org/releases/dbus/dbus-1.8.6.tar.gz [1861784/1861784] -> "/home/yo/anoncoin/depends/work/download/dbus-1.8.6/dbus-1.8.6.tar.gz.temp" [1]
2016-06-27 22:29:01 URL:https://www.x.org/releases/individual/proto/xproto-7.0.26.tar.bz2 [305321/305321] -> "/home/yo/anoncoin/depends/work/download/xproto-7.0.26/xproto-7.0.26.tar.bz2.temp" [1]
2016-06-27 22:31:02 URL:http://ftp.fau.de/qtproject/archive/qt/4.6/qt-everywhere-opensource-src-4.6.4.tar.gz [160837056/160837056] -> "/home/yo/anoncoin/depends/work/download/qt46-4.6.4/qt-everywhere-opensource-src-4.6.4.tar.gz.temp" [1]
2016-06-27 22:35:02 URL:http://download.oracle.com/berkeley-db/db-4.8.30.NC.tar.gz [22842330/22842330] -> "/home/yo/anoncoin/depends/work/download/bdb-4.8.30/db-4.8.30.NC.tar.gz.temp" [1]
2016-06-27 22:35:23 URL:http://miniupnp.free.fr/files/miniupnpc-1.9.20140701.tar.gz [76735/76735] -> "/home/yo/anoncoin/depends/work/download/miniupnpc-1.9.20140701/miniupnpc-1.9.20140701.tar.gz.temp"
So those are open source public libraries, none are hosted on anoncoin.net (I misread the log). But yes you have to allow outgoing connections to build the toolchain otherwise it will never work. Good luck! CS |
|
|
|
so cryptopia is still on chain v0.8.5.1-132-g73a4219-beta, did you contact them?
Hi, we have been unable to compile the new wallet, have spent a week trying, followed all the guides, tried every conceivable Linux version/combination, still never compiles and just returns an error ............
CXX libanoncoin_server_a-main.o
main.cpp: In function 'bool LoadBlockIndexDB()':
main.cpp:3109:32: error: 'BlockHashCorrectionMap' has no member named 'reserve'
main.cpp:3177:19: error: 'BlockMap' has no member named 'reserve'
main.cpp: In function 'bool ProcessMessage(CNode*, std::string, CDataStream&)':
main.cpp:4135:18: warning: unused variable 'fFromChanged' [-Wunused-variable]
main.cpp:4659:24: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
make[2]: *** [libanoncoin_server_a-main.o] Error 1
make[2]: Leaving directory `/root/anoncoin/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/root/anoncoin/src'
make: *** [all-recursive] Error 1
Any ideas? Hi, I have never seen this error before. Also there is nothing about the errors at 3109 and 3177 that I can find on the net about bitcoin. Thus I tried to compile it again in a Mint 17.1 VM, after erasing all data and following https://wiki.anoncoin.net/How_to_build_Anoncoin_from_source#Ubuntu_64_bit_or_Debian_8sudo apt-get update
sudo apt-get upgrade
sudo apt-get install g++ git automake
sudo apt-get install autoconf make libtool pkg-config libqt4-network libqtgui4 No problem with those. I did not execute this line: sudo apt-get install libboost-all-dev git libdb++-dev libssl-devcd
git clone https://github.com/Anoncoin/anoncoin.git
cd anoncoin
./autogen.sh
cd depends
make -j`nproc` I had an issue here with retrieving the libboost library from anoncoin.net... 404 not found ... had to retry 3 times then it downloaded it correctly. dir
cd ..
./configure --prefix=`pwd`/depends/x86_64-unknown-linux-gnu
make -j`nproc` No issues, anoncoind, anoncoin-qtc and all others were built correctly. It seems your issue is occuring at the very early stage of the last make -j`nproc`. Did you have any problem with the former make? During the build of the toolchain? Maybe the toolchain conflict with your dependencies? BTW as a reminder, block 555555 is in 9 days so the hardfork will occur very soon, everybody shall update ASAP! |
|
|
|
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
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/DifficultyThe 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. 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. 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. |
|
|
|
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. 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. 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. |
|
|
|
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? |
|
|
|
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. |
|
|
|
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. 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. 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. 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. |
|
|
|
Hey Cryptoslave, Do you have an eta as to when we will hit block that results in hard fork? I thought it was early June but recognize that could just be the original launch. Also, have there been any discussion about getting re-listed post hard fork on any exchanges? I'm assuming this hardfork will also fix the stuck coin issue (i.e., cryptsy screwing up broadcast, having to get rawtxid, begging killer or another miner to mine stuck transaction?). Thanks again. Haven't stopped never stopping lol.
Hi tomothy  It will fork in 19440 blocks, which shall be around Wednesday 6 July 2016, at 8h30 GMT. I asked Bittrex but they seems to not look forward to as there was not much volume before (because all volume for western market was on Crapsy, sadly). Also exchanges still remember the TX fees problems and they don't like this, although some like BTC38 or exchangeD or Cryptopia never complained of this. And Crapsy we know was using this bad TX broadcasting as an excuse to cover their scam, they also did it with several coin to pay BigVern is 1.5 million house he gave to his wife and divorced so gov cannot take it away from him when he will get hopefully sued for fraud. So basically every ANC holder on Crapsy (there were 350000 ANC iirc) paid for BigVern swimming pool and he made up the TX bad broadcasting as an excuse. But then Bittrex also complained so I cannot think they did not have some problem at some point. Nevertheless now the TX fee logic and IPV4/I2P connectivity is completely fixed and I also have put back an hidden feature in the console called 'resendwallettransactions'. 23:56:37

help resendwallettransactions
23:56:37

resendwallettransactions
Immediately re-broadcast unconfirmed wallet transactions to all peers.
Note: the wallet code periodically re-broadcasts automatically.
Returns: array of transaction ids that were re-broadcast.
Thank you for your long term care about Anoncoin |
|
|
|
Does this coin still plan to introduce the zerocoin tech? Any details on this would be greatly appreciated Since 2014 and the price crash, Gnosis went away for more than a year. The coin development went almost to a halt because Meeh and Gnosis were both absent. Fortunately, following calls to the community by Lunokhod and me, GroundRod stepped in as the new Lead Developer in early 2015. GroundRod started first by reworking all the code to bitcoin 0.9.x then later up to Bitcoin 0.10.99 codebase. In doing so he put alot of new functionnality from Bitcoin and repaired the many problems the old Anoncoin wallet 0.8.5.6 has such as poor protocol communication, I2P SAM module issues, innacurate transaction fees and the crap difficulty algo KGW was removed for a PID at next Hardfork. I helped him by giving idea and debugging this new wallet last year until he went away in September 2015. Then development stopped until I finished the GroundRod 0.9.6.9 build with the help of Orignal (C++ I2P router i2pd dev). This led to this very 0.9.6.11 build. A few months ago, Gnosis went back to the team with a friend of him, Ssuag. They plan to both finish the zerocoin implementation, Gnosis for the main Zerocoin code and Ssuag for Zerocoin GUI in Anoncoin. We believe in trustless mixing on the blockchain. Right now we acknowledge as good trustless option only Zerocoin and CoinShuffle. Compared to zcash, which use a one-out-of-many to trust setup, or even to the failed zerocoin implementation such as in zerovert, zerocoin in anoncoin will be setup in a trustless manner using RSA UFOs (generalized RSA moduli of unknown complete factorization) which Gnosis did generate previously. In fact the development schedule can be found on the wiki. Release A is finished and is this very build with hardfork@block 555555. Release B is worked upon by me currently and will feature multi-POW (YEScrypt, Lyra2RE2, Scrypt) to have CPU-GPU-ASIC mining on the Anoncoin network. Release C will be zerocoin with RSA-UFO by Gnosis and Ssuag. |
|
|
|
AnonCoin blockchain, freshly synced, is available for download at CryptoChainer.com. This snapshot is from the new wallet. This is a very old coin, and takes nearly forever to sync from scratch. Hi steve321, http://216.14.113.56/cryptochainer.chains/chains/AnonCoin_blockchain.zip : The requested URL /cryptochainer.chains/chains/AnonCoin_blockchain.zip was not found on this server. Also, it may have been the case the blockchain was slow to synch on 0.8.5.6, but with this new client 0.9.6.11 featuring Headers-first synchronisation it is much more quick! Here is a test I did today: 21h50: start a freshly installed Anoncoin 0.9.6.11 64 bit with no blockchain and no bootstrap.dat, on a win7 laptop 21h50-23h30: Synchronisation of the block-headers takes 1h40 (see the first part of the graph, with smallest bandwidth). It may seems the client is doing nothing as the blocks increment slowly, but the progress can be followed by checking the bandwidth use or by typing 'getchaintips' in the debug console.  23h30: begin block download from 16 peers in parallel (the blocks increment quickly and bandwidth increase alot). Header-first synchronisation as adapted in Anoncoin 0.9.6.11 download the headers from 2 peers in parallel but the blocks from all the peers, here from 16 peers which is the max outbound connections possible.  1h30: Anoncoin 0.9.6.11 was fully synched after 3h40 and 506 MB. So I would not say "this coin takes nearly forever to sync from scratch!" Synching through an I2P-only session takes about three time as long without bootstrap. The bootstrap can be downloaded following those instructions. |
|
|
|
ANONCOIN 0.9.6.12 ANONCOIN NEW VERSION 0.9.6.12 RELEASED - 12 OCTOBER 2016 - HARDFORK @ BLOCK 585555We announce the official release of the new master based on Anoncoin 0.9.6.12. This new version (v0.9.6.12-3fd47af) is an obligatory update of Anoncoin with an HARDFORK @ block 585555 Featured changes in this version are the following: Difficulty algorithm tuned: - PID tuning to make diff adjustment less aggressive: NMAXDIFFINCREASE "200" -> 150 (less difficulty increase, to avoid huge spike in diff) NMAXDIFFDECREASE "170" -> 130 (less difficulty decrease, to avoid lots of easy mined block) DMININTEGRATOR 170 -> 176 (less difficulty increase on long term because it is not needed as testnet showed) DMAXINTEGRATOR 190 -> 195 (more difficulty decrease as we have seen multipool jumping on/off in long term slow the blockchain) WEIGHTEDAVGTIPBLOCKS_UP 4 -> 9 (taking more blocks into the average up slow down diff increase and avoid huge spike in diff) WEIGHTEDAVGTIPBLOCKS_DOWN 6 -> 20 (taking much more blocks into the average down slow down the difficulty decrease and hence avoid too many easy blocks in a row) PID_PROPORTIONALGAIN 1.7 -> 1.6 (reduce aggressiveness of proportional term) PID_INTEGRATORTIME 172800 -> 129600 (integral term of 1.5 day to adjust quickly to abnormal number of emitted block) PID_INTEGRATORGAIN 5 -> 8 (the integral term now has more weight in the difficulty calculation, the ranges are respectively of (180-176)*8=32 vs 50 for difficulty going up and of (195-180)*8=120 vs 50 for difficulty going down. So compared to the previous settings, the difficulty can adjust more readily to a slow blockchain to achieve 180 sec avg per block.) PID_DERIVATIVEGAIN 0 -> 3 (adjust quickly to change of block time ie at apex of difficulty it will drop quicker, and at lowest turn up quicker) - Auto-adjustment of difficulty via getblocktemplate to a low one if no block is found in 30 minutes - The difficulty is now expressed again into a positive >1 number, because people and services complained of 0-1 range - Blockchain synchronization issues fix (in case no block is found for a long time because of miner exodus, mining will be allowed up to one week old unsynchronized chain) - Bug because of toolchain build of protobuf solved Old version featured the following: - Full I2P-SAM support - An upgraded to bitcoin 0.10.99 code - Many excellent improvements such as for instance header-first synchronisation, leading to much quicker I2P synchronisation and block download - Deterministic fork selection - A rewritten communication protocol (I2P and clearnet) - No more using IRC for synching peers - Anoncoin's test network (testnet) and regression test mode (regtest) available - A new Kimoto Gravity Well v 2.0 using curves that is much quicker to calculate (it will be useful only for blocks before the hardfork and for first synching as KGW will be obsoleted by PID) - A second new innovative difficulty algo "GroundRod RetargetPID" using a PID (Proportional - Integral - Derivative) controller, that will be enforced at block 555555 as the new difficulty retargetting system - Real hashes calculation and not pseudo difficulty (we will be the only Scrypt coin to use true hashes in calculus of difficulty) - Multisig Anoncoin address - An improved mining through I2P only, to go forward a fully I2P darknet coin - Themes support in anoncoin-qtt (currently for Win32, OS-X and linux, not for win64) - SAM support ported to 0.10.99 and working with both Java and C++ implementation of I2P (Orignal's i2pd, LibI2Pd) - New I2P and DNS seednodes - Headless building with toolchain - New alert key management - Auto generation of I2P addresses provided the java I2P router is configured with default options during setup - Bug fixes Every Anoncoin user shall update to this 9.6.12 version ASAP. This is a mandatory upgrade, as after block 585555 the old peers will be disconnected. The version 9.6.11 will be obsolete when the HARDFORK block 585555 will be mined. This will occur the 27 October or in about 2 weeks. To update to the new version (v0.9.6.12-3fd47af), simply rebuild master following this guide: To build from source: https://wiki.anoncoin.net/How_to_build_Anoncoin_from_sourceWindows build are available here: https://github.com/Anoncoin/anoncoin/releases/tag/v0.9.6.12https://github.com/Anoncoin/anoncoin/releases/download/v0.9.6.12/anoncoin-0.9.6.12-win64-setup.exeanoncoin-0.9.6.12-win64-setup.exe Checksum: MD5 AC0B96AB335BE6E7E78B7D325AF4EBB3 SHA-1 DDB9A4BF777A870D874D872FCB381EF05FBF5E38 https://github.com/Anoncoin/anoncoin/releases/download/v0.9.6.12/anoncoin-0.9.6.12-win32-setup.exeanoncoin-0.9.6.12-win32-setup.exe Checksum: MD5 564AE5FAC81FC550389071FB9C2BF927 SHA-1 7F7A9E2C303682EA9056DA55136D25C391BE3873 CS About Anoncoin: - Launch date: June 6, 2013. - Type: Proof of work with Scrypt hashing algorithm. - Total coin supply: 3,103,954 ANC. - Block target speed: 3 minutes (before block 87777, it was every 3.42 minutes) - Block difficulty retargeting: Block 555555 upward: GroundRod Retarget PID - retarget every block using Proportional-Integrative-Derivative developed in house by GroundRod algorithm Block 555554-87777: Kimoto Gravity Well - retarget every block Block 87777-1: ~1680 blocks using classic BTC algorithm - Premine: 1000 blocks (4200 ANC) that were returned to the community by community donations and a public faucet. - Anonymity: Built in support of I2P and Tor. Zerocoin to be implemented in a future release. - Current block reward: 2.5 ANC per block. - Block reward schedule: 4.2 ANC for blocks until 42,000; 7 ANC until block 77,777; a 10 ANC bonus block for 77778; 5 ANC until block 306,600; and then halving of block rewards every 306,600 blocks (approximately every 638 days). Official windows and OSX builds: https://github.com/Anoncoin/anoncoin/releases/tag/v0.9.6.12anoncoin-0.9.6.12-win64-setup.exe Checksum: MD5 AC0B96AB335BE6E7E78B7D325AF4EBB3 SHA-1 DDB9A4BF777A870D874D872FCB381EF05FBF5E38 anoncoin-0.9.6.12-win32-setup.exe Checksum: MD5 564AE5FAC81FC550389071FB9C2BF927 SHA-1 7F7A9E2C303682EA9056DA55136D25C391BE3873 To build from source: https://wiki.anoncoin.net/How_to_build_Anoncoin_from_sourceExchanges:Clearnet: Nova Exchange ANC/BTC. correct chain!Darknet:Exchanged.I2P (link needs I2P client). First Ever Darknet CryptoCurrency Exchange. Trade altcoins anonymously. ANC/BTC. Clearnet proxy link correct chain!Tor correct chain!I2p correct chain!Bitcointalk threadCharts:Sosobtc ANC/CNY BTC38Dc-charts ANC/CNY BTC38Marketcap and mining difficultyCoinGeckoCoinMarketcapCoinwarz shall updateBlock explorersCryptoidDark GamexMining Poolshash-to-coins.com correct chain!prohashing.com correct chain!tompool.org correct chain!xpool.net P2Pool correct chain!ypool.ga correct chain! correct chain!
[url=http://ispace.co.uk/]ispace.co.uk disabledmultipool.us disabledI2P powered  With full mining compatibility over I2P, I2P darknet exchange (ExchangeD.i2p) and complete I2P integration built in the wallet, Anoncoin can gives a full experience of the I2P darknet. TOR powered  GitHub link: https://github.com/Anoncoin/anoncoin/releases/tag/v0.9.6.12Official site: https://anoncoin.net/Official wiki: https://wiki.anoncoin.net/Anoncoin_WikiA message from Meeh concerning the change of leadership Previous threads:Re: Official Anoncoin chat thread (including history)Official Anoncoin Information, FAQ & Description thread. I2P/Tor explained [Mod]Special thanks to our developers and long term fans: Meeh, K1773R, BroTroxer, Gnosis, Lunokhod, Cryptoslave, GroundRod, Mrebum, Abyss, Ssuag, Orignal, Alacast, Geekz, N00n & all others
This build could not have been done without the long term commitment and excellent work of GroundRod who updated all the codebase to 0.10.99, developed the difficulty retarget algorithm GroundRod PID, reworked SAM support, reworked the communication protocol, implemented the regtest mode, developed a new alert key management, worked on the test suites and implemented the toolchain build.
|
|
|
|
 ANONCOIN 0.9.6.13Anoncoin Core & PurpleI2P present:ANCI2Pd 1.0.13.0 - Anoncoin & I2Pd bundle - 13 june 2017The first stand-alone cryptocurrency and C++ I2Pd router bundle!
Featuring the latest version of Anoncoin 0.9.6.13 & i2pd 2.14.0
Easy to install, easy to use, your IP address is completely obfuscated by the I2P integration!
Recent deanonymization attacks that exploit weaknesses in the Bitcoin peer-to-peer (P2P) networking protocols are impossible for Anoncoin thanks to the I2P traffic routing.
Enjoy!To install, just execute the self-extracting file, go in the chosen folder and then execute StartANCI2PdPortable.exe ANCI2Pd 1.0.13.0 Windows version (32 bits) only:
https://github.com/Anoncoin/anoncoin/releases/tag/1.0.13.0
https://github.com/Anoncoin/anoncoin
https://github.com/PurpleI2P/i2pd
Special thanks to Orignal, R4SAS, Omen and all contributors from i2pd team and irc2p ru channel
For those who prefer the full installer over the anci2pd bundle:Anoncoin 0.9.6.13 Setup for win32 and win64:
https://github.com/Anoncoin/anoncoin/releases/tag/5e441d8 |
|
|
|
NEW VERSION 0.9.6.11 RELEASED - HARDFORK @ BLOCK 555555We announce the official release of the new master based on Anoncoin 0.9.6.11. This new version is an obligatory update with an HARDFORK @ block 555555 Featured in this version are the following: - An upgraded to bitcoin 0.10.99 code - Many excellent improvements such as for instance header-first synchronisation, leading to much quicker I2P synchronisation and block download - Deterministic fork selection - A rewritten communication protocol (I2P and clearnet) - No more using IRC for synching peers - Anoncoin's test network (testnet) and regression test mode (regtest) available - A new Kimoto Gravity Well v 2.0 using curves that is much quicker to calculate (it will be useful only for blocks before the hardfork and for first synching as KGW will be obsoleted by PID) - A second new innovative difficulty algo "GroundRod RetargetPID" using a PID (Proportional - Integral - Derivative) controller, that will be enforced at block 555555 as the new difficulty retargetting system - Real hashes calculation and not pseudo difficulty (we will be the only Scrypt coin to use true hashes in calculus of difficulty) - Multisig Anoncoin address - An improved mining through I2P only, to go forward a fully I2P darknet coin - Themes support in anoncoin-qtt (currently for Win32, OS-X and linux, not for win64) - SAM support ported to 0.10.99 and working with both Java and C++ implementation of I2P (Orignal's i2pd, LibI2Pd) - New I2P and DNS seednodes - Headless building with toolchain - New alert key management - Auto generation of I2P addresses provided the java I2P router is configured with default options during setup - Bug fixes Everyone shall update to this 9.6.11 version ASAP. This is a mandatory upgrade, as after block 555555 the old peers will be disconnected. The version 8.5.6 will be obsolete when the HARDFORK block 555555 will be mined. Official windows builds: https://anoncoin.net/downloads/0.9.6.11/Release win32.zip Checksum: MD5 0FF381D8C7DBD6710F73219EB9A22B3E SHA-1 725E8EA19076E304B99743DE022BCAEACAE98CA6 Release win64.zip Checksum: MD5 C7430DBD0DB0F69351F4E2D632B3F2F2 SHA-1 1CB53AFD9E94B51E0F06649C6FEAD7A780ECCC20 To build from source: https://wiki.anoncoin.net/How_to_build_Anoncoin_from_sourceCS
|
|
|
|
So far the testnet is still running without any trouble But we need more beta-tester! Every one that can build on linux or OSX can join us to finish this testing! You cooperation will be very appreciated. If you want to participate go on #anoncoin on I2P and ask for me in the channel stating you want to try the testnet. Thank you We are currently doing a live testnet to try the hardfork setting! Anyone who wants to join us is welcome to join! Please come check on #anoncoin on I2P we will tell you how you can participate (windows, OSX or linux)... Thank you for your help CS |
|
|
|
We are currently doing a live testnet to try the hardfork setting! Anyone who wants to join us is welcome to join! Please come check on #anoncoin on I2P we will tell you how you can participate (windows, OSX or linux)... Thank you for your help CS |
|
|
|
Hey!
0.8.5.6 is newest wallet?
It looks pretty old, any ETA on new release?
Hi Conqueror, Well, as said in February , I have now finished version A for my part of the work, taking over GroundRod work. You can check the commits at Github. Right now Ssuag is finishing to optimize the I2P parameters encoding that will ask for less interaction from the user in his branch. When he will have finish his work, we will merge both branchs, do another testnet and this will become the new master. Meanwhile I am now working on implementing multi POW for release B, this will include 3 algos: Scrypt (ASIC Friendly), Lyra2RE2 (GPU Friendly), YEScrypt (CPU Friendly). This is not an easy task because our codebase is 0.10.99 and we cannot copy/paste the code of others coins like it is mostly done due to our multiple optimization and I2P code. Thus we will launch release A with Scrypt only before release B with multi POW enabled. CS |
|
|
|
|
Show Posts
