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

[jleonc01]

Good night what would happen with the difficulty of the network? Are the very small rewards

[1715623205]

1715623205

[1715623205]

1715623205

[1715623205]

1715623205

[chronosphere]

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

WTF

[The Frisian]

Well, you are wrong here.

The difference is that instead of banning good nodes straight away it let them try to give you the new block again.

It's a little tricky part but i'll try to explain it

When you get a block (Proper or not) at first the wallet say ok if all is good. Then a few sec later you get another block with the same height.
What happens here is that you (your wallet) ban that node directly for giving you a block you already have. This can be bad since it's all about the longest chain of blocks.
If you don't allow a retry of submiting the block (and chain) from that peer, it might be that the peer you just banned has the longest chain.

Without this setting, poolinfo (inc. my personal wallet) would been out of sync and on the wrong chain fast. I've even tried setting that to 200 and that wasn't good enough. Poolinfo needs 500 on banscore just to be open about which chain to follow and be able to properly see which block and chain it should follow. Also the reason for poolinfo got stuck yesterday, it had banned good peers without letting them try more.

But my wallet won't sync anymore!

[111magic]

Magi is aware of this and its an item on the Magi Roadmap. Big miners will look for fast profit. If the unique blockreward system drops the rewards it will not give them enough profit & they will move to other coins.
The idea of Magi is to be more fair than other currencies like btc or others. Everybody in the world can mine Magi with a simple computer. So everybody can earn some XMG. In the world a $ gives different value. For somebody its not much and for others its a lot. With other currencies you need money to get more money. So if you have a huge miningfarm you can collect more money with mining btc. The rich get richer.
Sure Magi will need more improvements in the future but remember Magi team is not huge & it will take time to find the end point were all things will be as Magi likes it to be.

Personal i'am with Magi from the start. I'am not looking for fast money (gave more than 100k XMG away with campaigns & give-aways) but i like the whole idea about Magi.
If Magi can achieve this goal than whole world will look at this unique decentralized currency.
Everybody who liked the help with this feel welcome!

Regards
111magic

Just reading 4 pages of posts i missed.
Thought of a post i added here some pages back.
Changing mindsets of people is not an easy goal to achieve. But Magi will continue as it did the last almost 3 years. In time Magi saw the community grow & more people like and appriciate the concept of the Coin of the Magi. During these years Magi is to strong to give up and will continue with achieving the goals.

💪

[Flapmin]

does setgenrate true crash anyone elses wallet?

[ex33s]

Well, you are wrong here.

The difference is that instead of banning good nodes straight away it let them try to give you the new block again.

It's a little tricky part but i'll try to explain it

When you get a block (Proper or not) at first the wallet say ok if all is good. Then a few sec later you get another block with the same height.
What happens here is that you (your wallet) ban that node directly for giving you a block you already have. This can be bad since it's all about the longest chain of blocks.
If you don't allow a retry of submiting the block (and chain) from that peer, it might be that the peer you just banned has the longest chain.

Without this setting, poolinfo (inc. my personal wallet) would been out of sync and on the wrong chain fast. I've even tried setting that to 200 and that wasn't good enough. Poolinfo needs 500 on banscore just to be open about which chain to follow and be able to properly see which block and chain it should follow. Also the reason for poolinfo got stuck yesterday, it had banned good peers without letting them try more.

But my wallet won't sync anymore!

Then that might be because the peer you syncing from banned you because the above reason.
It's a pure bitch when that happens! Basically what happens there is your wallet won't sync and you very open to get on a fork cause you can't connect to proper peers. And in this case you might been transmitting a bad block to that peer and they said Naha! Not a good block. Good bye, i've banned you. Since they got a propper block 1 sec before you sent that block. This is where banscore comes into play, it don't ban you straight away! It let you try a couple of times before.



 

[My9bot]

@ex33s   i think you are again on a fork

[My9bot]

yepp 2 chains again


getblockhash 1453445
9952860471fbabfcd8784949cc5eb2d0d13647b7abbe09ed33b756fc62e4e5bf


other wallet

getblockhash 1453445

000000005565d193be0350b4e52df245a3f32bf9d6e935c9c5b87b438bc1e364

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

[akuci]

Everyone is on the wrong chain looks like...

[ex33s]

@ex33s   i think you are again on a fork

Yup, you'r right. Fixing it now.

[My9bot]

@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

[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

[The Frisian]

@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?

[malafaya]

0.54 XMG block rewards. Nice going, big hashers 

[My9bot]

wow 20 blocks in 10 mins 

[chronosphere]

Another good idea:

Can we not change the rewards algo so that there is a zero block reward possible?

This would chase away the high hashraters and botnets becuase if it exceeds that which would drop the coin below 2 XMG block reward then the block reward drops ALL THE WAY to zero reward until the pool and/or global hash rates drop.

What i am saying is this limiter should be applied by the Dev as a whole to the global network so the speed is limited to below a certain max global threshold so no one pool can do these attacks....as well as a Pool by Pool input so the owner of the pool can put in a minimum reward threshold and a max speed cap per account and max connections per IP limiter and list the rules on the home page.

There should also be a global limiter so that it drops to zero reward if the network is being 5o+1 attacked or other DDoS mining techniques of unethical miners, except for pools that are under another threshold you could call "global limiter exception speed" which is a max has rate of a small pool so they do not shut down if the large pools are getting DDOs'd that way the coin can keep the blockchain moving even if the pools are being attacked in other situations, the small pools with lower net hash rate won't get set to zero reward but any pool exceeding the global limit speed per pool will be set to zero under X threshold input for the dev to have control over this and agreements about pool reward voted on once the new systems tested out and debugged.

Please allow a new shift to this zero block reward paradigm once block rewards drop below say...5 XMG-10XMG.

I would prefer it personally with my vote that the rewards, if being violated past 15 XMG block reward than mining gets paused till pool hashrate is back under the proper speeds.

If everyone is willing to be paused when attacks are happening, then we can filter out the asshats who are refusing to follow the polite rules of this coin.  They are not changing by being asked nicely.  The only way, as the other guy who i called disrespectful did say, is to heal the vulnerabilities.

Perhaps we allow the pools to choose their own limit threshold?  I advice 15 because it will keep everyone lowering their hash to comply to the limits.  However this would lead to a lower max speed allowed if it were to keep the rewards higher.

There is a Tao of Magi that must be followed to understand this coin.

It is VERY Dao.  If one sees that less is more and more is less, then one can understand this.  Those that do not understand this should be punished by the pool blocking all connections or pausing hash movement until the attacking hash has stopped blasting the pool, or alternatively, my suggestion of setting up a lower minimum XMG of ZERO so that if pool hashrate = > than threshold limiter, reward sets to zero xmg until hash rate drops below the max level that allows the minimum block reward input.

If they attack the pool to keep it shut down this is illegal.  This is considered black hat hacking and can be prosecuted by law.

I believe a zero XMG block reward drop if hash rates of the combined pool are below 15 XMG would be the best approach...  

That would keep the take very nice for everyone, including the idiot botnetters who are being abusive of the kindness of the non-enforced limitation, if they stick to the advised speed limits or not get any reward at all.  

You cannot be polite about this any longer due to this new phenomenon, adaptation is mandatory.

That would be awesome!

Thanks!

Enoch

[the_drugs]

I'm not sure if these are all tied together, but as i see it there are a number of major issues facing magi right now.
First and foremost is the issue of securing the blockchain. At this point and after this number of forks and pools on the wrong chain(s) something needs to be done, if that means taking mining offline for a number of days so be it. I've been against a rollback this entire time as well, but at this point if this will fix the issues currently facing the network what must be done must be done.
Secondly, something MUST be done about large miners, botnet mining, block rewards, and pool distribution. Perhaps there is someway to rework the m7m algorithm to FORCE the -e stipulation to be observed based on network hash, as well as local hash.
Third, I feel a lot of blame falls not on the developers of magi, but the community or rather those looking to exploit magi for a quick return, as well as the pools and operators for flat out refusing to enforce the "maximum" hashrates, as well as continuing to let this abuse slide.
We need to fix our blockchain and our coin, 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.

[oVPN]

this explorer is connected to devs node: http://178.17.174.27:8280/m-chain

[oVPN]

@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