[ANN] [XMG] MAGI | CPU mining | mPoW | mPoS | [MagiPay]

[Spexx]

I sent coins to myself at 8 Apr (150XMG), i get 10XMG at 12 Apr, 28 XMG at 13 Apr...
Now my weight is 496, net is 51k, expected time : 1day, lol.
I guess i have to send myself again, ( but all my coins are together in 1 address already) lol

Well the weight is good in comparison to the balance in the wallet, which is a good sign. I have one wallet here where I sent all my coins to myself on 7th April and the weight is still rising. The weight is now almost three times the balance in the wallet. Expected time to earn reward is 32 minutes and the rewards are coming in roughly that often, but then the balance in that wallet is rather more than yours

You should not have to send all your coins to yourself again just yet and you should see the weight continue to rise, but I think that if you want rewards to come in more often you might need some more coins. I am not an expert on the inner workings of the thing and just observe how the wallet behaves, but the smallest balance that I have done tests with is 600 XMG.

[Arah]

well... is there any sence of mining atm? i mean: if you are mining with 100khash/s you'll get about 2 coins per day 
that's a waste of electricity...

[111magic]

Z0n0 congrats, notice you are senior now!

 

Almost amigo!!

[111magic]

Random Magic Staking sent!

[Lightsplasher]

Random Magic Staking sent!

Someone sent me a nice tip, magic happens!  Thank you somebody!  What a great coin and wonderful community! 

[feldenthorne]

That is really frustrating and I have not seen a similar problem for something like twenty years - and that was somebody else's problem at the time. There is always one! I cannot even reproduce that on any of my machines - nothing I do will make it output the date in that format, so maybe I am missing something but at least that shows me that it is a rare thing. I have been using that code snippet for grabbing the date and using the numbers for something like thirty years. It is used in every bit of software currently available from me for XMG certainly. There are some vague references to this on the Web but the options they refer to are not present on my machines. I can use some extra code to get around it, but I will have to patch literally everything. I have put this issue on my watchlist for Autominer V4 currently under development.

It looks like it only happens on one of my computers (and a virtual machine on that computer). It works for my regular desktop, my laptop, and even in my sandbox VMs on other computers.

I'll look into catching the exact output string for you (and hopefully a telling non-printable character or something similar) and let you know through PMs if it's any different. At any rate, it looks like an isolated incident, albeit repeatable on that computer. Let me know if you'd like any information about it.

[Spexx]

That is really frustrating and I have not seen a similar problem for something like twenty years - and that was somebody else's problem at the time. There is always one! I cannot even reproduce that on any of my machines - nothing I do will make it output the date in that format, so maybe I am missing something but at least that shows me that it is a rare thing. I have been using that code snippet for grabbing the date and using the numbers for something like thirty years. It is used in every bit of software currently available from me for XMG certainly. There are some vague references to this on the Web but the options they refer to are not present on my machines. I can use some extra code to get around it, but I will have to patch literally everything. I have put this issue on my watchlist for Autominer V4 currently under development.

It looks like it only happens on one of my computers (and a virtual machine on that computer). It works for my regular desktop, my laptop, and even in my sandbox VMs on other computers.

I'll look into catching the exact output string for you (and hopefully a telling non-printable character or something similar) and let you know through PMs if it's any different. At any rate, it looks like an isolated incident, albeit repeatable on that computer. Let me know if you'd like any information about it.

Thanks for that. I was wondering if it was maybe a server version of Windows or something. The Windows command language set has always been deficient in a decent system service for handling time and date strings, so you always have to write your own. No need for you to investigate further. I know what it is doing and have already patched the code to handle it. Latest patched version on link now. Anybody who did not encounter a problem with the previous version does not need this update. I will incorporate this patch into all my other software packages in due course. The Miner Speed Controller renames old log files The PoolStats utility creates historic data files using the same code and will need immediate attention. All Setup files use it too for creating backups of old file versions.

Nice little job for a junior programmer

[Spexx]

well... is there any sence of mining atm? i mean: if you are mining with 100khash/s you'll get about 2 coins per day 
that's a waste of electricity...

I am using Sweet Spot targeting and wasting less electricity.

However tempting it might be to give it up, it is actually vital that smaller miners stick with it and keep sending the message to the big miners that they are in the wrong place. They should be on the Multipool with their huge hashrates and keep it down on the XMG blockchain. That way we can all benefit. Win win all round.

[feldenthorne]

I know what it is doing and have already patched the code to handle it. Latest patched version on link now.

Just ran the updated package to test it - the patch is solid and everything worked without a hitch! Great job, Spexx.

Edit: Adding results because they were requested

Popup: https://i.imgur.com/3HQViJW.png

And the contents of BenchResultMultiplex-04-15-2015-15-39-59-48.txt are:

Code:

System CPU name  : AMD Phenom(tm) II X4 955 Processor 
System CPU type  : 1 Physical CPU(s), 4 Core(s) per CPU, 4 Thread(s) 
CPU clock speed  : 3200.0 MHz 
Benchmark result : 49.99 Kh/s 
Hashrate per core: 12.49 Kh/s 
CPU speed factor : 15.62 hashes/Mcycle 
Core speed factor: 3.90 hashes/Mcycle/core

[Spexx]

I know what it is doing and have already patched the code to handle it. Latest patched version on link now.

Just ran the updated package to test it - the patch is solid and everything worked without a hitch! Great job, Spexx.

So where are your results then?

Ah I see. Jolly good

Nice core speed factor BTW.

[B.T.Coin]

So where are your results then?

I have tried every version so far but no luck It looks as if the CPU doesn't even kick into turbo mode.

[Spexx]

So where are your results then?

I have tried every version so far but no luck It looks as if the CPU doesn't even kick into turbo mode.

You too? Even with the very latest version? I have a headache. I expect it did not produce figures.txt. It's weird. It ought to work. The cut-down version of the same code will work on the collected data and give you the result. https://www.dropbox.com/s/4w5rsyosk5kx66f/benchmark-redo.exe but only for the standard benchmark results - not the multiplex.

[light85bit]

I sent coins to myself at 8 Apr (150XMG), i get 10XMG at 12 Apr, 28 XMG at 13 Apr...
Now my weight is 496, net is 51k, expected time : 1day, lol.
I guess i have to send myself again, ( but all my coins are together in 1 address already) lol

Well the weight is good in comparison to the balance in the wallet, which is a good sign. I have one wallet here where I sent all my coins to myself on 7th April and the weight is still rising. The weight is now almost three times the balance in the wallet. Expected time to earn reward is 32 minutes and the rewards are coming in roughly that often, but then the balance in that wallet is rather more than yours

You should not have to send all your coins to yourself again just yet and you should see the weight continue to rise, but I think that if you want rewards to come in more often you might need some more coins. I am not an expert on the inner workings of the thing and just observe how the wallet behaves, but the smallest balance that I have done tests with is 600 XMG.

Thank you Spexx, but i doublt that i can have more XMG, that's all i have. Now i only get 2.5XMG/day. There was times that i got 2.5XMG/hours, but i only managed to mine for a few hours, lol.

[111magic]

Random Magic Staking sent!

Someone sent me a nice tip, magic happens!  Thank you somebody!  What a great coin and wonderful community! 

You are the first who noticed!
 

[z0n0]

Random Magic Staking sent!

Someone sent me a nice tip, magic happens!  Thank you somebody!  What a great coin and wonderful community! 

You are the first who noticed!
 

I also think I received some extra XMG



 

[111magic]

Is that you on the picture?

[kondiomir]

Freddy Mercury mate Queen!

[light85bit]

Random Magic Staking sent!

Thats Magic! i've just got a huge amount of XMG: 10 days of working !
Thanks 111magic! 

[B.T.Coin]

You too? Even with the very latest version? I have a headache. I expect it did not produce figures.txt. It's weird. It ought to work. The cut-down version of the same code will work on the collected data and give you the result. https://www.dropbox.com/s/4w5rsyosk5kx66f/benchmark-redo.exe but only for the standard benchmark results - not the multiplex.

That executable in the link only unpacks 1 file to my drive, which is benchmark-redo.bat which does not work by itself. What other files should I put in the directory?

[kurzer42]

Hi there, I've just run the Benchmark, works fine for me:

Standard:

Code:

System CPU name  : Intel(R) Xeon(R) CPU E3-1230 v3 @ 3.30GHz 
System CPU type  : 1 Physical CPU(s), 4 Core(s) per CPU, 8 Thread(s) 
CPU clock speed  : 3299.0 MHz 
Benchmark result : 80.40 Kh/s 
Hashrate per core: 10.05 Kh/s 
CPU speed factor : 24.37 hashes/Mcycle 
Core speed factor: 3.04 hashes/Mcycle/core

Multiplex:

Code:

System CPU name  : Intel(R) Xeon(R) CPU E3-1230 v3 @ 3.30GHz 
System CPU type  : 1 Physical CPU(s), 4 Core(s) per CPU, 8 Thread(s) 
CPU clock speed  : 3299.0 MHz 
Benchmark result : 80.58 Kh/s 
Hashrate per core: 10.07 Kh/s 
CPU speed factor : 24.42 hashes/Mcycle 
Core speed factor: 3.05 hashes/Mcycle/core 

I'm rather new to Magi. Great coin and superb community!