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

[starmman]

[SNIP]

I can upload the debuglog for you if you need.

I had a similar problem before and a full reload of the blockchain with the good nodes in my magi.conf helped me.

[joelao95]

Doesnt help the Wallet cant get across block 1217757, curious is that only 1 Wallet is affected all others run fine.

Code:

trying connection [2a02:8108:8b40:d18:7c2b:c1cd:eab:179c]:8233 lastseen=211.4hrs
Added 618 addresses from 104.207.149.217: 9 tried, 9591 new
Added 659 addresses from 104.207.149.217: 9 tried, 9562 new
Added 334 addresses from 104.207.149.217: 9 tried, 9568 new
connection timeout
connection timeout
trying connection 87.78.184.144:8233 lastseen=66.4hrs
connection timeout
trying connection 197.253.33.170:8233 lastseen=1.1hrs
connection timeout
trying connection 24.140.248.78:8233 lastseen=1.1hrs
connection timeout
trying connection 97.102.77.41:8233 lastseen=5.1hrs
connection timeout
trying connection 190.142.243.32:8233 lastseen=156.6hrs
received block d6cf05d12962e8050414
ProcessBlock: ORPHAN BLOCK, prev=000000001a3ae11324ab
received block 000000001a3ae11324ab
ProcessBlock: ORPHAN BLOCK, prev=000000002ab5124acfec
received block 000000002ab5124acfec
ProcessBlock: ORPHAN BLOCK, prev=4ecb39f3529c09caee2e
received block 0000000027ba1ac55030
Misbehaving: 62.210.252.207:8233 (0 -> 100) DISCONNECTING
disconnecting node 62.210.252.207:8233
ERROR: ProcessBlock() : block with too little proof-of-work
connection timeout
trying connection 2.236.133.147:8233 lastseen=89.7hrs
connection timeout
trying connection 84.215.7.210:8233 lastseen=1.1hrs
Flushed 9577 addresses to peers.dat  61ms
connection timeout
trying connection 46.188.1.45:8233 lastseen=1.1hrs
connection timeout
trying connection 37.214.136.230:8233 lastseen=44.6hrs
connection timeout
trying connection 24.140.248.78:8233 lastseen=1.1hrs
socket no message in first 60 seconds, 0 1
disconnecting node 104.131.42.100:8233
connection timeout
trying connection 37.47.104.190:8233 lastseen=673.3hrs
connection timeout
trying connection 87.212.198.241:8233 lastseen=1.1hrs
connection timeout
trying connection 187.78.19.191:8233 lastseen=67.9hrs
connection timeout
trying connection 188.66.69.56:8233 lastseen=1.1hrs
connection timeout
trying connection 220.214.11.117:8233 lastseen=121.0hrs
connection timeout
trying connection 24.140.248.78:8233 lastseen=1.1hrs
received block 0dcaf99ecad91eb3f70b
ProcessBlock: ORPHAN BLOCK, prev=d6cf05d12962e8050414
connection timeout
trying connection 95.42.179.205:8233 lastseen=1.1hrs
connection timeout
trying connection [2601:196:8901:898a:51c1:337c:5f7d:68fa]:8233 lastseen=177.7hrs
connection timeout
trying connection 89.204.155.43:8233 lastseen=890.8hrs
connection timeout
trying connection 154.119.225.5:8233 lastseen=1.1hrs
connection timeout
trying connection 96.248.122.64:8233 lastseen=6.2hrs
connection timeout
trying connection 24.140.248.78:8233 lastseen=1.1hrs
connection timeout
trying connection [2a06:8ec0:3::1:28e6]:8233 lastseen=2.3hrs
connected [2a06:8ec0:3::1:28e6]:8233
send version message: version 71051, blocks=1217757, us=[2003:c3:a3c3:7700:71bd:fbe5:cf03:5005]:8233, them=[2a06:8ec0:3::1:28e6]:8233, peer=[2a06:8ec0:3::1:28e6]:8233
Added time data, samples 9, offset -22 (+0 minutes)
nTimeOffset = -23  (+0 minutes)
Moving [2a06:8ec0:3::1:28e6]:8233 to tried
receive version message: version 71051, blocks=1219032, us=[2003:c3:a3c3:7700:71bd:fbe5:cf03:5005]:50836, them=[2a06:8ec0:3::1:28e6]:8233, peer=[2a06:8ec0:3::1:28e6]:8233
trying connection 104.251.215.107:8233 lastseen=0.3hrs
connected 104.251.215.107:8233
send version message: version 71051, blocks=1217757, us=87.157.60.239:8233, them=104.251.215.107:8233, peer=104.251.215.107:8233
received block 0000000003025a87a9cc
ProcessBlock: ORPHAN BLOCK, prev=0dcaf99ecad91eb3f70b
trying connection 46.188.1.45:8233 lastseen=1.1hrs
trying connection 104.128.225.215:8233 lastseen=385654.5hrs
connection timeout
trying connection 91.155.183.83:8233 lastseen=1.1hrs
Added 619 addresses from 2a06:8ec0:3::1:28e6: 10 tried, 9764 new
received block 0000000017106db73b6d
ProcessBlock: ORPHAN BLOCK, prev=0000000003025a87a9cc
Added 639 addresses from 2a06:8ec0:3::1:28e6: 10 tried, 9894 new
connection timeout
Added 332 addresses from 2a06:8ec0:3::1:28e6: 10 tried, 9940 new
trying connection 104.128.225.240:8233 lastseen=385654.5hrs
connection timeout
trying connection 91.155.183.83:8233 lastseen=1.1hrs
connection timeout
trying connection 104.128.225.241:8233 lastseen=385654.5hrs
Added time data, samples 10, offset -24 (+0 minutes)
receive version message: version 71041, blocks=1219033, us=87.157.60.239:63622, them=104.251.215.107:8233, peer=104.251.215.107:8233
Flushed 9950 addresses to peers.dat  46ms
connection timeout
trying connection 197.253.33.170:8233 lastseen=1.1hrs
connection timeout
trying connection 104.131.42.100:8233 lastseen=385654.5hrs
connected 104.131.42.100:8233
send version message: version 71051, blocks=1217757, us=87.157.60.239:8233, them=104.131.42.100:8233, peer=104.131.42.100:8233
trying connection 178.33.228.14:8233 lastseen=385654.5hrs
received block 0000000027ba1ac55030
Misbehaving: 110.11.227.163:8233 (0 -> 100) DISCONNECTING
disconnecting node 110.11.227.163:8233
ERROR: ProcessBlock() : block with too little proof-of-work
connection timeout

I can upload the debuglog for you if you need.

I suppose you already tried restarting the wallet. Firstly, see if block 1217757 is on the right chain. A quick verification is to check its hash

daemon:

Code:

magid getblockhash 1217757

qt-wallet under console:

Code:

getblockhash 1217757

819506440fe4287e605022bac64465b36a26d9fc2e0c5d9423f0fe63428a3960 should be the output. Some details of this block: https://chainz.cryptoid.info/xmg/block.dws?819506440fe4287e605022bac64465b36a26d9fc2e0c5d9423f0fe63428a3960.htm

Once this is confirmed, put the following in magi.conf to force connecting with these nodes only (no addnode), then restart wallet:

Code:

connect=104.128.225.215
connect=104.128.225.240
connect=104.128.225.241
connect=104.131.42.100
connect=216.189.144.186
connect=216.189.144.211
connect=216.189.144.212
connect=104.131.42.100
connect=xmg.suprnova.cc

If the above doesn't help, we might consider resync the blockchain; use the block data here: http://coinmagi.org/bin/block-chain. If you can upload the debug.log, I can double check.

[Visi0n4ry]

[SNIP]

I can upload the debuglog for you if you need.

I had a similar problem before and a full reload of the blockchain with the good nodes in my magi.conf helped me.

Doesnt help the Wallet cant get across block 1217757, curious is that only 1 Wallet is affected all others run fine.

Code:

trying connection [2a02:8108:8b40:d18:7c2b:c1cd:eab:179c]:8233 lastseen=211.4hrs
Added 618 addresses from 104.207.149.217: 9 tried, 9591 new
Added 659 addresses from 104.207.149.217: 9 tried, 9562 new
Added 334 addresses from 104.207.149.217: 9 tried, 9568 new
connection timeout
connection timeout
trying connection 87.78.184.144:8233 lastseen=66.4hrs
connection timeout
trying connection 197.253.33.170:8233 lastseen=1.1hrs
connection timeout
trying connection 24.140.248.78:8233 lastseen=1.1hrs
connection timeout
trying connection 97.102.77.41:8233 lastseen=5.1hrs
connection timeout
trying connection 190.142.243.32:8233 lastseen=156.6hrs
received block d6cf05d12962e8050414
ProcessBlock: ORPHAN BLOCK, prev=000000001a3ae11324ab
received block 000000001a3ae11324ab
ProcessBlock: ORPHAN BLOCK, prev=000000002ab5124acfec
received block 000000002ab5124acfec
ProcessBlock: ORPHAN BLOCK, prev=4ecb39f3529c09caee2e
received block 0000000027ba1ac55030
Misbehaving: 62.210.252.207:8233 (0 -> 100) DISCONNECTING
disconnecting node 62.210.252.207:8233
ERROR: ProcessBlock() : block with too little proof-of-work
connection timeout
trying connection 2.236.133.147:8233 lastseen=89.7hrs
connection timeout
trying connection 84.215.7.210:8233 lastseen=1.1hrs
Flushed 9577 addresses to peers.dat  61ms
connection timeout
trying connection 46.188.1.45:8233 lastseen=1.1hrs
connection timeout
trying connection 37.214.136.230:8233 lastseen=44.6hrs
connection timeout
trying connection 24.140.248.78:8233 lastseen=1.1hrs
socket no message in first 60 seconds, 0 1
disconnecting node 104.131.42.100:8233
connection timeout
trying connection 37.47.104.190:8233 lastseen=673.3hrs
connection timeout
trying connection 87.212.198.241:8233 lastseen=1.1hrs
connection timeout
trying connection 187.78.19.191:8233 lastseen=67.9hrs
connection timeout
trying connection 188.66.69.56:8233 lastseen=1.1hrs
connection timeout
trying connection 220.214.11.117:8233 lastseen=121.0hrs
connection timeout
trying connection 24.140.248.78:8233 lastseen=1.1hrs
received block 0dcaf99ecad91eb3f70b
ProcessBlock: ORPHAN BLOCK, prev=d6cf05d12962e8050414
connection timeout
trying connection 95.42.179.205:8233 lastseen=1.1hrs
connection timeout
trying connection [2601:196:8901:898a:51c1:337c:5f7d:68fa]:8233 lastseen=177.7hrs
connection timeout
trying connection 89.204.155.43:8233 lastseen=890.8hrs
connection timeout
trying connection 154.119.225.5:8233 lastseen=1.1hrs
connection timeout
trying connection 96.248.122.64:8233 lastseen=6.2hrs
connection timeout
trying connection 24.140.248.78:8233 lastseen=1.1hrs
connection timeout
trying connection [2a06:8ec0:3::1:28e6]:8233 lastseen=2.3hrs
connected [2a06:8ec0:3::1:28e6]:8233
send version message: version 71051, blocks=1217757, us=[2003:c3:a3c3:7700:71bd:fbe5:cf03:5005]:8233, them=[2a06:8ec0:3::1:28e6]:8233, peer=[2a06:8ec0:3::1:28e6]:8233
Added time data, samples 9, offset -22 (+0 minutes)
nTimeOffset = -23  (+0 minutes)
Moving [2a06:8ec0:3::1:28e6]:8233 to tried
receive version message: version 71051, blocks=1219032, us=[2003:c3:a3c3:7700:71bd:fbe5:cf03:5005]:50836, them=[2a06:8ec0:3::1:28e6]:8233, peer=[2a06:8ec0:3::1:28e6]:8233
trying connection 104.251.215.107:8233 lastseen=0.3hrs
connected 104.251.215.107:8233
send version message: version 71051, blocks=1217757, us=87.157.60.239:8233, them=104.251.215.107:8233, peer=104.251.215.107:8233
received block 0000000003025a87a9cc
ProcessBlock: ORPHAN BLOCK, prev=0dcaf99ecad91eb3f70b
trying connection 46.188.1.45:8233 lastseen=1.1hrs
trying connection 104.128.225.215:8233 lastseen=385654.5hrs
connection timeout
trying connection 91.155.183.83:8233 lastseen=1.1hrs
Added 619 addresses from 2a06:8ec0:3::1:28e6: 10 tried, 9764 new
received block 0000000017106db73b6d
ProcessBlock: ORPHAN BLOCK, prev=0000000003025a87a9cc
Added 639 addresses from 2a06:8ec0:3::1:28e6: 10 tried, 9894 new
connection timeout
Added 332 addresses from 2a06:8ec0:3::1:28e6: 10 tried, 9940 new
trying connection 104.128.225.240:8233 lastseen=385654.5hrs
connection timeout
trying connection 91.155.183.83:8233 lastseen=1.1hrs
connection timeout
trying connection 104.128.225.241:8233 lastseen=385654.5hrs
Added time data, samples 10, offset -24 (+0 minutes)
receive version message: version 71041, blocks=1219033, us=87.157.60.239:63622, them=104.251.215.107:8233, peer=104.251.215.107:8233
Flushed 9950 addresses to peers.dat  46ms
connection timeout
trying connection 197.253.33.170:8233 lastseen=1.1hrs
connection timeout
trying connection 104.131.42.100:8233 lastseen=385654.5hrs
connected 104.131.42.100:8233
send version message: version 71051, blocks=1217757, us=87.157.60.239:8233, them=104.131.42.100:8233, peer=104.131.42.100:8233
trying connection 178.33.228.14:8233 lastseen=385654.5hrs
received block 0000000027ba1ac55030
Misbehaving: 110.11.227.163:8233 (0 -> 100) DISCONNECTING
disconnecting node 110.11.227.163:8233
ERROR: ProcessBlock() : block with too little proof-of-work
connection timeout

I can upload the debuglog for you if you need.

I suppose you already tried restarting the wallet. Firstly, see if block 1217757 is on the right chain. A quick verification is to check its hash

daemon:

Code:

magid getblockhash 1217757

qt-wallet under console:

Code:

getblockhash 1217757

819506440fe4287e605022bac64465b36a26d9fc2e0c5d9423f0fe63428a3960 should be the output. Some details of this block: https://chainz.cryptoid.info/xmg/block.dws?819506440fe4287e605022bac64465b36a26d9fc2e0c5d9423f0fe63428a3960.htm

Once this is confirmed, put the following in magi.conf to force connecting with these nodes only (no addnode), then restart wallet:

Code:

connect=104.128.225.215
connect=104.128.225.240
connect=104.128.225.241
connect=104.131.42.100
connect=216.189.144.186
connect=216.189.144.211
connect=216.189.144.212
connect=104.131.42.100
connect=xmg.suprnova.cc

If the above doesn't help, we might consider resync the blockchain; use the block data here: http://coinmagi.org/bin/block-chain. If you can upload the debug.log, I can double check.

Thank you for your quick answers!
Unfortunately i already followed starmman and did the resync.
But maybe this will help others with the same problem, also it would be interesting to know how this happened.

[starmman]

Thank you for your quick answers!
Unfortunately i already followed starmman and did the resync.
But maybe this will help others with the same problem, also it would be interesting to know how this happened.

Indeed it was really good to see some alternative ways of debugging the wallets - I like this forum - I'm learning more each day

[th3.r00t]

I've notice that the price info disappeared from wallet from about 2 days.

Also the wallet isn't staking from atleast 10 hours


Code:

getmininginfo
{
"blocks" : 1220363,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : {
"proof-of-work" : 2.04336221,
"proof-of-stake" : 0.01807929,
"search-interval" : 1
},
"blockvalue" : {
"difficulty-V2" : 3.18456382,
"blockvalue" : 2.77791977
},
"netmhashps" : 44.34277312,
"netstakeweight" : 928195.69517220,
"errors" : "",
"pooledtx" : 0,
"stakeweight" : {
"minimum" : 17615,
"maximum" : 0,
"combined" : 17615
},
"Expected PoS (hours)" : 1,
"stakeinterest" : 0.03125170,
"testnet" : false,
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 44342773,
"testnet" : false
}

[111magic]

There was some great volume on XMG overnight - I'm loving that kind of volatility

Me also. Its very good for Magi to get some great volume.

[rotzbouf]

Having some sync issues with the wallet. I tried already to purge the data folder for a full resync but now I am stuck at block 0.
I have put the below to my conf.

connect=104.128.225.215
connect=104.128.225.240
connect=104.128.225.241
connect=104.131.42.100
connect=216.189.144.186
connect=216.189.144.211
connect=216.189.144.212
connect=104.131.42.100
connect=xmg.suprnova.cc

[Visi0n4ry]

Having some sync issues with the wallet. I tried already to purge the data folder for a full resync but now I am stuck at block 0.
I have put the below to my conf.

connect=104.128.225.215
connect=104.128.225.240
connect=104.128.225.241
connect=104.131.42.100
connect=216.189.144.186
connect=216.189.144.211
connect=216.189.144.212
connect=104.131.42.100
connect=xmg.suprnova.cc

What exactly do you mean with "I tried already to purge the data folder", you need to close the Wallet and delete "blocks" "database" "peers.dat" NOT wallet.dat go to your config and put

Code:

addnode=104.128.225.215
addnode=104.128.225.240
addnode=104.128.225.241
addnode=104.131.42.100
addnode=216.189.144.186
addnode=216.189.144.211
addnode=216.189.144.212
addnode=104.131.42.100
addnode=xmg.suprnova.cc

into it, save exit.

Go to http://coinmagi.org/bin/block-chain download m-block-chain.zip and unzip "blocks" and "database" into your wallet folder.

Start wallet, now it should recync the last few blocks.

[rotzbouf]

Well, purging data folder means delete all content except wallet.dat and magi.conf from the ~/.magi folder.

Will change the connect line into addnode and try again.

Edit: Ok the connect command seems to be the problem. After changing connect into addnode in my config, it starts syncing again.

[starmman]

Well, purging data folder means delete all content except wallet.dat and magi.conf from the ~/.magi folder.

Will change the connect line into addnode and try again.

Edit: Ok the connect command seems to be the problem. After changing connect into addnode in my config, it starts syncing again.

Great to hear =) Hopefully everybody is back on the blockchain again now =D

[Bajank]

XMG ..
good for trade

[starmman]

XMG ..
good for trade

I agree, Magi is one of my favourite coins to trade, and probably the most profitable - but also think its a good one to hold too - volatility is quite nice - but also the market cap has an upward trend.

[The Frisian]

XMG ..
good for trade

I agree, Magi is one of my favourite coins to trade, and probably the most profitable - but also think its a good one to hold too - volatility is quite nice - but also the market cap has an upward trend.

XMG volume on Poloniex is very low, not good!

[joelao95]

Well, purging data folder means delete all content except wallet.dat and magi.conf from the ~/.magi folder.

Will change the connect line into addnode and try again.

Edit: Ok the connect command seems to be the problem. After changing connect into addnode in my config, it starts syncing again.

"Connect" will force connection with the nodes only we're running. There seems no issues with "connect" as I just tried.

[joelao95]

I've notice that the price info disappeared from wallet from about 2 days.

Also the wallet isn't staking from atleast 10 hours


Code:

getmininginfo
{
"blocks" : 1220363,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : {
"proof-of-work" : 2.04336221,
"proof-of-stake" : 0.01807929,
"search-interval" : 1
},
"blockvalue" : {
"difficulty-V2" : 3.18456382,
"blockvalue" : 2.77791977
},
"netmhashps" : 44.34277312,
"netstakeweight" : 928195.69517220,
"errors" : "",
"pooledtx" : 0,
"stakeweight" : {
"minimum" : 17615,
"maximum" : 0,
"combined" : 17615
},
"Expected PoS (hours)" : 1,
"stakeinterest" : 0.03125170,
"testnet" : false,
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 44342773,
"testnet" : false
}

I can see that you seem to have PoS coming. What does "getmininginfo" give?

I don't see issues with price info; try to click on it to refresh.

[starmman]

XMG ..
good for trade

I agree, Magi is one of my favourite coins to trade, and probably the most profitable - but also think its a good one to hold too - volatility is quite nice - but also the market cap has an upward trend.

XMG volume on Poloniex is very low, not good!

I notice that this often happens when the BTC price is rising sharply (or during POI), Magi usually gets more volume when BTC is falling or flat. Both times we had issues with Bittrex it was during sharp increases of BTC, I think the reason is because not so many people want to sell their Magi.

[starmman]

Volume is up a bit more today now - I also see market cap has peaked above $200k again, signs are okay - but would be better if we can get more volume, once my trading robot has bedded in, I'll change some parameters which will likely help a little bit, my trading volume isn't so high yet though so probably wont make an enormous impact to start with - but every little bit helps =D.

[ujang1]

XMG ..
good for trade

I agree, Magi is one of my favourite coins to trade, and probably the most profitable - but also think its a good one to hold too - volatility is quite nice - but also the market cap has an upward trend.

XMG volume on Poloniex is very low, not good!

It's too bad that there no market manipulation. Small volume = small interest from Polo to keep this coin at exchange.

[starmman]

XMG ..
good for trade

I agree, Magi is one of my favourite coins to trade, and probably the most profitable - but also think its a good one to hold too - volatility is quite nice - but also the market cap has an upward trend.

XMG volume on Poloniex is very low, not good!

It's too bad that there no market manipulation. Small volume = small interest from Polo to keep this coin at exchange.

We could certainly do with a couple of larger investors on polo looking at Magi, any idea how we can get more interest?

Magi volume has always been at the low end of the Polo charts and now the volume is actually higher than average since the start of this year - certainly in terms of USD volume. check CMC from 01/11/2016 to 03/03/2017 (before that was a massive pump which skews the charts), you'll see things are heading in the right direction

[starmman]

It's too bad that there no market manipulation. Small volume = small interest from Polo to keep this coin at exchange.

We could certainly do with a couple of larger investors on polo looking at Magi, any idea how we can get more interest?

Magi volume has always been at the low end of the Polo charts and now the volume is actually higher than average since the start of this year - certainly in terms of USD volume. check CMC from 01/11/2016 to 03/03/2017 (before that was a massive pump which skews the charts), you'll see things are heading in the right direction

Comparing volume from Jan/Mar to Jan/Mar last year our volume is up x10 or x20 - highest 24hr volume was ~350USD last year - this year we are looking at ~17000USD, lowest this year is about 170 USD and last year 28USD, looks almost like a different coin =D