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

[lhedwin]

For one interested to solo mining:

Setup magi.conf to include:

Code:

daemon=1
server=1
rpcport=8232
rpcallowip=127.0.0.1
rpcuser=randome_username
rpcpassword=randome_rpcpassword

Run:

Code:

minerd --url=http://127.0.0.1:8232 -u randome_username -p randome_rpcpassword -t thread_numbers -e cpu_efficiency

Does not produce block changes! Maybe you need to add a line?

Code:

minerd --url=http://127.0.0.1:8232 -u randome_username -p randome_rpcpassword -t thread_numbers -e cpu_efficiency --coinbase-addr=Purse

Unless you have a different version, address is not necessary as coins mined will go into your wallet (the wallet should be running when you run solo mining).

trying solo but ain't working

[2017-08-20 10:53:13] 2 miner threads started, using 'm7mhash' algorithm.
[2017-08-20 10:53:13] HTTP request failed: The requested URL returned error: 401
[2017-08-20 10:53:13] json_rpc_call failed, retry after 30 seconds

used the above code (without the --coinbase-addr...) and added the below to the original magi.conf that was created during installing the wallet:

Code:

daemon=1
server=1
rpcport=8232
rpcallowip=127.0.0.1
rpcuser=randome_username
rpcpassword=randome_rpcpassword

assistance guys?

Did you open the 8232 port in your firewall? check it in your browser:

http://localhost:8232

has to ask you for user and passwaord, if not, you have to open the 8232 port in your firewall.

sorry about my english.

[minerclaim.net]

Happy to announce some changes on https://poolinfo.systms.org/

• Zpool information has been added to https://poolinfo.systms.org/#pools
• Added information about each pools network block which shows you which block their wallet is at.
• Added information about last block found they found

Thanks a lot. Network Block Information is very helpful for us!

[Apprentice]

[/quote]

Did you open the 8232 port in your firewall? check it in your browser:

http://localhost:8232

has to ask you for user and passwaord, if not, you have to open the 8232 port in your firewall.

sorry about my english.


[/quote]

tried with the browser, it is asking for a username and pass. but don't which user name and pass to enter! 

[tommyrsk]

Happy to announce some changes on https://poolinfo.systms.org/

• Zpool information has been added to https://poolinfo.systms.org/#pools
• Added information about each pools network block which shows you which block their wallet is at.
• Added information about last block found they found

Thank you. Thats great and important informations during this time beeing.
Well done work with the poolinfo 

[Apprentice]

so for Zpool, you mine in XMG and you get paid in bitcoins?

[AngryWhiteWolf]

so for Zpool, you mine in XMG and you get paid in bitcoins?

No, you are paid in XMG. Go to wallet page, enter your wallet address and you'll see your balances (immatured and confirmed).

[tommyrsk]

TrasMaMod XMG pool is now online and is only in connected/sync with 104.128.225.215 as mentioned from dev.

This is done with removing all connect and addnode in magi.conf and then insert only:

Code:

connect=104.128.225.215

It is important that you also removes peers.dat when you do this.

TrasMaMod XMG pool practice maximum 300KH/s per user to support the network and make the coin equal for all.

[cryptouser]

Happy to announce some changes on https://poolinfo.systms.org/

• Zpool information has been added to https://poolinfo.systms.org/#pools
• Added information about each pools network block which shows you which block their wallet is at.
• Added information about last block found they found

Awesome !!! Thank you.

[deztroyr1]

Happy to announce some changes on https://poolinfo.systms.org/

• Zpool information has been added to https://poolinfo.systms.org/#pools
• Added information about each pools network block which shows you which block their wallet is at.
• Added information about last block found they found

Awesome !!! Thank you.

hmm it seems like all the pools are running except m-hash. perhaps i should move to another one -.-

new wallet version is working properly so i'm happy with that.
Maybe update first post with the new wallet links. it still says 1.3.1 in OP

[111magic]

Happy to announce some changes on https://poolinfo.systms.org/

• Zpool information has been added to https://poolinfo.systms.org/#pools
• Added information about each pools network block which shows you which block their wallet is at.
• Added information about last block found they found

Awesome !!! Thank you.

hmm it seems like all the pools are running except m-hash. perhaps i should move to another one -.-

new wallet version is working properly so i'm happy with that.
Maybe update first post with the new wallet links. it still says 1.3.1 in OP

Good one. Thanks Joe will update it asap.

[akuci]

Suprnova still down.

[111magic]

Suprnova still down.

Yes spoke with ocminer yesterday very late. Will restart today.

[K1lo]

So I woke up to this:



I had hoped for maybe one or two blocks given the pools going up and down.. but clearly I'm on a fork.. again. 

[Vitalik_Pedik]

Again!? Bloody hell

And will again and again, untill my suggestions will accept, point by point.

[111magic]

Check the post from Joe and follow that info

[Vitalik_Pedik]

Check the post from Joe and follow that info

Your advice to me?

[111magic]

Check the post from Joe and follow that info

Your advice to me?

Looks like its not easy to find the right chain. Joe posted some info about it last night.
Best advice is take some time to read those first.

[111magic]

I understand this is frustrating while this is the situation we have at this moment, and becomes quite most recently. My looking back the chain turns out a lot of PoW blocks mined right after the fork point pointing to one /few miners own considerable hash to push the chain faster than the rest, and I go the direction that the big miners somehow reported by people might be the cause. I'd see this a dilemma we're facing when we try to maintain the whole network hash up to a limit but few parties can bring in huge hash from whichever channels they can acquire. This is the plan we are thinking of to take on at this moment:

1) Please connect to the chain that 104.128.225.215 and poolinfo.systms.org are on. Shortly, I'll get an updated block data / wallet for downloads.

Edit: You can use the block date from here to catch up http://coinmagi.org/bin/block-chain/

Place connect=104.128.225.215 in magi.conf, or

magid -connect=104.128.225.215

2) We will make changes to the PoW ASAP. I must admit and make such a note upfront here that there is no guarantee that we'll be 100% isolated from hard fork, and there is always a probability unless we grow up to a scale that no one can compete the rest in both PoS and PoW. I recognize a weak point that we keep the network hash to a lower limit to favor low-hash miner, and that is where we're suffering from, while I would remain to stay on this.

Please make suggestions.

Be sure you adjust the magi.conf

[Vitalik_Pedik]

The only way to avoid splitting in future is to accept and execute my suggestions:
1. Hardcode main pools in client (need list) to be guarantors of the chain, not forever. For example, we have 10 pools in list, if 7 of 10 accepted block, that block true.
2. Try to find out vector of attack (pow or pos) and develop a protection system.
3. Test protection system several times with emulation of attack
4. Remove hardcoded pools.

Without this steps, we will have new splits again and again.

[111magic]

The only way to avoid splitting in future is to accept and execute my suggestions:
1. Hardcode main pools in client (need list) to be guarantors of the chain, not forever. For example, we have 10 pools in list, if 7 of 10 accepted block, that block true.
2. Try to find out vector of attack (pow or pos) and develop a protection system.
3. Test protection system several times with emulation of attack
4. Remove hardcoded pools.

Without this steps, we will have new splits again and again.

Thanks iam sure Joe will look into this.
This is what i like. Working together on solutions