Pages:
Author

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

newbie
Activity: 17
Merit: 0

Now mining one coin requires again orders of magnitude more electricity than during the short-lived ASIC rampage. Draw your own conclusion what this means for the market price of the coin.


It means network hashrate will drop until electricity required to mine a coin is about the same as before.  Market forces, ya know.
newbie
Activity: 14
Merit: 0
which miner and config you are using?
newbie
Activity: 30
Merit: 0
why do the blocks stand still? very slowly

Because of the now low hashrate trying to tackle high difficulty. It's adjusting.
newbie
Activity: 12
Merit: 0
why do the blocks stand still? very slowly
newbie
Activity: 30
Merit: 0
Any news on GUI wallets?

Later on today I think.

I would always suggest to give the cli a go, it's dead simple Smiley
jr. member
Activity: 44
Merit: 1
Any news on GUI wallets?
newbie
Activity: 30
Merit: 0
A great effort by Thaer and with some help of cryptochangements and all those in the community that supported. A nice successful fork, carried out smoothly.

All working lovely on OCUK Pool, at around 200Kh/s, got a block quickly: http://msr.ocukminingpool.com/#

XMR-Stak 2.4.3 with cryptonight_7 currency.

full member
Activity: 307
Merit: 101
Would this fork indicate the price increase?

Now mining one coin requires again orders of magnitude more electricity than during the short-lived ASIC rampage. Draw your own conclusion what this means for the market price of the coin.

EDIT: Congrats to everyone who bought tons of MSR in the past few days for ~$1. I couldn't believe that someone would dump tens of thousands of coins into those low bids, losing at least 20-25% revenues instantly and much much more by not hodling for a few weeks longer.
jr. member
Activity: 44
Merit: 1
Would this fork indicate the price increase?
newbie
Activity: 34
Merit: 0
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!
full member
Activity: 307
Merit: 101
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.
newbie
Activity: 13
Merit: 0
looking good, difficulty dropping rapidly


it's a beautiful thing. I wonder where it will bottom out?
member
Activity: 134
Merit: 10
looking good, difficulty dropping rapidly
full member
Activity: 307
Merit: 101
so when does the difficulty come tumbling back down again?

With every single new block found.

EDIT: Block 170001 mined.
newbie
Activity: 13
Merit: 0
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?
full member
Activity: 307
Merit: 101
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.
newbie
Activity: 13
Merit: 0
Frozen on block #169999
full member
Activity: 391
Merit: 105
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).

member
Activity: 134
Merit: 11
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?
member
Activity: 134
Merit: 11
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)
Pages:
Jump to: