Topic: [ANN] [XMG] MAGI | CPU mining | mPoW | mPoS | [MagiPay] - page 396. (Read 2375631 times)

They are misunderstand economics. Low hashrate => more coins =>less price. High hashrate => less coins =>more price. Finally, here is no $ difference, high hashrate or low. But they really think price will be the same after high hashrate will be banned. Yes, we can ban, but after down net hashrate from 60MH to 6 MH XMG price will go down from 0.00005 to 0.000005. Nearsighted communism.

nice
thx

My wallet is running again, now for almost 12 hours, and staking, using banscore=500.
I can see it goes wrong once in a while, becauase of unconfirmed stakes. (? rows)

Really there is only one way to fight agains big hashrates and botnets.   It is do coin not interesting.

It possible in two ways,  
1) Make coin not interested,  just do not profitable.. or lower than competitors
2) Remove reward limit and reward everyone with fixed value in block (like other coins does)

Any administrative methods like create trust pools, ban ip`s etc  will not work and do more problem than helps. And it is against cryptocoin paradigm, nobody include developers should not regulate anything.

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


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.

magi.conf:


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.

You are right, he's connecting again.

You can, it's not a permanent ban.

There is a setting for bantime (default is 86400 seconds which is 24 hrs) after that the peer removes the ban on the ip address.

On poolinfo, i've set bantime to 2 hrs instead of the default of 24 hrs

So this means I can never use my wallet again?

Good afternoon!

My question is solo extraction.

I started the purse. Configured magi.conf. Started the miner.

Everything is working!!!

When I log into ip 127.0.0.1 port 8232. login and password.

I'm getting this line here.

{"Result": null, "error": {"code": - 32700, "message": "Parse error"}, "id": null}

Is this normal or is there a problem with me?

It's each peer that bans and it's not the network itself. So can't do anything about it.

List of issues:

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

Let me know what's missing.

I'd agree to a certain extent.

Well, that was easy... will be completely in sync in a few minutes.
Thank you!

Thanks for setting up the explorer.

I updated the OP. The following post (link on OP too) collects most of stuffs.

https://bitcointalksearch.org/topic/m.21177317

BTW, the following NOMP pools:

http://magi.altexplorer.xyz/
http://h2701744.stratoserver.net:85

Thanks to penambang and edward0181

Check out https://poolinfo.systms.org/ for MPOS pools

Solo vs pool mining, pool mining is recommended.

@My9bot once you have things set up, I'll get it into info page. Thanks for help.

Thank you!
I missed that link to the blockchain download. 

download the blockchain before you sync to make it easier and follow joe's guide to connect only to his node,

I am trying to sync but I keep stalling out on block 132605

http://178.17.174.27:8280/m-chain/json.php?d=bestblockhash

this explorer is connected to devs node: http://178.17.174.27:8280/m-chain

I'm not sure if these are all tied together, but as i see it there are a number of major issues facing magi right now.
First and foremost is the issue of securing the blockchain. At this point and after this number of forks and pools on the wrong chain(s) something needs to be done, if that means taking mining offline for a number of days so be it. I've been against a rollback this entire time as well, but at this point if this will fix the issues currently facing the network what must be done must be done.
Secondly, something MUST be done about large miners, botnet mining, block rewards, and pool distribution. Perhaps there is someway to rework the m7m algorithm to FORCE the -e stipulation to be observed based on network hash, as well as local hash.
Third, I feel a lot of blame falls not on the developers of magi, but the community or rather those looking to exploit magi for a quick return, as well as the pools and operators for flat out refusing to enforce the "maximum" hashrates, as well as continuing to let this abuse slide.
We need to fix our blockchain and our coin, then worry about fair mining rewards/botnet/massive hashrates, then worry about how to deal with pools dominating the network hashrate and refusing to act against miners with large hashrates.