sorry, i stopped to read at line #9
Quote
Risto Pietila
aka rpietila
aka smooth
But thanks anyway for the fun.aka rpietila
aka smooth
Topic: [ANN] AEON [2019-09-27: Upgrade to version 0.13.0.0 ASAP HF@1146200 Oct 25] - page 195. (Read 625666 times)
December 26, 2015, 06:54:18 AM
sorry, i stopped to read at line #9
December 26, 2015, 03:02:55 AM
You're the guy who called spoetnik a genius, so sorry if I don't take you at your word. Do you have proof of this scam accusation? I'd like some proof of spot's genius too, but I know that isn't happening.
December 24, 2015, 11:19:22 AM
you can also give a try to myagui's build here: https://bitcointalksearch.org/topic/m.12800804
December 23, 2015, 09:13:20 PM
December 23, 2015, 05:14:32 PM
Is anyone mining with Nvidia GTX970?
What miner should I use on windows?
What miner should I use on windows?
December 22, 2015, 04:53:00 PM
...
Our friends over at Monero (moneromooo in particular) have figured out how to use Tor with Cryptonote coins using the torsocks wrapper, so you can enjoy using AEON with Tor-protected anonymity at the network level.
...
There is probably a way to do something similar on Windows, but I don't know it. Anyone?
Our friends over at Monero (moneromooo in particular) have figured out how to use Tor with Cryptonote coins using the torsocks wrapper, so you can enjoy using AEON with Tor-protected anonymity at the network level.
...
There is probably a way to do something similar on Windows, but I don't know it. Anyone?
according to the tor faq, there is freecap http://freecap.ru/eng/ and torcap http://www.freehaven.net/~aphex/torcap/. i noticed also torcap2 at https://github.com/cpatulea/TorCap2
torcap gave me nothing, no activity into the log...
torcap2 return "error injected hook in the process"
freecap is a 9 years old freeware
, i configured it with socks4 (socks4a not available) on port 9050 (tor is running). i'm able to launch aeond via freecap but how i can check anonymity of aeond? freecap log is enable but log file is not created. December 22, 2015, 05:55:19 AM
TOR is a great addition.
No one should have ever put a DNS dependency in a coin. DNS is essentially fucked up in terms of security, privacy and decentralization.
...
In the case of Monero there are some issues with DNS being blocked and required some code changes, but AEON does not use DNS, so we don't have to worry about that issue at all.
...
In the case of Monero there are some issues with DNS being blocked and required some code changes, but AEON does not use DNS, so we don't have to worry about that issue at all.
...
No one should have ever put a DNS dependency in a coin. DNS is essentially fucked up in terms of security, privacy and decentralization.
December 21, 2015, 04:53:27 PM
Good news!
Our friends over at Monero (moneromooo in particular) have figured out how to use Tor with Cryptonote coins using the torsocks wrapper, so you can enjoy using AEON with Tor-protected anonymity at the network level.
1. Make sure you are running a Tor demon. With Ubuntu Linux you can just apt-get install tor and you'll be all set
2. torsocks aeond --p2p-bind-ip 127.0.0.1 --hide-my-port
In the case of Monero there are some issues with DNS being blocked and required some code changes, but AEON does not use DNS, so we don't have to worry about that issue at all.
There is one message (harmless) that gets reported during IGD (UPnP) setup, but that can be ignored. I added a --no-igd option in github, so you can use that to get rid of the message if you build from the latest source, but it isn't really necessary.
Depending on the version of torsocks you have installed, you may get some messages about missing symbols. Those can also be ignored.
There is probably a way to do something similar on Windows, but I don't know it. Anyone?
Our friends over at Monero (moneromooo in particular) have figured out how to use Tor with Cryptonote coins using the torsocks wrapper, so you can enjoy using AEON with Tor-protected anonymity at the network level.
1. Make sure you are running a Tor demon. With Ubuntu Linux you can just apt-get install tor and you'll be all set
2. torsocks aeond --p2p-bind-ip 127.0.0.1 --hide-my-port
In the case of Monero there are some issues with DNS being blocked and required some code changes, but AEON does not use DNS, so we don't have to worry about that issue at all.
There is one message (harmless) that gets reported during IGD (UPnP) setup, but that can be ignored. I added a --no-igd option in github, so you can use that to get rid of the message if you build from the latest source, but it isn't really necessary.
Depending on the version of torsocks you have installed, you may get some messages about missing symbols. Those can also be ignored.
There is probably a way to do something similar on Windows, but I don't know it. Anyone?
Thank you moneromooo and smooth! I retweeted your announcement https://twitter.com/AeonCoin/status/678890981136056320
December 21, 2015, 05:49:26 AM
Good news!
Our friends over at Monero (moneromooo in particular) have figured out how to use Tor with Cryptonote coins using the torsocks wrapper, so you can enjoy using AEON with Tor-protected anonymity at the network level.
1. Make sure you are running a Tor demon. With Ubuntu Linux you can just apt-get install tor and you'll be all set
2. torsocks aeond --p2p-bind-ip 127.0.0.1 --hide-my-port
In the case of Monero there are some issues with DNS being blocked and required some code changes, but AEON does not use DNS, so we don't have to worry about that issue at all.
There is one message (harmless) that gets reported during IGD (UPnP) setup, but that can be ignored. I added a --no-igd option in github, so you can use that to get rid of the message if you build from the latest source, but it isn't really necessary.
Depending on the version of torsocks you have installed, you may get some messages about missing symbols. Those can also be ignored.
There is probably a way to do something similar on Windows, but I don't know it. Anyone?
Our friends over at Monero (moneromooo in particular) have figured out how to use Tor with Cryptonote coins using the torsocks wrapper, so you can enjoy using AEON with Tor-protected anonymity at the network level.
1. Make sure you are running a Tor demon. With Ubuntu Linux you can just apt-get install tor and you'll be all set
2. torsocks aeond --p2p-bind-ip 127.0.0.1 --hide-my-port
In the case of Monero there are some issues with DNS being blocked and required some code changes, but AEON does not use DNS, so we don't have to worry about that issue at all.
There is one message (harmless) that gets reported during IGD (UPnP) setup, but that can be ignored. I added a --no-igd option in github, so you can use that to get rid of the message if you build from the latest source, but it isn't really necessary.
Depending on the version of torsocks you have installed, you may get some messages about missing symbols. Those can also be ignored.
There is probably a way to do something similar on Windows, but I don't know it. Anyone?
December 09, 2015, 04:24:17 AM
Min difficulty increased to 10k at http://52.8.47.33:8080
my bandwith is limited and with fixed diff as low as 2k, bill was growing too much.
but i'm not sure that low fixed diff is the guilty, the api was draining a lot of bandwith too, the refresh rate of the front-end is now lowered at 30s. i will see how it's possible to lower min diff according to bandwith consumption.
my bandwith is limited and with fixed diff as low as 2k, bill was growing too much.
but i'm not sure that low fixed diff is the guilty, the api was draining a lot of bandwith too, the refresh rate of the front-end is now lowered at 30s. i will see how it's possible to lower min diff according to bandwith consumption.
December 06, 2015, 04:04:13 AM
I read somewhere that Aeon plans to use the Monero db code once it is finalized and released. Are there any short term development goals for Aeon right now? Or are we essentially waiting on the Monero db to port to Aeon before more development continues?
I have used both 9.6 and the pruning branch and am happy with the results. Keep up the great work!
I have used both 9.6 and the pruning branch and am happy with the results. Keep up the great work!
The primary current short term goal is merging the Cryptonote reference GUI (which in turn is based on Bitcoin-Qt). It is mainly going slowly due to limited development time. It won't be held up waiting for the DB merge, nor vice versa. There are also some other blockchain and wallet improvements I have lined up to go into new releases but aren't enough to motivate a new release on their own yet.
December 06, 2015, 01:42:35 AM
I read somewhere that Aeon plans to use the Monero db code once it is finalized and released. Are there any short term development goals for Aeon right now? Or are we essentially waiting on the Monero db to port to Aeon before more development continues?
I have used both 9.6 and the pruning branch and am happy with the results. Keep up the great work!
I have used both 9.6 and the pruning branch and am happy with the results. Keep up the great work!
December 04, 2015, 10:36:59 PM
Did you try the pruning branch? If you are that close, the savings from pruning should be more than enough make it work.
Is it on your github? I didn't see any links to it on the front page, so I just went with the main source.
Sorry, finding it is slightly obscure since it is officially just a test release. It has gotten quite a bit of testing though, perhaps enough to promote it to a link on the first page. You can skip step 1 if you just want to sync from scratch. The file copy is only needed to convert an existing blockchain file.
Pruning (aka Light Full Node) test release
This release optionally prunes the blockchain by dropping no-longer-needed information once it is processed and verified by your node. This reduces both memory and storage requirements, and perhaps more importantly reduces the rate at which both increase over time. With pruning enabled, the daemon continues to function as a full node on the network in nearly every way. I will be posting a FAQ to answer some other questions about the details of the pruning functionality.
Please test, especially if you have a smaller memory configuration. Very small memory configurations (<2 GB? -- I'm not sure) won't work with this, but if you have something that has been barely able to run the daemon previously, this should improve your performance quite a bit. Certainly some smaller-memory systems (at a minimum 3-4 GB of RAM, if not smaller) should be able to successfully run a node now. I'm not sure if any 32-bit operating systems can handle it, although it is possible.
Since converting an existing blockchain requires enough RAM to at least load it first, resyncing from scratch with the --pruning option may be a better option for smaller-memory systems until pruned bootstraps become available.
Instructions:
1. Copy your blockchain.bin file to blockchain-pruned.bin in the same location. The daemon uses different files to store the pruned and unpruned versions of the blockchain. Once testing is complete if you want to delete the unpruned blockchain to free up disk space that is fine, but I don't recommend it right away EDIT: there have been some issues with compatibility of the .bin files so I recommend backing up all of those files before using a test release.
2.
3. Start node with the --pruning option. You should get a message at startup about the blockchain being pruned (this is done using the blockchain-pruned.bin file; your original blockchain.bin file is unchanged).
4. Exit node to save the pruned blockchain and reset RAM usage.
5. Start node again with the --pruning option.
6. If any problems occur you can switch back to unpruned (start daemon without --pruning)
Report any issues (or even if no issues)
Limitations: a pruned node can not be used to rescan or restore a wallet that is older than the pruning period (10 000 blocks, or about 28 days). Also, if a pruned node is disconnected from the network for more than the duration of this pruning period, it will potentially not be able to recover on its own, and will need to be resynced from scratch or with a bootstrap. The second restriction is fixable and can be addressed later. Otherwise it should be functionality complete.
Neither this test release nor the pruning feature is recommended for important nodes such as pools, exchanges, etc. Please continue to use the standard version at this time for those purposes.
Thanks for testing!
This release optionally prunes the blockchain by dropping no-longer-needed information once it is processed and verified by your node. This reduces both memory and storage requirements, and perhaps more importantly reduces the rate at which both increase over time. With pruning enabled, the daemon continues to function as a full node on the network in nearly every way. I will be posting a FAQ to answer some other questions about the details of the pruning functionality.
Please test, especially if you have a smaller memory configuration. Very small memory configurations (<2 GB? -- I'm not sure) won't work with this, but if you have something that has been barely able to run the daemon previously, this should improve your performance quite a bit. Certainly some smaller-memory systems (at a minimum 3-4 GB of RAM, if not smaller) should be able to successfully run a node now. I'm not sure if any 32-bit operating systems can handle it, although it is possible.
Since converting an existing blockchain requires enough RAM to at least load it first, resyncing from scratch with the --pruning option may be a better option for smaller-memory systems until pruned bootstraps become available.
Instructions:
1. Copy your blockchain.bin file to blockchain-pruned.bin in the same location. The daemon uses different files to store the pruned and unpruned versions of the blockchain. Once testing is complete if you want to delete the unpruned blockchain to free up disk space that is fine, but I don't recommend it right away EDIT: there have been some issues with compatibility of the .bin files so I recommend backing up all of those files before using a test release.
2.
Quote
3. Start node with the --pruning option. You should get a message at startup about the blockchain being pruned (this is done using the blockchain-pruned.bin file; your original blockchain.bin file is unchanged).
4. Exit node to save the pruned blockchain and reset RAM usage.
5. Start node again with the --pruning option.
6. If any problems occur you can switch back to unpruned (start daemon without --pruning)
Report any issues (or even if no issues)
Limitations: a pruned node can not be used to rescan or restore a wallet that is older than the pruning period (10 000 blocks, or about 28 days). Also, if a pruned node is disconnected from the network for more than the duration of this pruning period, it will potentially not be able to recover on its own, and will need to be resynced from scratch or with a bootstrap. The second restriction is fixable and can be addressed later. Otherwise it should be functionality complete.
Neither this test release nor the pruning feature is recommended for important nodes such as pools, exchanges, etc. Please continue to use the standard version at this time for those purposes.
Thanks for testing!
December 04, 2015, 10:25:55 PM
Nevermind, my hashrate just exploded! Maybe I wasn't fully synced earlier.
hashrate: 77.1579
hashrate: 77.1579
Make sure you are fully utilizing your cache. This may require more threads than Monero, depending on your core count and cache size, and whether hyperthreads are supported.
Don't expect great efficiency without AES-NI though. Still, better than nothing.
December 04, 2015, 09:06:22 PM
Nevermind, my hashrate just exploded! Maybe I wasn't fully synced earlier.
hashrate: 77.1579
hashrate: 77.1579
December 04, 2015, 08:28:26 PM
hashrate: 0.3158
is that normal?
mining monero on the same machine i'd be getting like 30-40 H/s
Did you try the pruning branch? If you are that close, the savings from pruning should be more than enough make it work.
Is it on your github? I didn't see any links to it on the front page, so I just went with the main source.
My HR for Monero is 35 H/s and for Aeon it's 86 H/s for a modern Pentium dual core non AES-NI
(running both cores)
December 04, 2015, 08:16:26 PM
hashrate: 0.3158
is that normal?
mining monero on the same machine i'd be getting like 30-40 H/s
Did you try the pruning branch? If you are that close, the savings from pruning should be more than enough make it work.
Is it on your github? I didn't see any links to it on the front page, so I just went with the main source.
December 04, 2015, 07:11:14 PM
Thanks smooth.
I had 4G of swap already, but I'm trying again now with 6G! Let's go!
I had 4G of swap already, but I'm trying again now with 6G! Let's go!
Did you try the pruning branch? If you are that close, the savings from pruning should be more than enough make it work.
December 04, 2015, 06:14:10 PM
Thanks smooth.
I had 4G of swap already, but I'm trying again now with 6G! Let's go!
I had 4G of swap already, but I'm trying again now with 6G! Let's go!
December 04, 2015, 01:18:38 PM
Trying to sync the 0.9.6 aeond for the first time, the daemon keeps getting killed for some reason...any ideas?
Then I start it up again and I have to start syncing the blockchain from 0.
I'm also running bitmonerod on this machine, so maybe its too much for it to handle at the same time?
edit: After starting over, the daemon gets killed at the same point, just after the checkpoint for 540000.
Then I start it up again and I have to start syncing the blockchain from 0.
I'm also running bitmonerod on this machine, so maybe its too much for it to handle at the same time?
Code:
2015-Dec-03 23:40:32.289786 [P2P2]CHECKPOINT PASSED FOR HEIGHT 540000 <94e19cf9d5a16ae90f67c321f8376b87da21d6d6c2cb0957b9ab558dca66c1dc>
Killed
Killed
edit: After starting over, the daemon gets killed at the same point, just after the checkpoint for 540000.
That seems like out of memory (Linux "OOM killer"). You can try the pruning branch which uses somewhat less. You can also try adding a bit of swap on your system. If the shortfall isn't too large, swap will help without performance being too terrible. Installing the dphys-swapfile package on Ubuntu will manage swap automatically for you, not sure if there is a non-manual swap solution on other distros.
Jump to: