[NEW POOL & MINER] - BitcoinPool.com - Jump In! ~NO FEES~ :)

[GuyGallowglass]

I having the same problems as bobR.

I've had a bitcoinpool payment that hasn't been confirmed for almost two days sitting in my bitcoin client. Yet a payment I received last night from a forum member has been confirmed 75 times.

so they are stuck in this stage?:

http://img.techpowerup.org/110325/Capture086.jpg

I also have three like this, remained 0/ unconfirmed. :-/

So basically, we just have to wait it out?  Or there something we each individually have to contact the admin for?

[1713480767]

1713480767

[1713480767]

1713480767

[1713480767]

1713480767

[1713480767]

1713480767

[geebus]

The backlog is over 1500 transactions now: http://www.bitcoincharts.com/bitcoin/ (5 of them are my bitcoinpool payouts)

It was about 1200 half a day ago, so it's going in the wrong direction...

There is a network flood of small transactions going on right now... of those 1500, I'd guesstimate that ~1000 of them are spammed transactions.

[geebus]

I also have three like this, remained 0/ unconfirmed. :-/

So basically, we just have to wait it out?  Or there something we each individually have to contact the admin for?

There is nothing that we can do about it. The pool has already sent the payment, and no longer has the bitcoins. It is purely a matter of waiting for the network to sort out the transactions and get them included into new blocks.

Unfortunately, someone seems to be flooding the network with micro-payments right now, which is causing a significant delay in the amount of time it's taking low priority transactions to get processed.

A transaction can be marked as lower priority if the amount is low, the transaction fee paid to send it is low, or nonexistent, and if there are other higher priority transactions in front of it. It's a queue that the network has to work through.

I've honestly never seen it this delayed before, but rest assured, you will get them eventually. I'm sorry it's taking awhile, but it's out of our hands.

We're currently looking into ways to avoid this situation in the future. We hope to have a resolution in place by the end of the weekend.

[GuyGallowglass]

I also have three like this, remained 0/ unconfirmed. :-/

So basically, we just have to wait it out?  Or there something we each individually have to contact the admin for?

There is nothing that we can do about it. The pool has already sent the payment, and no longer has the bitcoins. It is purely a matter of waiting for the network to sort out the transactions and get them included into new blocks.

Unfortunately, someone seems to be flooding the network with micro-payments right now, which is causing a significant delay in the amount of time it's taking low priority transactions to get processed.

A transaction can be marked as lower priority if the amount is low, the transaction fee paid to send it is low, or nonexistent, and if there are other higher priority transactions in front of it. It's a queue that the network has to work through.

I've honestly never seen it this delayed before, but rest assured, you will get them eventually. I'm sorry it's taking awhile, but it's out of our hands.

We're currently looking into ways to avoid this situation in the future. We hope to have a resolution in place by the end of the weekend.

I'm not blaming you or anyone else, I'm just trying to better understand what is going on... and you really cleared things up.

I really appreciate what you are doing and to keep up the good work

[geebus]

I'm not blaming you or anyone else, I'm just trying to better understand what is going on... and you really cleared things up.

I really appreciate what you are doing and to keep up the good work

No worries, I didn't think you were pointing the finger at us or anything. Sorry if it came off a little defensive. 

For peace of mind though, anyone who is interested can read about transaction priorities and how the network sorts them in relation to transaction fees and age by reading the Bitcoin Wiki article on Transaction Fees: https://en.bitcoin.it/wiki/Transaction_Fee

[FairUser]

The backlog is over 1500 transactions now: http://www.bitcoincharts.com/bitcoin/ (5 of them are my bitcoinpool payouts)

It was about 1200 half a day ago, so it's going in the wrong direction...

Yes.  It appears someone is flooding the bitcoin network with hundreds of mini payments, and it's causing this very long delay in anyone getting paid.  Why they're doing this, I don't know.  They don't gain anything from it other than being an asshole and causing everyone to wait.

Patience is required at this point. 
I got about 7.84 btc waiting to be confirmed.

[FairUser]

This is gee & fairusers thread
Don't feed trolls
LMGTFY

This is gee & fairusers thread

bobR, it's rude and confusing to others not get our names correct.
It is "Geebus" and "Fairuser".
Please double check you spelling, punctuation, and grammer before you hit the "post" button.
Thank you.

[FairUser]

PATIENCE PLEASE

1) From the time I go to sleep to the time I wake up, there are generally a couple dozen posts.  I'm more worried about my day job from the time I wake up to the time I get home, so if I don't reply to your post within an hour or six after you post it, please try and keep in mind that running this pool doesn't count as my day job and I'm doing my best to juggle my personal life, work life, and bitcoin life.

2) When over half the new posts on this thread are just flames from the trolls who quotes the entire message from another user, it immediately kicks in my mental BullShit/Troll filter as I try to ignore them.  Sometime's I will miss a valid question or concern because it has 4 posts before and 5 posts after it from the troll.  So if I missed your question, I apologize in advance.  If you're feeling ignored, don't be afraid to PM me.

3) We know that someone is flooding the bitcoin network with transactions.  You will get paid as soon as the network can work through all the transactions.


Thank you for your patience.

[blakel]

Taking a quick glance through http://www.bitcoincharts.com/bitcoin/ it seems the issue is that the 50 BTC gained from the block gets distributed to the miners like this:

1. Pay x BTC to miner 1, 50-x comes back to a pool account.
2. With the change from the payout to miner 1, pay miner 2
3. With the change from miner 2, pay miner 3
4. etc.

So depending on where you are in that chain it could be awhile before all of transactions before you have cleared so that your transaction can clear.

Maybe I am interpreting the information at http://www.bitcoincharts.com/bitcoin/ wrong though?

Isn't it possible to take the 50 BTC and send it to all the miners in one transaction? Then everyone would clear at the same time and there wouldn't be 90 transactions every time the pool solves a block.

[geebus]

Taking a quick glance through http://www.bitcoincharts.com/bitcoin/ it seems the issue is that the 50 BTC gained from the block gets distributed to the miners like this:

1. Pay x BTC to miner 1, 50-x comes back to a pool account.
2. With the change from the payout to miner 1, pay miner 2
3. With the change from miner 2, pay miner 3
4. etc.

So depending on where you are in that chain it could be awhile before all of transactions before you have cleared so that your transaction can clear.

Maybe I am interpreting the information at http://www.bitcoincharts.com/bitcoin/ wrong though?

Isn't it possible to take the 50 BTC and send it to all the miners in one transaction? Then everyone would clear at the same time and there wouldn't be 90 transactions every time the pool solves a block.

There is a way to do so, yes. It involves using a patch applied to the latest Git of Bitcoin (0.3.21) to create the new type of transaction, however, when sending those types of transactions, the only other nodes in the network that can process them correctly are those also running 0.3.21 (If I'm not mistaken).

Presently, we're sending each payment individually.

[demonofelru]

Hello when I run the modified poclbm it crashes every now and then.  It crashed twice since I started a couple hours ago is it ok if I just use the regular miner? My efficiency shouldn't be too bad since it's a 6970.

Edit: The non mod one never crashed BTW.

[geebus]

Hello when I run the modified poclbm it crashes every now and then.  It crashed twice since I started a couple hours ago is it ok if I just use the regular miner? My efficiency shouldn't be too bad since it's a 6970.

Edit: The non mod one never crashed BTW.

It may have crashed when we restarted bitcoind on the server. It's about 1 second of downtime, but if a miner requests a getwork while bitcoind is off, it ends up sending an error back to the miner, and the miner doesn't know how to handle it, so it crashes.

But, as it is stated in our FAQ, it's not required that you use our modified miner, just highly encouraged. 

[demonofelru]

Thanks for the info I'll start the mod miner in the morning that way I can keep an eye on it I'll freeze if it crashes while I'm sleeping it's my heater lol

[FairUser]

Hello when I run the modified poclbm it crashes every now and then.  It crashed twice since I started a couple hours ago is it ok if I just use the regular miner? My efficiency shouldn't be too bad since it's a 6970.

Edit: The non mod one never crashed BTW.

We have heard about this from 1 other user.  It's kinda hit and miss when trying to debug this since the output log from the other user contained no debug information and no errors or execeptions.  Between Geebus and I, we test our miner on Windows 7 32bit and 64bit, Windows XP 32bit, and Ubuntu server 10.04.  If it works for a round on these systems, we then release it publicly.

We sure could use your help to diagnose this problem.  Please include the following information.

• What OS you're using.
• 32 or 64 bit?
• The make and model of your video card.
• How many video cards you are using.
• The make and model of your motherboard.
• The make and model of your CPU.
• The speed of your CPU, the speed of your FSB, and the speed of your memory.
• Please use the "--log" option to get an output log.  This will tell us about what time it crashed, and how long it ran before it crashed.
• Driver version (Catalyst version, or GeForce version)
• AMDAPP SDK or nVidia OpenCL SDK version

Sorry it's not working as expected.  I hope we can track down the bug and get it fixed soon.  We like it when our miners can work 24/7 without a problem.

Thank you for the feedback.

EDIT: Added Geebus's recommendations to this post.

[FairUser]

Thanks for the info I'll start the mod miner in the morning that way I can keep an eye on it I'll freeze if it crashes while I'm sleeping it's my heater lol

Here is the quick fix if you're using windows:

Create a new batch script.  I call mine  "Start Mining.bat"
It should contain the following code.

Code:

@echo off
:BITCOIN
poclbm-mod.exe --user=YOURUSERNAME --pass=YOURPASSWORD -d 0 -f 120 --host bitcoinpool.com --port 8334 --log
GOTO BITCOIN

That will automatically restart poclbm-mod if it crashes.  Hope that helps you until we track down the problem.

[geebus]

*** QUICK UPDATE ***

• Fixed a bug in the payment system to process payments payments for blocks at 120 confirmations instead of 121.
• Changed the system that deactivates accounts to mark an account inactive after 28 days of inactivity, up from 7.

We're still working on fixing payments to reduce the number of transactions and hopefully have them process faster. We'll keep you posted.

[demonofelru]

Hello when I run the modified poclbm it crashes every now and then.  It crashed twice since I started a couple hours ago is it ok if I just use the regular miner? My efficiency shouldn't be too bad since it's a 6970.

Edit: The non mod one never crashed BTW.

We have heard about this from 1 other user.  It's kinda hit and miss when trying to debug this since the output log from the other user contained no debug information and no errors or execeptions.  Between Geebus and I, we test our miner on Windows 7 32bit and 64bit, Windows XP 32bit, and Ubuntu server 10.04.  If it works for a round on these systems, we then release it publicly.

We sure could use your help to diagnose this problem.  Please include the following information.

• What OS you're using.
• 32 or 64 bit?
• The make and model of your video card.
• How many video cards you are using.
• The make and model of your motherboard.
• The make and model of your CPU.
• The speed of your CPU, the speed of your FSB, and the speed of your memory.
• Please use the "--log" option to get an output log.  This will tell us about what time it crashed, and how long it ran before it crashed.
• Driver version (Catalyst version, or GeForce version)
• AMDAPP SDK or nVidia OpenCL SDK version

Sorry it's not working as expected.  I hope we can track down the bug and get it fixed soon.  We like it when our miners can work 24/7 without a problem.

Thank you for the feedback.

EDIT: Added Geebus's recommendations to this post.

Hello I'll get more precise information when I wake am too lazy to get up and double check but I know most so here goes.

OS: Windows 7 Ultimate 64 Bit
GPU: HIS 6950 flashed to 6970 Memory down clocked to about 500 Mhz core up to 970 MHz I believe I upped the volts too I think 1.150 but will double check this. Only one GPU on this rig.
MOBO: Asus P5Q Deluxe don't remember BIOS version the one before last and never flashed the beta UEFI will double check if need be.
CPU: Intel Q9550 stock clocks I believe 2.83 GHz FSB also I believe stock is 333 with 8.5 multiplier would make sense with 2.83
RAM: 4GB G.skill at 1066
Log: I'll try to get when I wake up.
CCC: 11.3 SDK 2.2
Not running from source using regular windows binaries.

Also you didn't ask but my PSU is a coolermaster real power pro it does 1000w sustained and 1200w max my circuit breaker for my room blows at around 1600w I believe so shouldn't be PSU.

Lastly it was weird I called it a crash because it wasn't generating but it still informed me of new blocks it was just a bunch of longpolling new blocks in the CLI it did have an error but I closed it before checking both times.

[nphard]

I have a simple request/question.  I noticed the payment threshold is capped at 1.  Is there a reason for this?  I figured since all the free transactions lately have been a burden on the network and I don't need quick payments I'd set my threshold higher.

[dishwara]

*** QUICK UPDATE ***

• Fixed a bug in the payment system to process payments payments for blocks at 120 confirmations instead of 121.
• Changed the system that deactivates accounts to mark an account inactive after 28 days of inactivity, up from 7.

We're still working on fixing payments to reduce the number of transactions and hopefully have them process faster. We'll keep you posted.

If you really want to fix transaction problem with less fees & less netwrok load, then instead of 0.01-1.0, let the user choose how much he wants to withdraw. I normally put 3 or 5 in other pools, but when tried in yours got error that i choose btw 0.01 -1.0 only.
Also, i am expecting reply for my pm

[slush]

FairUser, my pool (and afaik tycho's too) is accepting sendtomany, so processing of this type transactions is quite fast. I can really recommend it to you, it saves bitcoin network resources a lot. Then it is also reasonable to set up 0.01 fee on it, because payouts are accepted even when network is spammed. Sendmany is able to compress 30 payout transactions into one kB (0.01 fee) so I think it is acceptable.