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

[Vitalik_Pedik]

Can anybody provide a link to a known good copy of the blockchain?

Thanks in advance!

If TrasMaMod connected only to 104.128.225.215 node and they last block compare to https://poolinfo.systms.org/ better to ask them to dump current blockchain for you.

Is there a block explorer to verify block height? Not sure how many chain splits are out there so need some solid way to get on and verify the correct chain tip

Only https://poolinfo.systms.org/, all other can be wrong.

Thanks!

On another note has the dev provided any technical explanation of what caused this latest issue? Is there only 1 dev on this coin now?

page or so back he replied to me and said he knows of the issues and is working on it.

i got a reply from joe. I hope this doesnt get me in trouble.

Hi Jeremy,

I'm very aware of the issue, and trying to make out fixes (hard fork). It was happening on the PoS; unfortunately I've to have extended days; I'll keep posted.

-Joe

Happy to do a screenshot to prove its from joe.

Yes he working on creation of new issues. This is not joke.

[1714914444]

1714914444

[Jeremy450]

Can anybody provide a link to a known good copy of the blockchain?

Thanks in advance!

If TrasMaMod connected only to 104.128.225.215 node and they last block compare to https://poolinfo.systms.org/ better to ask them to dump current blockchain for you.

Is there a block explorer to verify block height? Not sure how many chain splits are out there so need some solid way to get on and verify the correct chain tip

Only https://poolinfo.systms.org/, all other can be wrong.

Thanks!

On another note has the dev provided any technical explanation of what caused this latest issue? Is there only 1 dev on this coin now?

page or so back he replied to me and said he knows of the issues and is working on it.

i got a reply from joe. I hope this doesnt get me in trouble.

Hi Jeremy,

I'm very aware of the issue, and trying to make out fixes (hard fork). It was happening on the PoS; unfortunately I've to have extended days; I'll keep posted.

-Joe

Happy to do a screenshot to prove its from joe.

Yes he working on creation of new issues. This is not joke.

https://media2.giphy.com/media/U2nN0ridM4lXy/giphy.gif

[DisasterFaster]

Can anybody provide a link to a known good copy of the blockchain?

Thanks in advance!

If TrasMaMod connected only to 104.128.225.215 node and they last block compare to https://poolinfo.systms.org/ better to ask them to dump current blockchain for you.

Is there a block explorer to verify block height? Not sure how many chain splits are out there so need some solid way to get on and verify the correct chain tip

Only https://poolinfo.systms.org/, all other can be wrong.

Thanks!

On another note has the dev provided any technical explanation of what caused this latest issue? Is there only 1 dev on this coin now?

page or so back he replied to me and said he knows of the issues and is working on it.

i got a reply from joe. I hope this doesnt get me in trouble.

Hi Jeremy,

I'm very aware of the issue, and trying to make out fixes (hard fork). It was happening on the PoS; unfortunately I've to have extended days; I'll keep posted.

-Joe

Happy to do a screenshot to prove its from joe.

Yes he working on creation of new issues. This is not joke.

I think it might be helpful to have more technical details about the problem or problems and then be able to get input from other devs.

1 dev on a coin can be a bit overwhelming that's for sure...

[Foo_Plinger]

Can anyone contact the admin for https://pom.m-hash.com/ pool?  I have been locked for weeks, unable to contact anyone there

[Jeremy450]

GGGGRRRRRRRR This dam wallet needs a manual sync function!!!!!!!!!!

Was in sync for a hour or so and now over 40 blocks out!!!!!!

and the stupid thing wont dam sync again even after multiple program restartts!

[The Doktor]

Is joe's node still "Correct? It seems about 50 blocks behind minerclain & poolinfo, but the same as trasmamod.

[tazzz013]

Anyone have an idea how to fix the wallet sync issue?  Or are we on standby.

[Jeremy450]

looks like
minerclaim.net
PoM Pool
Coinmagi XMG Pool
and
Coin of Magi

possibly on the wrong/future chain??

cant seem push the wallet past 1822914

[txwooley]

Anyone have the latest chain snapshot?  I am 1000 blocks behind but the snapshot from https://m-core.org/bin/block-chain/ is old.  Only goes up to 1813042.  I solved 3 blocks last night solo mining but they are probably on the wrong fork.

Sigh...

[s0litaire]

Is joe's node still "Correct? It seems about 50 blocks behind minerclain & poolinfo, but the same as trasmamod.

I'm going with:

If I've not heard anything to the contrary from Joe, then his chain is the "correct" one to be on.

I'm using the same magi.conf details as Trasmamod posted a few posts above, about only having a single connect node listed and listen= set to Zero, (which stops it picking up blocks from other nodes that might be on a different blockchain.) :

Code:

connect=104.128.225.215
listen=0

[edward0181]

Anyone have the latest chain snapshot?  I am 1000 blocks behind but the snapshot from https://m-core.org/bin/block-chain/ is old.  Only goes up to 1813042.  I solved 3 blocks last night solo mining but they are probably on the wrong fork.

Sigh...

is of this morning.

https://poolinfo.systms.org/chain.tar.gz

[Jeremy450]

Anyone have the latest chain snapshot?  I am 1000 blocks behind but the snapshot from https://m-core.org/bin/block-chain/ is old.  Only goes up to 1813042.  I solved 3 blocks last night solo mining but they are probably on the wrong fork.

Sigh...

thats the lastest one available.

[Jeremy450]

Is joe's node still "Correct? It seems about 50 blocks behind minerclain & poolinfo, but the same as trasmamod.

I'm going with:

If I've not heard anything to the contrary from Joe, then his chain is the "correct" one to be on.

I'm using the same magi.conf details as Trasmamod posted a few posts above, about only having a single connect node listed and listen= set to Zero, (which stops it picking up blocks from other nodes that might be on a different blockchain.) :

Code:

connect=104.128.225.215
listen=0

makes no difference what you use. theres still a issue cos dev is on 1822915 and 1 or 2 other pools. but the
minerclaim.net
PoM Pool
Coinmagi XMG Pool
and
Coin of Magi
are on 1822980

i've tried multiple nodes and they all go to 1822915

right now one knows who's is telling the truth.

going by the amount of unconfirmed coins i have in minerclaim i think they are on the wrong chain.

[s0litaire]

Anyone have the latest chain snapshot?  I am 1000 blocks behind but the snapshot from https://m-core.org/bin/block-chain/ is old.  Only goes up to 1813042.  I solved 3 blocks last night solo mining but they are probably on the wrong fork.

Sigh...

That's the last "safe"/"Correct" block in the chain before the split. so best start from there to stop any more errors.

Change your magi.conf to remove any "addnode" entries and only have a single "connect=" listed. Also make sure "listen=" is set to Zero

Code:

connect=104.128.225.215
listen=0

replace your "Database" and "Block" folders with the ones from 1813042 snapshot. Wait for it to sync (it might take an couple of hours.)
Then do a :

Code:

checkwallet

then

Code:

repairwallet

in the wallet console and restart the wallet.

You might loose the coins mined unfortunately!

(I was happily mining on the test wallet and made a nice 160xmg which I know were going away once I got back on the main wallet)   so you're not alone in the pain of loosing xmg

[txwooley]

Thanks guys.  I loaded the last known good snapshot and synced with Joe.  As predicted, I lost everything I mined yesterday.

I am now on 1822918.  The link to  poolinfo.systms shows them on block 1822985.  I think I'll stick with Joes for now.  Hopefully he is working on a fix.

[tazzz013]

Anyone have the latest chain snapshot?  I am 1000 blocks behind but the snapshot from https://m-core.org/bin/block-chain/ is old.  Only goes up to 1813042.  I solved 3 blocks last night solo mining but they are probably on the wrong fork.

Sigh...

That's the last "safe"/"Correct" block in the chain before the split. so best start from there to stop any more errors.

Change your magi.conf to remove any "addnode" entries and only have a single "connect=" listed. Also make sure "listen=" is set to Zero

Code:

connect=104.128.225.215
listen=0

replace your "Database" and "Block" folders with the ones from 1813042 snapshot. Wait for it to sync (it might take an couple of hours.)
Then do a :

Code:

checkwallet

then

Code:

repairwallet

in the wallet console and restart the wallet.

You might loose the coins mined unfortunately!

(I was happily mining on the test wallet and made a nice 160xmg which I know were going away once I got back on the main wallet)   so you're not alone in the pain of loosing xmg

Thanks for your info, wallet seems to back in sync.  What does the change on listen=1 to listen=0 do?

[tazzz013]

Minerclaim is just a mess right now. Confirms are beyond slow.   Got a feeling I'm gonna loose here

XMG Account Balance
Confirmed    0.491210
Unconfirmed 3.037001

[icecoin2000]

Wallet debuglog :


trying connection 104.128.225.215 lastseen=0.0hrs
connected 104.128.225.215
send version message: version 71064, blocks=1821844, us=0.0.0.0:0, them=104.128.225.215:8233, peer=104.128.225.215:8233
receive version message: version 71064, blocks=1822934, us=31.209.18.153:38873, them=104.128.225.215:8233, peer=104.128.225.215:8233
Flushed 8942 addresses to peers.dat  15ms
received block 000000017c1729d9f0bf
ProcessBlock: ORPHAN BLOCK, prev=000000018863b1645665
Flushed 8942 addresses to peers.dat  16ms
received block a6c7243194fbadbe7d2b
Misbehaving: 104.128.225.215:8233 (0 -> 100) DISCONNECTING
disconnecting node 104.128.225.215
ERROR: ProcessBlock() : block with too little proof-of-stake


Debug window:
Current number of block 1821844


https://poolinfo.systms.org/   gives a couple of different network blocks for the pools..  

 

[tommyrsk]

What does the change on listen=1 to listen=0 do?

it means: Do not accept any incomming request from other nodes, you are then sticked only to the node you specified with connect=

[The Seller]

That's the last "safe"/"Correct" block in the chain before the split. so best start from there to stop any more errors.

Change your magi.conf to remove any "addnode" entries and only have a single "connect=" listed. Also make sure "listen=" is set to Zero

Code:

connect=104.128.225.215
listen=0

replace your "Database" and "Block" folders with the ones from 1813042 snapshot. Wait for it to sync (it might take an couple of hours.)
Then do a :

Code:

checkwallet

then

Code:

repairwallet

in the wallet console and restart the wallet.

You might loose the coins mined unfortunately!

(I was happily mining on the test wallet and made a nice 160xmg which I know were going away once I got back on the main wallet)   so you're not alone in the pain of loosing xmg

You're a great friend, your information is useful to someone else's friend. Continue like this park,