joelao95 (OP)
Legendary
Offline
Activity: 1190
Merit: 1009
Coin of the Magi!
|
|
August 23, 2017, 09:14:16 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.
|
|
|
|
jorrit
Newbie
Offline
Activity: 41
Merit: 0
|
|
August 23, 2017, 09:15:44 AM |
|
Mining at Suprnova is not working for me using the Magi minner. Anybody else having this issue?
|
|
|
|
Windozxpert
|
|
August 23, 2017, 09:27:25 AM |
|
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 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 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.
|
There's no I in team, but there is a "Me" if you jumble it up. ~ House, M.D.
|
|
|
edward0181
|
|
August 23, 2017, 09:32:47 AM |
|
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
|
|
|
|
Vitalik_Pedik
Newbie
Offline
Activity: 168
Merit: 0
|
|
August 23, 2017, 09:37:51 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.
|
|
|
|
ex33s
|
|
August 23, 2017, 09:38:25 AM |
|
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 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 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.
|
|
|
|
AngryWhiteWolf
|
|
August 23, 2017, 09:46:40 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.
|
|
|
|
orcanice
|
|
August 23, 2017, 09: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.
|
|
|
|
dqy007
Member
Offline
Activity: 81
Merit: 10
|
|
August 23, 2017, 09:58:39 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
|
|
|
|
ex33s
|
|
August 23, 2017, 10:06:15 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://bitcointalk.org/index.php?topic=735170.msg21124786#msg21124786
|
|
|
|
sCyborg
Newbie
Offline
Activity: 6
Merit: 0
|
|
August 23, 2017, 10:10:51 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.
|
|
|
|
oVPN
|
|
August 23, 2017, 10:48:47 AM Last edit: August 23, 2017, 11:06:06 AM by oVPN |
|
magi.conf banscore=500 maxconnections=128 connect=104.128.225.215
add following to enable staking:
|
oVPN.to Anonymous Services
|
|
|
malafaya
|
|
August 23, 2017, 10:58:04 AM Last edit: August 23, 2017, 11:11:32 AM by malafaya |
|
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
|
|
August 23, 2017, 11:00:59 AM Last edit: August 23, 2017, 11:16:43 AM by oVPN |
|
@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...
|
oVPN.to Anonymous Services
|
|
|
111magic
Legendary
Offline
Activity: 1750
Merit: 1005
|
|
August 23, 2017, 11:38:04 AM Last edit: August 23, 2017, 11:53:09 AM by 111magic |
|
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!!
|
bitcoin: bc1qyadvvyv29z08ln2ta7g3uqwzkscr7wq4p09wuz
|
|
|
My9bot
|
|
August 23, 2017, 12:01:40 PM |
|
is anyone against a rollback???
|
|
|
|
My9bot
|
|
August 23, 2017, 12:03:46 PM |
|
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
|
|
|
|
joelao95 (OP)
Legendary
Offline
Activity: 1190
Merit: 1009
Coin of the Magi!
|
|
August 23, 2017, 12:41:09 PM |
|
To ALL,
The fork takes place from one pool to another, and that I believe something fundamental needs a clarification as we haven't seen this before. This has messed around the mining. I suggest stop mining at this time until we firstly 1) get a keep-it-going solution, and 2) root cause finding and a solution to the fork. The mining just going on, unfortunately, doesn't make sense to me, and I would propose a rollover back to a fair point. Let me know if rollover sounds good to you, and where you want to startover.
Here I am going to nail down the plan that we believe better suite for the current situation, and make the corresponding wallet release at tonight.
1) A keep-it-going solution:
* New wallet release * A Main Block chain from a starting point block #, afterwards, you can mine on that and all mining will be valid
Though I prefer starting from where all pools were down, pls vote for rollback vs non-rollback (rollback see my prior post) if this is still the case
Detail information will be posted.
In this period, I expect options of mining:
* Solo mining * Mining through pools, such as, P2Pool, NOMP if one can offer that I can see easy work compared to MPOS * MPOS if anyone would like to offer
2) Fix
This will be a parallel effort; as to how will be posted. Once Fix is done, we will bring fix to the main chain.
This is a balanced solutions to keep us going as I can see. I will make 1) to happen later today; guide will be posted.
|
|
|
|
Windozxpert
|
|
August 23, 2017, 12:43:48 PM |
|
To ALL,
The fork takes place from one pool to another, and that I believe something fundamental needs a clarification as we haven't seen this before. This has messed around the mining. I suggest stop mining at this time until we firstly 1) get a keep-it-going solution, and 2) root cause finding and a solution to the fork. The mining just going on, unfortunately, doesn't make sense to me, and I would propose a rollover back to a fair point. Let me know if rollover sounds good to you, and where you want to startover.
Here I am going to nail down the plan that we believe better suite for the current situation, and make the corresponding wallet release at tonight.
1) A keep-it-going solution:
* New wallet release * A Main Block chain from a starting point block #, afterwards, you can mine on that and all mining will be valid
Though I prefer starting from where all pools were down, pls vote for rollback vs non-rollback (rollback see my prior post) if this is still the case
Detail information will be posted.
In this period, I expect options of mining:
* Solo mining * Mining through pools, such as, P2Pool, NOMP if one can offer that I can see easy work compared to MPOS * MPOS if anyone would like to offer
2) Fix
This will be a parallel effort; as to how will be posted. Once Fix is done, we will bring fix to the main chain.
This is a balanced solutions to keep us going as I can see. I will make 1) to happen later today; guide will be posted. My vote: Pick up where the pools left off. No rollback.
|
There's no I in team, but there is a "Me" if you jumble it up. ~ House, M.D.
|
|
|
sCyborg
Newbie
Offline
Activity: 6
Merit: 0
|
|
August 23, 2017, 12:46:15 PM |
|
Yeah preferably no rollback.
|
|
|
|
|