How does one use this with i2p?
To use the daemon on I2P ONLY do the following: 1. Download and install I2P ( www.geti2p.net ), then start it. (It will run as a daemon, so don't expect any window) 2. Wait a minute or two, then navigate to http://127.0.0.1:7657/configclients3. Make sure to start the "SAM application bridge" (Tip: After starting it, check it for autostart and save configuration) 4. In run (enter the start menu and type run on windows Vista/7) type %appdata% 5. Open or create the Anoncoin folder 6. Create/edit the anoncoin.conf file 7. make sure to set the following options: rpcuser, rpcpassword and onlynet=i2p 8. (Optional) you can set i2p=1 instead of onlynet=i2p Example: rpcuser=someone rpcpassword=super_secret_password onlynet=i2p Note The difference between i2p=1 and onlynet=i2p is that i2p=1 allows the Anoncoin client to interact with clearnet/Tor also. While onlynet=i2p will only connect to I2P nodes. Fantastic. In a crypto-to-crypto trading environment, privacy like this is assuring. Great work on this. P.S. Does that mean i2p anoncoin can only transact with other i2p-connected anoncoiners? If you use the "onlynet=i2p" flag your client will only connect with i2p nodes. But like I, use some nodes with "i2p=1" which works like a "gateway" between I2P and clearnet(internet) making sure the I2P network is synced with the network on clearnet(internet) and TOR. The same rules would apply for e.g "onlynet=tor". |
|
|
|
Thanks for all the feedback  Just a heads up on the main AnonCoin.net "About Coin" Page #4 has a misspelling in the first word Strength : "Strengt in numbers. Crypto, Services, and users." https://anoncoin.net//TheCoin.htmlThanks for noticing and reporting!  Spelling is corrected |
|
|
|
Glad to welcome Anoncoin to the Cryptsy.com family!
Thanks for adding it to Cryptsy |
|
|
|
I cant sync the wallet  , i add some node, but cant sync the wallet . Can some oen send me some new node ? Here are some clearnet nodes; 198.144.187.112 54.214.83.193 193.150.121.24 193.150.121.28 141.0.73.226 172.31.9.115 172.245.219.144 173.213.80.183 74.91.18.186 199.48.160.234 193.150.121.66 193.150.121.68 193.150.121.69 Hope this will help you! |
|
|
|
How does one use this with i2p?
To use the daemon on I2P ONLY do the following: 1. Download and install I2P ( www.geti2p.net ), then start it. (It will run as a daemon, so don't expect any window) 2. Wait a minute or two, then navigate to http://127.0.0.1:7657/configclients3. Make sure to start the "SAM application bridge" (Tip: After starting it, check it for autostart and save configuration) 4. In run (enter the start menu and type run on windows Vista/7) type %appdata% 5. Open or create the Anoncoin folder 6. Create/edit the anoncoin.conf file 7. make sure to set the following options: rpcuser, rpcpassword and onlynet=i2p 8. (Optional) you can set i2p=1 instead of onlynet=i2p Example: rpcuser=someone rpcpassword=super_secret_password onlynet=i2p Note The difference between i2p=1 and onlynet=i2p is that i2p=1 allows the Anoncoin client to interact with clearnet/Tor also. While onlynet=i2p will only connect to I2P nodes. |
|
|
|
Thanks for all the feedback |
|
|
|
Thanks man, i bet the coin will e on cryptsy soon, im in there all the time, im trying to promote it to the exchange!
And thank you for promoting it to the exchange  |
|
|
|
Great coin guys its number 1 on coinchoose been reading the threads for a while now, i think this coin has greatness in it, thumbs up for the devs! If you want to give some love heres my adress
AJyphwUsRYQsJQnNKJ1mgAiYMKKAQTdf7X
Thanks and keep up the great work!
Thanks a lot We had a dev meeting yesterday and a new client should be out within the next two days with many changes, also including the GUI changes in screenshots above. That client should be mandatory within three months. I will get back on this thread with a full changelog I sent you some coins |
|
|
|
I've added Anoncoin to my big beta altchain block explorer at http://altcha.in/chain/Anoncoin. It's still in development and I'm working to add more chains but it is available most of the time. I sometimes take it down to load additional chains. Donations accepted at ALtCoinY7h8GAUTsWioN2Viv4WPN2VKq2A Cheers! Thanks sent you some ANC |
|
|
|
I am having a hard time keeping connections on the anoncoind client. I am watching the log and see a lot of IP's with random other ports coming in like 9200,1901,9378 vs the majority athat are 9377 as I think is expected. When I grab the IP's with odd ports (that are refused connections) and change the port to 9377 I can connect and if I add the modified IP:port to my config its a new connection. This seems like odd behavior?
Thanks for the report. I will start dig into it right away. I think it might be related to the darknet support, since I2P and TOR doesn't use ip:port the same way as tcp does. I'll update this post when I've found out of it. |
|
|
|
could u check my account too?
Your balance is updated |
|
|
|
Giving a pool a shot again, I started a few others only to find the mmcfe front end was ripping users off, however this fork is very active and seem to be pretty legit, https://github.com/TheSerapher/php-mmcfe-ng I hope they keep working the bugs out of the old mmcfe that is pretty useless for altcoins now. Come and try it out if you like and if my theory that this new front end is better! I could use a few k to see if its working well! http://anc.usr.ioproportional payout stratum only @ stratum+tcp://anc.usr.io:3333 Thanks, I will add it to the wiki @ github I started a few others only to find the mmcfe front end was ripping users off
Yes, it seems so, but it only affects some users. I will dig into this.
Hmmm... I just mined for some hours, found many blocks, "Paid shares: 31626" and got only 3.49 coins. Can't be right...
I checked the logs and updated your balance. It seems to be the bug mentioned above here. I will research it, and fix the problem. Same I found 6 blocks on my own pool now so payout of 42 coins in 2 hours vs the 1.6 coins in 5 hours, something off. Updated yours balance as well. |
|
|
|
Trying to compile on Debian... diatonic@alt:~/anoncoin/src$ make -j1 -f makefile.unix USE_UPNP=-
make -C ../i2psam -f makefile.unix
make[1]: Entering directory `/home/diatonic/anoncoin/i2psam'
g++ -c -m64 -pipe -O2 -fPIC -Wall -W -D_REENTRANT -o i2psam.o i2psam.cpp
i2psam.cpp: In member function ‘void SAM::Socket::close()’:
i2psam.cpp:195:9: error: ‘::close’ has not been declared
make[1]: *** [i2psam.o] Error 1
make[1]: Leaving directory `/home/diatonic/anoncoin/i2psam'
make: *** [i2psam] Error 2 help? We have verified that the code does compile successfully on Ubuntu 12.04 LTS. I do not know why it would fail on Debian. Can you tell us which Debian and g++ you are using? I will setup a lab machine with the same version to do troubleshooting. I can not compile the daemon or the qt version on Ubuntu 13.04, I get the same errors. I was able to compile on Ubuntu 13.04 with standard libraries from the dpkg system with the code from my last commit. (Commited minutes ago) So please try a "git pull origin master" and then try build again. I hope this works for you as well |
|
|
|
|
I've found out the i2psam library will build successfully on a linux with boost version 1.4.6, but not with boost version 1.4.9. I'm working on a fix now.
|
|
|
|
Even the newest QT has runtime errors. Dear..
Could you report any productive information instead of just saying "it's not working"? * What says the crash report? * When did it happen? * Was you doing anything on the client? * Does it complain about a dll? * Windows 7? 8? xp? * Optional: screenshot? A serious bugreport would include that information. Before you can provide any more information other than "it's not working" we can't know what your problem is and it would not be fixed until someone more helpful reports it. The windows version is always tested on at least 4 windows computers before it reaches release stage. So if you're having problem, please report them in details. |
|
|
|
Trying to compile on Debian... diatonic@alt:~/anoncoin/src$ make -j1 -f makefile.unix USE_UPNP=-
make -C ../i2psam -f makefile.unix
make[1]: Entering directory `/home/diatonic/anoncoin/i2psam'
g++ -c -m64 -pipe -O2 -fPIC -Wall -W -D_REENTRANT -o i2psam.o i2psam.cpp
i2psam.cpp: In member function ‘void SAM::Socket::close()’:
i2psam.cpp:195:9: error: ‘::close’ has not been declared
make[1]: *** [i2psam.o] Error 1
make[1]: Leaving directory `/home/diatonic/anoncoin/i2psam'
make: *** [i2psam] Error 2 help? Could you run: dpkg -l | grep boostAnd paste the boost version here. I think this is a boost issue. Working on it now |
|
|
|
diff increase...some people go away..saddddd..  No it was just one, and it was me. My rig crashed and I can't do anything while at work. Wll be back when I'm home |
|
|
|
yes..i think you should payout soon..i have for some hours..i didn't see my ballance increase..so i stoped..now..every thing ok..i 'am still mining..
You got ... "new balance" Sorry the delay, I had to check logs and the database to make sure you got the right amout + some extra for the inconvenience. I will update again in some hours. |
|
|
|
Client update!New windows builds are out. Some potential buffer overflows where detected while building with i586-mingw32-msvc (GCC 4.4). This build is built with i686-w64-mingw32 (GCC 4.6) and the problems got solved. Note If you still use the first release, you must upgrade now. The protocol has switched and you will be unable to receive new blocks until you have upgraded. Note2 If you upgraded to 0.7.2.2, please upgrade/redownload since the potential buffer overflows could result in the client doing odd things. Links: http://anoncoin.net/downloads/anoncoin-0.7.2.3-win32-setup.exe - Installer (QT Client, daemon & source) http://anoncoin.net/downloads/anoncoin-qt-7.2.3-win32.zip - Zip file (QT Client, daemon & source) http://anoncoin.net/downloads/anoncoin-daemon-7.2.3.zip - Zip file (Daemon & source) OSX UpdateThe OSX version is built dynamically and seems to work fine. Before a release it needs to be recompiled and the required libraries is needed to be included in the bundle. Release should happen within few days. Maybe even later today.
|
|
|
|
|
Show Posts
