Official Anoncoin chat thread (including history)

[A L I E N]

update your project news pls.
The last update was august 30th.

LOL

[meeh]

update your project news pls.
The last update was august 30th.

What have changed that you feel need updating?

[fendlestick]

Could you make it so I can host a .onion using just the wallet and my local machine as the server?

[meeh]

Could you make it so I can host a .onion using just the wallet and my local machine as the server?

Yes that's no problem.

There are two setups;
#1 - Only Tor: You will only announce your address on Tor. Anoncoin will not broadcast outside of of Tor. So your ISP won't see you're running Anoncoin. NSA will however if they want because of the 1024RSA/DH key's Tor currently using.
#2 - Tor/Clearnet bridge: You're on both. You recive new blocks from the pools on clearnet and help broadcast them into the Tor network.

What you do is:

Setup #1 - Only Tor
Apply this to your anoncoin.conf
onlynet=tor
externalip=XXXX
tor=127.0.0.1:9050
addnode=m6xwmit3jovw34r2.onion
addnode=aqmdzilaqayzjb6o.onion
addnode=sf2px26xdsqphkef.onion
addnode=wwniwxrykmk2wtcw.onion


And something like this to your torrc:

HiddenServiceDir /var/lib/tor/anoncoin_nodeXX/
HiddenServicePort 9377 127.0.0.1:9377


Then restart your Tor server.
Read the content of file and change it with the XXXX in the anoncoin.conf

I usualy just do "sudo cat /var/lib/tor/anoncoin_nodeXX/hostname" to get the tor hidden service address.

Setup #1 - Tor/Clearnet bridge
Apply this to your anoncoin.conf

listen=1
discover=1
proxy=127.0.0.1:9050
externalip=XXXX


And something like this to your torrc:

HiddenServiceDir /var/lib/tor/anoncoin_nodeXX/
HiddenServicePort 9377 127.0.0.1:9377


Then restart your Tor server.
Read the content of file and change it with the XXXX in the anoncoin.conf


Note: If you're on windows, please locate the torrc and see the examples for "HiddenServiceDir" in the comments of the file for how to set it up with windows paths instead of unix paths


I hope this works for you! Feel free to ask quetions if something was unclear

[cyberstef]

Why is there so much delay between some blocks. 84414,84415,84416

http://explorer.anoncoin.net/chain/Anoncoin?count=50&hi=84416

Target block should be around 3-4min... Is it a problem with the difficulty algo?

Thanks. Keep going with the good work!

[fendlestick]

Could you make it so I can host a .onion using just the wallet and my local machine as the server?

Yes that's no problem.

There are two setups;
#1 - Only Tor: You will only announce your address on Tor. Anoncoin will not broadcast outside of of Tor. So your ISP won't see you're running Anoncoin. NSA will however if they want because of the 1024RSA/DH key's Tor currently using.
#2 - Tor/Clearnet bridge: You're on both. You recive new blocks from the pools on clearnet and help broadcast them into the Tor network.

What you do is:

Setup #1 - Only Tor
Apply this to your anoncoin.conf
onlynet=tor
externalip=XXXX
tor=127.0.0.1:9050
addnode=m6xwmit3jovw34r2.onion
addnode=aqmdzilaqayzjb6o.onion
addnode=sf2px26xdsqphkef.onion
addnode=wwniwxrykmk2wtcw.onion


And something like this to your torrc:

HiddenServiceDir /var/lib/tor/anoncoin_nodeXX/
HiddenServicePort 9377 127.0.0.1:9377


Then restart your Tor server.
Read the content of file and change it with the XXXX in the anoncoin.conf

I usualy just do "sudo cat /var/lib/tor/anoncoin_nodeXX/hostname" to get the tor hidden service address.

Setup #1 - Tor/Clearnet bridge
Apply this to your anoncoin.conf

listen=1
discover=1
proxy=127.0.0.1:9050
externalip=XXXX


And something like this to your torrc:

HiddenServiceDir /var/lib/tor/anoncoin_nodeXX/
HiddenServicePort 9377 127.0.0.1:9377


Then restart your Tor server.
Read the content of file and change it with the XXXX in the anoncoin.conf


Note: If you're on windows, please locate the torrc and see the examples for "HiddenServiceDir" in the comments of the file for how to set it up with windows paths instead of unix paths


I hope this works for you! Feel free to ask quetions if something was unclear

That is fantastically simple! Thanks, I will give it a go.

[BroTroxer]

Why is there so much delay between some blocks. 84414,84415,84416

http://explorer.anoncoin.net/chain/Anoncoin?count=50&hi=84416

Target block should be around 3-4min... Is it a problem with the difficulty algo?

Thanks. Keep going with the good work!

This is due to the huge amount of hashing power being introduced for a few minutes at the time by the hit 'n run pools. They increase the difficulty and then move on to the next insta-mine victim leaving the regular miners to solve the high diff blocks.

[Desten]

Default port is conflicting with litecoin. Fix this.
PS: coin deleted after 5 second run. LOL. Fastest wallet death in my little collection.

[meeh]

Default port is conflicting with litecoin. Fix this.
PS: coin deleted after 5 second run. LOL. Fastest wallet death in my little collection.

What? Alll the ports is changed. Please post the port number you're talking abut.

[kriwest]

Just out of curiosity; how is the poker network and VPN coming along?

[Desten]

What? Alll the ports is changed. Please post the port number you're talking abut.

anoncoin-qt-0.7.4.zip, downloaded today:

  -port=<port>           Listen for connections on <port> (default: 9333 or testnet: 19333)

and anoncoin-daemon-0.7.4.zip, didn't started successfully, wants libgcc_s_sjlj-1.dll - after giving them this lib -qt and daemon crashes with x0000007d error.

[meeh]

What? Alll the ports is changed. Please post the port number you're talking abut.

anoncoin-qt-0.7.4.zip, downloaded today:

  -port=<port>           Listen for connections on <port> (default: 9333 or testnet: 19333)

and anoncoin-daemon-0.7.4.zip, didn't started successfully, wants libgcc_s_sjlj-1.dll - after giving them this lib -qt and daemon crashes with x0000007d error.

About the port: https://github.com/Anoncoin/anoncoin/blob/master/src/protocol.h#L22 - No, it's 9377.

But yes, you're correct about the view. In 0.7.4 the help displays 9333. https://github.com/Anoncoin/anoncoin/blob/master/src/init.cpp#L248

Thanks for noticing.

About libgcc_s_sjlj-1.dll, it should lie in the directory above daemon. The first directory after unziping, where anoncoin-qt.exe is.

[Desten]

About libgcc_s_sjlj-1.dll, it should lie in the directory above daemon. The first directory after unziping, where anoncoin-qt.exe is.

It should, but doesn't lie there.

[meeh]

About libgcc_s_sjlj-1.dll, it should lie in the directory above daemon. The first directory after unziping, where anoncoin-qt.exe is.

It should, but doesn't lie there.

Sorry I misread, though it was libgcc_s_dw2-1.dll

Hmm, odd. I also found this.
http://www.qtcentre.org/threads/39639-MinGW-w64-dependency-on-LIBGCC_S_SJLJ-1-DLL

But you're the first reporting it.

Could you post your operating system, version & architecture? If you don't want to post it in the thread please send me a PM.

I've open a issue on it and will fix it in the next release. Meanwhile I'm gonna check if I can retrieve the file from you. It's a known MinGW dll file from the MinGW64 environment.

[ronimacarroni]

I am now convinced that the difficulty setting was a bad idea.
I have never seen a coin swing so wildly.
Do you guys even mine your own coin to keep the difficulty level at a reasonable level?
Oh well I'm keeping them, but I hope it becomes more stable in the future.

[Desten]

I am now convinced that the difficulty setting was a bad idea.
I have never seen a coin swing so wildly.
Do you guys even mine your own coin to keep the difficulty level at a reasonable level?
Oh well I'm keeping them, but I hope it becomes more stable in the future.

You mean difficulty changes each "n" blocks? If yes, then same idea released in spt, each two blocks difficulty changes. I think it's too often.
Don't know how this done in that coin...

[BroTroxer]

I am now convinced that the difficulty setting was a bad idea.
I have never seen a coin swing so wildly.
Do you guys even mine your own coin to keep the difficulty level at a reasonable level?
Oh well I'm keeping them, but I hope it becomes more stable in the future.

We keep mining it ourselves, but even when the pools had a stable hashrate of 100+ mh/s it was not enough to battle the "raiders".

To sum it up;
We have tried applying as much stable hashing power as possible to stabilize this. A huge thanks go out to all miners participating in keeping it as stable as possible.
We have asked pool operators to be as fair as possible when it comes to awarding PPLNS to avoid "hit 'n run" pools.
We have viewed the behavior of the blocks as the diff change, and noticed that this is no longer caused by the pools.

In conclusion it is mainly caused by someone solo mining with probably twice the hashrate of the pools combined, and run off with 80% the easy blocks. This probably requires 300 mh/s or more. We simply cannot battle this amount of power to stabilize it permanently. In addition to this, the hashrate that was already growing well at the pools went back down as miners left when the coin devalued on cryptsy. This pretty much gives away the blocks on low diff with only a few seconds between them to the huge solo farm, swinging the diff very high for the faithful miners to work on until they come back for another run.

Unless we get a lot more stable hashrate on the pools, this behavior is likely to continue. I believe most users agree when I say this is becoming unbearable, and might trigger another hard fork update in a not too distant future to hopefully fix this issue, and stop the exploration once and for all.

[ronimacarroni]

I am now convinced that the difficulty setting was a bad idea.
I have never seen a coin swing so wildly.
Do you guys even mine your own coin to keep the difficulty level at a reasonable level?
Oh well I'm keeping them, but I hope it becomes more stable in the future.

We keep mining it ourselves, but even when the pools had a stable hashrate of 100+ mh/s it was not enough to battle the "raiders".

To sum it up;
We have tried applying as much stable hashing power as possible to stabilize this. A huge thanks go out to all miners participating in keeping it as stable as possible.
We have asked pool operators to be as fair as possible when it comes to awarding PPLNS to avoid "hit 'n run" pools.
We have viewed the behavior of the blocks as the diff change, and noticed that this is no longer caused by the pools.

In conclusion it is mainly caused by someone solo mining with probably twice the hashrate of the pools combined, and run off with 80% the easy blocks. This probably requires 300 mh/s or more. We simply cannot battle this amount of power to stabilize it permanently. In addition to this, the hashrate that was already growing well at the pools went back down as miners left when the coin devalued on cryptsy. This pretty much gives away the blocks on low diff with only a few seconds between them to the huge solo farm, swinging the diff very high for the faithful miners to work on until they come back for another run.

Unless we get a lot more stable hashrate on the pools, this behavior is likely to continue. I believe most users agree when I say this is becoming unbearable, and might trigger another hard fork update in a not too distant future to hopefully fix this issue, and stop the exploration once and for all.

Thanks for the update.
Other than that you guys have been doing a good job.

[branefreez]

Hi, again! I just wanted to let you know, again, that the ANC Lotto is down again with the EXCEPTION of

EXCEPTION: Unable to connect to http://xxx:xxx@127.0.0.1:7332

I thought it would be nice to let you know; and the ANC Faucet is giving me HTTP 500 errors.

[meeh]

Hi, again! I just wanted to let you know, again, that the ANC Lotto is down again with the EXCEPTION of

EXCEPTION: Unable to connect to http://xxx:xxx@127.0.0.1:7332

I thought it would be nice to let you know; and the ANC Faucet is giving me HTTP 500 errors.

Thanks. Fixed. (Odd, monit should monitor it and start it if it for some reason stops.)