sixteendigits
|
|
November 28, 2013, 02:01:19 PM |
|
sent coins from coinmine.pl to cryptsy and bter and they are showing up at neither hours later
|
|
|
|
sixteendigits
|
|
November 28, 2013, 02:03:50 PM |
|
tickets being received in my client just fine so it isn't the pool
|
|
|
|
Ancikv
Newbie
Offline
Activity: 46
Merit: 0
|
|
November 28, 2013, 02:25:53 PM |
|
have to leave the pool, we just money's worth ...
|
|
|
|
SpeedDemon13
|
|
November 28, 2013, 03:45:28 PM |
|
sent coins from coinmine.pl to cryptsy and bter and they are showing up at neither hours later
I'm having the same issue too. I send them from coinmine.pl to cryptsy or coinmine.pl to TIX wallet, nothing at all. We are wasting electricity to mine nothing at this rate. feeleep is the operator of coinmine.pl, isn't he?
|
CRYPTSY exchange: https://www.cryptsy.com/users/register?refid=9017 BURST= BURST-TE3W-CFGH-7343-6VM6R BTC=1CNsqGUR9YJNrhydQZnUPbaDv6h4uaYCHv ETH=0x144bc9fe471d3c71d8e09d58060d78661b1d4f32 SHF=0x13a0a2cb0d55eca975cf2d97015f7d580ce52d85 EXP=0xd71921dca837e415a58ca0d6dd2223cc84e0ea2f SC=6bdf9d12a983fed6723abad91a39be4f95d227f9bdb0490de3b8e5d45357f63d564638b1bd71 CLAMS=xGVTdM9EJpNBCYAjHFVxuZGcqvoL22nP6f SOIL=0x8b5c989bc931c0769a50ecaf9ffe490c67cb5911
|
|
|
SpeedDemon13
|
|
November 28, 2013, 03:47:30 PM |
|
I obtained 72 Kx on Gigabyte 7950 at -I 12 At -I 13 too many HW. Is this normal?
Set the intensity lower. I had to use -I 10 or -I 11.
|
CRYPTSY exchange: https://www.cryptsy.com/users/register?refid=9017 BURST= BURST-TE3W-CFGH-7343-6VM6R BTC=1CNsqGUR9YJNrhydQZnUPbaDv6h4uaYCHv ETH=0x144bc9fe471d3c71d8e09d58060d78661b1d4f32 SHF=0x13a0a2cb0d55eca975cf2d97015f7d580ce52d85 EXP=0xd71921dca837e415a58ca0d6dd2223cc84e0ea2f SC=6bdf9d12a983fed6723abad91a39be4f95d227f9bdb0490de3b8e5d45357f63d564638b1bd71 CLAMS=xGVTdM9EJpNBCYAjHFVxuZGcqvoL22nP6f SOIL=0x8b5c989bc931c0769a50ecaf9ffe490c67cb5911
|
|
|
johan11
|
|
November 28, 2013, 05:05:46 PM |
|
sent coins from coinmine.pl to cryptsy and bter and they are showing up at neither hours later
I'm having the same issue too. I send them from http://tix.botpool.net to cryptsy TIX wallet, nothing at all. Any idea?
|
|
|
|
Ancikv
Newbie
Offline
Activity: 46
Merit: 0
|
|
November 28, 2013, 05:08:49 PM |
|
Tix successfully repeated the fate of the dead forks. Well, or if the developers do is not to fix them problem . And I would like to believe in a brighter future.
|
|
|
|
iGotSpots
Legendary
Offline
Activity: 2548
Merit: 1054
CPU Web Mining 🕸️ on webmining.io
|
|
November 28, 2013, 05:14:14 PM |
|
Tix successfully repeated the fate of the dead forks. Well, or if the developers do is not to fix them problem . And I would like to believe in a brighter future.
Dead forks don't have a $5 million market cap What issues are you guys having? Mine is working just fine on a lot of machines so I need reports if something is wrong Sending coins from a pool to Cryptsy is an issue with either the pool withdraws or Cryptsy deposits, not the network or the QT
|
|
|
|
SpeedDemon13
|
|
November 28, 2013, 05:32:08 PM |
|
Tix successfully repeated the fate of the dead forks. Well, or if the developers do is not to fix them problem . And I would like to believe in a brighter future.
Dead forks don't have a $5 million market cap What issues are you guys having? Mine is working just fine on a lot of machines so I need reports if something is wrong Sending coins from a pool to Cryptsy is an issue with either the pool withdraws or Cryptsy deposits, not the network or the QT Just strange that even if it's a minor issue, why haven't the QT and/or checkpoint been updated? I sent a ticket to Cryptsy about the deposit/transaction issues and believe it's fine to deposit from a pool as long as it's not a P2Pool. I know Cryptsy is having issue with server overload at the moment, hopefully they get those new server online asap and fix any database issues in the transition.
|
CRYPTSY exchange: https://www.cryptsy.com/users/register?refid=9017 BURST= BURST-TE3W-CFGH-7343-6VM6R BTC=1CNsqGUR9YJNrhydQZnUPbaDv6h4uaYCHv ETH=0x144bc9fe471d3c71d8e09d58060d78661b1d4f32 SHF=0x13a0a2cb0d55eca975cf2d97015f7d580ce52d85 EXP=0xd71921dca837e415a58ca0d6dd2223cc84e0ea2f SC=6bdf9d12a983fed6723abad91a39be4f95d227f9bdb0490de3b8e5d45357f63d564638b1bd71 CLAMS=xGVTdM9EJpNBCYAjHFVxuZGcqvoL22nP6f SOIL=0x8b5c989bc931c0769a50ecaf9ffe490c67cb5911
|
|
|
iGotSpots
Legendary
Offline
Activity: 2548
Merit: 1054
CPU Web Mining 🕸️ on webmining.io
|
|
November 28, 2013, 05:34:34 PM |
|
Tix successfully repeated the fate of the dead forks. Well, or if the developers do is not to fix them problem . And I would like to believe in a brighter future.
Dead forks don't have a $5 million market cap What issues are you guys having? Mine is working just fine on a lot of machines so I need reports if something is wrong Sending coins from a pool to Cryptsy is an issue with either the pool withdraws or Cryptsy deposits, not the network or the QT Just strange that even if it's a minor issue, why haven't the QT and/or checkpoint been updated? I sent a ticket to Cryptsy about the deposit/transaction issues and believe it's fine to deposit from a pool as long as it's not a P2Pool. I know Cryptsy is having issue with server overload at the moment, hopefully they get those new server online asap and fix any database issues in the transition. Checkpoint I can do without updating the QT. I'll post the node I'm using to update checkpoints this weekend after Thanksgiving shit is done. It won't help anything except get rid of that error message, though. It doesn't affect functionality at all So the checkpoint is too old message is the only issue you guys are having with the QT itself? That's a nice easy fix that can be hotfixed. Won't even need to download a new QT, I can just update the checkpoint server
|
|
|
|
johan11
|
|
November 28, 2013, 06:38:10 PM |
|
Tix successfully repeated the fate of the dead forks. Well, or if the developers do is not to fix them problem . And I would like to believe in a brighter future.
Dead forks don't have a $5 million market cap What issues are you guys having? Mine is working just fine on a lot of machines so I need reports if something is wrong Sending coins from a pool to Cryptsy is an issue with either the pool withdraws or Cryptsy deposits, not the network or the QT Just strange that even if it's a minor issue, why haven't the QT and/or checkpoint been updated? I sent a ticket to Cryptsy about the deposit/transaction issues and believe it's fine to deposit from a pool as long as it's not a P2Pool. I know Cryptsy is having issue with server overload at the moment, hopefully they get those new server online asap and fix any database issues in the transition. Now deposit on Cryptsy working.
|
|
|
|
SpeedDemon13
|
|
November 28, 2013, 06:39:51 PM |
|
Tix successfully repeated the fate of the dead forks. Well, or if the developers do is not to fix them problem . And I would like to believe in a brighter future.
Dead forks don't have a $5 million market cap What issues are you guys having? Mine is working just fine on a lot of machines so I need reports if something is wrong Sending coins from a pool to Cryptsy is an issue with either the pool withdraws or Cryptsy deposits, not the network or the QT Just strange that even if it's a minor issue, why haven't the QT and/or checkpoint been updated? I sent a ticket to Cryptsy about the deposit/transaction issues and believe it's fine to deposit from a pool as long as it's not a P2Pool. I know Cryptsy is having issue with server overload at the moment, hopefully they get those new server online asap and fix any database issues in the transition. Checkpoint I can do without updating the QT. I'll post the node I'm using to update checkpoints this weekend after Thanksgiving shit is done. It won't help anything except get rid of that error message, though. It doesn't affect functionality at all So the checkpoint is too old message is the only issue you guys are having with the QT itself? That's a nice easy fix that can be hotfixed. Won't even need to download a new QT, I can just update the checkpoint server Cool, thanks. Seems like Cryptsy has just fixed the issue with deposit and withdrawals.....It would be nice to kind of spruce up the QT and update it a little, but not a major thing if the checkpoint is getting updated.
|
CRYPTSY exchange: https://www.cryptsy.com/users/register?refid=9017 BURST= BURST-TE3W-CFGH-7343-6VM6R BTC=1CNsqGUR9YJNrhydQZnUPbaDv6h4uaYCHv ETH=0x144bc9fe471d3c71d8e09d58060d78661b1d4f32 SHF=0x13a0a2cb0d55eca975cf2d97015f7d580ce52d85 EXP=0xd71921dca837e415a58ca0d6dd2223cc84e0ea2f SC=6bdf9d12a983fed6723abad91a39be4f95d227f9bdb0490de3b8e5d45357f63d564638b1bd71 CLAMS=xGVTdM9EJpNBCYAjHFVxuZGcqvoL22nP6f SOIL=0x8b5c989bc931c0769a50ecaf9ffe490c67cb5911
|
|
|
iGotSpots
Legendary
Offline
Activity: 2548
Merit: 1054
CPU Web Mining 🕸️ on webmining.io
|
|
November 28, 2013, 06:43:38 PM |
|
Tix successfully repeated the fate of the dead forks. Well, or if the developers do is not to fix them problem . And I would like to believe in a brighter future.
Dead forks don't have a $5 million market cap What issues are you guys having? Mine is working just fine on a lot of machines so I need reports if something is wrong Sending coins from a pool to Cryptsy is an issue with either the pool withdraws or Cryptsy deposits, not the network or the QT Just strange that even if it's a minor issue, why haven't the QT and/or checkpoint been updated? I sent a ticket to Cryptsy about the deposit/transaction issues and believe it's fine to deposit from a pool as long as it's not a P2Pool. I know Cryptsy is having issue with server overload at the moment, hopefully they get those new server online asap and fix any database issues in the transition. Checkpoint I can do without updating the QT. I'll post the node I'm using to update checkpoints this weekend after Thanksgiving shit is done. It won't help anything except get rid of that error message, though. It doesn't affect functionality at all So the checkpoint is too old message is the only issue you guys are having with the QT itself? That's a nice easy fix that can be hotfixed. Won't even need to download a new QT, I can just update the checkpoint server Cool, thanks. Seems like Cryptsy has just fixed the issue with deposit and withdrawals.....It would be nice to kind of spruce up the QT and update it a little, but not a major thing if the checkpoint is getting updated. We have some fun things planned soon
|
|
|
|
SpeedDemon13
|
|
November 28, 2013, 06:47:59 PM |
|
Tix successfully repeated the fate of the dead forks. Well, or if the developers do is not to fix them problem . And I would like to believe in a brighter future.
Dead forks don't have a $5 million market cap What issues are you guys having? Mine is working just fine on a lot of machines so I need reports if something is wrong Sending coins from a pool to Cryptsy is an issue with either the pool withdraws or Cryptsy deposits, not the network or the QT Just strange that even if it's a minor issue, why haven't the QT and/or checkpoint been updated? I sent a ticket to Cryptsy about the deposit/transaction issues and believe it's fine to deposit from a pool as long as it's not a P2Pool. I know Cryptsy is having issue with server overload at the moment, hopefully they get those new server online asap and fix any database issues in the transition. Checkpoint I can do without updating the QT. I'll post the node I'm using to update checkpoints this weekend after Thanksgiving shit is done. It won't help anything except get rid of that error message, though. It doesn't affect functionality at all So the checkpoint is too old message is the only issue you guys are having with the QT itself? That's a nice easy fix that can be hotfixed. Won't even need to download a new QT, I can just update the checkpoint server Cool, thanks. Seems like Cryptsy has just fixed the issue with deposit and withdrawals.....It would be nice to kind of spruce up the QT and update it a little, but not a major thing if the checkpoint is getting updated. We have some fun things planned soon Right on...Sweet....
|
CRYPTSY exchange: https://www.cryptsy.com/users/register?refid=9017 BURST= BURST-TE3W-CFGH-7343-6VM6R BTC=1CNsqGUR9YJNrhydQZnUPbaDv6h4uaYCHv ETH=0x144bc9fe471d3c71d8e09d58060d78661b1d4f32 SHF=0x13a0a2cb0d55eca975cf2d97015f7d580ce52d85 EXP=0xd71921dca837e415a58ca0d6dd2223cc84e0ea2f SC=6bdf9d12a983fed6723abad91a39be4f95d227f9bdb0490de3b8e5d45357f63d564638b1bd71 CLAMS=xGVTdM9EJpNBCYAjHFVxuZGcqvoL22nP6f SOIL=0x8b5c989bc931c0769a50ecaf9ffe490c67cb5911
|
|
|
Ancikv
Newbie
Offline
Activity: 46
Merit: 0
|
|
November 28, 2013, 08:09:05 PM |
|
Tix successfully repeated the fate of the dead forks. Well, or if the developers do is not to fix them problem . And I would like to believe in a brighter future.
Dead forks don't have a $5 million market cap What issues are you guys having? Mine is working just fine on a lot of machines so I need reports if something is wrong Sending coins from a pool to Cryptsy is an issue with either the pool withdraws or Cryptsy deposits, not the network or the QT Capitalisation ? On live fork , reliable systems are not lost transactions and coins
|
|
|
|
SpeedDemon13
|
|
November 28, 2013, 10:35:38 PM |
|
Finally my QT sync's completely. After re-downloading the QT and the blocks, now I don't get the damn error anymore. Plus I did all the addnodes too, now I can trust the using QT again...lol
|
CRYPTSY exchange: https://www.cryptsy.com/users/register?refid=9017 BURST= BURST-TE3W-CFGH-7343-6VM6R BTC=1CNsqGUR9YJNrhydQZnUPbaDv6h4uaYCHv ETH=0x144bc9fe471d3c71d8e09d58060d78661b1d4f32 SHF=0x13a0a2cb0d55eca975cf2d97015f7d580ce52d85 EXP=0xd71921dca837e415a58ca0d6dd2223cc84e0ea2f SC=6bdf9d12a983fed6723abad91a39be4f95d227f9bdb0490de3b8e5d45357f63d564638b1bd71 CLAMS=xGVTdM9EJpNBCYAjHFVxuZGcqvoL22nP6f SOIL=0x8b5c989bc931c0769a50ecaf9ffe490c67cb5911
|
|
|
iGotSpots
Legendary
Offline
Activity: 2548
Merit: 1054
CPU Web Mining 🕸️ on webmining.io
|
|
November 28, 2013, 10:40:35 PM |
|
Finally my QT sync's completely. After re-downloading the QT and the blocks, now I don't get the damn error anymore. Plus I did all the addnodes too, now I can trust the using QT again...lol
Excellent news. Told you everything was ok
|
|
|
|
SpeedDemon13
|
|
November 29, 2013, 05:55:25 AM |
|
Every thing is working fine at tix.coinmine.pl TIX mining pool, it was Cryptsy that was having the issue. I want to thank feeleep for doing his best to help me out.
|
CRYPTSY exchange: https://www.cryptsy.com/users/register?refid=9017 BURST= BURST-TE3W-CFGH-7343-6VM6R BTC=1CNsqGUR9YJNrhydQZnUPbaDv6h4uaYCHv ETH=0x144bc9fe471d3c71d8e09d58060d78661b1d4f32 SHF=0x13a0a2cb0d55eca975cf2d97015f7d580ce52d85 EXP=0xd71921dca837e415a58ca0d6dd2223cc84e0ea2f SC=6bdf9d12a983fed6723abad91a39be4f95d227f9bdb0490de3b8e5d45357f63d564638b1bd71 CLAMS=xGVTdM9EJpNBCYAjHFVxuZGcqvoL22nP6f SOIL=0x8b5c989bc931c0769a50ecaf9ffe490c67cb5911
|
|
|
Ancikv
Newbie
Offline
Activity: 46
Merit: 0
|
|
November 29, 2013, 08:54:50 AM |
|
Again stop transactions ?
|
|
|
|
kevcoin
Member
Offline
Activity: 77
Merit: 10
|
|
November 30, 2013, 01:29:54 AM |
|
botpool down? I can't access the site but my miner appears to still be connected
|
|
|
|
|