Bitcoin Forum
September 22, 2020, 11:26:37 PM *
News: Latest Bitcoin Core release: 0.20.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1]
1  Bitcoin / Bitcoin Discussion / Who will join us today for SOPA Blackout? on: January 18, 2012, 10:45:03 AM
I am amazed at how few sites in the bitcoin community are not supporting the blackout today.  I just visited most of the other pools and several bitcoin blog sites, and it seems only BitcoinPool is supporting the SOPA blackout. We would like to encourage other pools or bitcoin related sites to join us in doing so.

We think it boils down to this: If they get the equipment in place and legislation passed then what will stop them from censoring port 8333 instead of port 53?  A few thousand angry bitcoin users?

BitcoinPool is not doing a complete blackout, but every page on the site will have a blackout overlay until you click on it.
2  Bitcoin / Pools / ** BitcoinPool.com back online after DDoS attack ** on: June 29, 2011, 11:56:51 PM
As many of our user's have noticed service has been less than good the last few days.  This was caused by a DDoS attack.  We have managed to get control of the situation by notifying hosting providers and blocked several thousand IP addresses in several dozen class C networks.

The main Russian ISP that the attacks were coming from is Yandex LLC.  When we blocked the attackers IP address or an entire class C network, within minutes the attacker would be using a different address in a completely different class C network.  After doing this song and dance for several hours, we realized that it was mostly coming from Yandex and sent off an e-mail to their abuse address.  We haven't received a response from them, so we took drastic action and blocked every IP address owned by Yandex.  After blocking Yandex, everything seems to have returned to normal.  If you are a user in our pool coming from this network, please PM me your IP address and I will white-list it.

We'd like to apologize to our users for the inconvenience of this attack.  We're keeping a close eye on logs and traffic analyzers to monitor for any new attacks so we can block them before they disrupt the pool any further. 

Thank you for your understanding and tolerance for the situation, we appreciate it.

Best Regards Smiley

3  Other / Meta / Why do some pools get pinned and others don't? on: June 12, 2011, 10:43:24 AM
Why do some pools get the pleasure of being pinned to the top of this thread and others don't?
4  Bitcoin / Development & Technical Discussion / Block confirmed after only 104 blocks later, not 120. on: June 11, 2011, 04:21:27 AM
Start here:  http://blockexplorer.com/b/129803
Follow the address it was paid to:  1LdrTWcXu5qYvEggB6PodEs2proXrQMNLs
I'm going to copy and paste this, so sorry if the formatting is off.

Transaction?   Block?   
5a91af17b3...   Block 129803 (2011-06-10 11:12:25)
21a9a054a0...   Block 129907 (2011-06-10 23:32:50)   

How did a block get confirmed after just 104 blocks?  Shouldn't this be 120 blocks like the blocks before and after it?

Now to make this even more strange/frustrating, our pool (bitcoinpool) had a block ( 129806 ) go orphaned *after* we paid out on it 120 blocks later.  Our code explicitly checks to make sure the block is valid AND confirmed before we pay out, and it was paid out BEFORE it went orphaned. Then about 2 blocks after it was confirmed, it changed to Orphaned.

Here's a dump from our 'listgenerated' from bitcoind.
[
    {
        "account" : "",
        "category" : "generate",
        "amount" : 50.04000000,
        "confirmations" : 239,
        "block_hash" : "00000000000012fbcf784971681c91eac50040480aa1525f8548d1ac6d4a06bd",
        "block_index" : 0,
        "txid" : "a445379234a83536814f8196388b295792696b79dcf8920aafd3664edf220df8",
        "time" : 1307676121
    },
    {
        "account" : "",
        "category" : "orphan",
        "amount" : 50.11351319,
        "confirmations" : 0, <-- Should be 140
        "txid" : "7db5b5e710fcad4957cc1d498bf008bea27b8ded618a9f74eab9f91c9799f505",
        "time" : 1307705806
    },
    {
        "account" : "",
        "category" : "immature",
        "amount" : 50.12306040,
        "confirmations" : 72,
        "block_hash" : "0000000000000d5d50045d8e321b7d97f988f497b80fb1fa4ca98e9725bcdab3",
        "block_index" : 0,
        "txid" : "a53a442e87a53cd06e6298b055da89b7b59716ccfa23aba29c47ff22365bc84e",
        "time" : 1307733695
    },
    {
        "account" : "",
        "category" : "immature",
        "amount" : 50.26881957,
        "confirmations" : 36,
        "block_hash" : "0000000000000d74bcd54e04d45e2750af8e3700e2b6f9daa42f1a6498d331db",
        "block_index" : 0,
        "txid" : "f9ffe4f638a3c08523357351088bc8d5d260000c76305db4c4ccefa6fb09add8",
        "time" : 1307750373
    }
]

The TX ID:  7db5b5e710fcad4957cc1d498bf008bea27b8ded618a9f74eab9f91c9799f505  doesn't exist in block explorer.

So here's the questions I'd appreciate an answer to are:

1) How does a block get "confirmed" after only 104 blocks?
2) How does a block go "orphaned" after it's been "confirmed" (meaning, it reached 120 blocks then went "orphaned" shortly after that)?
3) Are these signs that something strange is happening in the block chain, and if so, could it be someone else doing this on purpose?


Thank you in advance for any good explanation.

5  Bitcoin / Pools / MAJOR UPGRADE @ BitcoinPool.com ~ No Fees ~ Are you still paying to be a miner? on: June 09, 2011, 06:37:20 PM
We've been working hard to bring you a much more friendly web site, more features, and a overall better Bitcoin Pool.

After several sleepless nights, we got the entire infrastructure of BitcoinPool.com upgraded.  Users can now have separate passwords for their miners and accounts.  You can set up different types of notification for when your miner dies or gets below a specified speed.  The overall service is running amazing fast now compared to what it was before.  We broken each part of the pool processes into it's own server, and connected EVERYTHING with 1Gbps Ethernet.  We got a NEW 50/50Mbps FIBER LINE activated, so there is a plenty of bandwidth available.  All the infrastructure now has battery backups for all the servers, monitor, and the network switch.  Everything could run for about 30-40 minutes if the power goes out.  The Fiber Optic connection has about a 4 hour backup battery too.  So *if* we we're to have a short power outage, we should be alright.

Here's a break down of what we are now using for the pool.  Some things have changes from what we originally planned, but it's all good.
=========================================================================
++ SERVER: MySQL ++
Dell 1950 1U Server
2 x Intel® Xeon® Processor E5405 (12M Cache, 2.00 GHz, 1333 MHz FSB) Quad-core processors
8 x 2GB DDR2 (16GB)
2 x 1Gbps NICs
2 x 250GB 7.2K RPM drives in a RAID 0 configuration
2 x 670 PSU for power redundancy

++ SERVER: Pool daemon (for miners) ++
Dell 1950 1U Server
2 x Intel® Xeon® Processor E5405 (12M Cache, 2.00 GHz, 1333 MHz FSB) Quad-core processors
8 x 1GB DDR2 (8GB)
2 x 1Gbps NICs
2 x 250GB 7.2K RPM drives in a RAID 0 configuration
2 x 670 PSU for power redundancy

++ SERVER: Website / Forum ++
Dell  1750 1U Server
2 x Intel® Xeon® Processor
8 x 1GB DDR2 (8GB)
2 x 1Gbps NICs
2 x 250GB 7.2K RPM drives in a RAID 0 configuration
2 x 670 PSU for power redundancy

++ SERVER: NAS Backup ++
2TB Seagate w/ 1Gbps NIC

++ NETWORK: Switch ++
HP ProCurve 48 Port Gigabit Switch

++ POWER: Battery Backups ++
2 x CyberPower AVR UPS Battery Backup. Each supports up to 900Watts.
1 x APC 1300 XS
 
++ POWER: Management ++
1 x APC Rack PDU Metered 1U, 120V, 20A
=========================================================================

PICS

The old server.  Yeah, not that impressive.


The NEW SERVERS!






A view from the back side of the 42U


Both of the 42U Racks.  My roommates is on the left, mine is on the right.


It was already installed, we just needed to get it activate.  Yes, this is FIBER OPTIC run to the home, on a business account.  The servers are about 30ft of Cat5e away from this box.


And of course we need a speedtest.  I couldn't find any servers that would max out the line, but this is the best I could find. Smiley


Geebus working...


Myself working...


So that just about sums it up.  The servers are doing very well so far.  We hope you appreciate all the effort and lack of sleep we've put into getting things up to speed.  We're still doing some code updates here and there, and plan on releasing a few more tools on the site as well in the up coming days.  We'd also like to say a special THANK YOU to coderman for his help with tuning the DB to being able to handle several million records at any given moment.  

Stop on by and check it out.


HAPPY MINING!   Grin

- Bitcoin Pool Staff
6  Bitcoin / Mining / BitcoinPool.com is back Online! on: June 02, 2011, 08:03:41 PM
BitcoinPool.com had a service interruption this morning that has since been resolved. 
The pool is back online.  We apologize for any inconvenience this may have caused.

7  Bitcoin / Mining / [NEW POOL & MINER] - BitcoinPool.com - Jump In! ~NO FEES~ :) on: March 08, 2011, 12:03:41 PM
We are proud to announce a new bitcoin mining pool has opened: http://bitcoinpool.com

Please feel FREE to join the pool.  http://bitcoinpool.com/newuser.php

Our official forums where questions can be asked is at:
http://www.bitcoinpool.com/forum/

Our pool pays miner for the percentage of work done based on;
(the number of shares your miner has contributed) divided by (total number of shares in the round) times 50. Our server is now in Beta, payout functionality has been fully tested and debugged these last two weeks.  Additional features will be appearing in the next few weeks as the pool grows in popularity.

This pool does not support the “pay-per-share” method (bitpenny's pool) or “weight based shares" (slush's pool) which favors faster cards and devalue's shares over time after they've been solved.  

Now let's cover some of the finer points of the bitcoin pool.

- WE DO NOT FORCE DONATIONS OR TAKE A PERCENTAGE OF THE PAYOUTS.  WE DO NOT REQUIRED ANY SIGNUP FEES OR ANY OTHER FORMS OF FORCED PAYMENTS.  We do encourage and are thankful for any donations we receive.  Our donation address is:   1AMnDUgnZTZJUcSR5Eevt6PnxWLmdq75Zn

- We have set a maximum number of users to 2000.  We will be able to increase this number if a majority of the miners on our server are mining with our efficient bitcoin miner.

- The solved block is equally paid out to all those who contributed in the round.  

- Anti-fraud protection.  We only accept shares from the current block, in the current round.

- Anti-flood protection.  Our server ensures that user's are not making an excessive number of useless requests to our server, and bans them by account and IP address in the event abuse is detected.

- We show the stats of all users in the pool because we believe in being transparent.  By showing all the stats of each users, everyone can determine for themselves if something is not right (like the server operator taking bitcoin's off the top).  

- We are the only bitcoin pool that shows the efficiency of the bitcoin miners.  This is VERY important because we can now see which miner's are causing an excessive load on the server.  If this is a problem for you, please update your miner to our modified version of m0mchill's miner that is MUCH more efficient.

- We are the only bitcoin pool that has released a modified version of a bitcoin miner (m0mchill's) that can achieve 100% efficiency.  The more efficient each user is, the more users we can support on the server, and that means we will find more blocks at a faster rate for the pool.

- The listed shares and efficiency of each user is reset at the beginning of the next round.

- You can use multiple miner's on a single account, however you will not be able to see the individual stats of each miner if you choose to do so.


MINING EFFICIENTLY

For the sake of understanding what we mean by “Efficiency”, let us define it for you.
EFFiciency = (The number of submitted shares) / (The number of requested getworks) * 100.

   Geebus and I raised a very important question in m0mchill's thread, and that question was “why doesn't the miner work through all (2^32 or) 4,294,967,296 hashes?”  The answer we got was not a satisfactory or a legitimate response to the original question, and we objected with real stats showing that decreasing your askrate for getwork request does NOT increase the probability that you will find a share or answer quicker.  In fact, you can find more than 1 answer/share per getwork, and that simply requesting a new getwork every 10 or 20 seconds is not the best route to finding shares.

The bottom line from our research was this:
- The same number of shares can be found in a 10 hour period using a askrate of 10 seconds OR our more efficient miner.  You will get about the same number of shares either way.

- Because the same number of shares are found in a given period, there is no reason why people should be using a decreased askrate.  The goal is to look for bitcoin's more efficiently, and when the miner's efficiency is closer to 100%, the amount of resources and bandwidth on the server is DRAMATICALLY reduced, and that means we can support MORE USERS.

- More user's means we as a pool can find blocks faster!

In order to make this happen, we had to make some changes to m0mchill's miner.  We now use what is referred to as a “variable askrate”, which means that the miner looks at the average speed of your card as it processed the previous getwork, and adjusts the askrate so your card will search the entire getwork for any possible answers.  In addition to being more efficient, we also show the current getwork you're working on, how much of that getwork has been processed, your efficiency, the percentage of invalid/stale shares, and the percentage of empty getworks.

Here's a screen shot of our miner, and as you can see it's a bit different than m0mchill's original miner.



If you would like to see the efficiency of your existing miner, then join our pool and run your miner for a couple of hours to see how efficient it really is.  When you're ready to get a more efficient miner, you can download our miner and watch your efficiency rise dramatically.  For all those who said we didn't know what we were talking about, you would be well advised to try this miner before making anymore comments.  We spent months working on the code of m0mchill's miner, countless hours of testing and statistical analysis, and it is by far the most efficient miner out right now.  But why should you believe us, just because we said so?  No, you should try it yourself and compare it to your existing miner, then make up your own mind about whether or not this is a more efficient miner.

You can download our modified miner from:  http://bitcoinpool.com
You can sign up for a new account at:  http://bitcoinpool.com/newuser.php
Additional Frequently Asked Questions can be found at:  http://bitcoinpool.com/faq.php

Please feel free to ask any questions you may have.  We will do our best to answer your questions.  
We are excited to launch this new pool and invite everyone to come jump in with us.  

We look forward to seeing you all in the pool,

Fairuser & Geebus
8  Bitcoin / Mining / Mining inefficiency due to discarded work on: January 30, 2011, 11:32:43 PM
I keep seeing these "invalid or stale" a couple of times a day.

30/01/2011 15:26, bea41297, accepted
30/01/2011 15:26, bea41297, invalid or stale
30/01/2011 15:27, b9c26c57, accepted
30/01/2011 15:27, fb27e19a, invalid or stale

Notice the two lines at the top in bold.  
Could there possibly be more than one answer per getwork?
As you can see, I got the answer previously, then got the same answer again.
Then on the last line, it just came back invalid...probably cause someone else got the answer to the getwork before I did.

Is every getwork unique?  If so, how did I get the same answer twice?

UPDATE:  Got two more
30/01/2011 15:30, e67d85ec, invalid or stale
30/01/2011 15:36, f1f124d9, invalid or stale
Pages: [1]
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!