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

[enjolras]

Something wrong is happening with the blockchain again. Difficulty is ridiculously low for the hashrate. I have 1.4.4.1 connected to the main node only, just managed to solo mine a block a few minutes ago (with very low hashrate), and it has been orphaned on the spot. I guess that we are facing a fork again, along with problems in difficulty adjustment, but won't enter into technical details because my knowledge is not that good, so let's hear from the gurus.

Regards

[1714032400]

1714032400

[1714032400]

1714032400

[vascrs11]

Well, not so bad after all....

Difficulty is low, but actuall shares are not... I don't think we are going to get such amounts

[ex33s]

What we are seeing now is the new Pow - PoS rules being effective and keeping mining low.

I'm not worried at all

[crackfoo]

What we are seeing now is the new Pow - PoS rules being effective and keeping mining low.

I'm not worried at all

so this is normal then:

ThreadRPCServer method=submitblock
ERROR: AcceptBlock() : proof-of-work block violation (prior PoS not seen or wait 10 mins) (height = 1481839)
ERROR: ProcessBlock() : AcceptBlock FAILED

[crombiecrunch]

What we are seeing now is the new Pow - PoS rules being effective and keeping mining low.

I'm not worried at all

so this is normal then:

ThreadRPCServer method=submitblock
ERROR: AcceptBlock() : proof-of-work block violation (prior PoS not seen or wait 10 mins) (height = 1481839)
ERROR: ProcessBlock() : AcceptBlock FAILED

ive been getting that as well

[crackfoo]

What we are seeing now is the new Pow - PoS rules being effective and keeping mining low.

I'm not worried at all

so this is normal then:

ThreadRPCServer method=submitblock
ERROR: AcceptBlock() : proof-of-work block violation (prior PoS not seen or wait 10 mins) (height = 1481839)
ERROR: ProcessBlock() : AcceptBlock FAILED

ive been getting that as well

when I look in my explorer... I see PoS blocks within a few mins ago...

[ex33s]

What we are seeing now is the new Pow - PoS rules being effective and keeping mining low.

I'm not worried at all

so this is normal then:

ThreadRPCServer method=submitblock
ERROR: AcceptBlock() : proof-of-work block violation (prior PoS not seen or wait 10 mins) (height = 1481839)
ERROR: ProcessBlock() : AcceptBlock FAILED

Yup, those are the rules being effective.

- Implemented a block generation rule: PoW / PoS blocks are mined / minted by following a pattern: 1) at least two PoS blocks minted between two consecutive PoW blocks, or PoW blocks generated every 10 minutes; 2) at least one PoW block is found in five consecutive PoS blocks, or PoS blocks generated every 3 minutes;

- Difficulty adjustment will be changed to four-block exponential moving average. When there is violation in aforementioned PoW / PoS generation rule, the difficulty remains unchanged.

[crackfoo]

What we are seeing now is the new Pow - PoS rules being effective and keeping mining low.

I'm not worried at all

so this is normal then:

ThreadRPCServer method=submitblock
ERROR: AcceptBlock() : proof-of-work block violation (prior PoS not seen or wait 10 mins) (height = 1481839)
ERROR: ProcessBlock() : AcceptBlock FAILED

Yup, those are the rules being effective.

- Implemented a block generation rule: PoW / PoS blocks are mined / minted by following a pattern: 1) at least two PoS blocks minted between two consecutive PoW blocks, or PoW blocks generated every 10 minutes; 2) at least one PoW block is found in five consecutive PoS blocks, or PoS blocks generated every 3 minutes;

- Difficulty adjustment will be changed to four-block exponential moving average. When there is violation in aforementioned PoW / PoS generation rule, the difficulty remains unchanged.

ok... well I'll let it run for a bit longer and see if the pool gets a block...

[ex33s]

What we are seeing now is the new Pow - PoS rules being effective and keeping mining low.

I'm not worried at all

so this is normal then:

ThreadRPCServer method=submitblock
ERROR: AcceptBlock() : proof-of-work block violation (prior PoS not seen or wait 10 mins) (height = 1481839)
ERROR: ProcessBlock() : AcceptBlock FAILED

ive been getting that as well

when I look in my explorer... I see PoS blocks within a few mins ago...

2 pos between each pow

[crackfoo]

2 pos between each pow

ok... looks like we just found a block.

so I'll leave magi running and re-enabled on www.zpool.ca

cheers

[ex33s]

2 pos between each pow

ok... looks like we just found a block.

so I'll leave magi running and re-enabled on www.zpool.ca

cheers

Nice to hear, poolinfo will also keep updating the information from your pool

[crombiecrunch]

I still have it it running on thecryptopool.com

just dont have the hash power there yet

[xinwao]

Well, not so bad after all....

How many CPUs is required to mine 2btc/day?

[crackfoo]

is someone pushing nova to update now to the latest client?

Thanks

[oxothuk]

10:29:46: ERROR Magicoin Unable to sign block, wallet locked?
10:29:46: * REJECTED Sad Magicoin block 1481595 1 txs
2017-09-17 10:29:46: REJECTED XMG block 1481595

Is someone have such error?  
I have block decode err but sometimes I see "Unable to sign block" error.



PS: Found problem, this err appear on pos blocks

[The Frisian]

Am I right if I see that the hashrate is around 1000 MH/s?
And all is going right now, just nice mining reward, going to everyone and not only going to the big ones.
My staking is also going well, look at the 1000+ coins blocks.
Well, let's see what happen over a few more blocks..
It seems Joe made again the best developments of all.

[Windozxpert]

2 pos between each pow

ok... looks like we just found a block.

so I'll leave magi running and re-enabled on www.zpool.ca

cheers

Thanks for bringing Magi back on xpool!

[BoomCrypt]

Hi there just a question or 2

in the wallet console i see "setgenerate" is still in the command line is it still able to wallet mine?

I am using the GUI cpu-miner and solo mining , just really to test out my new ryzen processor (see if i can break it really ) or should i just go to a pool ?? i have it set to 8 cores at 100% but only using just of 50% of cpu usage , is there a way to use more cores ?
and the scan time it is set to 5 , should i leave it at 5 or how does that effect the mining ?

new to Magi looking for a little of feed back and advice

[jleonc01]

Hashrate  NET 624 Kh/s
Minerclaim 46,290.26 KH/s

I do not understand

[abbeytim]

ok so Difficulty adjustment starting at 1482000 (around this Saturday morning EST)


he was off a day


anyways we are almost to that  1481981 now