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

[Myth888]

List of issues:

http://m-core.org/issues.txt

Let me know what's missing.

Another issue:
I keep getting banned from the main node, and have no clue why:

Code:

trying connection 104.128.225.215 lastseen=0.0hrs
connected 104.128.225.215
send version message: version 71061, blocks=1451225, us=0.0.0.0:0, them=104.128.225.215:8233, peer=104.128.225.215:8233
socket closed
disconnecting node 104.128.225.215

Same when I start from scratch with 0 blocks. Two IPs banned in two days, always around midnight - 1am but that might be a coincidence.

Guess it might be related to https://bitcointalk.org/index.php?topic=735170.msg21232956#msg21232956, but editing banscore should not matter with whitelist=104.128.225.215 if I understand it correctly.

I don't think that is a ban, disconnect can happen for multiple reasons like network issues.

I get that, but I'm getting this very same message for 48 hours now, while it's running without issues on an other IP.
If I proxy the connection through another IP, it connects without issues, so it must be an IP ban.
And I got two nodes banned already, can't explain why though.

try adding
 banscore=500
dont ask why i dont know why but some users recommended it

[1714905941]

1714905941

[1714905941]

1714905941

[Apprentice]

all known pool hashrate is around 30Mhs, the network is 90Mhs 

[ex33s]

List of issues:

http://m-core.org/issues.txt

Let me know what's missing.

Another issue:
I keep getting banned from the main node, and have no clue why:

Code:

trying connection 104.128.225.215 lastseen=0.0hrs
connected 104.128.225.215
send version message: version 71061, blocks=1451225, us=0.0.0.0:0, them=104.128.225.215:8233, peer=104.128.225.215:8233
socket closed
disconnecting node 104.128.225.215

Same when I start from scratch with 0 blocks. Two IPs banned in two days, always around midnight - 1am but that might be a coincidence.

Guess it might be related to https://bitcointalk.org/index.php?topic=735170.msg21232956#msg21232956, but editing banscore should not matter with whitelist=104.128.225.215 if I understand it correctly.

I don't think that is a ban, disconnect can happen for multiple reasons like network issues.

I get that, but I'm getting this very same message for 48 hours now, while it's running without issues on an other IP.
If I proxy the connection through another IP, it connects without issues, so it must be an IP ban.
And I got two nodes banned already, can't explain why though.

try adding
 banscore=500
dont ask why i dont know why but some users recommended it

banscore increases the score (or misbehave as shown in logs), default is 100. With banscore of 500 you are allowing connected peers to submit "bad" blocks to you up to 5 times per ip before your peer bans the other peer.
The reason I'm using it now is as workaround for when a proper block is sent but something went wrong, that would case an misbehave score of 100 straight away and causing your peer to ban the other peer for 24 hrs (default setting, if you want to change it. Setting is bantime).
Not allowing the re-submit right now gives you an high chance of banning all proper peers and letting you fall behind. This is a workaround for a problem Joe has listed as an issue.

Hope this gives a bit of clarity on how banscore works and why i'm using it as an workaround for now.

I'm running poolinfo with these settings

Code:

banscore=500
bantime=7200

Which means poolinfo is allowing 5 major missbehaves (1 major is 100 in score) and when they hit a score of 500, poolinfo will ban that ip for 2 hrs (7200 seconds) before allowing that peer to reconnect.

[filoozom]

List of issues:

http://m-core.org/issues.txt

Let me know what's missing.

Another issue:
I keep getting banned from the main node, and have no clue why:

Code:

trying connection 104.128.225.215 lastseen=0.0hrs
connected 104.128.225.215
send version message: version 71061, blocks=1451225, us=0.0.0.0:0, them=104.128.225.215:8233, peer=104.128.225.215:8233
socket closed
disconnecting node 104.128.225.215

Same when I start from scratch with 0 blocks. Two IPs banned in two days, always around midnight - 1am but that might be a coincidence.

Guess it might be related to https://bitcointalk.org/index.php?topic=735170.msg21232956#msg21232956, but editing banscore should not matter with whitelist=104.128.225.215 if I understand it correctly.

I don't think that is a ban, disconnect can happen for multiple reasons like network issues.

I get that, but I'm getting this very same message for 48 hours now, while it's running without issues on an other IP.
If I proxy the connection through another IP, it connects without issues, so it must be an IP ban.
And I got two nodes banned already, can't explain why though.

try adding
 banscore=500
dont ask why i dont know why but some users recommended it

banscore increases the score (or misbehave as shown in logs), default is 100. With banscore of 500 you are allowing connected peers to submit "bad" blocks to you up to 5 times per ip before your peer bans the other peer.
The reason I'm using it now is as workaround for when a proper block is sent but something went wrong, that would case an misbehave score of 100 straight away and causing your peer to ban the other peer for 24 hrs (default setting, if you want to change it. Setting is bantime).
Not allowing the re-submit right now gives you an high chance of banning all proper peers and letting you fall behind. This is a workaround for a problem Joe has listed as an issue.

Hope this gives a bit of clarity on how banscore works and why i'm using it as an workaround for now.

I'm running poolinfo with these settings

Code:

banscore=500
bantime=7200

Which means poolinfo is allowing 5 major missbehaves (1 major is 100 in score) and when they hit a score of 500, poolinfo will ban that ip for 2 hrs (7200 seconds) before allowing that peer to reconnect.

Right, but this shouldn't matter with whitelist=104.128.225.215 on my side I think, which means that 104.128.225.215 banned my IPs for misbehaving, doesn't it?
I didn't ban anyone, and starting with a fresh wallet doesn't change anything.

[TheKingInYellow]

I noticed my wallet is now saying it's out of sync again despite being at the current block.

What gives? Is Magi just fucked now? Are any exchanges even accepting deposits?

[Windozxpert]

Minerclaim: Please send me the 299 pre-fork XMG coins I mined before the fork. I've sent in the request via email, but your site says to post concerns here.

[Windozxpert]

I noticed my wallet is now saying it's out of sync again despite being at the current block.

What gives? Is Magi just fucked now? Are any exchanges even accepting deposits?

No exchanges that I know of, they all say the developer requested a maintenance period to get the permanent fix out. The current implementation is only a temporary fix.

[TheKingInYellow]

I noticed my wallet is now saying it's out of sync again despite being at the current block.

What gives? Is Magi just fucked now? Are any exchanges even accepting deposits?

No exchanges that I know of, they all say the developer requested a maintenance period to get the permanent fix out. The current implementation is only a temporary fix.

I'm really worried my magi may be stuck on the forked chain. 

[starmman]

Ok, I'm giving up. I wish you all happy mining and a lot of XMG.

Sure this episode in the magi saga will be ended soon. =)

[111magic]

Ok, I'm giving up. I wish you all happy mining and a lot of XMG.

Sure this episode in the magi saga will be ended soon. =)

Yes and than Magi is going to a much better episode!
Magi will continue working on improvements and build on a great future. Every currency had his periods with issues.
Most important is how the currency solve the issue.
Sometimes it takes more time to find a good solution for difficult issue. I have faith in Joe.
He can do magic things. Mark my words!

[gunka]

Minerclaim:
My setting is 0, so that there is no automatic output of coins.
Today they were sent to my wallet in Bitrix, as it happened.

https://chainz.cryptoid.info/xmg/address.dws?946c3d4z8hVwJtcm8FgWg79FDvD49cr9Cb.htm

The wallet on the stock exchange is off and I worry that I lost my coins.
There was no confirmation on the mail about the transfer, although the settings are also indicated.

I do not understand why this happens.
The pool is silent like a moshomini.
Yes the amount is small. But who asked you to translate independently, when the wallet on the stock exchange is closed and I did not plan to do it until it was opened.
You violate your own rules.

[Myth888]

List of issues:

http://m-core.org/issues.txt

Let me know what's missing.

Another issue:
I keep getting banned from the main node, and have no clue why:

Code:

trying connection 104.128.225.215 lastseen=0.0hrs
connected 104.128.225.215
send version message: version 71061, blocks=1451225, us=0.0.0.0:0, them=104.128.225.215:8233, peer=104.128.225.215:8233
socket closed
disconnecting node 104.128.225.215

Same when I start from scratch with 0 blocks. Two IPs banned in two days, always around midnight - 1am but that might be a coincidence.

Guess it might be related to https://bitcointalk.org/index.php?topic=735170.msg21232956#msg21232956, but editing banscore should not matter with whitelist=104.128.225.215 if I understand it correctly.

I don't think that is a ban, disconnect can happen for multiple reasons like network issues.

I get that, but I'm getting this very same message for 48 hours now, while it's running without issues on an other IP.
If I proxy the connection through another IP, it connects without issues, so it must be an IP ban.
And I got two nodes banned already, can't explain why though.

try adding
 banscore=500
dont ask why i dont know why but some users recommended it

banscore increases the score (or misbehave as shown in logs), default is 100. With banscore of 500 you are allowing connected peers to submit "bad" blocks to you up to 5 times per ip before your peer bans the other peer.
The reason I'm using it now is as workaround for when a proper block is sent but something went wrong, that would case an misbehave score of 100 straight away and causing your peer to ban the other peer for 24 hrs (default setting, if you want to change it. Setting is bantime).
Not allowing the re-submit right now gives you an high chance of banning all proper peers and letting you fall behind. This is a workaround for a problem Joe has listed as an issue.

Hope this gives a bit of clarity on how banscore works and why i'm using it as an workaround for now.

I'm running poolinfo with these settings

Code:

banscore=500
bantime=7200

Which means poolinfo is allowing 5 major missbehaves (1 major is 100 in score) and when they hit a score of 500, poolinfo will ban that ip for 2 hrs (7200 seconds) before allowing that peer to reconnect.

thanks for the explanation.

[cryptosamuri]

Sorry I haven't seen this posted in the last little while and Before i do any thing to add pressure to the network, I thought I would ask. Is it OK to start staking again. and if so can some give me a run down of how or a page reference to goto. Thank you for all the work you have been doing Joe on getting the coin back up and running. If there is anything this newbie can do to help let me know. I just got given some extra time by my work I wasn't expecting so if you need someone to help just shoot me and pm. again thank you for all that you are doing and for what your coin stands for.

[gmit]

Sometimes it takes more time to find a good solution for difficult issue. I have faith in Joe.
He can do magic things. Mark my words!

money and emotions? bad combination

[zdrovie]

Wallet can not be synced. Is there a problem?

I am new user and can not update my wallet.

[8count]

Since the last wallet update it all seems to be running sweet for me solo mining. Thanks Joe great work as usual.

[jcreyesb]

Since the last wallet update it all seems to be running sweet for me solo mining. Thanks Joe great work as usual.

What´is your hash? i am mining solo, and only 3 block i discovered

[chronosphere]

Hello again forum,

I wanted to ask, does anyone have any way for me to get my BTC paid for coins that i sent to Bittrex when this all broke down?

They are in my wallet and real coins but they are stuck in unconfirmed state.  I had over 155 XMG sent.  I have the transaction code but it does not appear on the "official" blockchain.  How do I restore the function and submit the coins to be confirmed?  They never actually arrived at Bittrex.  They funds bounced and returned to my wallet but because it happened during a weird time, they are stuck in limbo.   I understand that the ones I mined just before things started to get repaired recently on a NOMP chain lost around 50 but since then earned around the same on the right chain, i see why they would have been stuck in unconfirmed limbo in my wallet.

I have a full track record of all the transactions involved in creating this balance via BTC trade on Bittrex then sending transfer and even the unconfirmed transaction of it being sent. 

How do I fix this   It is the only remaining error on the wallet I am having issues with now that it is synced to the dev node.  I have tried repair wallet etc it is fully repaired.

[kamarul.jutawan]

http://pom.m-hash.com   also not paid my coins after it went down for few days

[Prabhuvinod]

I am also using http://pom.m-hash.com  . It went down for few days and then my entire data(workers, balance, transactions etc) is swept clean on the website. Good thing my auto payment limit is very small, i lost only few dozens on Magi. But still it hurts.