Even with the price of BTC going up.. ANC is also going up at the same time.
This is truly impressive. The price goes organically.
Topic: Official Anoncoin chat thread (including history) - page 233. (Read 530660 times)
This is truly impressive. The price goes organically.
Even with the price of BTC going up.. ANC is also going up at the same time.
This new build does not like my wallet.dart i keep getting error reading wallet.dat even though is had has success reading it here and there.
this happens if the builder uses different libdb than you do with your (old) client.wallet.dat is also a BDB, any *coind should be build with 4.8>= && <5 libdb or wallet.dat wont be compatible.
@meeh: did you build with 4.8 or 5+?
This new build does not like my wallet.dart i keep getting error reading wallet.dat even though is had has success reading it here and there.
wtf, why dont you build yourself?
because of boost issueshttps://bitcointalk.org/index.php?topic=227287.620
wtf, why dont you build yourself?
Isn't TOR riddled with backdoors now?
We don't prioritise Tor. This coin is customized for I2P, not Tor. You can run it on Tor, but you can run any coin on Tor so it's not making this one special.
And if you have followed the news you should know that OFFICIALLY everyone caught by the police in the last past have made stupid decidions making them getting caught. It was no technical issue that caught them.
Anyway, Tor is open source. Feel free too read the source code for backdoors
https://gitweb.torproject.org/tor.git?a=tree;hb=HEAD - the source code
Fixed it for you. I don't believe for a second that the government doesn't have a way to unmask Tor users with a high percentage of success, although I don't know enough about the internal workings of I2P to comment on it. Now, I don't believe Tor has a backdoor in it. Simply put, there aren't enough legit nodes to make it unlikely that a single entity can run enough exit nodes to have a high probability of being both an entry and exit node for someone. Especially for an entity like the US Government. You can buy a LOT of VPSs for less than the cost of a fighter jet, probably enough to become the majority of exit nodes on the Tor network. And we don't even know their full capabilities. They're likely able to monitor all traffic in the US, and if you combine that with them running a ton of evil exit nodes, then they can start unmasking Tor users.
Thanks meeh and your work !
Hey devs, can you stop force pushing the master branch please?
Force push the master branch? I don't get what you're talking about. We're using master-0.8 now, and it is a protocol switch so if you don't upgrade you will be disconnected from the Anoncoin network.
Hey devs, can you stop force pushing the master branch please?
As a reminder to those who haven't updated yet.
Anoncoin New mandatory client release. Be sure to upgrade your client as soon as possible. The Old version will be incompatible from block 87.777!
This update will fork to improve the difficulty adjustment. We can not allow the hit 'n run mining to continue as it makes coin transfers slow, and the mining unfair to regular miners.
We have implemented several improvements based on user feedback, and the dev teams own experiences.
Changes to block target and difficulty:
The Kimoto's Gravity well will improve upon the rapid difficulty adjustment, providing smoother transactions, improving security by rejecting blocks that are a direct result of "hit 'n run" mining by large coin jumping pools.
The target time has been changed to 3 minutes. This means there will be ~480 blocks per 24 hours instad of the previous ~420.
Overall this improvement will be noticed by most users by the faster, more stable transaction times.
Please visit our website to obtain the latest version today; https://anoncoin.net
Anoncoin New mandatory client release. Be sure to upgrade your client as soon as possible. The Old version will be incompatible from block 87.777!
This update will fork to improve the difficulty adjustment. We can not allow the hit 'n run mining to continue as it makes coin transfers slow, and the mining unfair to regular miners.
We have implemented several improvements based on user feedback, and the dev teams own experiences.
Changes to block target and difficulty:
The Kimoto's Gravity well will improve upon the rapid difficulty adjustment, providing smoother transactions, improving security by rejecting blocks that are a direct result of "hit 'n run" mining by large coin jumping pools.
The target time has been changed to 3 minutes. This means there will be ~480 blocks per 24 hours instad of the previous ~420.
Overall this improvement will be noticed by most users by the faster, more stable transaction times.
Please visit our website to obtain the latest version today; https://anoncoin.net
Will do - thanks and apologies for the oversight
No problem. It's much for your own good, not mine.
Running software you don't know what will do on your computer can lead to bad things..
Will do - thanks and apologies for the oversight
Hi and thanks,
If you're going to use our software, can you please read what I write about it first?
Quoting myself from the release post:
A known GUI issue when stuck at high diff, the GUI claim it's unsynced. (Will be fixed in a release right after 87777)
So nothing to worry about. It will show syned when next block is found
If you're going to use our software, can you please read what I write about it first?
Quoting myself from the release post:
A known GUI issue when stuck at high diff, the GUI claim it's unsynced. (Will be fixed in a release right after 87777)
So nothing to worry about. It will show syned when next block is found
Hi - great project - I was having a problem syncing the blockchain on an version of the client I built from git clone just before noticing the new release. So I built the "v0.8.5.5-g313123c-beta" version which was linked in the announcement.
Unfortunatelty I have the same problem - the blockchain sync gets stuck on block 86101 with all the peers refusing to connect (see debug.log) I've deleted the blockchain and the peers.dat and had same problem on all nets.
I couldn't find any info about this, am I doing something wrong?
Unfortunatelty I have the same problem - the blockchain sync gets stuck on block 86101 with all the peers refusing to connect (see debug.log) I've deleted the blockchain and the peers.dat and had same problem on all nets.
Code:
ProcessBlock: ACCEPTED
received block 2dcfc5e8391f916e66702055e6d2bb2e1c310f2e9afad4d72dd9fe5265fc6f2f
Committing 5 changed transactions to coin database...
SetBestChain: new best=2dcfc5e8391f916e66702055e6d2bb2e1c310f2e9afad4d72dd9fe5265fc6f2f height=86096 log2_work=48.632728 tx=108288 date=2013-10-12 07:23:20 progress=0.016431
ProcessBlock: ACCEPTED
received block 3db306f475d5a822c121db578b7d3c8b1ac026852efa4a886679f76d71bdde0a
Committing 1 changed transactions to coin database...
SetBestChain: new best=3db306f475d5a822c121db578b7d3c8b1ac026852efa4a886679f76d71bdde0a height=86097 log2_work=48.63288 tx=108289 date=2013-10-12 07:24:01 progress=0.016431
ProcessBlock: ACCEPTED
received block 97049acd28a6b7c1540719f3e3d415b15c91b3aec767c77df3cdd9b3a74b6266
Committing 7 changed transactions to coin database...
SetBestChain: new best=97049acd28a6b7c1540719f3e3d415b15c91b3aec767c77df3cdd9b3a74b6266 height=86098 log2_work=48.633094 tx=108292 date=2013-10-12 07:28:35 progress=0.016432
ProcessBlock: ACCEPTED
received block 6cce92ea3628a9447d44f03eba857eb85ede55ee588745e9fa776d276c3a4ff4
Committing 1 changed transactions to coin database...
SetBestChain: new best=6cce92ea3628a9447d44f03eba857eb85ede55ee588745e9fa776d276c3a4ff4 height=86099 log2_work=48.633397 tx=108293 date=2013-10-12 07:29:11 progress=0.016432
ProcessBlock: ACCEPTED
received block b84e3eeabe7c984ce241f0a3f2101166c3095a5a4e2f308ef38f90231a9df80a
Committing 1 changed transactions to coin database...
SetBestChain: new best=b84e3eeabe7c984ce241f0a3f2101166c3095a5a4e2f308ef38f90231a9df80a height=86100 log2_work=48.633826 tx=108294 date=2013-10-12 07:29:48 progress=0.016432
Committing 21 changed transactions to coin database...
SetBestChain: new best=aedd4c31086630b48daaf0ce50f3288647fe6ee154f3fbbbbc7977da35926678 height=86101 log2_work=48.634432 tx=108301 date=2013-10-12 07:48:00 progress=0.016433
ProcessBlock: ACCEPTED
getblocks 85769 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks 85997 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks 86001 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks 86073 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks 86073 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks 85997 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks 86001 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks 86019 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks 86073 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks 85997 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks 86001 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks 86019 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks 86073 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks 85997 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks 86001 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks 86019 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks 86073 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks 86019 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks 86073 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks 85997 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks 86001 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks 86019 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks 86073 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks 86019 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks 86073 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks 84669 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks stopping at limit 85168 2f9931e1094b8fe41d9266d8ff7c48d85e3b62194f86ced882ba1ce11cf9c13c
getblocks 84977 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks stopping at limit 85476 92bd1c56201c4a22200a79ba7775fb42771cffb7c787036943858f228aea22b5
getblocks 85001 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks stopping at limit 85500 b47a55401f421c5fe092fb34360c4401a704ba7c5bd0a78078f601e658178d83
getblocks 85002 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks stopping at limit 85501 0ad82aed6ed1bfd161602f2fbdf5c214f4f4894d474b4a635e11f74ce9baa197
getblocks 85026 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks stopping at limit 85525 e3da8cdf7187ed4e1bae5d876c633e07abb81c465ff7f4fe045042adb1862971
getblocks 85093 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks stopping at limit 85592 736e7ce9335650c7fa2e86213328aba1130ab157cfee08fde935ed3acacd96d6
getblocks 85245 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks stopping at limit 85744 709716c1560a4fcf186911543545570a13359193b7da5b5aa12cf301c1f6fa72
getblocks 85446 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks stopping at limit 85945 bcc920a9049e2f60488a4e46f2baa46612e17fbd2dd389a67d60399693530f2c
getblocks 85501 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks stopping at limit 86000 c20065fdad201b9c54e797db1dc7f03f27d2a221db7593b7001463bfe8f178b5
getblocks 85528 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks stopping at limit 86027 d9bfe976df4252fd78d7eb1bd5a2828d20aa9447e96ec0fbb0185f8352355269
getblocks 85531 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks stopping at limit 86030 fa0cb06ea5901337c40174a13ab97afd06003b8547989ee3051809cab8415d12
getblocks 85537 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks stopping at limit 86036 16befef6652d95f99f8e540a884a384c9d61d9a0985e7264a8bfa759a366a894
getblocks 85555 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks stopping at limit 86054 eb25970b7a6bf5776c6f115cc5f1e89d877ee443e4a63f5991e0c82b663c26f6
getblocks 85583 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks stopping at limit 86082 12316292c1a2ab2cc15996fa0af96a0969ab1a27ecfbd8edef0e53adc31eba04
getblocks 85664 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks 85245 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks stopping at limit 85744 709716c1560a4fcf186911543545570a13359193b7da5b5aa12cf301c1f6fa72
getblocks 85446 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks stopping at limit 85945 bcc920a9049e2f60488a4e46f2baa46612e17fbd2dd389a67d60399693530f2c
getblocks 85501 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks stopping at limit 86000 c20065fdad201b9c54e797db1dc7f03f27d2a221db7593b7001463bfe8f178b5
getblocks 85528 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks stopping at limit 86027 d9bfe976df4252fd78d7eb1bd5a2828d20aa9447e96ec0fbb0185f8352355269
getblocks 85531 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks stopping at limit 86030 fa0cb06ea5901337c40174a13ab97afd06003b8547989ee3051809cab8415d12
getblocks 85537 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks stopping at limit 86036 16befef6652d95f99f8e540a884a384c9d61d9a0985e7264a8bfa759a366a894
getblocks 85769 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks 85997 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks 86001 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks 86019 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks 86073 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
connection timeout
getblocks 86019 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks 85073 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks stopping at limit 85572 3e93a4dd4ead17790464bcc03ab176cdede2cbbb1ffc479473aa21cd1311a26b
trying connection 93.139.60.39:9377 lastseen=1.1hrs
getblocks 86073 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks 85506 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks stopping at limit 86005 85adb60641a3b12d100d36c8a56f280f34447cf81fdb41c84f82575a6cb84297
getblocks 85939 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks 85555 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks stopping at limit 86054 eb25970b7a6bf5776c6f115cc5f1e89d877ee443e4a63f5991e0c82b663c26f6
getblocks 85583 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks stopping at limit 86082 12316292c1a2ab2cc15996fa0af96a0969ab1a27ecfbd8edef0e53adc31eba04
getblocks 85664 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks 85769 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks 85997 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
connection timeout
trying connection 199.38.85.200:9377 lastseen=1.1hrs
connected 199.38.85.200:9377
send version message: version 70006, blocks=86101, us=59.167.234.153:9377, them=199.38.85.200:9377, peer=199.38.85.200:9377
socket recv error 104
disconnecting node 199.38.85.200:9377
trying connection 162.209.99.129:9377 lastseen=135.9hrs
connect() failed after select(): Connection refused
trying connection 46.162.125.40:9377 lastseen=6.4hrs
getblocks 86001 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks 86019 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks 86073 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
connection timeout
trying connection 24.55.2.13:9377 lastseen=20.8hrs
connection timeout
trying connection 188.165.194.201:0 lastseen=87.4hrs
connection timeout
trying connection 82.239.49.238:9377 lastseen=78.2hrs
connection timeout
trying connection 72.213.161.160:9377 lastseen=59.1hrs
connection timeout
trying connection 209.193.94.158:0 lastseen=129.1hrs
connect() failed after select(): Connection refused
trying connection 141.0.73.226:9377 lastseen=13.8hrs
connected 141.0.73.226:9377
send version message: version 70006, blocks=86101, us=59.167.234.153:9377, them=141.0.73.226:9377, peer=141.0.73.226:9377
trying connection 72.248.219.50:9377 lastseen=66.3hrs
Added time data, samples 14, offset +3 (+0 minutes)
receive version message: version 70006, blocks=86101, us=59.167.234.153:44790, them=wwniwxrykmk2wtcw.onion:9377, peer=141.0.73.226:9377
connection timeout
trying connection 67.220.38.62:0 lastseen=29.0hrs
connection timeout
trying connection 81.71.117.150:9377 lastseen=1.1hrs
Added 814 addresses from 141.0.73.226: 0 tried, 9614 new
Added 788 addresses from 141.0.73.226: 0 tried, 9838 new
Added 781 addresses from 141.0.73.226: 0 tried, 10001 new
Added 714 addresses from 141.0.73.226: 0 tried, 10062 new
connection timeout
trying connection 81.242.68.191:9377 lastseen=58.4hrs
connection timeout
trying connection 24.55.2.13:9377 lastseen=8.2hrs
connection timeout
trying connection 173.248.155.105:9378 lastseen=1.1hrs
connect() failed after select(): Connection refused
trying connection 198.23.229.14:9377 lastseen=1.1hrs
connection timeout
trying connection 31.129.127.188:0 lastseen=10.5hrs
connect() failed after select(): Connection refused
trying connection 198.23.229.14:9377 lastseen=31.3hrs
connection timeout
trying connection 91.121.118.76:0 lastseen=35.2hrs
connect() failed after select(): Connection refused
trying connection 70.79.24.157:0 lastseen=57.8hrs
connection timeout
trying connection 109.60.2.246:9377 lastseen=7.1hrs
connection timeout
trying connection 50.116.4.212:0 lastseen=113.7hrs
connect() failed after select(): Connection refused
trying connection 93.139.60.39:9377 lastseen=1.1hrs
connection timeout
trying connection 54.214.248.23:9377 lastseen=1.1hrs
connection timeout
trying connection 37.205.9.3:9377 lastseen=114.2hrs
connected 37.205.9.3:9377
send version message: version 70006, blocks=86101, us=59.167.234.153:9377, them=37.205.9.3:9377, peer=37.205.9.3:9377
trying connection 72.248.219.50:9377 lastseen=11.7hrs
Added time data, samples 15, offset +3 (+0 minutes)
nTimeOffset = +2 (+0 minutes)
receive version message: version 70005, blocks=86101, us=59.167.234.153:37748, them=37.205.9.3:9377, peer=37.205.9.3:9377
connection timeout
trying connection 66.7.215.57:0 lastseen=26.0hrs
connect() failed after select(): No route to host
trying connection 46.188.1.45:0 lastseen=89.8hrs
Added 955 addresses from 37.205.9.3: 0 tried, 10298 new
Added 947 addresses from 37.205.9.3: 0 tried, 10478 new
Added 948 addresses from 37.205.9.3: 0 tried, 10558 new
Added 678 addresses from 37.205.9.3: 0 tried, 10582 new
connection timeout
trying connection 198.23.229.14:9377 lastseen=1.1hrs
connection timeout
I couldn't find any info about this, am I doing something wrong?
Isn't TOR riddled with backdoors now?
We don't prioritise Tor. This coin is customized for I2P, not Tor. You can run it on Tor, but you can run any coin on Tor so it's not making this one special.
And if you have followed the news you should know that everyone caught by the police in the last past have made stupid decidions making them getting caught. It was no technical issue that caught them.
Anyway, Tor is open source. Feel free too read the source code for backdoors
https://gitweb.torproject.org/tor.git?a=tree;hb=HEAD - the source code
Isn't TOR riddled with backdoors now?
Finaly!
Mandatory upgrade! Windows users, upgrade ASAP
https://anoncoin.net/downloads/0.8.5.5/
We're changing to Kimoto diff patch on block 87777. And we're on 86075 now.
This time I've signed the builds with my GPG key, so they can be verified built by me.
Notes about the new client
* A known GUI issue when stuck at high diff, the GUI claim it's unsynced. (Will be fixed in a release right after 87777)
* Coin control
* Based on Bitcoin's source code 0.8.5.3
* Kimoto's Gravity well
Good times will come!
If you experience problem with the upgrade, try delete the blk* files and the peers.dat in your config dir!
Building for OSX and Linux now!
Mandatory upgrade! Windows users, upgrade ASAP
https://anoncoin.net/downloads/0.8.5.5/
We're changing to Kimoto diff patch on block 87777. And we're on 86075 now.
This time I've signed the builds with my GPG key, so they can be verified built by me.
Notes about the new client
* A known GUI issue when stuck at high diff, the GUI claim it's unsynced. (Will be fixed in a release right after 87777)
* Coin control
* Based on Bitcoin's source code 0.8.5.3
* Kimoto's Gravity well
Good times will come!
If you experience problem with the upgrade, try delete the blk* files and the peers.dat in your config dir!
Building for OSX and Linux now!
Jump to: