Topic: [ANN] [XMG] MAGI | CPU mining | mPoW | mPoS | [MagiPay] - page 395. (Read 2375972 times)

 that all sounds good untill you look at the code its already very complicated because there are
variables based on additional variables ...hmmm

 do you mean pool admins limiting per ip?

pumping the hash to knock miners interest has been the normal for a long time
this coin has no multipool if im mining magi on my cpu means im dedicated to mining  
im not even going to notice the hashrate on the network since i have no alternative
coins to mine on the same algo it matters absolutely not from moment to moment
at the end of the week if i check on my payouts and they suck i may decided to cpu mine
something else ... but not likely . the dedicated miner is just going to mine regardless of
the payout ... no one is mining up 1000s of magi to dump its a set it and forget it .
ive not looked into the entire story so maybe im missing something... the complaint is the
difficulty is to high and the reward is almost zero? if so in my very humble opinion good
a coin that fights back ... a complaint of mininers driving up the difficulty and then hopping
is no new story ... i really dont see the problem but i am ready to be corrected  

that high hashrate i dont think it is a DDOS attack. Probably a botnet with its own pool or rental with its own bot monitoring the blockchain or other pools and only activating when rewards are high. Otherwise they would mine on other chains which can take higher hash rates without affecting rewards as much. The only way to prevent this is making them not earn much when they suddenly jump in for a quick pump and dump mining.

The variable reward system is what makes this coin Magi coin. It is what makes the coins unique.

Some people are thinking that we could implement controls on pools. Yes we could but it would be for naught. Reason? With a little coding knowledge i could setup a pool with minimal effort. Well i dont really know how to code but i could pay someone to make just modify a already existing pool code i could grab for free online.

Hard coding it on the node will work much better but again nodes are also open source one could simply compile a clean one without the hard coded limits.

Banning ips or will not work either since botnets have different hashrates. rentals also same problem. Different ips for all.

I head bitcoin cash implemented an emergency protocol where after several hrs if they cant find this number of blocks difficulty is adjusted to 20% of the current difficulty. Maybe we can use this and implement a sudden payout reduction or increase instead of the normal slow adjustments when hash increases too much or decreases too much. But then if people wants to attack the coins they can simply hash high and remove it to keep reward low.

It is hard to really do anything. If it was possible to make it a solo only coin that would probably work out a bit better but not perfect as well.

>> returns to reasonable levels,

What is reasonable? Any constant in net algorithm work until not a lot people interested in this.
Forget for a second about botnets and hackers..    
For example, now algo limited by  20Mh/s  and it is work, coins become more popular, and now we have 40Mh/s fair solo miners.. And then what?  Admins decide change 20 to 40?  
And where this decentralisation? If only one man can easily decide change revenue for everyone.
Such manual manipulations is path to drop price or delist coin from markets.


>>DDOS attempt
What are you speak about, we didn`t speak about ddos or other hack attack..   For example, I or someone else  have  10000 remote devices, each is not strong enough (50-100Kh/s for example) and have different IP.
I can do attack do coin reward, I push required power to make revenue near zero and then wait until others stop mining..  then I start optimal power and get most of coins, until others not back.
And when they back - I start  from begining.  
It will work not because I doctor-evil and want to beat all this beautiful community... no...  just because it can be profitable, more profitable than other coins.

>>> I still say the problem would be addressed if there was a minimum block reward threshold of zero, that is triggered by input of minimum block reward due to hashrate.  I.e. if block reward of a pool falls below 10 XMG, for example, then block reward drops to zero until hash returns to reasonable levels, meanwhile any hackers doing a DDOS attempt on the pool should be IP logged and arrested if within a country that has laws against DDOS in a harmful manner to a server not owned by the hacker. 

been following your commits ... bravo sir/mam/dev
flappycoin will be swapping to m7m ... its not been easy
Ill be re ... removing some of the code i had to change to get it
to hash out a proper genesis block before pushing the source
were in the artwork phase now. Not only are we happy to have
a solid algo and plan to finalize the flappcoin recovery
but we are hopefull that this will spread out a bit of the hash
that has been hindering Magi were not a pump and dump
team this swap has been a year in the making
flappy will be swapping the chain from 10billion FLAP
down to 10 million FLAPS deflapation and we for one
welcome the payout structure ..AS IS fu%$ the botnet

soo ive been trying to keep it quiet people . but your still having the same arguments ... this is an amazing algo . it is Superior in almost every way. the problem is greed . why min a coin to the point of killing the payout ... I finished hashing a fresh merk root and gen block.   indeed flappy is swapping to m7m 

this is a bad idea and not a good idea 

i've said it before... people are selfish. nobody will drop their own hashrate for ur cause unless the zero block only applies to themselves.

i agree with oxothuk:

He does seem to have a good idea:

As oxotnuk (?) previously said, you cannt create mineable coin and ask people do not mine. Now you talk about 1000 kh, tomorrow miners create tens accounts on different pools and you'll said 1000 is too much and 500 is acceptable limit, next day - 300, next day - 150, etc. You will ban for IP - miners rent hundreds microinstances @Amazon for socks proxies. You'll limit block per minute - big miners simply occupy Magi and small miners get nothing. Administrative limits is not a solution, it's a witch-hunt.

Anyway, big miners are not idiots and will not mine less profitable coin. As you can see, here is week after fix, and max hashrate is about 30-60 MH (was 90 three weeks ago). It's normal - miners try botnets, see result and stop mining Magi. It is a only one way to stop big miners. I absolutely misunderstand dramatics last three days. We have algo, we know about reward mechanism. After time botnet owners will understand - it's more profitable to mine Magi with 1MH than 10MH or maybe even dont mine.

ban hash rate  ? Why not the mine another m7m coin for awhile

this is getting better and better..wow intersting

What are you talking about? There will be around 30-40MH after limitations too, not 6MH for sure. I'am not for 300 limit, but under 1000, and strict botnet\multiple account control. This coin have unique algo, so the rules must be unique. I know crypto is no rules, but if you want it to be a payment processor, you must have some rules, and insure people that noone will come with some crazy idea to gain huge amount of coins and crash your network, or missuse it. Do you like the block rewards in the past 6-7 hours? I'm sure you like it. So let it be always that good. There will always be smaller and bigger miners. Not everyone will be near 1000, so you will be earning a nice amount event with a 1000 limit becuase of high block rewards. I think 1000 is fair for everyone, or let the devs and the Magi team decide. I don't have anything against big miners, just don't ruin this coin because you want fast profit.

you're forked = you're f***ed

glad i could help you bro. happy staking

If you don't receive good stakes anymore, you're forked.

i'm reciving a lot of unconfirmed...no acepted stakes... similar to your image, but i'don't know why?

I don't think that is a ban, disconnect can happen for multiple reasons like network issues.