[ANN] [XMG] MAGI | CPU mining | mPoW | mPoS | [MagiPay] - page 425.

My9bot

full member

Activity: 239

Merit: 100

Quote from: My9bot on August 23, 2017, 07:01:40 AM

is anyone against a rollback???

A blockchain[1][2][3] – originally block chain[4][5] – is a continuously growing list of records, called blocks, which are linked and secured using cryptography.[1][6] Each block contains typically a hash pointer as a link to a previous block,[6] a timestamp and transaction data.[7] By design, blockchains are inherently resistant to modification of the data.
---wikipedia

My9bot

full member

Activity: 239

Merit: 100

is anyone against a rollback???

111magic

legendary

Activity: 1750

Merit: 1005

Quote from: sCyborg on August 23, 2017, 05:10:51 AM

Quote from: orcanice on August 23, 2017, 04:55:14 AM

Should'nt there be a warning sent out to users that dosen't read/use this forum? eg on the website before announcing a rollback. So they have a chance so shut down their mining else it would be a huge loss for some of them. - thats just my opinion.

Have to agree here not everyone is reading these forums, Hell most of the links on the website point to older wallets. the chain has been chugging along fine the last X hours for some so the could not know anything. anything other then a future rollback point which is announced everywhere not just here in a single response of 800+ comments. Even though the exchange might be offline people could still be doing transactions.

As Magi knows more details i will try to reach as much people i can with different forums, Twitter, Instagram, Facebook, trollboxen from the different exchanges and other social media.

To make things clear for people: hold with transactions until updates are released!!

oVPN

member

Activity: 116

Merit: 10

@malafaya, please remove quote text, that's useles to quote directly on next post. thank you.

sorry, did not know that. all our nodes are @1451367 now, where is 104.128.225.215?

got it: 104. is @1450926

shutting down all nodes...

malafaya

sr. member

Activity: 490

Merit: 256

Mind that poolinfo.systms.org and 104.128.225.215 are currently on different chains. Not sure if that's what you want to test.

oVPN

member

Activity: 116

Merit: 10

magi.conf

Code:

banscore=500
maxconnections=128
connect=104.128.225.215

add following to enable staking:

Code:

staking=1
posii=1

sCyborg

newbie

Activity: 6

Merit: 0

Quote from: orcanice on August 23, 2017, 04:55:14 AM

Should'nt there be a warning sent out to users that dosen't read/use this forum? eg on the website before announcing a rollback. So they have a chance so shut down their mining else it would be a huge loss for some of them. - thats just my opinion.

Have to agree here not everyone is reading these forums, Hell most of the links on the website point to older wallets. the chain has been chugging along fine the last X hours for some so the could not know anything. anything other then a future rollback point which is announced everywhere not just here in a single response of 800+ comments. Even though the exchange might be offline people could still be doing transactions.

ex33s

sr. member

Activity: 476

Merit: 250

Quote from: AngryWhiteWolf on August 23, 2017, 04:46:40 AM

Quote from: ex33s on August 23, 2017, 04:38:25 AM

Since all pools are down that i know of, solomining would be the only way to go right now.

Joe is talking about a rollback (see couple of posts above). Solo mining in this moment is waste of energy. Better wait until the situation will be clarified. I have the feeling that it'll be sorted very soon, community is helping.

I know, was asking if people would like to test my theory - https://bitcointalksearch.org/topic/m.21124786

dqy007

member

Activity: 81

Merit: 10

Quote from: Vitalik_Pedik on August 23, 2017, 04:37:51 AM

Quote from: joelao95 on August 23, 2017, 04:14:16 AM

Quote from: oVPN on August 23, 2017, 04:05:43 AM

@devs

if you rollback after weeks, your coin is dead!

The thing is that rollback has to be after fix, and fix needs to verify. We surely try to make it happen ASAP. Let me know your suggestions.

I support dev, coin will dead if we will not do anything.

Me to

orcanice

full member

Activity: 194

Merit: 100

Should'nt there be a warning sent out to users that dosen't read/use this forum? eg on the website before announcing a rollback. So they have a chance so shut down their mining else it would be a huge loss for some of them. - thats just my opinion.

AngryWhiteWolf

full member

Activity: 616

Merit: 100

Quote from: ex33s on August 23, 2017, 04:38:25 AM

Since all pools are down that i know of, solomining would be the only way to go right now.

Joe is talking about a rollback (see couple of posts above). Solo mining in this moment is waste of energy. Better wait until the situation will be clarified. I have the feeling that it'll be sorted very soon, community is helping.

ex33s

sr. member

Activity: 476

Merit: 250

Quote from: Windozxpert on August 23, 2017, 04:27:25 AM

Quote

At this point I was looking at how many times i got peers disconnected due to ERROR: ProcessBlock() : block with too little proof-of-work.
The proper chain told poolinfo that this is the block 10 times and actually disconnected and banned all 10 peers telling poolinfo about the proper block.

So to test my theory out, I increased banscore in magi.conf to 500 with

Code:

banscore=500

The debug log dropped from ~620MB to ~62MB in size (about the same running time +- a few hrs) + was able to recover from when poolinfo got invalid blocks.
I've seen in poolinfo logs block that was accepted but later on ORPHAN because the right chain was presented to poolinfo and thus got back on the right track.

So if you like to test this too, add this to
magi.conf

Code:

banscore=500

You might need to resync the chain if you are on a fork.

To test this properly, we are going to need to mine it. Anyone willing to try this out?

I'll throw some hashes that way to test. Where do you want it to go? Not that I have a whole lot, I think it was around 1 or 2 Mhs. I'm sure zpool would love to jump on that testing train with you. They've been adding and removing m7m the past few days constantly.

Since all pools are down that i know of, solomining would be the only way to go right now.

Vitalik_Pedik

newbie

Activity: 168

Merit: 0

Quote from: joelao95 on August 23, 2017, 04:14:16 AM

Quote from: oVPN on August 23, 2017, 04:05:43 AM

@devs

if you rollback after weeks, your coin is dead!

The thing is that rollback has to be after fix, and fix needs to verify. We surely try to make it happen ASAP. Let me know your suggestions.

I support dev, coin will dead if we will not do anything.

edward0181

full member

Activity: 276

Merit: 100

Quote from: oVPN on August 23, 2017, 04:01:58 AM

Quote from: edward0181 on August 22, 2017, 10:15:03 AM

That is the reason why I've send all my miners to my own wallet and created my own small pool to just keep mining. Don't care if it's going to be roll back or not. My wallets are on same chain as https://chainz.cryptoid.info/xmg/ and https://poolinfo.systms.org/ and I can see found blocks confirmed and created.

Will see what will happen.
Either way, feel free to use mine as long as it will keep running...
http://h2701744.stratoserver.net:85/

your pools offline, you went scamming with the coins? more than 120 blocks generated with you.

Nope. Just fixed the daemon. Wasn't reporting confirms. Now running again

Windozxpert

full member

Activity: 196

Merit: 100

Quote

At this point I was looking at how many times i got peers disconnected due to ERROR: ProcessBlock() : block with too little proof-of-work.
The proper chain told poolinfo that this is the block 10 times and actually disconnected and banned all 10 peers telling poolinfo about the proper block.

So to test my theory out, I increased banscore in magi.conf to 500 with

Code:

banscore=500

The debug log dropped from ~620MB to ~62MB in size (about the same running time +- a few hrs) + was able to recover from when poolinfo got invalid blocks.
I've seen in poolinfo logs block that was accepted but later on ORPHAN because the right chain was presented to poolinfo and thus got back on the right track.

So if you like to test this too, add this to
magi.conf

Code:

banscore=500

You might need to resync the chain if you are on a fork.

To test this properly, we are going to need to mine it. Anyone willing to try this out?

I'll throw some hashes that way to test. Where do you want it to go? Not that I have a whole lot, I think it was around 1 or 2 Mhs. I'm sure zpool would love to jump on that testing train with you. They've been adding and removing m7m the past few days constantly.

jorrit

newbie

Activity: 41

Merit: 0

Mining at Suprnova is not working for me using the Magi minner. Anybody else having this issue?

joelao95

legendary

Activity: 1190

Merit: 1009

Coin of the Magi!

Quote from: oVPN on August 23, 2017, 04:05:43 AM

@devs

if you rollback after weeks, your coin is dead!

The thing is that rollback has to be after fix, and fix needs to verify. We surely try to make it happen ASAP. Let me know your suggestions.

111magic

legendary

Activity: 1750

Merit: 1005

Quote from: oVPN on August 23, 2017, 04:05:43 AM

@devs

if you rollback after weeks, your coin is dead!

Understand what you mean! Thanks

oVPN

member

Activity: 116

Merit: 10

@devs

if you rollback after weeks, your coin is dead!

ex33s

sr. member

Activity: 476

Merit: 250

Quote from: malafaya on August 23, 2017, 03:56:32 AM

Quote from: ex33s on August 23, 2017, 03:35:34 AM

Quote from: malafaya on August 23, 2017, 03:32:05 AM

Quote from: ex33s on August 23, 2017, 03:18:30 AM

Long post

Same as my findings as well (except the banscore which I didn't play with), already reported to devs.

Alright, increasing banscore isn't really a fix but a way to test this out to narrow down the real problem and then fix it.

I increased the banscore to 500 just to give it a try. Trying to re-synch starting with last official blockchain.
I now get the "trusted" peer (104......) to send me an invalid block (prevHash seems unknown to the chain, too little proof of work) on exactly every 500 blocks. Only by restarting the wallet it gets back on track receiving the right block from the same peer.
Curiously enough, this 501st block which is invalid seems to follow a parallel chain because it seems to link to the invalid block of the previous wallet restart (its prevHash corresponds to the hash of the invalid block received in the previous run)... very intriguing. Theses hashes are not found at CryptoID explorer.

Intresting, did the same as you on my personal wallet and with banscore set to 500 and no issue what so ever on that. Only thing i saw was some peers sending invalid blocks but those where discarded properly.

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