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

[MaxDZ8]

A small company around here contacted me to explain them this crypto thing. I am supposed to give them a rough estimation of what they can produce with the few xeons they cannot manage to load (I think we're talking about 64 cores at most, for a few hours day).

Where can I find performance data?
I've seen some coins using google docs for this and I've been positively impressed with the usability.

As a side note, the proposed fork is a nice coincidence. I can tell for sure this will give me quite some troubles.

[1701768567]

1701768567

[1701768567]

1701768567

[1701768567]

1701768567

[1701768567]

1701768567

[1701768567]

1701768567

[1701768567]

1701768567

[sleepdog]

So the machines I leave running mining unattended over the weekend will be useless for two days after the hardfork?

[111magic]

So the machines I leave running mining unattended over the weekend will be useless for two days after the hardfork?

No if i read it right, Joelao95 wants to test this first.
So you can mine as usual!



The testnet wallet can be running with the mainnet wallet simultaneously.
Please take time to test it out and report hashrate before and after the hardfork, that will help us to refine the block-rewarding system once with the new algo. I will fire up the standalone miners soon later. I've already tested the hardfork in my side, so don't see any issues with that. After testnet, we will plug hard fork into the main net.

[sleepdog]

Ah, of course. Read that in a hurry this morning after seeing MaxDZ8's post above...

[111magic]

Ah, of course. Read that in a hurry this morning after seeing MaxDZ8's post above...

Lol had the same! I read everything twice and I had to drink coffee.
 

FYI:
I have received a request from a sponsor to place a new unique give-away. Costs for this giveaway are paid by this anonymous sponsor. 
So here it is: http://bitcoingarden.tk/forum/index.php?topic=1491.0

[hustler100]

Ah, of course. Read that in a hurry this morning after seeing MaxDZ8's post above...

Lol had the same! I read everything twice and I had to drink coffee.
 

FYI:
I have received a request from a sponsor to place a new unique give-away. Costs for this giveaway are paid by this anonymous sponsor. 
So here it is: http://bitcoingarden.tk/forum/index.php?topic=1491.0

I participated to show my support to the community 

[111magic]

Ah, of course. Read that in a hurry this morning after seeing MaxDZ8's post above...

Lol had the same! I read everything twice and I had to drink coffee.
 

FYI:
I have received a request from a sponsor to place a new unique give-away. Costs for this giveaway are paid by this anonymous sponsor.  
So here it is: http://bitcoingarden.tk/forum/index.php?topic=1491.0

I participated to show my support to the community  

Very nice picture!
Paid already!

[Bojcha]

Just to confirm that fork is happening in about 2.5 Hours?
Also would be good that pools confirms when they switch.

[djm34]

[M7M hardfork in testnet]

Here we are going a hardfork to be happening on 10/17/2014 8:00 PM EST. This update enhances the CPU mining. We will be living with the new algo from now on. In my view, this new M7M will pretty make it very hard to implement GPU miners. A major change is the addition of a sequential algorithm with iterative numerical computation using GMP floating-point numbers. I will expect this disables any on-going efforts of parallel implementation. GMP floating-point numbers allow "infinite" accuracy while we have to compromise to a certain level to avoid largely depressing hash rate. Surely I've taken the chance to further "mess up" the things that makes CPU hashing quite straightforward, while GPU mining even hard and impossible. Our block-rewarding system will give great chance for CPU mining too. As a consequence of the algo changing and hashing hard, the hash rate has to be compromised somewhere. The hashrate of my AMD 8350 is reduced from 79.2 kh/s (built-in mining) to 28.5 kh/s, and my VPS is reduced from 22.5 kh/s to 9.1 kh/s.

(woohoo the 2 points gaussian fit is back  ... this is so wrong mathematically physically... but I guess you don't care...)

At which block your hardfork ? (because at 8:00pm isn't a block number... ) and unless you want 2 forks you should say at which block it starts.... the funny thing is if some of the big whale don't change their wallet you are screwed, considering that the new wallet divide by 2~3 the hashrate... (if they keep the old one, they will have a clear advantage over the new fork... and could even take over  )

So you should really do a proper announcement with enough time before the hard fork so everybody can move to the new wallet.
not like your "hardfork in 5minutes"... as you did here...


Actually my problem with this coin (and I am pretty sure others feel the same) is that there is too much dev (divine) intervention and control.
But here everything here change change too much too often (since we should expect a second fork after the fork ( ) to adjust the reward system. (and when we see how things are announced... with not enough time to prepare for a fork... I am a bit worried about the future of the coin... )

Last point: What happens to the coin swap ?
Because the net hashrate gets divided by 2~3, the rate 1:4 is getting insanely high (compared to what you could get through mining).
And this point hasn't been debated at all.

The scarcity of the coin increases (again) while the magi holder keep their 1:4 swapping ratio 
It feels like xmg miner are getting really screwed over this one...

[111magic]

Just a brief comment.
I understand your comment.
The problem in this case is that the developer has been active until late tonight.
Maybe he did not view well in time.
The swap is precisely controlled so that the miners are protected.
In addition there is a donation for a possible second POM campaign.
Read these links, then you'll be informed.


Coin swap discussion thread: https://bitcointalk.org/index.php?topic=821170.0
Coin swap instructions and status: https://bitcointalk.org/index.php?topic=735170.msg8950501#msg8950501

[sleepdog]

So you should really do a proper announcement with enough time before the hard fork so everybody can move to the new wallet.
not like your "hardfork in 5minutes"... as you did here...

Seems like quite a few people aren't noticing the TESTNET part of the announcement...

[MaxDZ8]

At least change algo name. Keeping the same name makes no sense.

[djm34]

So you should really do a proper announcement with enough time before the hard fork so everybody can move to the new wallet.
not like your "hardfork in 5minutes"... as you did here...

Seems like quite a few people aren't noticing the TESTNET part of the announcement...

Noticed it but If I understand correctly:
the test through testnet is happening now
the fork at  10/17/2014 8:00 PM EST (ie sometimes this evening European time).

And quite frankly a fork is serious business, the message should be clear enough so that there is no place to interpretation. (here we have at least 2 persons who didn't understand the message in the same way... )

Usually most of the coin fork after an announcement with a week in advance... (with a block number high enough so everybody has enough time to move to the new wallet...). Here well we don't even know the block number...
The exchange will face the same problem, they won't have enough time to move to a new wallet either...

I know a coin which did fork without prior announcement: BBL, ended with 2 blockchain (1 for poloniex and another one for bittrex...  and died...)

[losk22]

Will all the old miners work on the new algorithm?

[111magic]

Your right (djm34)
Hope dev is awake soon to clear the sky.
Did you read the links i posted?

[djm34]

Your right (djm34)
Hope dev is awake soon to clear the sky.
Did you read the links i posted?

yes, the 1:16 ratio is a bit better, hope it will stop the exchange rate getting divided by 2 every weekend...

[Spexx]

What is all the fuss about? I think Joe made it clear enough that the hard fork is happening on the testnet. I thought that I had bad eyesight, but didn't miss that bit of info. Happy to report that I had the test wallet up and running in no time. Looking forward to seeing the new algo in action. I get 20~21 Kh/s  from the wallet on my AMD FX4100 (exactly half that possible with the current 64 bit standalone minerd.exe).

[djm34]

What is all the fuss about? I think Joe made it clear enough that the hard fork is happening on the testnet. I thought that I had bad eyesight, but didn't miss that bit of info. Happy to report that I had the test wallet up and running in no time. Looking forward to seeing the new algo in action. I get 20~21 Kh/s  from the wallet on my AMD FX4100 (exactly half that possible with the current 64 bit standalone minerd.exe).

with hardfork tonight on main network... which isn't enough time...  (I don't know if you have bad eyesight, but may-be concentration problem if your can't read the whole sentence   ... luckily for me you won't see that message either... that's why I started my message with the 3 words you didn't read in Joelao95 post...)

[sleepdog]

I'd say this sentence is pretty clear:

[M7M hardfork in testnet]

Here we are going a hardfork to be happening on 10/17/2014 8:00 PM EST.

i.e. there will be a fork on the testnet.

But then:

We will be living with the new algo from now on.

...makes it sound as if there will be a change on the real network. So it's not clear at all, let's wait and see what the dev has to say.

[djm34]

I'd say this sentence is pretty clear:

[M7M hardfork in testnet]

Here we are going a hardfork to be happening on 10/17/2014 8:00 PM EST.

i.e. there will be a fork on the testnet.

yes but it isn't yet 10/17/2014 8:00 PM EST, however it is already possible to test the new algo on testnet.
Which means this date doesn't refer to the testnet hardfork but to the main net hardfork.