Author

Topic: [ANN] AEON [2019-09-27: Upgrade to version 0.13.0.0 ASAP HF@1146200 Oct 25] - page 223. (Read 625666 times)

member
Activity: 115
Merit: 10
I should clarify, I did a rescan connected to a pruned node using my wallet.keys file, so it scanned from the beginning...
Had I used my synched up wallet file then yes my balance would not be affected.  Grin


Now that's odd. I don't think any received payments should be missing (so for example fully cold storage wallets are okay to do this) only if you had made payments out of the wallet those would not be rescanned.

If you can take a closer look and maybe provide details (PM is okay) that would be helpful.

sr. member
Activity: 309
Merit: 250
I just ran pruned client , double checking instructions and didn't see any reduction in RAM usage. Copied blockchain.bin to desktop, renamed blockchain-pruned.bin, pasted back into appdata Aeon folder. Run new client, saw pruning in the log, save after sync. Re-run client as batch file (aeond.exe --pruning) , resync and rechecked RAM useage is the same. Did I miss something? 
legendary
Activity: 2968
Merit: 1198
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.

I had a chance to test this out. It freed up about 1GB in both RAM and file size for blockchain-pruned.bin
This is a significant saving, indeed!

However, I wonder if users should really run pruned nodes knowing LMDB will be added in the near future.

It's complementary. The disk savings are permanent and ever-increasing. The current LMDB doubles the starting disk footprint too, although hopefully that ratio can be improved.

Quote
Additionally, they might unknowingly run a pruned node and find out some of their coins may not be showing up in the balance. I tested an old wallet and sure enough, with pruned blocks simplewallet cannot verify all so my total balance of coin came up less than expected. Is there a safeguard in simplewallet that can be implemented to tell the user that he must synch with an archive node?

Now that's odd. I don't think any received payments should be missing (so for example fully cold storage wallets are okay to do this) only if you had made payments out of the wallet those would not be rescanned.

If you can take a closer look and maybe provide details (PM is okay) that would be helpful.


Quote
I realized many are bitching about not having enough memory to run the daemon and such, and this is a great solution; but let's get real....4 extra GB of RAM is less than $20 these days so everyone should have at least 8GB RAM on their systems. Smiley  
But I'm guessing pruned nodes are targeted for mobile devices?

The storage savings is a big deal for mobile and embedded devices (we want people to run always-on nodes at very low power and cost) but also for cheap computers. There are a bunch of $100-$150 laptops now that are quite usable but ship with 32 GB of SSD storage, non-upgradable. They'll run AEON nodes just fine but not if the blockchain grows to much. Bitcoin has a 40 GB blockchain right now. Not even possible to run an unpruned node on those computers even if you wanted to.
member
Activity: 115
Merit: 10
Apologies for this TLDR question: Do I need to run the client on each comp where I want solo (gpu)?

The only way to solo mine with a GPU is to run your own pool, since the built in daemon miner can't GPU mine and the GPU miners can't connect directly to the daemon. As I am looking at setting up a pool I may have more advice on this later. EDIT: I see exciter0 posted some instructions. Thanks exciter0!

Likewise, if you run your own pool you can have as many of your own computers connecting to it as you want and you are still effectively solo mining.
Very nice!! yes thank you exciter0 ....I'm  running Windows 2008 on a Dell R410...But I'm thinking of wiping it for Linux. I'm decent at Linux and need to keep learning, any suggestions for what flavor to run on that server so as to use it as a pool machine??  Or anyone out there with a cryptonote pool "how to " for Windows?

You can always run ubuntu as a hyperv VM... or better yet, run Windows 2008 as a linux KVM VM. As for myself, I run my pool as a vm on VMware esxi. I would stick with plain Ubuntu, even though Linux Mint is more pleasing visually.
member
Activity: 115
Merit: 10
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.

I had a chance to test this out. It freed up about 1GB in both RAM and file size for blockchain-pruned.bin
This is a significant saving, indeed!

However, I wonder if users should really run pruned nodes knowing LMDB will be added in the near future.
Additionally, they might unknowingly run a pruned node and find out some of their coins may not be showing up in the balance. I tested an old wallet and sure enough, with pruned blocks simplewallet cannot verify all so my total balance of coin came up less than expected. Is there a safeguard in simplewallet that can be implemented to tell the user that he must synch with an archive node?

I realized many are bitching about not having enough memory to run the daemon and such, and this is a great solution; but let's get real....4 extra GB of RAM is less than $20 these days so everyone should have at least 8GB RAM on their systems. Smiley 
But I'm guessing pruned nodes are targeted for mobile devices?
sr. member
Activity: 309
Merit: 250
Apologies for this TLDR question: Do I need to run the client on each comp where I want solo (gpu)?

The only way to solo mine with a GPU is to run your own pool, since the built in daemon miner can't GPU mine and the GPU miners can't connect directly to the daemon. As I am looking at setting up a pool I may have more advice on this later. EDIT: I see exciter0 posted some instructions. Thanks exciter0!

Likewise, if you run your own pool you can have as many of your own computers connecting to it as you want and you are still effectively solo mining.
Very nice!! yes thank you exciter0 ....I'm  running Windows 2008 on a Dell R410...But I'm thinking of wiping it for Linux. I'm decent at Linux and need to keep learning, any suggestions for what flavor to run on that server so as to use it as a pool machine??  Or anyone out there with a cryptonote pool "how to " for Windows?
legendary
Activity: 2968
Merit: 1198
Apologies for this TLDR question: Do I need to run the client on each comp where I want solo (gpu)?

The only way to solo mine with a GPU is to run your own pool, since the built in daemon miner can't GPU mine and the GPU miners can't connect directly to the daemon. As I am looking at setting up a pool I may have more advice on this later. EDIT: I see exciter0 posted some instructions. Thanks exciter0!

Likewise, if you run your own pool you can have as many of your own computers connecting to it as you want and you are still effectively solo mining.
member
Activity: 115
Merit: 10
Can somebody give me a brief summary of what I need to do to set up a pool. I've done it a few times before (for XMR) but I'm not really up on which versions of the code to use for AEON, any patches needed, etc.

Post if you feel it is of general interest, otherwise PM.

Thanks!

Pretty much the same steps to getting a xmr pool working. Use MoneroMoo's fork, he has already added CN-lite.

Trying to remember the steps here, I used Ubuntu 15.04, but should be the same steps as on 14.04...

Assuming everything's installed on the same server, start up the daemon and simplewallet:

Code:
aeond --rpc-bind-ip 1.2.3.4 --rpc-bind-port 9998
simplewallet --wallet-file aeon-pool-wallet.bin --daemon-address 1.2.3.4:9998

I used non-default rpc port 9998 since I run many pools on the same server ;-)

Then install the pre-reqs and the pool code:
Code:
apt-get install git redis-server libboost1.55-all-dev nodejs-dev nodejs-legacy npm cmake libssl-dev
service redis-server start
git clone https://github.com/moneromooo/cryptonote-universal-pool aeon-pool
cd aeon-pool
git checkout aeon-light
npm rebuild

Then edit  ~/aeon-pool/config.json
I disabled payments since it's a private pool...and I made sure the pool fee is 100%  Wink
Code:
{
    "coin": "AEON",
    "symbol": "AEON",

 ...

    "poolServer": {
        "enabled": true,
        "clusterForks": "auto",
        "poolAddress": "WmthHeYEvTz5kSgsJviaVKEEExkRZZLduB5pfrJ2aWWf3m1dE7PTvdxKVyc9MAuhbCSisqe69uopkKiq2rbxbpzY2zeRRMGAp",
        "blockRefreshInterval": 500,
        "minerTimeout": 5000,
        "ports": [
            {
                "port": 5555,
                "difficulty": 30000,
                "desc": "Mid range hardware"
            },
            {
                "port": 4321,
                "difficulty": 40000,
                "desc": "High end hardware"
            }

...

    "payments": {
        "enabled": false,
        "interval": 600,
        "maxAddresses": 50,
        "mixin": 0,
        "transferFee": 5000000000,
        "minPayment": 100000000000,
        "denomination": 100000000000
    },
    "api": {
        "enabled": true,
        "hashrateWindow": 600,
        "updateInterval": 5,
        "port": 8118,
        "blocks": 30,
        "payments": 30,
        "password": "secret"
    },

    "daemon": {
        "host": "1.2.3.4",
        "port": 9998
    },

    "wallet": {
        "host": "1.2.3.4",
        "port": 8082
    },

    "redis": {
        "host": "127.0.0.1",
        "port": 6379
    }

start the pool with node init.js

Open another terminal and install your favorite web server:
apt-get install nginx
copy the aeon pool web pages to the doc root directory
Code:
mkdir /var/www/html/aeon
cp ~/aeon-pool/website-example/* /var/www/html/aeon

edit /var/www/html/aeon/config.js
Code:
var api = "http://1.2.3.4:8118";

var coinUnits = 1000000000000;

var poolHost = "1.2.3.4";

var irc = "irc.freenode.net/#";

var email = "support@localhost";

var cryptonatorWidget = ["AEON-BTC", "AEON-USD"];

var easyminerDownload = "https://github.com/zone117x/cryptonote-easy-miner/releases/";

var blockchainExplorer = "http://chainradar.com/aeon/block/";

var transactionExplorer = "http://chainradar.com/aeon/transaction/";

I think there's one more edit to either /var/www/html/aeon/index.html or /var/www/html/aeon/pages/home.html to get the hashrate to report correctly...

EDIT:  Here we go, you need to edit /var/www/html/aeon/pages/home.html to get it to show the hashrate properly...change from 60 to 240
Code:
       update: function(){

            $('#networkLastBlockFound').timeago('update', new Date(lastStats.network.timestamp * 1000).toISOString());

            updateText('networkHashrate', getReadableHashRateString(lastStats.network.difficulty / 240) + '/sec');

Credits to Moneromoo, he helped me out through PM and from his postings.
sr. member
Activity: 309
Merit: 250
@SRBOOTH:

There's no external GPU solo miners for any cryptonote as far as I know. Most definitely not for nvidia, since ccminer will only work with pools. If you really want to solo mine with nvidias (or AMDs AFAIK), you'll need to setup a private pool. That should be an interesting/fun project btw.  Smiley Happy Mining!

Edit: on the pruned version compiled for windows, I've posted (unofficial) binaries just yesterday:
https://bitcointalksearch.org/topic/m.12285871

Official ones should not take long I suppose, since Arux is back from all his summer partying  Grin

Edit ^2: the light-node (pruned) working well for me so far. I have made a couple of transfers without any issues, I have solo mined a block, and have gone through the cycle seeing a misbehaving peer get blocked. Good stuff!   Wink

Sweet!! and thanks for the info @myagui !! I am going to try and set a pool up for myself , I think smooth was looking to do the same.
legendary
Activity: 1154
Merit: 1001
@SRBOOTH:

There's no external GPU solo miners for any cryptonote as far as I know. Most definitely not for nvidia, since ccminer will only work with pools. If you really want to solo mine with nvidias (or AMDs AFAIK), you'll need to setup a private pool. That should be an interesting/fun project btw.  Smiley Happy Mining!

Edit: on the pruned version compiled for windows, I've posted (unofficial) binaries just yesterday:
https://bitcointalksearch.org/topic/m.12285871

Official ones should not take long I suppose, since Arux is back from all his summer partying  Grin

Edit ^2: the light-node (pruned) working well for me so far. I have made a couple of transfers without any issues, I have solo mined a block, and have gone through the cycle seeing a misbehaving peer get blocked. Good stuff!   Wink
sr. member
Activity: 309
Merit: 250
Apologies for this TLDR question: Do I need to run the client on each comp where I want solo (gpu)? I currently am running a full windows version. I can't get the gpu's to connect to the wallet in the same network. Port 11181?? I solo mine 1 wallet (not a cryptonote coin)  from 3 different comps in the same network all the time. I have never gpu solo'd a cryptonote. Could someone point me to a good set of instructions please??

I want to set this up in anticipation of running the pruned version when the windows compilation comes out Smiley
Thanks in advance!
hero member
Activity: 592
Merit: 500
I think that's a shame since you would expect a minimum of functionality as an incentive for someone to set-up a full node for this coin.
legendary
Activity: 2968
Merit: 1198
I really like this one. Heard about Aeon coin mining being enabled for android devices.
Any update regarding this topic?

Not yet demonstrated, but the code should compile on Android if someone wants to try it.
legendary
Activity: 1596
Merit: 1027
I really like this one. Heard about Aeon coin mining being enabled for android devices.

Any update regarding this topic?
legendary
Activity: 1154
Merit: 1001
Thanks GingerAle,
That is exactly the performance range I would expect, like Smooth was saying, roughly double the performance of regular cryptonight. You can definitely get it to run faster with overclocking, as cryptonight & cryptonight-light are more tolerant to overclocking than most other algorithms. Anyhow, looking really good, cheers!

Also a +1 about drivers, some versions are faster, others are slower. Even across different systems, it's not always the same driver that performs best (cards on risers vs cards directly on slots, paired with fast CPU vs paired with slow CPU, etc).

I didn't run it for long, but

-l 32x30

got me 520 on the 750 ti, and 578 h/s on that PNY OC version of the 750 ti (the one with 1220 clocks).

I also used nvidia 331 drivers. The driver version can affect things.
legendary
Activity: 1260
Merit: 1008
I didn't run it for long, but

-l 32x30

got me 520 on the 750 ti, and 578 h/s on that PNY OC version of the 750 ti (the one with 1220 clocks).

I also used nvidia 331 drivers. The driver version can affect things.

edited to add: this was on ubuntu 14.043
legendary
Activity: 1154
Merit: 1001
Correct smooth. But what I've seen in my limited experience here (as I don't have the ideal GPU models), is that without specific tuning for cryptonight-light, the performance will not automagically double, using the same launch settings as for regular cryptonight. I had observed ccminer hashing just marginally faster, if selecting cryptonight-light vs cryptonight on the same baseline settings (at least on Windows).

With proper launch settings, yes, the performance should be roughly double that of regular cryptonight. With ccminer, the ideal cryptonight-light performance, is probably found by using a launch string that uses double the number of threads as for regular cryptonight - in order to take advantage of the smaller workload.
As I understand, the ccminer thread synchronization and memory access behaves very differently in Linux, causing Linux miners to see most of the cryptonight-light gains even without tuning their launch parameters. In any case, proper tuning will provide the best results.
legendary
Activity: 2968
Merit: 1198
I don't have the proper launch settings for the 750TI myself though, don't have those cards anymore. I do have reports of cryptonight-light performance in the region of 500 h/s on these cards

Well look, the algorithm has half the iterations of regular cryptonight so at a bare minimum the hash rate should be close to 2x.

Anything less than that indicates a severe tuning problem.
legendary
Activity: 1154
Merit: 1001
Thanks for the feedback jwinterm. I know that most up-to-date ccminer forks are built with static libraries (so separate dll's are not required), but the cryptonight base from which .....

Working now myagui. Turns out I have cuda5.5, and both versions work, so I guess it was just the missing dll. I'm getting much lower hashrate on that windows computer though, around 250 h/s per 750ti, compared to about 425 h/s per card on ubuntu machine. So, don't know if that's cause I need to update cuda, or just cause windows sucks, but, anyway, it's working now Smiley

I have similar deficiencies on certain comps running my 750ti's. Not absolutely positive but I believe it boils down to the architecture of the machine and/or bios. Bios update risk not worth the reward. ...I know this btw because I have swapped 3 different ti's between about 5 different machines and then played musical chairs with them and the deficiencies persisted among the mobo/processor/bios architectures and not the variations in cards or software. ....not likely your fault Smiley

Thank you both for the inputs.

I would bet on something specific to that Windows setup as fault for the low speed, if not the dreaded "operator error"  Grin since that Windows hashrate sounds about right for regular cryptonight (as in missing the -A switch). Linux does generally better on the same hardware, that's for sure, and more so with any algorithm that is memory hard, where the Windows (WDDM) driver overhead really bogs down the performance.

Well, could also be that your Windows launch settings (threads & blocks) were not optimal. While on Linux, sub-optimal launch settings go partly unnoticed due to the comparative hashrate boost from Linux vs Windows. On Windows, less-than-perfect settings will cause much more of a performance hit.

I don't have the proper launch settings for the 750TI myself though, don't have those cards anymore. I do have reports of cryptonight-light performance in the region of 500 h/s on these cards, even on Windows. Note that both cryptonight & cryptonight-light allow for massive overclocks on the 750 TI, seeing as the GPU is hardly stressed at all.
hero member
Activity: 500
Merit: 500
There is a bug in the payment module of my pool. One miner is affected now. He's not paid since several days now. I'm aware of the problem and i will investigate ASAP
The coin are safe (but in the wallet pool, not in his personal wallet) His pending balance show correct information (the pool must paid to him this balance). My apologies for the delay.

[edit] 01/09/15, solved. there's no more pending balance above 0.5 . Payment module is Ok.
Jump to: