Bitcoin Forum
December 11, 2016, 08:30:58 AM *
News: To be able to use the next phase of the beta forum software, please ensure that your email address is correct/functional.
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 [437] 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 ... 744 »
  Print  
Author Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool  (Read 2035622 times)
PatMan
Hero Member
*****
Offline Offline

Activity: 924


Watch out for the "Neg-Rep-Dogie-Police".....


View Profile WWW
May 27, 2014, 11:25:55 PM
 #8721

Anyone have any definitive thoughts on how to get S2s working with p2pool at full capacity?  I can't justify losing 10% of my hashpower to use p2pool.

M

I got one arriving tomorrow - I'll let you know how I get on, but 10% is too much to lose for sure - especially at the price of them  Wink

"When one person is deluded it is called insanity - when many people are deluded it is called religion" - Robert M. Pirsig.  I don't want your coins, I want change.
Amazon UK BTC payment service - https://bitcointalk.org/index.php?topic=301229.0 - with FREE delivery!
http://www.ae911truth.org/ - http://rethink911.org/ - http://rememberbuilding7.org/
1481445058
Hero Member
*
Offline Offline

Posts: 1481445058

View Profile Personal Message (Offline)

Ignore
1481445058
Reply with quote  #2

1481445058
Report to moderator
1481445058
Hero Member
*
Offline Offline

Posts: 1481445058

View Profile Personal Message (Offline)

Ignore
1481445058
Reply with quote  #2

1481445058
Report to moderator
1481445058
Hero Member
*
Offline Offline

Posts: 1481445058

View Profile Personal Message (Offline)

Ignore
1481445058
Reply with quote  #2

1481445058
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1481445058
Hero Member
*
Offline Offline

Posts: 1481445058

View Profile Personal Message (Offline)

Ignore
1481445058
Reply with quote  #2

1481445058
Report to moderator
mdude77
Legendary
*
Offline Offline

Activity: 1358


View Profile
May 28, 2014, 12:43:14 AM
 #8722

Anyone have any definitive thoughts on how to get S2s working with p2pool at full capacity?  I can't justify losing 10% of my hashpower to use p2pool.

M

I got one arriving tomorrow - I'll let you know how I get on, but 10% is too much to lose for sure - especially at the price of them  Wink

I've got two S2s.  Both behave the same way.  Within minutes of pointing at a p2pool node, the hash rate drops to about 930gh/s or less. Sad

M

MMinerMonitor author, monitor/auto/schedule reboots/alerts/remote/MobileMiner for Ants and Spondoolies! Latest (5.2). MPoolMonitor author, monitor stats/workers for most pools, global BTC stats (current/nxt diff/USD val/hashrate/calc)! Latest (v4.2) 
Buyer beware of Bitmain hardware and services.
windpath
Legendary
*
Offline Offline

Activity: 938


View Profile WWW
May 28, 2014, 01:04:39 AM
 #8723

Anyone have any definitive thoughts on how to get S2s working with p2pool at full capacity?  I can't justify losing 10% of my hashpower to use p2pool.

M

I got one arriving tomorrow - I'll let you know how I get on, but 10% is too much to lose for sure - especially at the price of them  Wink

I've got two S2s.  Both behave the same way.  Within minutes of pointing at a p2pool node, the hash rate drops to about 930gh/s or less. Sad

M

Hey mdude...

I know you pretty knowledgeable, but figured I'd give you my run through:

1. I'm not sure if your node is local to your miners, whats your latency?
2. Set your pseudo share difficulty
3. give it some time? looking at your graphs I don't see a consecutive length of time of ~1TH/s hashing, and I do see good effiency and a decent share count, it will take some time to accurately represent your estimated payout, 3-4 days of consistent mining to get some shares in and see where your at...

Other than that, I peeked at the graphs on your node and everything else seems within regular parameters...

mdude77
Legendary
*
Offline Offline

Activity: 1358


View Profile
May 28, 2014, 01:10:58 AM
 #8724

Anyone have any definitive thoughts on how to get S2s working with p2pool at full capacity?  I can't justify losing 10% of my hashpower to use p2pool.

M

I got one arriving tomorrow - I'll let you know how I get on, but 10% is too much to lose for sure - especially at the price of them  Wink

I've got two S2s.  Both behave the same way.  Within minutes of pointing at a p2pool node, the hash rate drops to about 930gh/s or less. Sad

M

Hey mdude...

I know you pretty knowledgeable, but figured I'd give you my run through:

1. I'm not sure if your node is local to your miners, whats your latency?
2. Set your pseudo share difficulty
3. give it some time? looking at your graphs I don't see a consecutive length of time of ~1TH/s hashing, and I do see good effiency and a decent share count, it will take some time to accurately represent your estimated payout, 3-4 days of consistent mining to get some shares in and see where your at...

Other than that, I peeked at the graphs on your node and everything else seems within regular parameters...

1 - I've observed this running locally, across the country (my public node), and at least one other node that's close by.
2 - I've tried setting pseudo share difficulty as high as possible, which is apparently 1k.
3 - I stopped running at p2pool a while ago because of this problem.  Before that I tried different things over a period of close to a week before I gave up.

M

MMinerMonitor author, monitor/auto/schedule reboots/alerts/remote/MobileMiner for Ants and Spondoolies! Latest (5.2). MPoolMonitor author, monitor stats/workers for most pools, global BTC stats (current/nxt diff/USD val/hashrate/calc)! Latest (v4.2) 
Buyer beware of Bitmain hardware and services.
windpath
Legendary
*
Offline Offline

Activity: 938


View Profile WWW
May 28, 2014, 02:12:50 AM
 #8725

Anyone have any definitive thoughts on how to get S2s working with p2pool at full capacity?  I can't justify losing 10% of my hashpower to use p2pool.

M

I got one arriving tomorrow - I'll let you know how I get on, but 10% is too much to lose for sure - especially at the price of them  Wink

I've got two S2s.  Both behave the same way.  Within minutes of pointing at a p2pool node, the hash rate drops to about 930gh/s or less. Sad

M

Hey mdude...

I know you pretty knowledgeable, but figured I'd give you my run through:

1. I'm not sure if your node is local to your miners, whats your latency?
2. Set your pseudo share difficulty
3. give it some time? looking at your graphs I don't see a consecutive length of time of ~1TH/s hashing, and I do see good effiency and a decent share count, it will take some time to accurately represent your estimated payout, 3-4 days of consistent mining to get some shares in and see where your at...

Other than that, I peeked at the graphs on your node and everything else seems within regular parameters...

1 - I've observed this running locally, across the country (my public node), and at least one other node that's close by.
2 - I've tried setting pseudo share difficulty as high as possible, which is apparently 1k.
3 - I stopped running at p2pool a while ago because of this problem.  Before that I tried different things over a period of close to a week before I gave up.

M
It's strange... maybe our friends at Bitmain played with the CGMiner code some more and created an unintentional glitch?

All my S1's report accurately, don't have an S2 to play with...



jonnybravo0311
Legendary
*
Offline Offline

Activity: 1008


Mine at Jonny's Pool


View Profile WWW
May 28, 2014, 03:41:44 AM
 #8726

It would be nice to hear from others with S2s on p2pool to find out if the same loss of hash rate occurs for them as well.  Unfortunately, I don't have one to test, either.  I will, however, have an SP-10 delivered tomorrow - which unfortunately won't be hashing until Saturday evening because I'm on the other freaking side of the planet.  I will definitely be trying it out on p2pool, Eligius, BTCGuild and GHash.io to see if there are any significant differences in hash rate.

Anyone with S2s running on p2pool?

Jonny's Pool - Mine with us and help us grow!  Support a pool that supports Bitcoin, not a hardware manufacturer's pockets!  No SPV cheats.  No empty blocks.
-ck
Moderator
Legendary
*
Offline Offline

Activity: 2002


Ruu \o/


View Profile WWW
May 28, 2014, 03:45:52 AM
 #8727

Kano has an S2 now and is working on official code for cgminer that hopefully will rectify the behaviour of the driver they included with it.

Primary developer/maintainer for cgminer and ckpool/ckproxy.
Pooled mine at kano.is, solo mine at solo.ckpool.org
-ck
-ck
Moderator
Legendary
*
Offline Offline

Activity: 2002


Ruu \o/


View Profile WWW
May 28, 2014, 03:47:33 AM
 #8728

Is it just me or did the p2pool hash rate just double to almost 1ph/s?!
Last time it did a big jump like that it was the attack that was redirecting people's hashes from other pools to their own p2pool node.

Primary developer/maintainer for cgminer and ckpool/ckproxy.
Pooled mine at kano.is, solo mine at solo.ckpool.org
-ck
jonnybravo0311
Legendary
*
Offline Offline

Activity: 1008


Mine at Jonny's Pool


View Profile WWW
May 28, 2014, 04:39:46 AM
 #8729

Kano has an S2 now and is working on official code for cgminer that hopefully will rectify the behaviour of the driver they included with it.

Good news for S2 owners.

Jonny's Pool - Mine with us and help us grow!  Support a pool that supports Bitcoin, not a hardware manufacturer's pockets!  No SPV cheats.  No empty blocks.
ceslick
Full Member
***
Offline Offline

Activity: 161

digging in the bits... now ant powered!


View Profile WWW
May 28, 2014, 08:36:54 AM
 #8730


Hi,

Tried this, didn't work Sad

Managed to get it working by reinstalling twisted and zope a few times... Also forced python version to 2.7

Lets see how it goes

Will test a while

I did notice one error at one stage where it said it lost connection to bitcoind for 1.5 minutes. Any ideas?



Tried purging those and re installing them

Same result...

Twisted version 13.0.0-1 is installed

cd to folder where you have p2pool

cd /p2pool

./configure

make -j12

should do it

Replace ubuntu with Gentoo Smiley

http://www.integratedideas.net  - Home of Rock Solid Miners
NZ Based BTC P2Pool: http://www.integratedideas.net/p2pool-btc/  -  NZ Based DOGE P2Pool: http://www.integratedideas.net/p2pool-doge/
Cloud mining with CEX.IO: https://cex.io/r/2/ceslicknz/0/
PatMan
Hero Member
*****
Offline Offline

Activity: 924


Watch out for the "Neg-Rep-Dogie-Police".....


View Profile WWW
May 28, 2014, 10:03:18 AM
 #8731

Kano has an S2 now and is working on official code for cgminer that hopefully will rectify the behaviour of the driver they included with it.

This is good news! Kano done a great job with the S1 miner tweaks - I use it on all my S1's with excellent results.

I will gladly donate to the development of an S2 equivalent - suggest everyone else do the same  Wink

Peace.

"When one person is deluded it is called insanity - when many people are deluded it is called religion" - Robert M. Pirsig.  I don't want your coins, I want change.
Amazon UK BTC payment service - https://bitcointalk.org/index.php?topic=301229.0 - with FREE delivery!
http://www.ae911truth.org/ - http://rethink911.org/ - http://rememberbuilding7.org/
norgan
Sr. Member
****
Offline Offline

Activity: 308

Decentralize your hashing - p2pool - Norgz Pool


View Profile WWW
May 28, 2014, 10:09:04 AM
 #8732

Kano has an S2 now and is working on official code for cgminer that hopefully will rectify the behaviour of the driver they included with it.

This is good news! Kano done a great job with the S1 miner tweaks - I use it on all my S1's with excellent results.

I will gladly donate to the development of an S2 equivalent - suggest everyone else do the same  Wink

Peace.

whats the S1 miner tweaks he has done?

Miner, tech geek, operator of NorgzPool - Sydney Australia P2Pool Node creator of p2pool fancy front end

Tips: 1NorganBbymShTN2MMpfGzRYJF8mcPeXjv Exchange BTC locally in Australia or Donate to p2pool miners
jedimstr
Hero Member
*****
Offline Offline

Activity: 784



View Profile
May 28, 2014, 10:19:35 AM
 #8733

Kano has an S2 now and is working on official code for cgminer that hopefully will rectify the behaviour of the driver they included with it.

This is good news! Kano done a great job with the S1 miner tweaks - I use it on all my S1's with excellent results.

I will gladly donate to the development of an S2 equivalent - suggest everyone else do the same  Wink

Peace.

whats the S1 miner tweaks he has done?

Replacement updated version of CGMiner for the S1:
https://github.com/kanoi/cgminer-binaries/tree/master/AntS1

norgan
Sr. Member
****
Offline Offline

Activity: 308

Decentralize your hashing - p2pool - Norgz Pool


View Profile WWW
May 28, 2014, 10:42:08 AM
 #8734

Kano has an S2 now and is working on official code for cgminer that hopefully will rectify the behaviour of the driver they included with it.

This is good news! Kano done a great job with the S1 miner tweaks - I use it on all my S1's with excellent results.

I will gladly donate to the development of an S2 equivalent - suggest everyone else do the same  Wink

Peace.

whats the S1 miner tweaks he has done?

Replacement updated version of CGMiner for the S1:
https://github.com/kanoi/cgminer-binaries/tree/master/AntS1

awesome thanks!

Miner, tech geek, operator of NorgzPool - Sydney Australia P2Pool Node creator of p2pool fancy front end

Tips: 1NorganBbymShTN2MMpfGzRYJF8mcPeXjv Exchange BTC locally in Australia or Donate to p2pool miners
gigabitfx
Newbie
*
Offline Offline

Activity: 9


View Profile
May 28, 2014, 12:56:45 PM
 #8735

Hi Windpath, thanks for the info here, im running some s1 and was having hard time with google on a definitive response to setting the pseudo share.

couple of questions
1. is 0.00000116 a static constant, or based off dynamic number?  Wondering if i need to redo the math periodically to keep my miners running efficiently.
2. do you know of any downsides to restarting p2pool, i noticed i lost a few shares once i had done so, but technically i dont understand why that would be.  i did however update the -a payout address, perhaps that restages the pool?
3. "expected time to share" seems to stay around 7-12hrs, im assuming its because the pool doesn't have any stats to work off of yet?
4. "payout if a block were found NOW" seems to remain at 0, any tips on that?
5. know of any p2pool advanced docs/manuals out there?

Thanks for any info

Is it just me or did the p2pool hash rate just double to almost 1ph/s?!
I'm showing 682TH/s on my node, a nice jump....

If you have some new miners hitting your node you may want to set your share diff and pseudo share diff on your miner....

Code:
bitcoin_address/<share>+<pseudo_share>

If your running S1's set <share> to 0 ("0" defaults to lowest p2pool diff, currently 1677854.73)

And <pseudo_share> to 220.4 (optimized for 190GH/s)

<pseudo_share> is calculated as your hash rate in KH/s times 0.00000116

i.e. 190,000,000 * 0.00000116 = 220.4

Here is an example for an ant S1:

Code:
19vXrwKGUhK4cCU8tA4kWZgbChcmh9a6qj/0+220.4

If you have a hash rate over 1TH/s you might consider upping your share diff to something higher then the p2pool minimum to reduce network traffic and increase the value of your shares...
[/quote]
windpath
Legendary
*
Offline Offline

Activity: 938


View Profile WWW
May 28, 2014, 01:43:55 PM
 #8736

Hi Windpath, thanks for the info here, im running some s1 and was having hard time with google on a definitive response to setting the pseudo share.

couple of questions
1. is 0.00000116 a static constant, or based off dynamic number?  Wondering if i need to redo the math periodically to keep my miners running efficiently.
2. do you know of any downsides to restarting p2pool, i noticed i lost a few shares once i had done so, but technically i dont understand why that would be.  i did however update the -a payout address, perhaps that restages the pool?
3. "expected time to share" seems to stay around 7-12hrs, im assuming its because the pool doesn't have any stats to work off of yet?
4. "payout if a block were found NOW" seems to remain at 0, any tips on that?
5. know of any p2pool advanced docs/manuals out there?

Thanks for any info

Hi Gigabit,

I'm by no means the expert, still studying the code and learning, but I'll give you my best advice and if I'm wrong, or there is a better solution hopefully someone will jump in...

1. It's constant.
2. Restarting will dump all your peers, and re-start many of the stats. Accepted shares will not be lost during a restart, but will not show on your stats page after, obviously shares submitted during a restart will be lost or stale by the time your node is back up. I try to limit restarts as much as possible.
3. Expected time to share is based on your ~estimated~ hash rate, is subject to your miners luck/variance, and can vary greatly.
4. Once you get some shares in the current block this will change, also subject to variance, some days will be higher and some lower.
5. I don't. There are some good tutorials for getting it up and running efficiently here on the forum, and on some alt-coin forums, but no definitive docs that I have found...

Here is an example of the variance/luck, the bottom 2 miners have both been consistently mining on p2pool, the bottom one is currently in a streak of good luck, while the middle one is in a streak of what I'd call less then ideal luck...



It all balances out over time, a key to successfully mining on p2pool is having the patience and consistency to stick with it until it does Wink

mdude77
Legendary
*
Offline Offline

Activity: 1358


View Profile
May 28, 2014, 02:58:28 PM
 #8737

Hi Windpath, thanks for the info here, im running some s1 and was having hard time with google on a definitive response to setting the pseudo share.

In case you missed it, make sure you update your S1 with the cgminer patch for p2pool.

https://github.com/kanoi/cgminer-binaries/tree/master/AntS1

M

MMinerMonitor author, monitor/auto/schedule reboots/alerts/remote/MobileMiner for Ants and Spondoolies! Latest (5.2). MPoolMonitor author, monitor stats/workers for most pools, global BTC stats (current/nxt diff/USD val/hashrate/calc)! Latest (v4.2) 
Buyer beware of Bitmain hardware and services.
gigabitfx
Newbie
*
Offline Offline

Activity: 9


View Profile
May 28, 2014, 04:13:52 PM
 #8738

Can you share that frontend your using?  Im used to mining on slush's pool so I understand a little about variance.  mdude77 I do indeed have new cgminer for s1.

Im still confused about the data on the homepage and if my data is normal for a newly configured p2pool, or if i need to look further into it.  Here is the stats listed
http://s2.postimg.org/lh6uy5iqx/Capture.jpg

Is the "expected time to share" normal for my node uptime?  Ive seen others that show it down to an hour with similar pool speed as mine.  I suppose most of my confusion is that with slushs pool i see shares coming in from my miners much more frequently than this and of course they state the average btc for current round as well.  I feel im flying more blind with p2pool, especially with 0 as expected payout.  The vanilla p2pool interface showed an expected payout number, even when pool was freshly fired up and went up/down as data came through.





Hi Gigabit,

I'm by no means the expert, still studying the code and learning, but I'll give you my best advice and if I'm wrong, or there is a better solution hopefully someone will jump in...

1. It's constant.
2. Restarting will dump all your peers, and re-start many of the stats. Accepted shares will not be lost during a restart, but will not show on your stats page after, obviously shares submitted during a restart will be lost or stale by the time your node is back up. I try to limit restarts as much as possible.
3. Expected time to share is based on your ~estimated~ hash rate, is subject to your miners luck/variance, and can vary greatly.
4. Once you get some shares in the current block this will change, also subject to variance, some days will be higher and some lower.
5. I don't. There are some good tutorials for getting it up and running efficiently here on the forum, and on some alt-coin forums, but no definitive docs that I have found...

Here is an example of the variance/luck, the bottom 2 miners have both been consistently mining on p2pool, the bottom one is currently in a streak of good luck, while the middle one is in a streak of what I'd call less then ideal luck...

https://www.evernote.com/shard/s91/sh/7eb6221c-6c8d-4c28-a312-75f0814db881/4883b9429424359e3b46c058b2aa4f9f/deep/0/p2pool-variance1.png

It all balances out over time, a key to successfully mining on p2pool is having the patience and consistency to stick with it until it does Wink

windpath
Legendary
*
Offline Offline

Activity: 938


View Profile WWW
May 28, 2014, 05:15:32 PM
 #8739

Can you share that frontend your using?  Im used to mining on slush's pool so I understand a little about variance.  mdude77 I do indeed have new cgminer for s1.

Im still confused about the data on the homepage and if my data is normal for a newly configured p2pool, or if i need to look further into it.  Here is the stats listed


Is the "expected time to share" normal for my node uptime?  Ive seen others that show it down to an hour with similar pool speed as mine.  I suppose most of my confusion is that with slushs pool i see shares coming in from my miners much more frequently than this and of course they state the average btc for current round as well.  I feel im flying more blind with p2pool, especially with 0 as expected payout.  The vanilla p2pool interface showed an expected payout number, even when pool was freshly fired up and went up/down as data came through.

I'm actively developing the front end on my site, it's still in beta and requires PHP and a DB to be set up on the node.... It does address some of your concerns about not being able to see shares after a restart... I posted some of the preliminary code in this thread here if you want to check it out.

The expected time to share looks about right to me, here is one of my miners (2x S1), about double your speed, about 1/2 the expected time-to-share:

http://mining.coincadence.com/miner.php?id=13AxQAKFiy6Dks5Jwdbah3rhMJAJ9UzwHk


jonnybravo0311
Legendary
*
Offline Offline

Activity: 1008


Mine at Jonny's Pool


View Profile WWW
May 28, 2014, 11:12:02 PM
 #8740

Hi Windpath, thanks for the info here, im running some s1 and was having hard time with google on a definitive response to setting the pseudo share.

couple of questions
1. is 0.00000116 a static constant, or based off dynamic number?  Wondering if i need to redo the math periodically to keep my miners running efficiently.
2. do you know of any downsides to restarting p2pool, i noticed i lost a few shares once i had done so, but technically i dont understand why that would be.  i did however update the -a payout address, perhaps that restages the pool?
3. "expected time to share" seems to stay around 7-12hrs, im assuming its because the pool doesn't have any stats to work off of yet?
4. "payout if a block were found NOW" seems to remain at 0, any tips on that?
5. know of any p2pool advanced docs/manuals out there?

Thanks for any info

Great questions, gigabitfx.  I'd like to add to the information that windpath has already provided:

1) Setting pseudo-share difficulty determines how many shares from your miner that the p2pool node evaluates.  In p2pool, your miners must submit a share of a given difficulty to be considered.  For example, if you set your pseudo-share difficulty to 1, every single share your miner finds will be considered.  It makes the graph look very smooth, but floods the node with useless traffic.  If you set the pseudo-share difficulty to 1024, then only shares that are greater than 1024 will be considered.  The graph looks very spiky, but the node doesn't have to deal with the extraneous traffic.

The p2pool node will assign pseudo-share difficulty automatically based upon the node's combined hash rate.  If you're running your own private node, you really don't need to bother setting either pseudo-share or share difficulty.  If you're mining on someone else's node, then you might want to set them if the hash rate you're contributing is significantly higher/lower than what the node currently has.

2) You won't lose shares if you restart your node.  Your shares are stored in the share chain.  The default behavior of p2pool does not persist your node's shares across restarts (windpath solved this by creating a database); however, rest assured that every share you've found is part of the share chain.

3) Your expected time to share is based upon your hash rate and the current difficulty target.  The formula is exactly the same as the expected time to find a block of BTC:
Code:
Difficulty * 2**32 / hashrate / 86400 = number of days to find a share
It has no bearing on whether the node has been running for a while or have any stats to work with.

4) This is kind of misleading since it isn't well explained.  This value is the expected payout to the NODE's wallet - not to your miner - UNLESS your miner is the same wallet as your node.  So, let's assume you have started your node as:
Code:
./run_p2pool.py -a SOMEWALLETADDRESS
If you configure your miners with the user name "SOMEWALLETADDRESS" then that expected payout if block found now value will show what you expect.  If you configure your miners with the user name "ANOTHERWALLETADDRESS" then that expected payout value will show 0 (unless you charge a fee to mine on your node, in which case it would show whatever charges have been assessed to your miners).

5) I don't know of any advanced manuals.  The best information I've found is here on these forums, the p2pool wiki and through reading the p2pool code.  This thread is a great place to learn, although going through nearly 440 pages is kind of painful Wink

Hope this helps.

Jonny's Pool - Mine with us and help us grow!  Support a pool that supports Bitcoin, not a hardware manufacturer's pockets!  No SPV cheats.  No empty blocks.
Pages: « 1 ... 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 [437] 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 ... 744 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!