[ANN] Firo (FIRO) - Implementing ZKP privacy without trusted setup

[Brucelats]

Suprnova down again Omg. This is ridiculus omg!

[Jazek]

Suprnova down again Omg. This is ridiculus omg!

ocminer said he closed the pool. Read the suprnova info: "Pool is currently closed due to very poor quality of the coin, not syncable wallets and random crashes"

[olexx]

unfortunately the new "core_upgrade" wallet i've migrated to seems buggy as hell.. once it found a block it forked off the main chain and got stuck on that (found) block.

I'll go back to the stoneage-codebase wallet now, wait a lifetime for the resync (approx 3 days), then process the payouts and FINALLY close the pool for this coin, i'm done with it.

Bad news, I like suprnova. Maybe devs can help? Or let's go to zpool, we need to spread the hashrate.

[zcoinofficial]

There was an orphan block issue (stuck at block 54010) which can be resolved by going to Help > Debug Window > Console and typing in:

invalidateblock 36b6773ada5f879af88cae474c530c72cdcb0f40970890b60241d36a765cee8

This should put you on the correct chain. The fix has already been pushed on Github but are testing binaries.

We're starting our own pool soon to reduce problems like this at least until more pools pop up.

As for MPH stealing hashrate, we investigated into this with MPH and don't think this is true but due to an issue with people using Tpruvot's ccminer which has some differences from djm34's version.
Djm34 will come up with an official version soon for this but there's a community modified miner for this by ckraziel

Use binaries at own risk but I tested the miner and it seems okay and he did a pull request with the requested modification.
https://github.com/tpruvot/ccminer/pull/24

ccminer 2.2.1 x64 cuda 9: https://drive.google.com/open?id=0Bz5n9rB3aWeYYlpSVklUTTVIWGc
ccminer 2.2.1 x86 cuda 9: https://drive.google.com/open?id=0Bz5n9rB3aWeYaHZ1c0U1a3VGYkk

[mw5454]

Any plans when a hardware wallet integration for Trezor or Ledger might be released?

[mpirun]

I agree with all of you as for MPH vs. Suprnova comparison. However, what's worse, hash 'disappeared' or no working pool?.

My card produces  about 2900 Hash/second.
--supernova
(begin)  sep 21 13:55:53 CEST 2017  --> 0 zcoin
(end)    sep 28 09:58:04 CEST 2017 --> 1.31968557  
***0.1932 zcoins/day

If always on-line that should have produced 0.26 zcoins/day (averaged value when all works fine)

[ocminer]

There was an orphan block issue which can be resolved by going to Help > Debug Window > Console and typing in:

invalidateblock 36b6773ada5f879af88cae474c530c72cdcb0f40970890b60241d36a765cee8

This should put you on the correct chain. The fix has already been pushed on Github but are testing binaries.

Great that you find the issue after someone mined > 8h on the broken version of your wallet. Maybe you should think about developing and testing on testnet next time.

As for MPH stealing hashrate, we investigated into this with MPH and don't think this is true but due to an issue with people using Tpruvot's ccminer which has some differences from djm34's version.
Djm34 will come up with an official version soon for this but there's a community modified miner for this by ckraziel

Use binaries at own risk but I tested the miner and it seems okay and he did a pull request with the requested modification.
https://github.com/tpruvot/ccminer/pull/24

ccminer 2.2.1 x64 cuda 9: https://drive.google.com/open?id=0Bz5n9rB3aWeYYlpSVklUTTVIWGc
ccminer 2.2.1 x86 cuda 9: https://drive.google.com/open?id=0Bz5n9rB3aWeYaHZ1c0U1a3VGYkk

There's no problem with tpruvot's miner at all, why would hashrate be displayed correctly on other pools but not on MPH? But it's always good to "fix" things by breaking them.

And did you even check what's in the commit of that pull request ? It's basically just commenting out submitting stale shares:

https://github.com/tpruvot/ccminer/pull/24/commits/ab4487105eb2766face0b52db1a778fd1220fd39

I wonder if there's ANY technological knowledge here as I cannot see any kind of positive development whatsoever...

The old wallet is based on 0.8.x branch of bitcoin.. Years old.

Syncing takes about a week to finish to the current chain.

"importprivkey" forces a full resync of the chain - 2 weeks

Moving wallet.dat away (for backup) and restarting the wallet - again a full resync (2 weeks)...

"getblocktemplate" often says "connectinputs() failed" and doesn't deliver a template to work on

If there are several (zerocoin) tx'es in mempool the wallet responds slower and slower to getblocktemplate or other queries.


Maybe you want to fix up at least A FEW things and work with other pools as well as just with 95% hashrate centralization "MPH" fixing things for them in their favour.

[mpirun]

There was an orphan block issue which can be resolved by going to Help > Debug Window > Console and typing in:

invalidateblock 36b6773ada5f879af88cae474c530c72cdcb0f40970890b60241d36a765cee8

This should put you on the correct chain. The fix has already been pushed on Github but are testing binaries.

We're starting our own pool soon to reduce problems like this at least until more pools pop up.

As for MPH stealing hashrate, we investigated into this with MPH and don't think this is true but due to an issue with people using Tpruvot's ccminer which has some differences from djm34's version.
Djm34 will come up with an official version soon for this but there's a community modified miner for this by ckraziel

Use binaries at own risk but I tested the miner and it seems okay and he did a pull request with the requested modification.
https://github.com/tpruvot/ccminer/pull/24

ccminer 2.2.1 x64 cuda 9: https://drive.google.com/open?id=0Bz5n9rB3aWeYYlpSVklUTTVIWGc
ccminer 2.2.1 x86 cuda 9: https://drive.google.com/open?id=0Bz5n9rB3aWeYaHZ1c0U1a3VGYkk

again.... why there is not version for linux?. No linux, no serious/knowledgeable team behind.

[go6ooo1212]

..I've missed the MPH mining launch, is that the lyra2z algo same as MPH, or?
Which miner is it working with it also?

[zcoinofficial]

..I've missed the MPH mining launch, is that the lyra2z algo same as MPH, or?
Which miner is it working with it also?

Yes MPH is working on
http://zcoin.miningpoolhub.com/

The default miners work on it that are recommended on it.

[AizenSou]

I started to mine on suprnova like 5 hours ago. So far all seems good. Just block finding is super slow. We need more hashrate on Suprnova. DOnt mine on that shity mininghubpool that steals ur hashrate or reject part of it if you use ccminer.

unfortunately the new "core_upgrade" wallet i've migrated to seems buggy as hell.. once it found a block it forked off the main chain and got stuck on that (found) block.

I'll go back to the stoneage-codebase wallet now, wait a lifetime for the resync (approx 3 days), then process the payouts and FINALLY close the pool for this coin, i'm done with it.

Hi ocminer,

We have tried multiple times to reach u in slack but no respond. We apologize for the orphan problem and we almost immediately fixed the problem after seeing it (check commit https://github.com/zcoinofficial/zcoin/commit/3f96e023265214fabbe0438f06c77611aa53cb14)

We understand ur frustation as well but instead of being frustrating on it could u help us avoiding future problems by providing us the debug.log for the orphan block ?

Appreciate if u do that.

Regards,

Aizen

[crackfoo]

Hi,

We've added XZC to the miners multipool: www.zpool.ca

lyra2z pool:

http://www.zpool.ca/site/gomining?algo=lyra2z

Explorer:

http://www.zpool.ca/explorer/XZC

Peers:

http://www.zpool.ca/explorer/peers?id=1741

Blocks found by zpool:

http://www.zpool.ca/site/block?id=1741

Cheers!

we've finally popped our first block. Thanks to the new coming miners, keep it up

Cheers

[funnel]

There was an orphan block issue which can be resolved by going to Help > Debug Window > Console and typing in:

invalidateblock 36b6773ada5f879af88cae474c530c72cdcb0f40970890b60241d36a765cee8

This should put you on the correct chain. The fix has already been pushed on Github but are testing binaries.

We're starting our own pool soon to reduce problems like this at least until more pools pop up.

As for MPH stealing hashrate, we investigated into this with MPH and don't think this is true but due to an issue with people using Tpruvot's ccminer which has some differences from djm34's version.
Djm34 will come up with an official version soon for this but there's a community modified miner for this by ckraziel

Use binaries at own risk but I tested the miner and it seems okay and he did a pull request with the requested modification.
https://github.com/tpruvot/ccminer/pull/24

ccminer 2.2.1 x64 cuda 9: https://drive.google.com/open?id=0Bz5n9rB3aWeYYlpSVklUTTVIWGc
ccminer 2.2.1 x86 cuda 9: https://drive.google.com/open?id=0Bz5n9rB3aWeYaHZ1c0U1a3VGYkk

This miner works great in MPH with correct hashrate. Everybody use this one.

Thank you.

[avirdoz]

Does djm34's miner work fine on MPH?

[pr0ximus]

My wallet is struck at block 54010 for the whole day. Tried bootstrapping by adding the block chains from znode.io manually and resynced and that doesn't help too. Downloaded the latest Wallet (Zcoin v0.13.2.5-rc1) and that doesn't help too. Any help is greatly appreciated !

[majonezas]

There was an orphan block issue which can be resolved by going to Help > Debug Window > Console and typing in:

invalidateblock 36b6773ada5f879af88cae474c530c72cdcb0f40970890b60241d36a765cee8

This should put you on the correct chain. The fix has already been pushed on Github but are testing binaries.

We're starting our own pool soon to reduce problems like this at least until more pools pop up.

As for MPH stealing hashrate, we investigated into this with MPH and don't think this is true but due to an issue with people using Tpruvot's ccminer which has some differences from djm34's version.
Djm34 will come up with an official version soon for this but there's a community modified miner for this by ckraziel

Use binaries at own risk but I tested the miner and it seems okay and he did a pull request with the requested modification.
https://github.com/tpruvot/ccminer/pull/24

ccminer 2.2.1 x64 cuda 9: https://drive.google.com/open?id=0Bz5n9rB3aWeYYlpSVklUTTVIWGc
ccminer 2.2.1 x86 cuda 9: https://drive.google.com/open?id=0Bz5n9rB3aWeYaHZ1c0U1a3VGYkk

WOW!!! this ccminer 2.2.1 x 64 cuda gave hash boost from 6300 kH/s to 8200 kH/s with a little increase in power usage. thank you!

[Brucelats]

There was an orphan block issue which can be resolved by going to Help > Debug Window > Console and typing in:

invalidateblock 36b6773ada5f879af88cae474c530c72cdcb0f40970890b60241d36a765cee8

This should put you on the correct chain. The fix has already been pushed on Github but are testing binaries.

We're starting our own pool soon to reduce problems like this at least until more pools pop up.

As for MPH stealing hashrate, we investigated into this with MPH and don't think this is true but due to an issue with people using Tpruvot's ccminer which has some differences from djm34's version.
Djm34 will come up with an official version soon for this but there's a community modified miner for this by ckraziel

Use binaries at own risk but I tested the miner and it seems okay and he did a pull request with the requested modification.
https://github.com/tpruvot/ccminer/pull/24

ccminer 2.2.1 x64 cuda 9: https://drive.google.com/open?id=0Bz5n9rB3aWeYYlpSVklUTTVIWGc
ccminer 2.2.1 x86 cuda 9: https://drive.google.com/open?id=0Bz5n9rB3aWeYaHZ1c0U1a3VGYkk

Is this the actual fix or just "visual fix"?

This comment got me confused:

There's no problem with tpruvot's miner at all, why would hashrate be displayed correctly on other pools but not on MPH? But it's always good to "fix" things by breaking them.

And did you even check what's in the commit of that pull request ? It's basically just commenting out submitting stale shares:

https://github.com/tpruvot/ccminer/pull/24/commits/ab4487105eb2766face0b52db1a778fd1220fd39

[funnel]

My wallet is struck at block 54010 for the whole day. Tried bootstrapping by adding the block chains from znode.io manually and resynced and that doesn't help too. Downloaded the latest Wallet (Zcoin v0.13.2.5-rc1) and that doesn't help too. Any help is greatly appreciated !

This worked for me a few days ago, but the first time it showed me a warning and I pressed ok and it didn't work. Next time I manually started zcoin-qt.exe -reindex and it worked.

[Jazek]

There was an orphan block issue which can be resolved by going to Help > Debug Window > Console and typing in:

invalidateblock 36b6773ada5f879af88cae474c530c72cdcb0f40970890b60241d36a765cee8

This should put you on the correct chain. The fix has already been pushed on Github but are testing binaries.

We're starting our own pool soon to reduce problems like this at least until more pools pop up.

As for MPH stealing hashrate, we investigated into this with MPH and don't think this is true but due to an issue with people using Tpruvot's ccminer which has some differences from djm34's version.
Djm34 will come up with an official version soon for this but there's a community modified miner for this by ckraziel

Use binaries at own risk but I tested the miner and it seems okay and he did a pull request with the requested modification.
https://github.com/tpruvot/ccminer/pull/24

ccminer 2.2.1 x64 cuda 9: https://drive.google.com/open?id=0Bz5n9rB3aWeYYlpSVklUTTVIWGc
ccminer 2.2.1 x86 cuda 9: https://drive.google.com/open?id=0Bz5n9rB3aWeYaHZ1c0U1a3VGYkk

This miner works great in MPH with correct hashrate. Everybody use this one.

Thank you.

I got an increase in my hashrate from 3.3Mh/s to 3.8Mh/s

[pr0ximus]

My wallet is struck at block 54010 for the whole day. Tried bootstrapping by adding the block chains from znode.io manually and resynced and that doesn't help too. Downloaded the latest Wallet (Zcoin v0.13.2.5-rc1) and that doesn't help too. Any help is greatly appreciated !

This worked for me a few days ago, but the first time it showed me a warning and I pressed ok and it didn't work. Next time I manually started zcoin-qt.exe -reindex and it worked.

Tried that too and it did not help Any other suggestions?