Following are recommended in magi.conf when we have the chain up and running: rpcuser=rpcuser
rpcpassword=rpcpass
rpcport=8232
rpcallowip=127.0.0.1
listen=0
connect=104.128.225.215
|
|
|
|
Cryptos are not banks. Their ledgers ARE reversable. HUGE difference. If people expect cryptos to be like banks then they should go back to the fiat banks, frankly. This is a new frontier. If they can't deal with the heat kinds, then they should not be in the flames.
Those who choose this route are forging a NEW path, away from banks. In this realm, Rollbacks are POSSIBLE....
...
Enoch
I'm sorry for the situation but there must be a route being taken, and the one that most vote for to go with. We were in a dilemma that anyone would hate that to happen by the fork status that already left damages, and when it comes to a decision, that's hard but must be one that, we all know that, a decision won't go through 100% agreement, but to minimize impacts as much as possible. |
|
|
|
[...]
I will post detailed docs before 8/24/2017 at 7:00 PM EST time.
In parallel efforts of fixing the issue, we will make a separate test field, either testnet or a different chain.
Thanks for the info, Joe. PM me if you'd like an extra node in the test field. Thanks, I'll PM when come to that point. |
|
|
|
|
As I received many requests of no-rollback and also many posts here, we will take the majority that we will go on with the chain on 104.128.225.215 as is, NO ROLLBACK. However, I strongly believe the PoW reward needs a reset at this mode before fix is released in the near future, and the number I have in mind is maximum 15 XMG / block. This is a temporary solution so that we keep chain / mining going. I temporarily shut the node down until we make release of the wallet. Please be prepare for the mining which can be done through solo mining. Please ask if you have questions of starting up solo mining. In the meantime, we seek pools like NOMP; few people present help on NOMP. I appreciate this.
The target time of new wallet and having the chain up is tomorrow (8/24/2017), at 7:00 PM EST time.
Rest assured we won't touch the chain on 104.128.225.215. We will just let it grow, and always take 104.128.225.215 as the best chain. If you lost connection to it, pls have a reconnection. Sorry, again this is a temporary solution.
I will post detailed docs before 8/24/2017 at 7:00 PM EST time.
In parallel efforts of fixing the issue, we will make a separate test field, either testnet or a different chain.
|
|
|
|
My vote: Pick up where the pools left off. No rollback.
That's what I meant, if that part was not clear in the post. * Though I prefer starting from where all pools were down, *
Block #1450090, GMT: Tuesday, August 22, 2017 6:04:25 AM, before this, PoM pool was just down. |
|
|
|
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. |
|
|
|
@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. |
|
|
|
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.
Taking into account the response to the post, following plan:
1) Release a fix to the current issue and test it on the current chain that is running. As there are quite a few different forks out there, we will simply maintain the chain that the node 104.128.225.215 is running so that we keep an untouched chain there, and recommend all the tests done on this chain too. Following that, I suggest people, when interested to run the wallet or test, make sync to this node.
Unfortunately, we cannot provide ETA of the fix, but will update ASAP.
2) Once the fix is fully tested without issues, say continuously running through a week / weeks, we make the official release, and a rollback back to a certain block #. We will take the blockchain data from 104.128.225.215 to make a copy up to the #.
Since we will carry out some tests, it is quite reasonable that the testing period should be excluded that comes rollback. In terms of the suggestions previously, I propose the rollback point to block #1450090, that is, GMT: Tuesday, August 22, 2017 6:04:25 AM, when I made the post and suggestion of "stopping mining". Earlier yesterday, I requested Bittrex to put wallet in maintenance mode; so all sending to & withdraw from Bittrex wallet shall be earlier than the above proposed rollback block #.
Please suggest.
Let me know if I missed something.
p.s., If you're getting loss and resource on the mining, we might deal with that somehow.
|
|
|
|
|
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.
|
|
|
|
|
It looks a fork taking place that made suprnova firstly turn to a different chain, and then Zpool. This causes much increase in the block value to a higher value but unavailable to majority miners since they are still in suprnova and Zpool. In this case, it will be better to maintain the block value to a lower value until we fix the fork issue or the majority miners are able to mine on the main chain. I will update the source for the above purpose if we all agree.
|
|
|
|
104.128.225.215 needs maintenance, will be up shortly. |
|
|
|
My linux wallet (for solomine only) suddenly stop sync.
A replace "connect=104.128.225.215" with "addnode=104.128.225.215" and when connections has become > 1 sync continued.
So connection to only one node to save chain is not working, therefore we will have new split very very soon.
Actually "connect" allows one to catch up the chain by syncing to a specific node. Once you're done that, you can remove connect lines. |
|
|
|
I just got a reply from Minerclaim support. Despite the coins that i have mined previously have been confirmed which at least took 500 blocks to be confirmed and are unlikely from a wrong chain they have confiscated the coins. Please avoid using pools that are dishonest. There are a lot of pools of other pools out there.
To the guys from Minerclaim. Enjoy the coins.
Minerclaim has worked with me and helped a lot on resolving issues especially took extra time on this far more than what I can imagine. The mess is from the chain back and forth. To all having loss in the incident from Minerclaim & elsewhere, pls make the claim to us as mentioned in https://bitcointalk.org/index.php?topic=735170.msg21044020#msg21044020. |
|
|
|
If you're saying blocks were not found, it just takes some time depending on the network. |
|
|
|
Thanks i actually got it running a few hrs ago with a lot of searching involved. But still figuring out how to add more miners to a single wallet without adding the ip for each one...
You can enable different IP by having in magi.conf |
|
|
|
|
Show Posts
