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

[catfish78]

Welcome to the magi community catfish78,

To check to see if you are on the correct chain you can check the blockheight on this site
https://poolinfo.systms.org/#magi

Then check the blockheight in your wallet in the console by typing

Code:

getblockcount

they should be the same our at worst less than 10 out if your wallet is fully synchronised

Good luck with the mining

Thank You! Very simple way to check it!

I'm in the right track and got 2 blocks - very happy 

[mscoin]

What means  stratum_recv_line failed?

It probably means you're not connecting to the pool.
Do you have some kind of firewall on your side that could be blocking your connection to the pool?

I turn off all firewall and try on two networks and two different machines.

[tommyrsk]

Can someone clearly confirm that we should only be mining at 300 KH/s per person or per mining rig? I just have some i7 machines that lay around doing nothing so i sent them off mining XMG.

The max speed of 300KH/s per user is a limit that is set by us on our pool TrasMaMod. That means persons who mine over 300KH/s must reduce their mining speed, if not, they are miners we dont want on the pool, and will be banned.

This limit has nothing to do with the general mining in the network.
BUT: we encourages every pool owners to do similar as us.

[Boocha466]

Can someone clearly confirm that we should only be mining at 300 KH/s per person or per mining rig? I just have some i7 machines that lay around doing nothing so i sent them off mining XMG.

The max speed of 300KH/s per user is a limit that is set by us on our pool TrasMaMod. That means persons who mine over 300KH/s must reduce their mining speed, if not, they are miners we dont want on the pool, and will be banned.

This limit has nothing to do with the general mining in the network.
BUT: we encourages every pool owners to do similar as us.

LoL - http://prntscr.com/gd8ahi 678 kh/s

[penambang]

More mempool error on my NOMP pool

Code:

received block 000000001a86d38a2eb1
SetBestChain: new best=000000001a86d38a2eb19f1238358b9db3bb0590a60c650671de722bb179c5a4  height=1452104  money supply=7991958  trust=66013855359244  date=08/25/17 17:05:45
Stake checkpoint: 47c28008
ProcessBlock: ACCEPTED
ERROR: mempool transaction missing input
ERROR: mempool transaction missing input
ERROR: mempool transaction missing input
ERROR: mempool transaction missing input
ERROR: mempool transaction missing input
ERROR: mempool transaction missing input
ERROR: mempool transaction missing input
ERROR: mempool transaction missing input
ERROR: mempool transaction missing input
ERROR: mempool transaction missing input
Flushing wallet.dat
Flushed wallet.dat 1ms
Flushed 0 addresses to peers.dat  1ms
received block 00000000796ec87c78c0
SetBestChain: new best=00000000796ec87c78c01eb782ad5169206578826d3ff9aa045d3baf9da66e3a  height=1452105  money supply=7991963  trust=66013855364592  date=08/25/17 17:06:41
Stake checkpoint: fb0aac60
ProcessBlock: ACCEPTED
ERROR: mempool transaction missing input
ERROR: mempool transaction missing input
ERROR: mempool transaction missing input
ERROR: mempool transaction missing input
ERROR: mempool transaction missing input
ERROR: mempool transaction missing input
ERROR: mempool transaction missing input
ERROR: mempool transaction missing input
ERROR: mempool transaction missing input
ERROR: mempool transaction missing input
Flushing wallet.dat
Flushed wallet.dat 0ms

My magi.conf:

Code:

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

# server=1 to accept JSON-RPC commands
server=1
daemon=1
# listen=1 to accept connections from outside
listen=0

# RPC connection from localhost allowed
rpcallowip=127.0.0.1

connect=104.128.225.215

posii=0

Did you ever get this figured out?  Its happening to my wallet now

My problem solved by importing private key to new wallet, no more mempool error for now.

[tommyrsk]

LoL - http://prntscr.com/gd8ahi 678 kh/s

User has been warned. If there is no improvements in short time. He will be banned.
(we warn first before blocking)

[gunka]

Can someone clearly confirm that we should only be mining at 300 KH/s per person or per mining rig? I just have some i7 machines that lay around doing nothing so i sent them off mining XMG.

The max speed of 300KH/s per user is a limit that is set by us on our pool TrasMaMod. That means persons who mine over 300KH/s must reduce their mining speed, if not, they are miners we dont want on the pool, and will be banned.

This limit has nothing to do with the general mining in the network.
BUT: we encourages every pool owners to do similar as us.

LoL - http://prntscr.com/gd8ahi 678 kh/s

LOL

xmg.minerclaim.net
The Max Hashrate per User is 250KH/s
https://xmg.minerclaim.net/index.php?page=statistics&action=pool
Everyone has more than 250 kh/s  )))))

[starmman]

LoL - http://prntscr.com/gd8ahi 678 kh/s

User has been warned. If there is no improvements in short time. He will be banned.
(we warn first before blocking)

Great that action is being taken - hopefully the chain will keep up... tons of posts on the thread today - its difficult to keep up - dont think I've ever seen so much activity on here. Great that lots more people are starting to take notice of Magi =D

[pmsk]

Can someone clearly confirm that we should only be mining at 300 KH/s per person or per mining rig? I just have some i7 machines that lay around doing nothing so i sent them off mining XMG.

The max speed of 300KH/s per user is a limit that is set by us on our pool TrasMaMod. That means persons who mine over 300KH/s must reduce their mining speed, if not, they are miners we dont want on the pool, and will be banned.

This limit has nothing to do with the general mining in the network.
BUT: we encourages every pool owners to do similar as us.

Do you really think it's a solution? It's not question for you, but question for all. There is no problem to create 10-20-100 accounts, configure mining sw and in the end to get a perfect picture: 100 users with 40kh/s instean one with 4000kh/s.

[tommyrsk]

@TrasMaMod owner

Please fix your pools dashboard. It just stops refreshing after a while.

There is none known issues with the dashboard. I'm using it by my self and has no issue. It could be some browser related.

Code:

Refresh interval: 5 seconds, worker and account 5 seconds. Hashrate based on shares submitted in the past 5 minutes.

[AngryWhiteWolf]

Do you really think it's a solution? It's not question for you, but question for all. There is no problem to create 10-20-100 accounts, configure mining sw and in the end to get a perfect picture: 100 users with 40kh/s instean one with 4000kh/s.

It's a good start. Let them try, could have unpleasant surprises. Especially if the coins mined using hash rate above limit are not paid.

[jmik]

Unless they use a very sophisticated setup, all those accounts would have the same IP though. That's pretty easy to detect.

Do you really think it's a solution? It's not question for you, but question for all. There is no problem to create 10-20-100 accounts, configure mining sw and in the end to get a perfect picture: 100 users with 40kh/s instean one with 4000kh/s.

[The Frisian]

My wallet, version 1.4.3.0 stopped synching this morning.
Worked like  charm until this morning.
Does anyone knows why?

[My9bot]

Unless they use a very sophisticated setup, all those accounts would have the same IP though. That's pretty easy to detect.

Do you really think it's a solution? It's not question for you, but question for all. There is no problem to create 10-20-100 accounts, configure mining sw and in the end to get a perfect picture: 100 users with 40kh/s instean one with 4000kh/s.

than use proxys vpns ...
useless....
you can´t stop them

[Apprentice]

Do you really think it's a solution? It's not question for you, but question for all. There is no problem to create 10-20-100 accounts, configure mining sw and in the end to get a perfect picture: 100 users with 40kh/s instean one with 4000kh/s.

It's a good start. Let them try, could have unpleasant surprises. Especially if the coins mined using hash rate above limit are not paid.

you can't make a min-able coin and ask people to limit their hash rate. People will fire up whatever hash rate they can find to get coins.

[My9bot]

My wallet, version 1.4.3.0 stopped synching this morning.
Worked like  charm until this morning.
Does anyone knows why?

the think the main node at  104.128.225.215   its overloaded with connections

[The Frisian]

My wallet, version 1.4.3.0 stopped synching this morning.
Worked like  charm until this morning.
Does anyone knows why?

the think the main node at  104.128.225.215   its overloaded with connections

you could be right, but then nobody's wallet is working?

[My9bot]

no if  the node drop your connection try to restart your wallet

[The Frisian]

no if  the node drop your connection try to restart your wallet

did this many times already.

[sCyborg]

[2017-08-26 13:17:30] m7m block 1452868, diff 1.87, net 45.11 MH/s

another big jump in just a short while hope they'll notices there mistake sooner rather then later xD

edit:
[2017-08-26 13:20:53] m7m block 1452871, diff 2.17, net 52.52 MH/s