Pool URL:
https://mining.bitcoinaffiliatenetwork.comSignup at:
https://mining.bitcoinaffiliatenetwork.com/index.php?page=registerBlocks:
https://www.blocktrail.com/BTC/pool/bitaffnetPayment System: PPS + 10% Bonus.
Payment Intervals: 1,2,4,8,12,24 hours.
Merged Mining: Currently NMC (PPS)
A team of us have been actively developing what we consider is technically the most accurate/transparent/profitable pool in existence.
We're transparent. We're accurate. How can we prove that?
Use your miner's statistics... not ours... to determine what your payout should be. Our pool statistics should only be second to yours.
Example:
Step 1...This user is using a 2 TH Prospero X3 kit. Hashrate
2,030GH/s.
![](https://ip.bitcointalk.org/?u=http%3A%2F%2Fzmfiles.com%2Fblackarrow.png&t=665&c=RP8zMTeIJm_O5Q)
Using a difficulty calculator one can determine that this hashing speed should yield: 0.001074 BTC per hour.
(2030 GH/s plugged into
https://bitcoinwisdom.com/bitcoin/difficulty at network difficulty 39603666252)
Step 2...Miner configures their account to pay every 2 hours at our mining pool.
Step 3...Observe payments coming in....
![](https://ip.bitcointalk.org/?u=http%3A%2F%2Fzmfiles.com%2Fhourlypayouts.gif&t=665&c=beR9b4mlKbmljA)
* Note: It's important for us to be able to pay you at exactly the interval you specify plus or minus a few seconds. This reason being is that this makes it easy for you to visually see that you're getting paid what you're supposed to.
Based on expected return of 0.001074 BTC per hour... since this user specified to be paid every 2 hours... the earnings should be 0.002148 BTC. In the image above you can easily see that the payouts performed were very very close.
We also give you the average hash rate (calculated from the shares submitted by your miner) between each payment interval. We do this because it'll allow you to see easily verify that we've been accurately counting/paying the shares you've submitted throughout the entire day.
How do we stack up against other pools?One of our users did a 7 day test comparing our mining pool payouts to the following pools: (Ranked in order of highest paying to lowest paying)
1. BitAffnet
2. Eligius
3. Ghash.io
4. f2pool (discusfish)
5. eclipse
6. BTC Guild
7. Bitcoin.CZ
View here:
http://bluebearnc.com/comparing-mining-pools/So what's there for any miner to risk trying us out? Give us one hour of some of your hash rate and see the numbers for yourself.
You're welcome.
-BitAffNet
Quick glance at some features...We offer a realtime time lapse graph of your workers. It updates every 5 seconds.
![](https://ip.bitcointalk.org/?u=http%3A%2F%2Fzmfiles.com%2Fmyhashrate.png&t=665&c=4m8fu0Bqmwg61w)
We have a very accurate work information box that also updates every 5 seconds.
![](https://ip.bitcointalk.org/?u=http%3A%2F%2Fzmfiles.com%2Fworkerinformation.png&t=665&c=-NiwOEGTqqsU5g)
Round progress... I know we've grown tired of looking at a simple % indicator for indicating progress so we're now showing the top difficulty shares submitted in the current round thus far...
![](https://ip.bitcointalk.org/?u=http%3A%2F%2Fzmfiles.com%2Ftopshares.png&t=665&c=Wy15UYdvz5KWUw)
And a quick payment information summary box...
Our global stratum network...New! Stratum geo server. It automatically selects the closest server to your location.stratum+tcp://geo.bitcoindigger.com:3333
stratum+tcp://geo2.bitcoindigger.com:3333
See our geo stratum dns resolution work here:
https://www.whatsmydns.net/#A/geo.bitcoindigger.comNew! Port selectionPort 3333 for vardiff (default)
Port 3334 for maximum 512 difficulty (for slow miners < 750 GH/s)
Port 3335 for fixed 2048 difficulty (recommended for S4 and Dragon miners)
Port 3336 for fixed 8192 difficulty (future use)
* Special: shanghai.bitcoindigger.com:80 is open for miners in China having firewall problems.
Use one of the following servers if the geo server doesn't work for you or as a backup.
stratum+tcp://west1.bitcoindigger.com:3333 (Phoenix)
stratum+tcp://west2.bitcoindigger.com:3333 (Northern California)
stratum+tcp://sanfrancisco.bitcoindigger.com:3333 (San Francisco)
stratum+tcp://fremont.bitcoindigger.com:3333 (Fremont, CA)
stratum+tcp://dallas.bitcoindigger.com:3333 (Dallas, TX)
stratum+tcp://chicago.bitcoindigger.com:3333 (Chicago, Illinois)
stratum+tcp://georgia.bitcoindigger.com:3333 (Atlanta, Georgia)
stratum+tcp://east1.bitcoindigger.com:3333 (Virginia)
stratum+tcp://east2.bitcoindigger.com:3333 (New York, NY)
stratum+tcp://newjersey.bitcoindigger.com:3333 (New Jersey, NJ)
stratum+tcp://nyiix.bitcoindigger.com:3333 (IX, Telehouse - New York)
stratum+tcp://nyiix2.bitcoindigger.com:3333 (IX, Telehouse - New York)
stratum+tcp://miami.bitcoindigger.com:3333 (Miami, Florida)
stratum+tcp://ireland.bitcoindigger.com:3333 (Ireland)
stratum+tcp://london.bitcoindigger.com:3333 (UK)
stratum+tcp://paris.bitcoindigger.com:3333 (Paris, France)
stratum+tcp://amsterdam.bitcoindigger.com:3333 (Netherlands)
stratum+tcp://amsterdam2.bitcoindigger.com:3333 (Netherlands)
stratum+tcp://shanghai.bitcoindigger.com:3333 (Shanghai, CN)
stratum+tcp://tokyo.bitcoindigger.com:3333 (Tokyo, JP)
stratum+tcp://tokyo2.bitcoindigger.com:3333 (Tokyo, JP 2nd DC)
stratum+tcp://sydney.bitcoindigger.com:3333 (Sydney, AU)
stratum+tcp://sydney2.bitcoindigger.com:3333 (Sydney, AU 2nd DC)
stratum+tcp://singapore.bitcoindigger.com:3333 (Singapore)
stratum+tcp://singapore2.bitcoindigger.com:3333 (Singapore, 2nd DC)
stratum+tcp://saopaulo.bitcoindigger.com:3333 (Sao Paulo, Brazil)