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

[wmikrut]

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

[Myth888]

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

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

[wmikrut]

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

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

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

[joelao95]

@joe
pls add a api to your main node  at  104.128.225.215  to get the bestBlockHash than i can code a forkMonitor,

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

Thanks for setting up the explorer.

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

https://bitcointalk.org/index.php?topic=735170.msg21177317#msg21177317

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.

[wmikrut]

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

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

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

[joelao95]

Another good idea:
...

I'd agree to a certain extent.

[joelao95]

List of issues:

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

Let me know what's missing.

[ex33s]

@ex33s   i think you are again on a fork

Yup, you'r right. Fixing it now.

wow  10 mins a you are up again
nice work

Fully synced and on correct chain.

Thanks

can you fix my ban?

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

[Boocha466]

List of issues:

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

Let me know what's missing.

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?

[The Frisian]

can you fix my ban?

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

So this means I can never use my wallet again?

[ex33s]

can you fix my ban?

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

So this means I can never use my wallet 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

[The Frisian]

can you fix my ban?

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

So this means I can never use my wallet 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

You are right, he's connecting again.

[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.

magi.conf:

Code:

rpcuser=magirpc
rpcpassword=8kDXwzM2HP3Xcwg9f6gUyD8FHi9d64GKhN3iSxo4xaP7

server=1
rpcport=8232
rpcbind=0.0.0.0
rpcallowip=********* # IP of my banned daemon

listen=1 # but only one single IP is allowed to access the port via firewall, it's the daemon on the first IP that was banned and the daemon for my pool
connect=104.128.225.215
whitelist=104.128.225.215 # added after first ban

staking=0
posii=0

stakesplitthreshold=1000
stakecombinethreshold=500

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.

[oxothuk]

... 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.

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.

[The Frisian]

Another issue:
I keep getting banned from the main node, and have no clue why:
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.

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)

[My9bot]

@joe
pls add a api to your main node  at  104.128.225.215  to get the bestBlockHash than i can code a forkMonitor,

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

nice
thx

[pmsk]

... 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.

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.

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.

[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.

[kadok29]

Another issue:
I keep getting banned from the main node, and have no clue why:
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.

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)

i'm reciving a lot of unconfirmed...no acepted stakes... similar to your image, but i'don't know why?

[The Frisian]

i'm reciving a lot of unconfirmed...no acepted stakes... similar to your image, but i'don't know why?

If you don't receive good stakes anymore, you're forked.