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

[Apprentice]

Is any other coin good for cpu mining now? Any suggestion?

You can mine Monero with cpu, need a good one though.
Am using 4 xeons each hashing at around 200Khs

[jbmustaq]

first of all it should be 200H/s not kh/s there is no server available in the market which can do that much hashing.  The best is E7 server which goes to 2Kh/s. If you have 200H/s each server then it's waste of time and money as 1 coin will be generated in around months time.

[Apprentice]

first of all it should be 200H/s not kh/s there is no server available in the market which can do that much hashing.  The best is E7 server which goes to 2Kh/s. If you have 200H/s each server then it's waste of time and money as 1 coin will be generated in around months time.

that's true, 200Hs. I have other rigs too, but XMR still can be mined by CPU. Plus I have them from free and do not pay for electricity.
XMR is at $47

[jbmustaq]

I also have 4 servers giving out 200+ H/s. I am going for fx8300 as it's hashrate is around 400H/s

[Apprentice]

first of all it should be 200H/s not kh/s there is no server available in the market which can do that much hashing.  The best is E7 server which goes to 2Kh/s. If you have 200H/s each server then it's waste of time and money as 1 coin will be generated in around months time.

BTW, did a test drive for 10min the other day on 3 x E7 at 23 threads each and got around 18xxHs on each. Added 4 intel Phi and 16 x P100... wow  
Wish can use this hardware for mining...  

[jbmustaq]

wow that some hashing power.

[jyj]

Start branching again? I used my purse to dig to 43.245 XMG

[DobroFenix]

pool is down?
https://pp.userapi.com/c840221/v840221913/27602/7z9DCvAKIT4.jpg

[defyance]

any news from the devs? safe to load up 1.4 wallet yet?

[111magic]

Yes Dobrofenix. We are waiting for the launch of new developments/improvements. Keep eyes on this thread.

[111magic]

any news from the devs? safe to load up 1.4 wallet yet?

No defyance. Looks like that wallet had some issues.
Version 1.4.01 is in development!

[DobroFenix]

Yes Dobrofenix. We are waiting for the launch of new developments/improvements. Keep eyes on this thread.

Approximately how long to expect?
Since I'm thinking of going to another pool

[111magic]

Yes Dobrofenix. We are waiting for the launch of new developments/improvements. Keep eyes on this thread.

Approximately how long to expect?
Since I'm thinking of going to another pool

I don't dare to give you an answer. Personal i think it will not take long. But we need to test all things first.
We learned in time!

[mozsi]

Any idea what caused the fork?

I wrote to Bittrex to stop their wallet, no answers yet, but their wallet says: 'The last block update occurred 997 minutes ago.'

[111magic]

Any idea what caused the fork?

I wrote to Bittrex to stop their wallet, no answers yet, but their wallet says: 'The last block update occurred 997 minutes ago.'

Already sent them message on twitter & by support.
Asked ig wallet could get comment wallet wallet maintenance until new wallets are tested and ready for launch.

[starmman]

Any idea what caused the fork?

I wrote to Bittrex to stop their wallet, no answers yet, but their wallet says: 'The last block update occurred 997 minutes ago.'

Already sent them message on twitter & by support.
Asked ig wallet could get comment wallet wallet maintenance until new wallets are tested and ready for launch.

Spotted the trex wallet was online - I guess there will be problems moving coins to it. I'm keeping my coins where they are for as long as I can - would be great to hear what caused the second fork.

[Apprentice]

can you please attach the magi.conf file or paste its contents so I can have to proper file.
thanks.

[starmman]

A quick recap to help others: -

To check your wallet is on the correct chain
You can type getblockcount under console to check to see if you are up to the correct block and compare against https://poolinfo.systms.org/#magi

To resync the blockchain
- Backup your wallet.dat
- Exit from m-wallet.exe
- Add oVPN's list to %Appdata%\magi\magi.conf (create the file if it doesn't exist)
- Delete your blocks, database, .lock and peers.dat files
- Download the blockchain and extract to your magi folder from http://coinmagi.org/bin/block-chain/
- Run m-wallet.exe (version 1.4)

If you are missing coins
Type repairwallet under console (make sure you have a backup of your wallet.dat)

Sample magi.conf

Code:

#client nodes
connect=213.32.21.37
connect=192.99.63.44
connect=89.34.96.133
connect=185.38.149.64
connect=193.124.182.62
connect=172.86.179.30
connect=95.211.186.214
connect=37.48.118.8
connect=37.48.118.9
connect=37.48.80.94
connect=5.79.74.141
connect=5.79.74.142
connect=5.79.74.140
connect=37.48.80.201
connect=95.211.209.73
connect=193.105.134.118
connect=193.105.134.120

# posii=0 to disable PoS staking; default = 1
posii=1

# Transaction under stake with a value greater than the threshold is being splitted
stakesplitthreshold=1000

# Transactions with values less than the threshold will combine into one
stakecombinethreshold=500

[GKar]

Yesterday my wallet was synced n working.
As of ~8am Central Time 08/12/2017 my wallet started to disconnect/connect. Been using the 2 nodes Paul posted via connect.

It appears I have yet again split/forked. 

@joe ..... any suggestions??

Try to restart first!

I have and also purged blockchain and loaded the d/l one from Joe.

Wallet will not maintain a connection. Constantly connects n disconnects,

[oVPN]

this network is stuckm,  213.32.21.37 poolinfo.systms.org

send version message: version 71051, blocks=0, us=95.211.209.73:8233, them=213.32.21.37:59018, peer=213.32.21.37:59018
receive version message: version 71061, blocks=1444963, us=95.211.209.73:8233, them=213.32.21.37:8233, peer=213.32.21.37:59018
Added 1 addresses from 213.32.21.37: 8 tried, 109 new
Misbehaving: 213.32.21.37:59018 (0 -> 100) DISCONNECTING
disconnecting node 213.32.21.37:59018
connection from 213.32.21.37:59184 dropped (banned)
connection from 213.32.21.37:59304 dropped (banned)
connection from 213.32.21.37:59384 dropped (banned)
connection from 213.32.21.37:59474 dropped (banned)
connection from 213.32.21.37:59590 dropped (banned)
connection from 213.32.21.37:59690 dropped (banned)
connection from 213.32.21.37:59782 dropped (banned)