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 
Topic: [ANN] [XMG] MAGI | CPU mining | mPoW | mPoS | [MagiPay] - page 393. (Read 2375631 times)
Since the last wallet update it all seems to be running sweet for me solo mining. Thanks Joe great work as usual.
Wallet can not be synced. Is there a problem?
I am new user and can not update my wallet.
I am new user and can not update my wallet.
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!
He can do magic things. Mark my words!
money and emotions? bad combination
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.
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://bitcointalksearch.org/topic/m.21232956, 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.
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.
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. =)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!
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. =) 
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?
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.
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?
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.
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.
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?
What gives? Is Magi just fucked now? Are any exchanges even accepting deposits?
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://bitcointalksearch.org/topic/m.21232956, 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.
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://bitcointalksearch.org/topic/m.21232956, 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.
all known pool hashrate is around 30Mhs, the network is 90Mhs 
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://bitcointalksearch.org/topic/m.21232956, 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
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
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://bitcointalksearch.org/topic/m.21232956, 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.
...
there is a delay on how the rewards adjust based on hashrates. Thats how the botnets and rentals play magi. They only mine when the reward is high and only stay until the rewards have come down.
Ok. That makes sense. So if I understand correctly, the difficulty of a block isn't determined 'on the spot' based on the current net hashrate? What is the reason for this? Because it's practically not possible?
It sounds to me that it's now based on an average hashrate of the x past hours/days. Is this correct?
Can I compare this with the BTC idea where they recalculate the difficulty every 2016 blocks? More miners, block difficulty increases, in MAGI something similar happens but on a faster scale?
Edit using the comment of Flapmin:
...
err... difficulty is calculated right away as i can observe but rewards adjust a little slower than difficulty. maybe it averages a few blocks to make it more stable and not so erratic. there is a graph somewhere but i didnt bother to study it too much. bitcoin adjusts its difficulty per 2000+ blocks btw. just a point of comparison.
looks to be an attempt at better distobution also please note the 8 hr maturity on coins change
witch i fully agree with i had already changed to 8 hrs on flaps
Difficulty recalculation is now based on the blocks from the last 8 hours? Or did I interpret that wrong?
I need some help on the following matter:
Block: 1454526
https://chainz.cryptoid.info/xmg/block.dws?0000000053997f467c61ca283e41fff8e4488fac15ed8404f286109fbd58d26f.htm
Reward: 1.29372498 XMG
Difficulty: 1.77659401
Block: 1454477
https://chainz.cryptoid.info/xmg/block.dws?0000000072474a8741189f665a7db58c7c0eb0bb6cb5fccbf81292249e834ddd.htm
Reward: 3.64482276 XMG
Difficulty: 1.76140945
In MAGI, the difficulty is calculated based on the net hash rate. So it seems that the net hash rate in both cases must've been more or less similar as the difficulties are almost the same.
Why is the reward in block 1454477 almost 3x as high as in block 1454526?
Block: 1454526
https://chainz.cryptoid.info/xmg/block.dws?0000000053997f467c61ca283e41fff8e4488fac15ed8404f286109fbd58d26f.htm
Reward: 1.29372498 XMG
Difficulty: 1.77659401
Block: 1454477
https://chainz.cryptoid.info/xmg/block.dws?0000000072474a8741189f665a7db58c7c0eb0bb6cb5fccbf81292249e834ddd.htm
Reward: 3.64482276 XMG
Difficulty: 1.76140945
In MAGI, the difficulty is calculated based on the net hash rate. So it seems that the net hash rate in both cases must've been more or less similar as the difficulties are almost the same.
Why is the reward in block 1454477 almost 3x as high as in block 1454526?
looks to be an attempt at better distobution also please note the 8 hr maturity on coins change
witch i fully agree with i had already changed to 8 hrs on flaps
alot of magi flaps?indeed lots to go over before swap and launch
flappycoin is being mined up pretty well . lots of changes
this coin has been threw we are still trying to decide witch mpow/mpos
best suites our project
Jump to: