Author

Topic: [ANN] [XMG] MAGI | CPU mining | mPoW | mPoS | [MagiPay] - page 438. (Read 2375995 times)

member
Activity: 119
Merit: 100
strange - i see something on Pom pool that I havent seen anywhere else..

275 pool workers and just 1 share..
Is that normal?

https://ibb.co/hCbUNQ
Looks like just my luck...
Low difficulty at moment. Have had that before

ha! its you! thats a nice block right there! Smiley))
full member
Activity: 276
Merit: 100
strange - i see something on Pom pool that I havent seen anywhere else..

275 pool workers and just 1 share..
Is that normal?

https://ibb.co/hCbUNQ
Looks like just my luck...
Low difficulty at moment. Have had that before
full member
Activity: 1179
Merit: 131
strange - i see something on Pom pool that I havent seen anywhere else..

275 pool workers and just 1 share..
Is that normal?

https://ibb.co/hCbUNQ

Probably normal when a block is found that quickly.
newbie
Activity: 168
Merit: 0
if "blocks" : 1449525 is true chain
and "difficulty" : {
        "proof-of-work" : 0.44014829,
        "proof-of-stake" : 0.00399164
    },
that mean significant pow part mining on other chain)
we have new split?
member
Activity: 119
Merit: 100
strange - i see something on Pom pool that I havent seen anywhere else..

275 pool workers and just 1 share..
Is that normal?

https://ibb.co/hCbUNQ
sr. member
Activity: 371
Merit: 250
All I see now are absurt high stakes flying around on PoS looking at the Magi Explorer...
just after block 1449484 7 blocks of 800XMG or more

https://imghost.io/image/P5pHC

This is not a stake reward.  It shows the number of coins that were used to stake the block.  Before all the issues happened it was best to have over 500 coins in a block to stake in five days because of the high difficulty.
sr. member
Activity: 371
Merit: 250
This could go on and on.  I think you will need to change the PoW algorithm and that could take some time to be done right and properly tested.  I would remove PoW for now and just run on PoS.  I believe this will probably stop the forking.  This is an unfair situation that may become more difficult as things progress imho.

If we can conclude this is caused by PoW and not by PoS I vote for this.

Just for the record, I have the feeling it's PoS that causes the fork... I've seen more hybrid/PoS coins having this kind of unexplained problems than pure PoWs. And seeing the printscreen that someone recently posted [EDIT: https://bitcointalksearch.org/topic/m.21041520 ], with tens of stakes in a couple of minutes makes my belief stronger.

I think any coin can fork but a PoS only coin has less issues from what I have seen.  A solo miner on PoW can get on their own chain and mine along literally for weeks causing issues as long as they are not locked out by other nodes, which is hard to do without a proper hard fork with a forced wallet version update.  On the other hand if a PoS only coin forks, eventually the miner has to reset the wallet because you run out of coins and therefor can't mine just by yourself, so long as there is a reasonable distribution of coins.  Hybrid coins do have more issues with forks but it can be solved, hopefully Joe can find a solution, I'm very impressed with his efforts.

To be brutally honest, there has been some indications of privately run GPU or other faster computer hardware being used, or perhaps large bot nets.  As these large sources of hash rate come on to the coin they produce sudden huge increases in the hash rate and can cause problems. In any case I vote to change the PoW algorithm at this point to make things more even for single CPU mining if nothing else.  Thus I feel PoW should be removed for now to give time for development of a better PoW algorithm.
full member
Activity: 343
Merit: 102
btw i tried to payout from POM while exclusively connected to Joes node. It paid out fine so i guess its still on the right chain. Just buggy api that doest report well.
full member
Activity: 343
Merit: 102
All I see now are absurt high stakes flying around on PoS looking at the Magi Explorer...
just after block 1449484 7 blocks of 800XMG or more
maybe we should turn off all staking for a day and see what happens

Normally I am responsible for 25% of the staking. My staking is off for more than 1 day now.
I see now only percentages under 10%. So I guess it has nothing to do with staking.

What I certainly know, is that the problems started when new miners came in with
hashes of more than 20 Mh/s. The block reward reduces then to all time low 0.1 XMG.

So I guess if it has something do with PoS or PoW, I choose for PoS.
But why can't it be something completely else?

What are Joe's ideas about this?

my suggestion is to completely shutdown either pow or pos for a period of time and see if it still forks or not. So at least we can figure out what is causing it for sure.
legendary
Activity: 1019
Merit: 1003
Senior Developer and founder of ViMeAv ICT
All I see now are absurt high stakes flying around on PoS looking at the Magi Explorer...
just after block 1449484 7 blocks of 800XMG or more
maybe we should turn off all staking for a day and see what happens

Normally I am responsible for 25% of the staking. My staking is off for more than 1 day now.
I see now only percentages under 10%. So I guess it has nothing to do with staking.

What I certainly know, is that the problems started when new miners came in with
hashes of more than 20 Mh/s. The block reward reduces then to all time low 0.1 XMG.

So I guess if it has something do with PoS or PoW, I choose for PoS.
But why can't it be something completely else?

What are Joe's ideas about this?
legendary
Activity: 1484
Merit: 1029
All I see now are absurt high stakes flying around on PoS looking at the Magi Explorer...
just after block 1449484 7 blocks of 800XMG or more
maybe we should turn off all staking for a day and see what happens
I'm not running a wallet right now - all seems a little crazy. If somebody has a huge wallet balance and didn't stake for a while such staking amounts could be possible - I get some pretty large rewards from some other coins...
full member
Activity: 343
Merit: 102
All I see now are absurt high stakes flying around on PoS looking at the Magi Explorer...
just after block 1449484 7 blocks of 800XMG or more
maybe we should turn off all staking for a day and see what happens
full member
Activity: 276
Merit: 100
All I see now are absurt high stakes flying around on PoS looking at the Magi Explorer...
just after block 1449484 7 blocks of 800XMG or more

https://imghost.io/image/P5pHC
full member
Activity: 500
Merit: 105
may you please post how to solo mine (for newbies).
thanks,
sr. member
Activity: 490
Merit: 256
This could go on and on.  I think you will need to change the PoW algorithm and that could take some time to be done right and properly tested.  I would remove PoW for now and just run on PoS.  I believe this will probably stop the forking.  This is an unfair situation that may become more difficult as things progress imho.

If we can conclude this is caused by PoW and not by PoS I vote for this.

Just for the record, I have the feeling it's PoS that causes the fork... I've seen more hybrid/PoS coins having this kind of unexplained problems than pure PoWs. And seeing the printscreen that someone recently posted [EDIT: https://bitcointalksearch.org/topic/m.21041520 ], with tens of stakes in a couple of minutes makes my belief stronger.

That was my screen, from that time Joe and I decided to stop staking.
So the last fork(s) was/were without MY staking.

I was not saying it was *your* staking, but that it could be staking in general, due to its speed which may not allow fast enough propagation of blocks.
newbie
Activity: 24
Merit: 0
TrasMamod has gone off.

https://poolinfo.systms.org/

Only right pool now is Pom.

Hope you are right... already lose the mining on 3 different pools and all the coins send to Bittrex (never confirm) i will stay on Pom for the rest of today, if this pool doesn't work i´ll give up with this coin for the moment...

full member
Activity: 343
Merit: 102
sorry seems like pom is still on the right chain, just probably a buggy api
jr. member
Activity: 39
Merit: 2
@Poolowners: Please provide us some informations via pm or send us a mail (check our profile) with the following informations:

Hash value of block 1449360
Hash value of block 1449320
Hash value of block 1449280

This would be helpful for further analyzing.

Thank you!
full member
Activity: 224
Merit: 100
This could go on and on.  I think you will need to change the PoW algorithm and that could take some time to be done right and properly tested.  I would remove PoW for now and just run on PoS.  I believe this will probably stop the forking.  This is an unfair situation that may become more difficult as things progress imho.

If we can conclude this is caused by PoW and not by PoS I vote for this.

Just for the record, I have the feeling it's PoS that causes the fork... I've seen more hybrid/PoS coins having this kind of unexplained problems than pure PoWs. And seeing the printscreen that someone recently posted [EDIT: https://bitcointalksearch.org/topic/m.21041520 ], with tens of stakes in a couple of minutes makes my belief stronger.

That was my screen, from that time Joe and I decided to stop staking.
So the last fork(s) was/were without MY staking.

Thanks
legendary
Activity: 1019
Merit: 1003
Senior Developer and founder of ViMeAv ICT
This could go on and on.  I think you will need to change the PoW algorithm and that could take some time to be done right and properly tested.  I would remove PoW for now and just run on PoS.  I believe this will probably stop the forking.  This is an unfair situation that may become more difficult as things progress imho.

If we can conclude this is caused by PoW and not by PoS I vote for this.

Just for the record, I have the feeling it's PoS that causes the fork... I've seen more hybrid/PoS coins having this kind of unexplained problems than pure PoWs. And seeing the printscreen that someone recently posted [EDIT: https://bitcointalksearch.org/topic/m.21041520 ], with tens of stakes in a couple of minutes makes my belief stronger.

That was my screen, from that time Joe and I decided to stop staking.
So the last fork(s) was/were without MY staking.
Jump to: