[ANN] [POW] [MSR] Masari - simple, scalable, and secure cryptocurrency

[Crocomoco]

When is the fork scheduled ? Do i need to withdraw all my MSR from Exchanges ?

[boomboombazookajeff]

When is the fork scheduled ? Do i need to withdraw all my MSR from Exchanges ?

SouthXChange and TradeOgre are aware of the fork, so they should be fine there. I'm not sure of Stocks.Exchange (someone please chime in). You're MSR should be safe in your wallet so long as you have the seed.

[Crocomoco]

When is the fork scheduled ? Do i need to withdraw all my MSR from Exchanges ?

SouthXChange and TradeOgre are aware of the fork, so they should be fine there. I'm not sure of Stocks.Exchange (someone please chime in). You're MSR should be safe in your wallet so long as you have the seed.

Thank you sir, you are too kind.

[toyo87]

Please what mining software is used to mine Masari?

[TacoBond]

Please what mining software is used to mine Masari?

xmr-stak works fine. if you are using vega56 or 64's i like cast miner http://www.gandalph3000.com/cast_xmr/cast-xmr-optimized-cryptonight-miner-for-rx-vega/

[wudafuxup]

Please what mining software is used to mine Masari?

You can use XMR Stak, XMRig, SRBminer, SGMiner, Claymore, SSG Miner, Cast XMR, ect.. There are a bunch of different miners you can use.

[wudafuxup]

What's up with the new windows CLI binaries. Brazen Badger seems to have issues every time I open it. I'm getting wierd symbols where letters are supposed to be.



Once the language is set I'm getting this error aswell.



The daemon seems to working fine however. Anyone else seeings these errors?

[nanona]

I had the problem that the v0.2.0.2 masari-wallet-cli would simply not recognize the wallet files from v0.1.4.0 as if there is no backward compatibility.
You input the wallet password and get some error: "Error: failed to load wallet: std::bad_alloc"

So I used --restore-deterministic-wallet and entered the seed from the old wallet, but... attention... it will then ask you for something like a seed encryption pasphrase. If you enter one, it will generate a completely new seed with a new address, i.e. a new wallter, not your old wallet. I don't remember if this seed encryption passphrase was there in previous versions, well at least I didn't use it. So I had to restore again, this time leaving that seed encryption passphrase blank and so it finally restored my old address, i.e. exactly my old wallet.

That's on Ubuntu 16.04 LTS. Not tried the Windows or MacOS version.

[cryptonote-social]

Celebrate the fork! Join our brand spankin' new Masari mining pool...

In celebration of the v5 fork we've added Masari to our community pool site:

https://cryptonote.social/msr/

There's no better time than now to join your small neighborhood friendly mining pool! We'd be delighted if you were to help get this off the ground.

West-coast USA based servers; no fees or minimum limits on withdrawals at this time.

[thaer]

I had the problem that the v0.2.0.2 masari-wallet-cli would simply not recognize the wallet files from v0.1.4.0 as if there is no backward compatibility.
You input the wallet password and get some error: "Error: failed to load wallet: std::bad_alloc"

So I used --restore-deterministic-wallet and entered the seed from the old wallet, but... attention... it will then ask you for something like a seed encryption pasphrase. If you enter one, it will generate a completely new seed with a new address, i.e. a new wallter, not your old wallet. I don't remember if this seed encryption passphrase was there in previous versions, well at least I didn't use it. So I had to restore again, this time leaving that seed encryption passphrase blank and so it finally restored my old address, i.e. exactly my old wallet.

That's on Ubuntu 16.04 LTS. Not tried the Windows or MacOS version.

If you rename your keys file (i.e. wallet-name.keys), it will solve the problem. This is because you have to clear your wallet cache (which would be wallet-name, no extension). A rename of the keys file instead of deleting the cache is the safest option (in case you accidentally delete your private key)

[thaer]

What's up with the new windows CLI binaries. Brazen Badger seems to have issues every time I open it. I'm getting wierd symbols where letters are supposed to be.

[img removed]

Once the language is set I'm getting this error aswell.

[img removed]

The daemon seems to working fine however. Anyone else seeings these errors?

This is the first case I'm seeing, what block is your daemon synced at?

[wudafuxup]

What's up with the new windows CLI binaries. Brazen Badger seems to have issues every time I open it. I'm getting wierd symbols where letters are supposed to be.

[img removed]http://Once the language is set I'm getting this error aswell.

[img removed]

The daemon seems to working fine however. Anyone else seeings these errors?

This is the first case I'm seeing, what block is your daemon synced at?

The daemon seems to be synchronized just fine. It's just the masari-wallet-cli that has wierd symbols. I was even getting them on my seed aswell (I'm not going to screenshot it for obvious reasons) >.<. I kept opening it until I managed to get an address where I could see the seed properly (hopefully it's ok).

[hyipmoon]

Frozen on block #169999

[nanona]

Frozen on block #169999

That's the effect of CPUs/GPUs now trying to find at ASIC difficulty the first block of the HF chain. I assume 170000 will be the first HF block (not sure since other coins count differently and 170001 would be the first HF block there).

If 170000 would still be on the common chain and 170001 be the HF block, then the chain being stuck at 169999 would be an attack. Someone controlling most ASICs could have switched them off and the chain would therefore not be able to reach the HF block. But the attacker would have done that earlier, not one block before the HF, for maximum damage. I therefore assume it is rather the above scenario.

EDIT: Block 170000 has been mined.

[SalvadorPerez]

Frozen on block #169999

That's the effect of CPUs/GPUs now trying to find at ASIC difficulty the first block of the HF chain. I assume 170000 will be the first HF block (not sure since other coins count differently and 170001 would be the first HF block there).

If 170000 would still be on the common chain and 170001 be the HF block, then the chain being stuck at 169999 would be an attack. Someone controlling most ASICs could have switched them off and the chain would therefore not be able to reach the HF block. But the attacker would have done that earlier, not one block before the HF, for maximum damage. I therefore assume it is rather the above scenario.

EDIT: Block 170000 has been mined.

so when does the difficulty come tumbling back down again?

[nanona]

so when does the difficulty come tumbling back down again?

With every single new block found.

EDIT: Block 170001 mined.

[online987659329]

looking good, difficulty dropping rapidly

[SalvadorPerez]

looking good, difficulty dropping rapidly

it's a beautiful thing. I wonder where it will bottom out?

[nanona]

looking good, difficulty dropping rapidly

it's a beautiful thing. I wonder where it will bottom out?

Simple. At $1-2 daily revenue per GPU.

[Honey989]

looking good, difficulty dropping rapidly

it's a beautiful thing. I wonder where it will bottom out?

Simple. At $1-2 daily revenue per GPU.

That would be great!