Topic: [PCN] ProCoin: ♕ Get Some! ♕ | Build A Service - Get A Bounty - Web Wallet - page 22. (Read 45613 times)

With no offence intended likewise, my partner and I at CrunchHarder are not only pool owners but are also on the dev team for a very well known top-10 coin ourselves, so we are fully prepared to fix and debug any issues that come up as they sometimes do - we can't always forsee these issues, but if they do occur we'll do our level best to help fix them. Good luck with whatever coins you choose to run pools for though.

No offence to the Procoin team but we saw this coming a few hours before launch and are very glad that we pulled out of running a pool for this underdeveloped coin. We just hoped that anyone who saw our message on our site got the warning and didnt waste their time and their precious hashes on this launch. We at Lifeforce knew about issues a few hours before and decided to wash our hands of it. I dont mean to be rude to the Procoin team, but we did waste our time setting a pool up for this coin only to discover at least one major issue with the coin daemon. At Lifeforce, we make damn sure to avoid setting up pools for coins that give us certain red flags as we know they are only going to be trouble for our miners at launch and going forward. We rather avoid the risk and hassle with these types of coins. However if you still want to mine there will always be a number of alternative pools out there who will set up pools for coins like this regardless of any issues. Either they don't know or don't care enough. Lifeforce make it their mission only run to pools for the coins that we think are worthy of our time and yours.

Again, my apologies to the Procoin team if this causes any offence however alot peoples time were wasted today/this evening.

Good luck all and happy mining.

http://www.Lifeforce.info - 0% fee for all our pools.



We will also say that the following pools were too damn lazy to make their own news pages and basically copied ours. Do you really want to mine with Pools who are too damn lazy to do a simple of job of making their own news page. That's up to you but we recommend you stay away from pool owners who cant make up their own stuff and steal from others:

https://pcn.forkpool.com/
http://pcn.sumpool.com/

Thanks Ikanunaki - it's good to get nice feedback - we're miners ourselves, so we know how it is to have to put trust in a pool owner you don't know and never met before - we appreciate the support, we try to maintain high standards in how we handle other peoples coins so it's nice to get good feedback even when things don't run as smoothly as we'd like them to. The coin devs have been great too though, and I'm sure we'll get this sorted soon.

Thank CrunchHarder. great job.

OK an update for everyone.

We have just spent about 2 hours chasing various confusing symptoms, since the issue manifests itself in various ways in MPOS and stratum.

At the heart of the issue is this:

A working wallet daemon behaves like this

$ vertcoind getbalance
1439.48282052  <--------------- THIS IS THE CONFIRMED BALANCE OF THE POOL WALLET
$ vertcoind getbalance "" 0
1489.48782052  <--------------- THIS IS THE TOTAL INCLUDING UNCONFIRMED BLOCKS

Wheras ProCoind behaves like this

$ ProCoind getbalance
91130.57034340   <--------------- THIS IS THE CONFIRMED BALANCE OF THE POOL WALLET
$ ProCoind getbalance "" 0
91130.57034340   <--------------- THIS IS THE CONFIRMED BALANCE OF THE POOL WALLET

Ie. no unconfirmed balances are being reported. Especially at this early stage in the coins life with blocks being found very fast, this leads to a _massive_ discrepancy in what is really in the wallet, and what MPOS thinks is in the wallet - ie. MPOS thinks funds are missing, but they aren't, they just aren't showing up yet (until they have confirmed), wheras in the "getbalance "" 0" call they should show up even if they're unconfirmed, as MPOS already locks them for the users at that point.

Therefore, in MPOS, in bitcoinwrapper.class.php

  // Wrapper method to get the real main account balance
  public function getrealbalance() {
    $this->oDebug->append("STA " . __METHOD__, 4);
    $aAccounts = parent::listaccounts();
    $dBalance = parent::getbalance('');

Wallet balance reports incorrectly

and in the payout cron jobs (in payouts.php):

 if ($dMPTotalAmount > $dWalletBalance) {
    $log->logError(" Wallet does not cover MP payouts - Payout: " . $dMPTotalAmount . " - Balance: " . $dWa$
    $monitoring->endCronjob($cron_name, 'E0079', 0, true);


  if ($dAPTotalAmount > $dWalletBalance) {
    $log->logError(" Wallet does not cover AP payouts - Payout: " . $dAPTotalAmount . " - Balance: " . $dWa$
    $monitoring->endCronjob($cron_name, 'E0079', 0, true);


So the crons refuse to run, believing there isn't sufficient funds to cover the users locked balances even though there is enough.

Also, the liquid balance (the pool owners funds) becomes massively negative - eg. on our pool, many thousands of PCN. The scripts are obviously designed to detect conditions like this and fail over to requiring manual intervention so as to prevent incorrect payouts.

We also believe there are some other issues, but it's taking longer to debug those, because we're seeing _huge_ variations in the size of the payout runs which we are struggling to fully make sense of at this stage.

Basically, right now, we've forced a payout run to ensure users get most of their funds reasonably quickly. We need to sleep (it's 03:30 here now) so we'll continue investigating tomorrow when the coin devs are around to consult and help again.

Sorry for the inconvenience and disruption - we'll do our best to get it all squared away ASAP.

you guys are missing out for a shit coin. litecoin is paying double this week...

No payouts problems, get payed after each block! Spread hashrate, go for p2pool
We are finding blocks!

I made a repo for the p2pool source code: https://github.com/P2PHash/p2pool-procoin.
We need more hashrate!!

P2Pool benefits:
* No registration required
* Distributed hashrate
* Immediate payouts after a block is found
* Higher payouts with transaction fees paid to miners
* No account hack possible


Address: p2phash.com:22048
Fee: 1%
Start mining within seconds! Just point your miner to p2phash.com:22048 and use the ProCoin address from your wallet for username, the password doesn't matter.

URL is not up just yet
statistics at http://107.170.35.84:25567
Point your miners to cgminer --scrypt -o 107.170.35.84:25567 -u (your PCN wallet address) -p (anything you like)

OK so we all just wasted our time on this?

oh  crap... I'm not having much luck lately.... this is a brand new GPU ASUS R9 X290 Direct CUII and I tweaked the settings to get about 800/khs. I started the miner before going to bed and kept it running in my room and it was hell trying to sleep with the fans running but as I was really tired I managed to fall in and out of sleep.

Does anyone know what caused this?

They were clearly on a wrong blockchain / fork earlier.

Im afraid you havent mined much coins..

Does anyone know what happened to http://pcn.sumpool.com/ ?

I am a little annoyed because I went to sleep with my miner running and now in the morning I can't reach the pool. I chose that one because it had the lowest latency from my location.

Great, thanks.

If anyone has problems just message me. I will reply in a couple of hours (gonna take a nap).

i see coins are back. Good. Will mine there now and let you know.. since crunchharder has also have own problems.

Now hasing.at pay me all.......missing after and confirming before


Good and responsible work, knowing there are problems in the distributed code (I guess that will be part of premine coin)


      

i am in 

Everyone who mined at http://pcn.hashing.at please check your dashboard and let me know if anyone didn't receive their coins.

The payments are for all the blocks since launch, up to block 754 (including).

All the newer blocks were paid automatically by the system.

I don't shut down the pool anymore as everything works correctly at the moment.

Ok, it's time to make an announcement - we are dealing with a serious issue in the difficulty calculation and targeting code for the coin. If any other pool owner claims this bug doesn't affect them, I can assure you they are 100% wrong

First, I want to reassure everyone of two things:

1. The coin devs seem honest, upfront and transparent - they are helping us at CrunchHarder to troubleshoot the issue.

2. We are pretty sure we know what the issue is (but don't want to say yet in case we open up an exploit in the code)

My business partner is coming back early from a night out to work on this (it's now 1am on a Saturday morning here), and I have just got back about 2 hours ago from going out with my girlfriend and am spending my Saturday night fixing this. Please cut us all some slack - nothing is terribly broken, but there is an issue of some sort, and I believe that may be why the other pool (can't remember the name) has got unfairly accused of scamming and has shut down. We are spending our leisure time fixing this, and we certainly could do without any accusations of scamming - both of the main partners at CrunchHarder are coin devs on a very well known (not premined, not a scam) coin and we are absolutely commited to running this business with integrity and putting our users first.

Importantly, all the mined blocks are in the pool wallet - no-one is going to get scammed of their coins, and we will get to the bottom of the issue.

The reason I'm posting is, while we investigate, it's not safe to allow payouts to continue to run. As such, I've stopped the payout crons on CrunchHarder temporarily, with a view to enabling them again absolutely as soon as is possible. We haven't done this out of personal gain or a desire to protect ourselves from an excessive payout, but rather because if we don't do it, users shares may get credited wrongly and cause unfair and incorrect payouts. I won't leave you all waiting days without an update while this situation continues - if the crons can't be started again within a few hours, we'll update on progress and explain why there is a delay in re-enabling them.

I'll update as soon as I'm able - your mining efforts continue to be credited in the database, and blocks continue to be found - no-one is going to miss out, and if any other pool owner claims this bug doesn't affect them, I can assure you they are 100% wrong.

Now is the Crunch harder pool problem turn

    Two hours without pay.