⚒[CGA] Cryptographic Anomaly - The Elusive Coin⚒

[Molitor]

@Ralph12:

Make sure your miners don't fall back to a messed pool when anomaly.com goes out.

[ralph12]

Anyone having issues with anomalypool?

I just got home from work - haven't had the wallet running all day but had my miners working away at anomalypool. Didn't receive any payouts for the last 8+ hours (since about the time the pool went down for the upgrade).

Have just installed the new wallet and synced - as soon as the wallet was ready I started getting payouts again. But nothing for an 8+ hour period between the pool going down and me upgrading the wallet about 10 minutes ago.

Anyone else experience this?

You get the wallet from chainbrowser.com? That's the latest one. I'm not sure if the front page is right.

anomalypool has had intermittent outs, but nothing prolonged. You can check here http://anomalypool.com:2124/static/graphs.html?Day and see if you're actually doing anything. If it shows you're getting payouts and they haven't arrived yet, something's probably wrong on your end. But when you finally get synced, you should get all the coins you mined.

Thanks Molitor, I hadn't seen those graphs before. It think it looks a bit wierd - or is it just me that's wierd lol?

http://s27.postimg.org/q6yxv2kzn/anomaly1.png

[tertius993]

Firstly big thanks to the guys that have been working on this - really appreciate your efforts.

A clarification question if I may: is my understanding correct that the latest version (1.1.2.1) has a known bug in that if you close your synch'd wallet the local blockchain copy will be "lost" and you will need to re-synchronise?

Assuming that is correct then we are waiting for a further update to the client?

Would it be sensible to update the OP and the website with:
a) info about the known bug and how to deal with it so people are aware;
b) an estimate of when the next version will be released; and
c) some guidance as to whether people should update now (and live with the bug) or wait?

[Molitor]

@ralphs12: That's messed, yeah. But you're connected.

The returns (lower graph) tends to have a lot of gaps, but I don't understand your hashrate problem. Are you switching in and out of the pool?

I'm definitely not an expert and this is mostly voodoo experimentation, but in the config file I have:

 "user" : "<address>+0.0005"

I have 2x400KH/s. If you have half that, you can try +0.0001 and that will get rid of some of the "...requested work restart"

[ralph12]

@ralphs12: That's messed, yeah. But you're connected.

The returns (lower graph) tends to have a lot of gaps, but I don't understand your hashrate problem. Are you switching in and out of the pool?

I'm definitely not an expert and this is mostly voodoo experimentation, but in the config file I have:

 "user" : "<address>+0.0005"

I have 2x400KH/s. If you have half that, you can try +0.0001 and that will get rid of some of the "...requested work restart"

Thanks Molitor, much appreciated. I'll give it a go.

Haha voodoo experimentation. I love it.

[Molitor]

A clarification question if I may: is my understanding correct that the latest version (1.1.2.1) has a known bug in that if you close your synch'd wallet the local blockchain copy will be "lost" and you will need to re-synchronise?

This is correct. The wallet intentionally deletes the blockchain to get rid of forks. The bug is that it does it every time instead of once, or so I infer.

If I restart I have to delete the blockchain etc manually or it won't even start to sync and will be stuck at 8 weeks.

[Molitor]

@ralphs12: That's messed, yeah. But you're connected.

The returns (lower graph) tends to have a lot of gaps, but I don't understand your hashrate problem. Are you switching in and out of the pool?

I'm definitely not an expert and this is mostly voodoo experimentation, but in the config file I have:

 "user" : "<address>+0.0005"

I have 2x400KH/s. If you have half that, you can try +0.0001 and that will get rid of some of the "...requested work restart"

Thanks Molitor, much appreciated. I'll give it a go.

Haha voodoo experimentation. I love it.

You can also check your Scantime, Queue and Expiry. When the diff is low, I use Scantime 5, expiry 120, and Queue of 2. If the diff gets higher, I raise the scantime up to ~20. More voodoo joy. You gotta change something, then watch the charts for 5-10 minutes. It's a pain, buy you can vastly improve your returns.

No matter what I do, the lower chart is always spastic.

[wzttide]

Anyone having issues with anomalypool?

I just got home from work - haven't had the wallet running all day but had my miners working away at anomalypool. Didn't receive any payouts for the last 8+ hours (since about the time the pool went down for the upgrade).

Have just installed the new wallet and synced - as soon as the wallet was ready I started getting payouts again. But nothing for an 8+ hour period between the pool going down and me upgrading the wallet about 10 minutes ago.

Anyone else experience this?

You get the wallet from chainbrowser.com? That's the latest one. I'm not sure if the front page is right.

anomalypool has had intermittent outs, but nothing prolonged. You can check here http://anomalypool.com:2124/static/graphs.html?Day and see if you're actually doing anything. If it shows you're getting payouts and they haven't arrived yet, something's probably wrong on your end. But when you finally get synced, you should get all the coins you mined.

Thanks Molitor, I hadn't seen those graphs before. It think it looks a bit wierd - or is it just me that's wierd lol?

This is a little bit wierd, can you check your miner and everything? Other addresses don't have this problems at all. Nevertheless I'll investigate this further, but I can't promise you that I'll find anything, the graphs are pretty accurate.

[wzttide]

You can also check your Scantime, Queue and Expiry. When the diff is low, I use Scantime 5, expiry 120, and Queue of 2. If the diff gets higher, I raise the scantime up to ~20. More voodoo joy. You gotta change something, then watch the charts for 5-10 minutes. It's a pain, buy you can vastly improve your returns.

No matter what I do, the lower chart is always spastic.

Nice, will do this too

[tertius993]

@ralphs12: That's messed, yeah. But you're connected.

The returns (lower graph) tends to have a lot of gaps, but I don't understand your hashrate problem. Are you switching in and out of the pool?

I'm definitely not an expert and this is mostly voodoo experimentation, but in the config file I have:

 "user" : "<address>+0.0005"

I have 2x400KH/s. If you have half that, you can try +0.0001 and that will get rid of some of the "...requested work restart"

Interesting, what does the "+0.0005" do?  Can't see it in the cgminer readme.

[wzttide]

anomalypool.com bonus payouts: https://cryptocointalk.com/topic/4377-anomalypoolcom-stable-p2pool-without-a-fee/#entry43053

I hope I didn't forgot someone, if I did, please drop me a line.

[Molitor]

Firstly big thanks to the guys that have been working on this - really appreciate your efforts.

A clarification question if I may: is my understanding correct that the latest version (1.1.2.1) has a known bug in that if you close your synch'd wallet the local blockchain copy will be "lost" and you will need to re-synchronise?

Assuming that is correct then we are waiting for a further update to the client?

Would it be sensible to update the OP and the website with:
a) info about the known bug and how to deal with it so people are aware;
b) an estimate of when the next version will be released; and
c) some guidance as to whether people should update now (and live with the bug) or wait?

I would advise you to wait. There are more bugs than just that and they could potentialy destroy this coin if it gets out of hand... this is why I have neglected putting up the wallets (or really doing anything). You should be fine updating to 1.1.2.1 but keep in mind tomorrow there will be yet another MANDITORY update. Yes im sorry if this feels like we are using you as Beta testers for our updates but with the amount of hostility going on in this thread it has caused us to want to get our updates fixed as fast as possible. The reason this last one was released so quickly was because of the large amount of forks going on and we didn't want to completely lose the coin. Though in our hast we only created more problems while fixing others. So please have some patience. We are doing the best we can while working with a new coin concept.

That being said... STOP SOLO MINING! at least until we can get the network stable. Mine in Anomalypool.com for it's nodes are hardcoded so it will never fork! You can still mine in anomalypool without a working wallet. As long as you had made a wallet prior to all this crap and you don't delete your wallet.dat you will receive your coins!

I hope you don't take what I've said as hostile. If so, you're taking it exactly backwards. I (for one) don't want updates as fast as possible. I want them as good as possible. I've said all along not to rush, and test thoroughly before you release. C'mon dude, you're not using us as beta testers, you're using us as pre-alpha testers. In a real company, that last release would get someone fired.

Here's what I said before:

When GIT is updated with the hard coded nodes and the patch posted earlier and s4w3d0ff gives me the OK, I will go ahead and compile the latest version.

Are you going to test it before you release it? I know there's a rush to get out a good wallet, but at this point, if you release something broken, things could get brutal.

Well. Surprise.

You can't flip the bird at, Murphy's Law, Common Sense and software engineering 101 without repercussions.

All this may sound harsh, but if you were delaying things to fix bugs or test a newly compiled client, I'd be the first to defend you.

[ralph12]

Anyone having issues with anomalypool?

I just got home from work - haven't had the wallet running all day but had my miners working away at anomalypool. Didn't receive any payouts for the last 8+ hours (since about the time the pool went down for the upgrade).

Have just installed the new wallet and synced - as soon as the wallet was ready I started getting payouts again. But nothing for an 8+ hour period between the pool going down and me upgrading the wallet about 10 minutes ago.

Anyone else experience this?

You get the wallet from chainbrowser.com? That's the latest one. I'm not sure if the front page is right.

anomalypool has had intermittent outs, but nothing prolonged. You can check here http://anomalypool.com:2124/static/graphs.html?Day and see if you're actually doing anything. If it shows you're getting payouts and they haven't arrived yet, something's probably wrong on your end. But when you finally get synced, you should get all the coins you mined.

Thanks Molitor, I hadn't seen those graphs before. It think it looks a bit wierd - or is it just me that's wierd lol?

This is a little bit wierd, can you check your miner and everything? Other addresses don't have this problems at all. Nevertheless I'll investigate this further, but I can't promise you that I'll find anything, the graphs are pretty accurate.

Thanks wzttide. I'm not too stressed about it, was more curious. Don't waste any time on it, with my low hash speeds it's dog all anyway lol. Just a bit of fun!

[wzttide]

Firstly big thanks to the guys that have been working on this - really appreciate your efforts.

A clarification question if I may: is my understanding correct that the latest version (1.1.2.1) has a known bug in that if you close your synch'd wallet the local blockchain copy will be "lost" and you will need to re-synchronise?

Assuming that is correct then we are waiting for a further update to the client?

Would it be sensible to update the OP and the website with:
a) info about the known bug and how to deal with it so people are aware;
b) an estimate of when the next version will be released; and
c) some guidance as to whether people should update now (and live with the bug) or wait?

I would advise you to wait. There are more bugs than just that and they could potentialy destroy this coin if it gets out of hand... this is why I have neglected putting up the wallets (or really doing anything). You should be fine updating to 1.1.2.1 but keep in mind tomorrow there will be yet another MANDITORY update. Yes im sorry if this feels like we are using you as Beta testers for our updates but with the amount of hostility going on in this thread it has caused us to want to get our updates fixed as fast as possible. The reason this last one was released so quickly was because of the large amount of forks going on and we didn't want to completely lose the coin. Though in our hast we only created more problems while fixing others. So please have some patience. We are doing the best we can while working with a new coin concept.

That being said... STOP SOLO MINING! at least until we can get the network stable. Mine in Anomalypool.com for it's nodes are hardcoded so it will never fork! You can still mine in anomalypool without a working wallet. As long as you had made a wallet prior to all this crap and you don't delete your wallet.dat you will receive your coins!

I hope you don't take what I've said as hostile. If so, you're taking it exactly backwards. I (for one) don't want updates as fast as possible. I want them as good as possible. I've said all along not to rush, and test thoroughly before you release. C'mon dude, you're not using us as beta testers, you're using us as pre-alpha testers. In a real company, that last release would get someone fired.

Here's what I said before:

When GIT is updated with the hard coded nodes and the patch posted earlier and s4w3d0ff gives me the OK, I will go ahead and compile the latest version.

Are you going to test it before you release it? I know there's a rush to get out a good wallet, but at this point, if you release something broken, things could get brutal.

Well. Surprise.

You can't flip the bird at, Murphy's Law, Common Sense and software engineering 101 without repercussions.

All this may sound harsh, but if you were delaying things to fix bugs or test a newly compiled client, I'd be the first to defend you.

The problem is that the forks needed to be fixed asap, this had top prio to ensure nobody mines on a wrong chain and loses earnings. The devs do what they can - and yes, I see your point about code quality and tests

[Molitor]

@ralphs12: That's messed, yeah. But you're connected.

The returns (lower graph) tends to have a lot of gaps, but I don't understand your hashrate problem. Are you switching in and out of the pool?

I'm definitely not an expert and this is mostly voodoo experimentation, but in the config file I have:

 "user" : "<address>+0.0005"

I have 2x400KH/s. If you have half that, you can try +0.0001 and that will get rid of some of the "...requested work restart"

Interesting, what does the "+0.0005" do?  Can't see it in the cgminer readme.

The effect it has is to reduce the diff of the work it sends you. Notice you'll get something like 'Accepted .... diff nn/32' if you lower it to +0.0001, it lowers the bottom number, so you'll get 'Accepted .... diff nn/6' all the time. The bottom number will always be fixed, whereas without it, the bottom number will vary.

Maybe someone can give a good explanation...

I always raise that number just until MOST of the work restart errors go away. Usually between 0.0001 and 0.0009, lower when you have lower hashrates and to make work restart errors go away.

Works for me, anyway. I hope it works for you guys.

[awesomeperson451]

Anyone having issues with anomalypool?

I just got home from work - haven't had the wallet running all day but had my miners working away at anomalypool. Didn't receive any payouts for the last 8+ hours (since about the time the pool went down for the upgrade).

Have just installed the new wallet and synced - as soon as the wallet was ready I started getting payouts again. But nothing for an 8+ hour period between the pool going down and me upgrading the wallet about 10 minutes ago.

Anyone else experience this?

You get the wallet from chainbrowser.com? That's the latest one. I'm not sure if the front page is right.

anomalypool has had intermittent outs, but nothing prolonged. You can check here http://anomalypool.com:2124/static/graphs.html?Day and see if you're actually doing anything. If it shows you're getting payouts and they haven't arrived yet, something's probably wrong on your end. But when you finally get synced, you should get all the coins you mined.

Thanks Molitor, I hadn't seen those graphs before. It think it looks a bit wierd - or is it just me that's wierd lol?

This is a little bit wierd, can you check your miner and everything? Other addresses don't have this problems at all. Nevertheless I'll investigate this further, but I can't promise you that I'll find anything, the graphs are pretty accurate.

Check the graphs for my address, AFnYPruQpNqzi4UEquWPmA4vV2xf6gNGa1. I think the reason for the hashrate graph weirdness is caused the fact that ralph12 and I are probably both putting out around 100 kh/s. The graphs seem to calculate a hashrate using the amount of time between shares while using the share difficulty as a weight. The problem is that the hashrate is only calculated over a span of 1-3 minutes, and if a share isn't submitted in that time, it goes back down to 0. That means that the minimum hasrate that can be displayed is the hashrate needed to generate 1 share per 1-3 minutes. This explains why all the spikes you see are far higher than our actual hashrates. As for the odd spaces between payouts, I have no idea.

On a related note, I just got my .5 CGA for mining all day today! Thanks wzttide!

[mycointr]

new day...
new wallet..
new chain to download... 

i'm excited 

[tertius993]

s4w3d0ff I have sent you a PM.  Just a suggestion.

[Molitor]

Firstly big thanks to the guys that have been working on this - really appreciate your efforts.

A clarification question if I may: is my understanding correct that the latest version (1.1.2.1) has a known bug in that if you close your synch'd wallet the local blockchain copy will be "lost" and you will need to re-synchronise?

Assuming that is correct then we are waiting for a further update to the client?

Would it be sensible to update the OP and the website with:
a) info about the known bug and how to deal with it so people are aware;
b) an estimate of when the next version will be released; and
c) some guidance as to whether people should update now (and live with the bug) or wait?

I would advise you to wait. There are more bugs than just that and they could potentialy destroy this coin if it gets out of hand... this is why I have neglected putting up the wallets (or really doing anything). You should be fine updating to 1.1.2.1 but keep in mind tomorrow there will be yet another MANDITORY update. Yes im sorry if this feels like we are using you as Beta testers for our updates but with the amount of hostility going on in this thread it has caused us to want to get our updates fixed as fast as possible. The reason this last one was released so quickly was because of the large amount of forks going on and we didn't want to completely lose the coin. Though in our hast we only created more problems while fixing others. So please have some patience. We are doing the best we can while working with a new coin concept.

That being said... STOP SOLO MINING! at least until we can get the network stable. Mine in Anomalypool.com for it's nodes are hardcoded so it will never fork! You can still mine in anomalypool without a working wallet. As long as you had made a wallet prior to all this crap and you don't delete your wallet.dat you will receive your coins!

I hope you don't take what I've said as hostile. If so, you're taking it exactly backwards. I (for one) don't want updates as fast as possible. I want them as good as possible. I've said all along not to rush, and test thoroughly before you release. C'mon dude, you're not using us as beta testers, you're using us as pre-alpha testers. In a real company, that last release would get someone fired.

Here's what I said before:

When GIT is updated with the hard coded nodes and the patch posted earlier and s4w3d0ff gives me the OK, I will go ahead and compile the latest version.

Are you going to test it before you release it? I know there's a rush to get out a good wallet, but at this point, if you release something broken, things could get brutal.

Well. Surprise.

You can't flip the bird at, Murphy's Law, Common Sense and software engineering 101 without repercussions.

All this may sound harsh, but if you were delaying things to fix bugs or test a newly compiled client, I'd be the first to defend you.

The problem is that the forks needed to be fixed asap, this had top prio to ensure nobody mines on a wrong chain and loses earnings. The devs do what they can - and yes, I see your point about code quality and tests

I understand that, and I understand this is all hard work. But you still have to test things. Period. Rather than putting out that client, you could have simply told everyone not to solo, get on anomaly and don't worry because the coins are in the mail. It's infuriating because this coin has promise, and I respect you guys, but c'mon, you know you know better than to go from compiler to download link in one fell swoop. All this rushing is just making your job all the harder.

Again. Take all this as tough love.  And on the bright side, nobody's bitching about getting it on an exchange anymore.

[mycointr]

sorry to bother but...
is there a new-todays (10.02.2014) Windows wallet yet?