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

[jonathin.r]

I just now reallized something quite interesting...



Did I somehow spend money that I didn't have? How is my wallet showing that I have more money than I actually have?

[1715179896]

1715179896

[1715179896]

1715179896

[djm34]

I know it is uber fantastic idea, but what if you make the coin mineable only with... linux. It sounds a bit stupid even for me, but it can solve a problem - remove botnets. There are no linux botnets around. It seems a bit fantastic, but can make coin profitable.

I am fully agree with you. Only with "it sounds a bit stupid")

[jonathin.r]

I know it is uber fantastic idea, but what if you make the coin mineable only with... linux. It sounds a bit stupid even for me, but it can solve a problem - remove botnets. There are no linux botnets around. It seems a bit fantastic, but can make coin profitable.

I am fully agree with you. Only with "it sounds a bit stupid")

Linux only? That's what 95% of my miners run, but only accounts for only 35-ish% of my mining power. The Core i5-7200U in my Windows laptop, when it's rarely running, is more powerful than all my devices. Plus, I'm fairly sure that Vitalik's botnet is mostly comprised of VPSes running a variant of a Linux distro like Ubuntu, Redhat or Arch.

Not to mention that completely alienates the Windows XMG community.

[The Doktor]

I know it is uber fantastic idea, but what if you make the coin mineable only with... linux. It sounds a bit stupid even for me, but it can solve a problem - remove botnets. There are no linux botnets around. It seems a bit fantastic, but can make coin profitable.

I am fully agree with you. Only with "it sounds a bit stupid")

Linux only? That's what 95% of my miners run, but only accounts for only 35-ish% of my mining power. The Core i5-7200U in my Windows laptop, when it's rarely running, is more powerful than all my devices. Plus, I'm fairly sure that Vitalik's botnet is mostly comprised of VPSes running a variant of a Linux distro like Ubuntu, Redhat or Arch.

Not to mention that completely alienates the Windows XMG community.

More to the point, how would you make it only mineable in Linux? Can't do it.

[Jeremy450]

I just now reallized something quite interesting...

https://image.ibb.co/hSLP9S/Capture.png https://image.ibb.co/iVi0in/Capture.png https://preview.ibb.co/kFdNw7/Capture.png

Did I somehow spend money that I didn't have? How is my wallet showing that I have more money than I actually have?

a glitch?

[Jeremy450]

Now xmg.minerclaim.net:3333 is down

[jonathin.r]

Now xmg.minerclaim.net:3333 is down

I can confirm, though from looking through the logs leading up to my miners saying they couldn't connect, I saw that one of them had got 45/254 shares accepted. They most likely closed mining on 3333 until they resolve whatever backend issues they're experiencing.

[Jeremy450]

Now xmg.minerclaim.net:3333 is down

I can confirm, though from looking through the logs leading up to my miners saying they couldn't connect, I saw that one of them had got 45/254 shares accepted. They most likely closed mining on 3333 until they resolve whatever backend issues they're experiencing.

*sigh* now have to change all the miners again to port 7008

[Jeremy450]

Hmmmmm i think there is more wrong with minerclaim then meets the eye.

[joelao95]

I'll try to make out a test tonight as much as possible; since got a daily work to do, would depend how the thing proceeds.

I'm gonna post tomorrow.

[Jeremy450]

Either there's a problem with minerclaim or there is a major network issue.

Alot of boos and hashrates are very low.

WOW i just found out that supernova is already shutdown. like bullmining is going to do.

others is follow??

[The Doktor]

Either there's a problem with minerclaim or there is a major network issue.

Alot of boos and hashrates are very low.

WOW i just found out that supernova is already shutdown. like bullmining is going to do.

others is follow??

Something is very different this time. I'm showing the increased block reward, but not getting any orphans, and no blocks either. This is solo mining, like usual.

BTW, on the attack before this 1, my wallet was showing several times the orphans it usually gets during an attack. Either the attack is changing, or pools all going down is causing very low "legitimate" hashing power. I hope this doesn't kill the network.

[Jeremy450]

Either there's a problem with minerclaim or there is a major network issue.

Alot of boos and hashrates are very low.

WOW i just found out that supernova is already shutdown. like bullmining is going to do.

others is follow??

Something is very different this time. I'm showing the increased block reward, but not getting any orphans, and no blocks either. This is solo mining, like usual.

BTW, on the attack before this 1, my wallet was showing several times the orphans it usually gets during an attack. Either the attack is changing, or pools all going down is causing very low "legitimate" hashing power. I hope this doesn't kill the network.

i'm getting nothing right now with minerclaim its my hash is going between 40 - 600khs getting so many boos its crazy

[Jeremy450]

How do i setup solo mining using the windows wallet?

[Vitalik_Pedik]

Either there's a problem with minerclaim or there is a major network issue.

Alot of boos and hashrates are very low.

WOW i just found out that supernova is already shutdown. like bullmining is going to do.

others is follow??

Something is very different this time. I'm showing the increased block reward, but not getting any orphans, and no blocks either. This is solo mining, like usual.

BTW, on the attack before this 1, my wallet was showing several times the orphans it usually gets during an attack. Either the attack is changing, or pools all going down is causing very low "legitimate" hashing power. I hope this doesn't kill the network.

My main server down when I try to start regular attack)

https://media.giphy.com/media/l2JdWdiFeSv9DsBdm/giphy.gif

[jonathin.r]

Well, this is exciting!...
...And by exciting, I mean extremely frustrating.

It appears as if instead of orphaning blocks, this new hacker is now invalidating shares. Why go through the trouble of killing the blockchain when you could just weaken the network? I say "new hacker" because it wouldn't make sense for Vitalik to change tactics when he's already stealing thousands of XMG a week.

[Jeremy450]

looks like i got it to work. i got the machines to connect to my computer that has the wallet and they are show khs

how can i tell if its working?

[The Doktor]

How do i setup solo mining using the windows wallet?

Set up magi.conf as follows:

# You must set rpcuser and rpcpassword to secure the JSON-RPC api
rpcuser=*user*
rpcpassword=*pass*

# Listen for RPC connections on this TCP port:
rpcport=8232

# server=1 to accept JSON-RPC commands
server=1

# listen=1 to accept connections from outside
listen=0

# RPC connection from localhost allowed
# set this to your LAN address range to allow other local machines to connect. * means 0-255 IOW any machine on LAN
rpcallowip=192.168.0.*

# Add nodes to connect to specific peers
#connect=104.128.225.215

# Add nodes to connect to specific peers
addnode=104.128.225.215
addnode=45.35.251.73

# posii=1 to enable PoS staking; default = 0
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


Launch your miner with:

C:\XMGpoolminerWin64\m-minerd.exe -a m7mhash -o http://192.168.0.141:8232 -u *user* -p *pass* --threads 12

this breaks down as follows:
"C:\XMGpoolminerWin64\m-minerd.exe"  *** adjust to path of miner
                                            
-a m7mhash *** for magi mining

-o http://192.168.0.141:8232 *** address and port of wallet server

*user* *** user from magi.conf  don't use any *

*pass* *** pass from magi.conf

--threads 12 *** number of threads you want, no more than 1 per core

Don't forget to open your firewall for incoming connections to your wallet.

No yay or boo when mining solo, what you'll see if all is well is this:

C:\XMGpoolminerWin64>C:\XMGpoolminerWin64\m-minerd.exe -a m7mhash -o http://192.168.0.141:8232 -u ***** -p ***** --threads 12
[2018-05-05 02:06:23] Binding thread 0 to cpu 0
[2018-05-05 02:06:23] Binding thread 1 to cpu 1
[2018-05-05 02:06:23] Binding thread 2 to cpu 2
[2018-05-05 02:06:23] Binding thread 3 to cpu 3
[2018-05-05 02:06:23] Binding thread 4 to cpu 4
[2018-05-05 02:06:23] Binding thread 5 to cpu 5
[2018-05-05 02:06:23] Binding thread 6 to cpu 6
[2018-05-05 02:06:23] Binding thread 7 to cpu 7
[2018-05-05 02:06:23] Binding thread 8 to cpu 8
[2018-05-05 02:06:23] Binding thread 9 to cpu 9
[2018-05-05 02:06:23] Binding thread 10 to cpu 10
[2018-05-05 02:06:23] 12 miner threads started, using 'm7mhash' algorithm.
[2018-05-05 02:06:23] Binding thread 11 to cpu 11
[2018-05-05 02:06:23] No payout address provided, switching to getwork
[2018-05-05 02:06:52] thread 6: 262144 hashes, 9.29 khash/s
[2018-05-05 02:06:52] thread 9: 262144 hashes, 9.26 khash/s
[2018-05-05 02:06:52] thread 11: 262144 hashes, 9.25 khash/s
[2018-05-05 02:06:52] thread 8: 262144 hashes, 9.20 khash/s
[2018-05-05 02:06:52] thread 0: 262144 hashes, 9.20 khash/s
[2018-05-05 02:06:52] thread 4: 262144 hashes, 9.16 khash/s
[2018-05-05 02:06:52] thread 1: 262144 hashes, 9.10 khash/s
[2018-05-05 02:06:52] thread 7: 262144 hashes, 9.10 khash/s
[2018-05-05 02:06:52] thread 3: 262144 hashes, 9.07 khash/s
[2018-05-05 02:06:53] thread 2: 262144 hashes, 8.97 khash/s
[2018-05-05 02:06:53] thread 10: 262144 hashes, 8.82 khash/s
[2018-05-05 02:06:53] thread 5: 262144 hashes, 8.72 khash/s
[2018-05-05 02:06:56] thread 2: 35872 hashes, 9.22 khash/s
[2018-05-05 02:06:57] thread 9: 46314 hashes, 9.35 khash/s
[2018-05-05 02:06:57] thread 6: 46457 hashes, 9.18 khash/s
[2018-05-05 02:06:57] thread 0: 45994 hashes, 9.27 khash/s
[2018-05-05 02:06:57] thread 11: 46261 hashes, 8.99 khash/s
[2018-05-05 02:06:57] thread 8: 45994 hashes, 9.23 khash/s
[2018-05-05 02:06:57] thread 4: 45778 hashes, 9.26 khash/s
[2018-05-05 02:06:57] thread 1: 45507 hashes, 9.21 khash/s
[2018-05-05 02:06:57] thread 7: 45497 hashes, 9.26 khash/s
[2018-05-05 02:06:57] thread 10: 35265 hashes, 8.72 khash/s
[2018-05-05 02:06:57] thread 3: 45349 hashes, 9.29 khash/s
[2018-05-05 02:06:57] thread 5: 34876 hashes, 9.29 khash/s

If you get message about connect error, make sure wallet is running, check wallet address & port, user & pass, etc.
Also, try running a miner on same machine as wallet by using 127.0.0.1:port , this shoulg get around firewall problems.
Wallet must be in sync for mining to work.

[Jeremy450]

How do i setup solo mining using the windows wallet?

Set up magi.conf as follows:

# You must set rpcuser and rpcpassword to secure the JSON-RPC api
rpcuser=*user*
rpcpassword=*pass*

# Listen for RPC connections on this TCP port:
rpcport=8232

# server=1 to accept JSON-RPC commands
server=1

# listen=1 to accept connections from outside
listen=0

# RPC connection from localhost allowed
# set this to your LAN address range to allow other local machines to connect. * means 0-255 IOW any machine on LAN
rpcallowip=192.168.0.*

# Add nodes to connect to specific peers
#connect=104.128.225.215

# Add nodes to connect to specific peers
addnode=104.128.225.215
addnode=45.35.251.73

# posii=1 to enable PoS staking; default = 0
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


Launch your miner with:

C:\XMGpoolminerWin64\m-minerd.exe -a m7mhash -o http://192.168.0.141:8232 -u *user* -p *pass* --threads 12

this breaks down as follows:
"C:\XMGpoolminerWin64\m-minerd.exe"  *** adjust to path of miner
                                            
-a m7mhash *** for magi mining

-o http://192.168.0.141:8232 *** address and port of wallet server

*user* *** user from magi.conf  don't use any *

*pass* *** pass from magi.conf

--threads 12 *** number of threads you want, no more than 1 per core

Don't forget to open your firewall for incoming connections to your wallet.

No yay or boo when mining solo, what you'll see if all is well is this:

C:\XMGpoolminerWin64>C:\XMGpoolminerWin64\m-minerd.exe -a m7mhash -o http://192.168.0.141:8232 -u ***** -p ***** --threads 12
[2018-05-05 02:06:23] Binding thread 0 to cpu 0
[2018-05-05 02:06:23] Binding thread 1 to cpu 1
[2018-05-05 02:06:23] Binding thread 2 to cpu 2
[2018-05-05 02:06:23] Binding thread 3 to cpu 3
[2018-05-05 02:06:23] Binding thread 4 to cpu 4
[2018-05-05 02:06:23] Binding thread 5 to cpu 5
[2018-05-05 02:06:23] Binding thread 6 to cpu 6
[2018-05-05 02:06:23] Binding thread 7 to cpu 7
[2018-05-05 02:06:23] Binding thread 8 to cpu 8
[2018-05-05 02:06:23] Binding thread 9 to cpu 9
[2018-05-05 02:06:23] Binding thread 10 to cpu 10
[2018-05-05 02:06:23] 12 miner threads started, using 'm7mhash' algorithm.
[2018-05-05 02:06:23] Binding thread 11 to cpu 11
[2018-05-05 02:06:23] No payout address provided, switching to getwork
[2018-05-05 02:06:52] thread 6: 262144 hashes, 9.29 khash/s
[2018-05-05 02:06:52] thread 9: 262144 hashes, 9.26 khash/s
[2018-05-05 02:06:52] thread 11: 262144 hashes, 9.25 khash/s
[2018-05-05 02:06:52] thread 8: 262144 hashes, 9.20 khash/s
[2018-05-05 02:06:52] thread 0: 262144 hashes, 9.20 khash/s
[2018-05-05 02:06:52] thread 4: 262144 hashes, 9.16 khash/s
[2018-05-05 02:06:52] thread 1: 262144 hashes, 9.10 khash/s
[2018-05-05 02:06:52] thread 7: 262144 hashes, 9.10 khash/s
[2018-05-05 02:06:52] thread 3: 262144 hashes, 9.07 khash/s
[2018-05-05 02:06:53] thread 2: 262144 hashes, 8.97 khash/s
[2018-05-05 02:06:53] thread 10: 262144 hashes, 8.82 khash/s
[2018-05-05 02:06:53] thread 5: 262144 hashes, 8.72 khash/s
[2018-05-05 02:06:56] thread 2: 35872 hashes, 9.22 khash/s
[2018-05-05 02:06:57] thread 9: 46314 hashes, 9.35 khash/s
[2018-05-05 02:06:57] thread 6: 46457 hashes, 9.18 khash/s
[2018-05-05 02:06:57] thread 0: 45994 hashes, 9.27 khash/s
[2018-05-05 02:06:57] thread 11: 46261 hashes, 8.99 khash/s
[2018-05-05 02:06:57] thread 8: 45994 hashes, 9.23 khash/s
[2018-05-05 02:06:57] thread 4: 45778 hashes, 9.26 khash/s
[2018-05-05 02:06:57] thread 1: 45507 hashes, 9.21 khash/s
[2018-05-05 02:06:57] thread 7: 45497 hashes, 9.26 khash/s
[2018-05-05 02:06:57] thread 10: 35265 hashes, 8.72 khash/s
[2018-05-05 02:06:57] thread 3: 45349 hashes, 9.29 khash/s
[2018-05-05 02:06:57] thread 5: 34876 hashes, 9.29 khash/s

If you get message about connect error, make sure wallet is running, check wallet address & port, user & pass, etc.
Also, try running a miner on same machine as wallet by using 127.0.0.1:port , this shoulg get around firewall problems.
Wallet must be in sync for mining to work.

i've set the coinbase in mine

[The Doktor]

looks like i got it to work. i got the machines to connect to my computer that has the wallet and they are show khs

how can i tell if its working?

If it's showing hash instead of connect error, it's working. Look at my example.
Bad part is wallet shows nothing unless you get a block. I've been VNCing into all 9 machines to make sure they're still hashing, but I'm going to build a remotely accessible power meter to save me from that. If 1 machine stops mining, drop in power consumption is quite noticeable.