█▓▒░-< [ZPOOL.CA][BTC Multipool] The miners multipool >-░▒▓█ Paid 925+ BTC

[AngryDwarf]

mmm, wondering if the half payment issues have been caused by transaction size issues somewhere in the system?

[crackfoo]

I did get an email about some NOTE  payment failures earlier today but have been travelling. I'll check them out when I can and run through our payment  validation to pickup any missing/failed payments.

Thnx

[AngryDwarf]

Thanks

[AngryDwarf]

Happy New Year crackfoo and zpool miners.

I've been mining some DGB and that seems to have worked OK, so it looks like the issue was NOTE specific (dusty wallet perhaps?).
One thing I have noticed is that the 2 hourly payments don't always get immediately sent and don't have a transaction id. Eventually they get sent in a bunch. I assume the system is optimising the payments by waiting for a sufficient amount of miners transactions to be sent? I have the last remaining 3 DGB payments. Do I have to wait for other miners of DGB to mine enough DGB to release the transaction, or is there a time limit in which the transaction will eventually be sent? I'm wondering about this because I might have to mine some unpopular coins to reach the minimum orders size to dump them on an exchange.

Regarding the NOTE issues, I also have 2 small transactions that have not yet been sent for some time (hence the above query). I also have a pending balance on some digital credits that don't seem to have matured (this coin has  matured under the later DGB mine, so there seems to be a bit of an issue.)
Digital Credits (sha256)   0.000011 DGCS   0.1804%   0.000000   2d ago   Immature (6366)
   Digital Credits (sha256)   0.000019 DGCS   0.1078%   0.000000   2d ago   Immature (7291)
   Digital Credits (sha256)   0.000000 DGCS   0.0792%   0.000000   2d ago   Immature (7337)
In total I'm missing approx 4 NOTE and have some unconfirmed dust. I've left the wallet running, but my intention is that when this issue is sorted is to send the funds to an exchange to dump and decommission my wallet. It's got over 50 inputs and no coin control so the fee could be horrendous (never sent a NOTE transaction before).

Mining alt coins that the pool solves regularly could be a good way for me to obtain dash, ltc, doge etc. I can combine all my DGB inputs fee free quite quickly and send that to the exchange fee free, saving on the BTC exchange rate and high BTC transaction fees when the BTC network is busy.

Have a good day and I hope you can look into the NOTE issue when you can.

[JaredKaragen]

Ive got a site suggestion:

Could you somehow display the hashrate being pointed at each coin in the display somewhere?

Maybe something along the lines of:
When you are in the wallet pane, clicking the algorythm at the right will have it expand and show the hashrate directed by your account at each coin...

Or have it down where the rest of the hashrates are displayed.


Seemed like a nice idea anyways =)

[AngryDwarf]

Ive got a site suggestion:

Could you somehow display the hashrate being pointed at each coin in the display somewhere?

Maybe something along the lines of:
When you are in the wallet pane, clicking the algorythm at the right will have it expand and show the hashrate directed by your account at each coin...

Or have it down where the rest of the hashrates are displayed.


Seemed like a nice idea anyways =)

Probably a multi wallet summary page would be better.

[JaredKaragen]

I think the SHA256 share % vs pool hashrate is pretty far off.

Running ~20TH; pool reports 45;  share value ~35%...

5Th;  ~1/5 pool reported hashrate; share value ~13%


maybe a math error somewhere in the code? (browser FF, shouldnt make a difference for this I would think)

[crackfoo]

Happy New Year crackfoo and zpool miners.

I've been mining some DGB and that seems to have worked OK, so it looks like the issue was NOTE specific (dusty wallet perhaps?).
One thing I have noticed is that the 2 hourly payments don't always get immediately sent and don't have a transaction id. Eventually they get sent in a bunch. I assume the system is optimising the payments by waiting for a sufficient amount of miners transactions to be sent? I have the last remaining 3 DGB payments. Do I have to wait for other miners of DGB to mine enough DGB to release the transaction, or is there a time limit in which the transaction will eventually be sent? I'm wondering about this because I might have to mine some unpopular coins to reach the minimum orders size to dump them on an exchange.

Regarding the NOTE issues, I also have 2 small transactions that have not yet been sent for some time (hence the above query). I also have a pending balance on some digital credits that don't seem to have matured (this coin has  matured under the later DGB mine, so there seems to be a bit of an issue.)
Digital Credits (sha256)   0.000011 DGCS   0.1804%   0.000000   2d ago   Immature (6366)
   Digital Credits (sha256)   0.000019 DGCS   0.1078%   0.000000   2d ago   Immature (7291)
   Digital Credits (sha256)   0.000000 DGCS   0.0792%   0.000000   2d ago   Immature (7337)
In total I'm missing approx 4 NOTE and have some unconfirmed dust. I've left the wallet running, but my intention is that when this issue is sorted is to send the funds to an exchange to dump and decommission my wallet. It's got over 50 inputs and no coin control so the fee could be horrendous (never sent a NOTE transaction before).

Mining alt coins that the pool solves regularly could be a good way for me to obtain dash, ltc, doge etc. I can combine all my DGB inputs fee free quite quickly and send that to the exchange fee free, saving on the BTC exchange rate and high BTC transaction fees when the BTC network is busy.

Have a good day and I hope you can look into the NOTE issue when you can.

Thanks, getting back into this now.

Payments are generated every ~2 hours and inserted into the DB. Then they'll actually get sent usually ~10-20mins after that. So there will be a period of time where the payment will be listed as paid, but no tx, as it has yet to actually be sent. If the payment was actually created, it means there was already enough balance in the wallet to pay miners. If there wasn't, it would not get created until there is and your balance would simply continue to grow until it can be paid. At the same time, coins are not being sent to the exchange until the outstanding balances can be paid.

The min payouts are 0.001 every 2 hours and 0.0001+ (on sundays). It is a global minimum so it may take a long time if you're mining a coin that already has only micro block rewards. The majority of coins shouldn't be a problem.

I'm not sure why the tx's that was 1/2'd didn't get readjusted. I'll check into the balance and send off what you're owed. The code is designed to send 1/2 if the full balance couldn't be but should re-adjust the final balance accordingly...

something we'll look into.

[crackfoo]

I think the SHA256 share % vs pool hashrate is pretty far off.

Running ~20TH; pool reports 45;  share value ~35%...

5Th;  ~1/5 pool reported hashrate; share value ~13%


maybe a math error somewhere in the code? (browser FF, shouldnt make a difference for this I would think)

yeah, I haven't really grasped the values the pool presents sometimes. They do seem to fluctuate. I've tried to see why sometimes they are like that but do manual calculations seems to work out. A lot of the calculations are pulled from memcache so there may be times it's off/old/stale/reset? BTC in the pocket seems to be consistent so I don't want to start mucking with it.

but... I've yet to see the hashrates I'm renting, be that far off but I haven't rented SHA in a while.

[JaredKaragen]

Yeah,  Ive been doing a test nicehash rental to see what to expect to get at given hashrates and what I will need to hook up to hit my profit goals...  just using a calculator on the spot can be misleading because luck always has a hand in such things.  Saves me a step of hooking too much up at once, or not enough =)

It just kind of felt like anywhere from 5-10% of the expected share count was missing.... while trying to monitor as fairly and as accurate as possible....

Typically when I am renting;  I see maybe a difference between nicehash's pane, and pool reported speed at +-0.1TH for a 5TH rental....  which a small difference is to be accepted since I am guessing the pool bases the speed mostly off the shares' freq/size ratio...  But when looking at a 25TH pool;  and 5TH of that is my theoretical share size;  seemed low.

[McMont]

Can anyone provide me active nodes (addnode) to CrevaCoin? Thanks!

[crackfoo]

Can anyone provide me active nodes (addnode) to CrevaCoin? Thanks!

Can give these a try:

        "addr" : "54.93.35.41:22440",
        "addr" : "211.110.139.240:22440",
        "addr" : "85.25.198.151:22440",
        "addr" : "178.33.223.187:22440",

[AngryDwarf]

Thanks, getting back into this now.

Payments are generated every ~2 hours and inserted into the DB. Then they'll actually get sent usually ~10-20mins after that. So there will be a period of time where the payment will be listed as paid, but no tx, as it has yet to actually be sent. If the payment was actually created, it means there was already enough balance in the wallet to pay miners. If there wasn't, it would not get created until there is and your balance would simply continue to grow until it can be paid. At the same time, coins are not being sent to the exchange until the outstanding balances can be paid.

The min payouts are 0.001 every 2 hours and 0.0001+ (on sundays). It is a global minimum so it may take a long time if you're mining a coin that already has only micro block rewards. The majority of coins shouldn't be a problem.

I'm not sure why the tx's that was 1/2'd didn't get readjusted. I'll check into the balance and send off what you're owed. The code is designed to send 1/2 if the full balance couldn't be but should re-adjust the final balance accordingly...

something we'll look into.

Thanks for the explanation. Waiting for the scypt miners to squirrel away at PTC. However, I have experienced transactions with no transaction ID pending for hours. Also got a small DGB payment without transaction ID that keeps going to the top of the list every time DGB is paid.

Got the same block halving on VIA. Currently near four VIA down.

21h ago   5.67601885   bc55cc116dd1eea949ec592ffdb1409ca2ca...
Transaction Hash   Value   From (amount)   To (amount)
802dfe3f68ff447ee4868711a3a60476b575ce30f9f9260b4e396b43da46437b   5.000226   Generation   VtyHzNMp67sSSdyxPUMvqVnoq5t4c1LN1r (5.000226)
bc55cc116dd1eea949ec592ffdb1409ca2ca5503cbe00fe32e1ff4fdb50e7493   4.999774      Vaz5XxfLBSRtrfahvBMX82x7Ry64fbBN61 (2.16176457)
VxvPbrcVvbfMw8yHDpYvMrAmb9JTCBsneX (2.83800943)

[AngryDwarf]

mmm, seem to have an unexplained spike in pending VIA when I had stopped mining it. Could this be the transaction 1/2 adjustment being added on? Quite confusing if it adds it on to the earned value rather than deducting the 1/2 missing from the paid value.

[AngryDwarf]

So what is happening to these blocks with high immature figures?

Name   Time   Height   Amount   Status   Difficulty   Found Diff   Blockhash
   Via (VIA)   11m ago   1908544   5.05565642   Immature (15)   2567.110563   2982.323637   adb8ef481dc1ac6607f8d47b3fc7088184eb9e18ba3179f5c71d64fec3e35417
   Via (VIA)   3h ago   1908029   5   Immature (530)   2491.220645   3853.759533   27a81c987ca113f6ebd24b91b426008cc04bf1006dc5ef164c2345e42e7eb6d1
   Via (VIA)   6h ago   1907632   5   Immature (927)   2541.459737   3807.011811   a6c368f58917a6c3bde0f5a067f2662cee729c382f1312590a5c1c299129bdbd
   Via (VIA)   6h ago   1907580   5   Immature (979)   2441.891745   4158.812042   e795d04853ad2f008ca1566e91afd4c233f1e7d4e3dced72a8ea67c6d42b22c3
   Via (VIA)   7h ago   1907470   5   Immature (1089)   2591.277037   3172.329944   195e4c4531e17167e6780be05787ec78c01a01191554c8e5e157cff4fb55cfb8
   Via (VIA)   7h ago   1907404   5   Immature (1155)   2940.680268   3998.638564   256f61910985400a115c5152cbb6d365abe806090cc91a8011765f8541ea10b6
   Via (VIA)   9h ago   1907144   0   Orphan   2699.102997   4432.864163   dfb2c4f7ae13c6bfa24af0ee949224017e5d54ad5525770b826461f2287c558f
   Via (VIA)   22h ago   1905253   5   Immature (3306)   2397.713417   16734.983315   95c8bf0d0648e91f951fe3b1ad889ca85fb0b7bda06796ba96b719a632a0ee3b
   Via (VIA)   25h ago   1904819   5   Confirmed   3032.619417   5077.98337   9175307546dfec407ac91d9ffe09b144cbf1717cc1ed573316fa60af584776da

[elbandi]

So what is happening to these blocks with high immature figures?

Name   Time   Height   Amount   Status   Difficulty   Found Diff   Blockhash
   Via (VIA)   11m ago   1908544   5.05565642   Immature (15)   2567.110563   2982.323637   adb8ef481dc1ac6607f8d47b3fc7088184eb9e18ba3179f5c71d64fec3e35417
   Via (VIA)   3h ago   1908029   5   Immature (530)   2491.220645   3853.759533   27a81c987ca113f6ebd24b91b426008cc04bf1006dc5ef164c2345e42e7eb6d1
   Via (VIA)   6h ago   1907632   5   Immature (927)   2541.459737   3807.011811   a6c368f58917a6c3bde0f5a067f2662cee729c382f1312590a5c1c299129bdbd
   Via (VIA)   6h ago   1907580   5   Immature (979)   2441.891745   4158.812042   e795d04853ad2f008ca1566e91afd4c233f1e7d4e3dced72a8ea67c6d42b22c3
   Via (VIA)   7h ago   1907470   5   Immature (1089)   2591.277037   3172.329944   195e4c4531e17167e6780be05787ec78c01a01191554c8e5e157cff4fb55cfb8
   Via (VIA)   7h ago   1907404   5   Immature (1155)   2940.680268   3998.638564   256f61910985400a115c5152cbb6d365abe806090cc91a8011765f8541ea10b6
   Via (VIA)   9h ago   1907144   0   Orphan   2699.102997   4432.864163   dfb2c4f7ae13c6bfa24af0ee949224017e5d54ad5525770b826461f2287c558f
   Via (VIA)   22h ago   1905253   5   Immature (3306)   2397.713417   16734.983315   95c8bf0d0648e91f951fe3b1ad889ca85fb0b7bda06796ba96b719a632a0ee3b
   Via (VIA)   25h ago   1904819   5   Confirmed   3032.619417   5077.98337   9175307546dfec407ac91d9ffe09b144cbf1717cc1ed573316fa60af584776da

Via coin has 3600 block maturity: https://github.com/viacoin/viacoin/blob/master/src/main.h#L77
block time is 24 sec, so pool need to wait 1 day to spend the mined coins.

[AngryDwarf]

Via coin has 3600 block maturity: https://github.com/viacoin/viacoin/blob/master/src/main.h#L77
block time is 24 sec, so pool need to wait 1 day to spend the mined coins.

Thank you for the explanation. That worked. Got a VIA payement, but it was halved and there has be no readjustment to for over 6 hours. Pool says 30.5 VIA payed, only 21 received. I hope crackfoo can resolve this issue soon.

[elbandi]

Via coin has 3600 block maturity: https://github.com/viacoin/viacoin/blob/master/src/main.h#L77
block time is 24 sec, so pool need to wait 1 day to spend the mined coins.

Thank you for the explanation. That worked. Got a VIA payement, but it was halved and there has be no readjustment to for over 6 hours. Pool says 30.5 VIA payed, only 21 received. I hope crackfoo can resolve this issue soon.

i think the pool calculated, you get 30.5 via, but the pool has only 21 spendable coins. you will receive the remainder coins after the pool got the imature coins.

[AngryDwarf]

Via coin has 3600 block maturity: https://github.com/viacoin/viacoin/blob/master/src/main.h#L77
block time is 24 sec, so pool need to wait 1 day to spend the mined coins.

Thank you for the explanation. That worked. Got a VIA payement, but it was halved and there has be no readjustment to for over 6 hours. Pool says 30.5 VIA payed, only 21 received. I hope crackfoo can resolve this issue soon.

i think the pool calculated, you get 30.5 via, but the pool has only 21 spendable coins. you will receive the remainder coins after the pool got the imature coins.

There definitely seems to be some issue with the block half payment re-credit system. Last payment was for around 11 VIA, halved to 5.5 VIA. VIA account is now flat and other 5 VIA blocks have now been confirmed.

[crackfoo]

Via coin has 3600 block maturity: https://github.com/viacoin/viacoin/blob/master/src/main.h#L77
block time is 24 sec, so pool need to wait 1 day to spend the mined coins.

Thank you for the explanation. That worked. Got a VIA payement, but it was halved and there has be no readjustment to for over 6 hours. Pool says 30.5 VIA payed, only 21 received. I hope crackfoo can resolve this issue soon.

i think the pool calculated, you get 30.5 via, but the pool has only 21 spendable coins. you will receive the remainder coins after the pool got the imature coins.

There definitely seems to be some issue with the block half payment re-credit system. Last payment was for around 11 VIA, halved to 5.5 VIA. VIA account is now flat and other 5 VIA blocks have now been confirmed.

We've disabled the halving of payments for now, perhaps that will at least make the payments for non-BTC coins stable.