Topic: [ANN] [POW] [MSR] Masari - simple, scalable, and secure cryptocurrency - page 77. (Read 85155 times)

v10.2 is the latest version.
Those parameters you are using are not valid anymore.
It is xpool, xval and so on.
No, it doesn't work adding anything behind the address.

Still the pool shouldn't ramp the share difficulty up to 10000 when port 3333 or 5555 are used, when Claymore doesn't submit a fixed diff.

I compile it on Ubuntu. Make sure you have enough memory.
What error gives you?

You need last versión >= v9.7 and add "-allpools 1"

NsGpuCNMiner -a cryptonight -allpools 1 -o stratum+tcp://masari.superpools.net:5555 -u YOUR_WALLET_ADDRESS.5000 -p x

I use this program with AMD and it works without problems

Both pools adjust the difficulty up to 10000H no matter which port is being used, which is bad.
Putting a fixed difficulty behind the address [address.diff] won't work with the latest Claymore.
It gives a parsing error and likely discards everything after the address.

Windows binaries are now also available (MacOS binaries will be compiled later today):
https://github.com/masari-project/masari/releases/download/v0.1.2.0/masari-win-x64-v0.1.2.0.zip
sha256sum: 79b2efaa996ab58479c08d1b5e7839026100bdf39a4a85c7a7252883e388b0cb

Linux binaries for reference: https://github.com/masari-project/masari/releases/download/v0.1.2.0/masari-linux-x64-v0.1.2.0.tar.gz
sha256sum: 2d01c137bf1c0f8abc15bd898d7a4e755e2c77ea53d3a90bc206b5aa842c0044

Grade-school comments such as "dev got cocky like a triggered snowflake" don't help anybody nor adds context, and make you look like a noob.


As context for everybody here, a discussion was had yesterday regarding the difficulty calculation and I joined it by saying: "I'll  look into the difficulty calculation as well to see what can be done there" (was going to look into it after work, PST, v0.1.2.0 being the result)

Somebody was upset at the situation we have (due to be fixed in the upcoming hard fork), went through an unnecessary temper tantrum because it wasn't done right that very second, and everything he had said was filled with logical fallacies, mainly ad hominem attacks, and had little in terms of facts to back up what he was saying.

The said person in passing had indirectly mentioned "a coin you mentioned on bitcointalk" which prompted me to look into Sumokoin, and because it was an easy thing to check, within minutes I found the solution that addresses it by considering the statistical distribution of blocks, as well as the explanation of the issue (https://www.overleaf.com/articles/difficulty-adjustment-algorithms-in-cryptocurrency-protocols/ytcxbjvzrpbp/viewer.pdf ).

I worked on this immediately after my employment requirements were done for the day, and submitted v0.1.2.0 due in the upcoming protocol upgrade / hard fork.

Humans are emotional, and the user's emotions in the Slack group were getting the better of him, even though they were well intentioned. We'll all go through this though and everything is okay.

Cheers,
Thaer

Dev don't know shit.
Some guy on slack had to spoon-feed this bloody noob for days until he got it.
Instead of acknowledging the problem and working on a solution dev got cocky like a triggered snowflake.

Glad to hear there's an update! I was very put off when that miner came in.

Good. Perhaps you know a thing or two.  

https://masari.superpools.net/ is now in version v0.1.2.0

Thanks for devs!

Great job dev! That's quick

I have released a mandatory upgrade version v0.1.2.0, containing a protocol upgrade that changes the difficulty algorithm to handle these flash miners.

https://github.com/masari-project/masari/releases/tag/v0.1.2.0
Linux binaries: https://github.com/masari-project/masari/releases/download/v0.1.2.0/masari-linux-x64-v0.1.2.0.tar.gz

Windows and Mac binaries will be available tomorrow, and this is released early with Linux binaries to protect the exchanges and the pools involved

Everybody please update ASAP, as this hard fork could be due much sooner with the flash mining at play!

Looks like dev dont know what he is doing. This shit will get palyed. If he no smart then this is shit worth nothing. Dev do the right thing and change change what is needed. Or you dont know a thing?
Make your coin stronger. Protect it from bad actors/players/shitters/hash-jumpers/space travellers.

Maybe you dont care because you already have the biggest coin collection.

was miming this and riding the difficulty downtrend, then someone sent ridiculous amount of hashrate, I pulled my miner for now until difficulty is normal.

Hi dev, you might want to address this exploit issue as it can drive miners away. there was 26+ miners before now its down to 13.

We've considered reducing the difficulty window from 24 hours to 12 in the next protocol upgrade. If these persist, we can schedule a protocol upgrade sooner than originally planned and this should help mitigate the situation. We will also be looking at alternative difficulty calculations that can better handle these pumps.

A major priority for Masari is to have a consistent hash rate in the 10s of MH/s, which will protect against these kind of attacks. Having these problems means that the Masari's growing, and dealing with these issues is what will make the network stronger!

This is just a guess, but I think they're exploiting the lag in Masari's re-target time.  If you make a huge spike of hash for a little bit, you will get blocks very fast because the difficulty won't rise right away.  Then, once it is risen, you pull your hash and let other people mine on high difficulty for very slow blocktimes, until diff comes back down.  Then you repeat.

http://puu.sh/xPMOH/0cb7037f37.png
Someone keeps making the hash rate and difficulty skyrocket. 

or it could be things are stable for now and people who have joined in are mining with no problems and things are going slow and steady ahead )))

Whoa.

No new post, no new discussion. The thread seems inactive which leaves very bad impression on the coin.

Hello there.

 

Keep it up guys!

Amazing job done so far!