Bitcoin Forum
December 08, 2016, 06:23:51 PM *
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 ... 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 [667] 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 ... 744 »
  Print  
Author Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool  (Read 2032868 times)
p3yot33at3r
Sr. Member
****
Offline Offline

Activity: 266



View Profile
August 24, 2015, 04:21:18 PM
 #13321

When market crash (not bitcoin), shit happens on P2Pool (well, no ... it's Bitcoin Core) ...  Grin

Code:
2015-08-24 15:35:51 CreateNewBlock(): total size 749841
2015-08-24 15:36:08 CreateNewBlock(): total size 749924
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:22 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:23 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:23 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:36:25 CreateNewBlock(): total size 749906
2015-08-24 15:36:42 CreateNewBlock(): total size 749906
2015-08-24 15:36:59 CreateNewBlock(): total size 749909
2015-08-24 15:37:16 CreateNewBlock(): total size 749979
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:20 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:37:33 CreateNewBlock(): total size 749983
2015-08-24 15:37:49 CreateNewBlock(): total size 749879
2015-08-24 15:38:06 CreateNewBlock(): total size 749921
2015-08-24 15:38:23 CreateNewBlock(): total size 749904
2015-08-24 15:38:40 CreateNewBlock(): total size 749991
2015-08-24 15:38:58 CreateNewBlock(): total size 749915
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:00 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:15 CreateNewBlock(): total size 749965
2015-08-24 15:39:31 CreateNewBlock(): total size 749987
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:38 ERROR: AcceptToMemoryPool: inputs already spent
2015-08-24 15:39:48 CreateNewBlock(): total size 749993
2015-08-24 15:40:05 CreateNewBlock(): total size 749859
2015-08-24 15:40:07 UpdateTip: new best=000000000000000002f685ba27822de3e4d6f7c00942534a6830a6192495f020  height=371329  log2_work=83.253971  tx=81009383  date=2015-08-24 15:38:57 progress=0.999999  cache=0.1MiB(0tx)


I don't see anything like this on my nodes.......all is well.
1481221431
Hero Member
*
Offline Offline

Posts: 1481221431

View Profile Personal Message (Offline)

Ignore
1481221431
Reply with quote  #2

1481221431
Report to moderator
1481221431
Hero Member
*
Offline Offline

Posts: 1481221431

View Profile Personal Message (Offline)

Ignore
1481221431
Reply with quote  #2

1481221431
Report to moderator
I HATE TABLES I HATE TABLES I HA(╯°□°)╯︵ ┻━┻ TABLES I HATE TABLES I HATE TABLES
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1481221431
Hero Member
*
Offline Offline

Posts: 1481221431

View Profile Personal Message (Offline)

Ignore
1481221431
Reply with quote  #2

1481221431
Report to moderator
1481221431
Hero Member
*
Offline Offline

Posts: 1481221431

View Profile Personal Message (Offline)

Ignore
1481221431
Reply with quote  #2

1481221431
Report to moderator
1481221431
Hero Member
*
Offline Offline

Posts: 1481221431

View Profile Personal Message (Offline)

Ignore
1481221431
Reply with quote  #2

1481221431
Report to moderator
rav3n_pl
Legendary
*
Offline Offline

Activity: 1320


Don`t panic! Organize!


View Profile
August 24, 2015, 08:48:39 PM
 #13322

This errors in log happens when s1 try double spend and send txes that are using used inputs - like message shows.

1Rav3nkMayCijuhzcYemMiPYsvcaiwHni  Bitcoin stuff on my OneDrive
My RPC CoinControl for any coin https://bitcointalk.org/index.php?topic=929954
My SatoshDice bot https://bitcointalk.org/index.php?topic=897685
Richy_T
Legendary
*
Offline Offline

Activity: 1246


1RichyTrEwPYjZSeAYxeiFBNnKC9UjC5k


View Profile
August 25, 2015, 07:42:55 PM
 #13323


Code:
python ./run_p2pool.py RPC_USER RPC_PASS

RPC user and pass always set, it may work without it on localhost, will give it a try when I get a chance.

Hmm, what do you see when you do a 'ps -ef' ?

1RichyTrEwPYjZSeAYxeiFBNnKC9UjC5k
Medow
Sr. Member
****
Offline Offline

Activity: 296


---- The memeator ----


View Profile
August 26, 2015, 09:26:12 AM
 #13324

Hello:

I have a few questions about p2pool:

1) When a block found the share will be splitted between all node on all p2pool nodes. is this correct?

2) Does all nodes working on the same block ? and how they share between nodes?

3) Which node responsible on how to calculate every miner share on all nodes?

4) Let say a work on node for a day and left p2pool and after 2 days the p2pool hit a block can i still get paid for the shares a submit before 2 days from hitting a block or do i need to be active miner when the block hit?

5) If a node submit the right share and p2pool hit a block and that node have a fees of 1% does the node have it is fees first the the rest splatted on the other miners on every node?

6) when we run the p2pool what is the code to determine the node fees?

Thank you very much.
Meuh6879
Legendary
*
Offline Offline

Activity: 1092



View Profile
August 26, 2015, 11:42:54 AM
 #13325

1) the reward, not the shares ...

2) yes and P2P divide work in shared jobs (that why P2Pool have his sidechain with his shares)

3) P2Pool system with sidechain shares (if you don't work in the sidechain, you don't have reward)

4) Yes, because the sidechain of shared work contain somes jobs already done by your miner (jobs are associated at bitcoin receive adress).

5) Yes, but it's automated by P2Pool system (not by the admin. of node).

6) launch p2pool command with -h to view ALL the command available to set a node for miners.


Code:
>run_p2pool -h

usage: run_p2pool [-h] [--version]
                  [--net {bitcoin,fastcoin,litecoin,terracoin}] [--testnet]
                  [--debug] [-a ADDRESS] [-i NUMADDRESSES] [-t TIMEADDRESSES]
                  [--datadir DATADIR] [--logfile LOGFILE]
                  [--merged MERGED_URLS] [--give-author DONATION_PERCENTAGE]
                  [--iocp] [--irc-announce] [--no-bugreport]
                  [--p2pool-port PORT] [-n ADDR[:PORT]] [--disable-upnp]
                  [--max-conns CONNS] [--outgoing-conns CONNS]
                  [--external-ip ADDR[:PORT]] [--disable-advertise]
                  [-w PORT or ADDR:PORT] [-f FEE_PERCENTAGE]
                  [--bitcoind-config-path BITCOIND_CONFIG_PATH]
                  [--bitcoind-address BITCOIND_ADDRESS]
                  [--bitcoind-rpc-port BITCOIND_RPC_PORT] [--bitcoind-rpc-ssl]
                  [--bitcoind-p2p-port BITCOIND_P2P_PORT]
                  [BITCOIND_RPCUSERPASS [BITCOIND_RPCUSERPASS ...]]

p2pool (version 14.0)

optional arguments:
  -h, --help            show this help message and exit
  --version             show program's version number and exit
  --net {bitcoin,fastcoin,litecoin,terracoin}
                        use specified network (default: bitcoin)
  --testnet             use the network's testnet
  --debug               enable debugging mode
  -a ADDRESS, --address ADDRESS
                        generate payouts to this address (default: <address
                        requested from bitcoind>), or (dynamic)
  -i NUMADDRESSES, --numaddresses NUMADDRESSES
                        number of bitcoin auto-generated addresses to maintain
                        for getwork dynamic address allocation
  -t TIMEADDRESSES, --timeaddresses TIMEADDRESSES
                        seconds between acquisition of new address and removal
                        of single old (default: 2 days or 172800s)
  --datadir DATADIR     store data in this directory (default: <directory
                        run_p2pool.py is in>/data)
  --logfile LOGFILE     log to this file (default: data/<NET>/log)
  --merged MERGED_URLS  call getauxblock on this url to get work for merged
                        mining (example:
                        http://ncuser:ncpass@127.0.0.1:10332/)
  --give-author DONATION_PERCENTAGE
                        donate this percentage of work towards the development
                        of p2pool (default: 1.0)
  --iocp                use Windows IOCP API in order to avoid errors due to
                        large number of sockets being open
  --irc-announce        announce any blocks found on
                        irc://irc.freenode.net/#p2pool
  --no-bugreport        disable submitting caught exceptions to the author
  --disable-upnp        don't attempt to use UPnP to forward p2pool's P2P port
                        from the Internet to this computer
  --disable-advertise   don't advertise local IP address as being available
                        for incoming connections. useful for running a dark
                        node, along with multiple -n ADDR's and --outgoing-
                        conns 0

p2pool interface:
  --p2pool-port PORT    use port PORT to listen for connections (forward this
                        port from your router!) (default: bitcoin:9333,
                        fastcoin:23660, litecoin:9338, terracoin:9323)
  -n ADDR[:PORT], --p2pool-node ADDR[:PORT]
                        connect to existing p2pool node at ADDR listening on
                        port PORT (defaults to default p2pool P2P port) in
                        addition to builtin addresses
  --max-conns CONNS     maximum incoming connections (default: 40)
  --outgoing-conns CONNS
                        outgoing connections (default: 6)
  --external-ip ADDR[:PORT]
                        specify your own public IP address instead of asking
                        peers to discover it, useful for running dual WAN or
                        asymmetric routing

worker interface:
  -w PORT or ADDR:PORT, --worker-port PORT or ADDR:PORT
                        listen on PORT on interface with ADDR for RPC
                        connections from miners (default: all interfaces,
                        bitcoin:9332, fastcoin:5150, litecoin:9327,
                        terracoin:9322)
  -f FEE_PERCENTAGE, --fee FEE_PERCENTAGE
                        charge workers mining to their own bitcoin address (by
                        setting their miner's username to a bitcoin address)
                        this percentage fee to mine on your p2pool instance.
                        Amount displayed at http://127.0.0.1:WORKER_PORT/fee
                        (default: 0)

bitcoind interface:
  --bitcoind-config-path BITCOIND_CONFIG_PATH
                        custom configuration file path (when bitcoind -conf
                        option used)
  --bitcoind-address BITCOIND_ADDRESS
                        connect to this address (default: 127.0.0.1)
  --bitcoind-rpc-port BITCOIND_RPC_PORT
                        connect to JSON-RPC interface at this port (default:
                        bitcoin:8332, fastcoin:9527, litecoin:9332,
                        terracoin:13332 <read from bitcoin.conf if password
                        not provided>)
  --bitcoind-rpc-ssl    connect to JSON-RPC interface using SSL
  --bitcoind-p2p-port BITCOIND_P2P_PORT
                        connect to P2P interface at this port (default:
                        bitcoin:8333, fastcoin:9526, litecoin:9333,
                        terracoin:13333 <read from bitcoin.conf if password
                        not provided>)
  BITCOIND_RPCUSERPASS  bitcoind RPC interface username, then password, space-
                        separated (only one being provided will cause the
                        username to default to being empty, and none will
                        cause P2Pool to read them from bitcoin.conf)



French ... but not so much   ---===---   P2P ... it's people at the end   ---===---   P2Pool (10,9 GH/s).
Comment miner des bitcoins ? Un tutoriel est là : https://bitcointalk.org/index.php?topic=1114415.0
Bitcoin change everything ... an explain of this fact : https://www.youtube.com/watch?v=joITmEr4SjY
Medow
Sr. Member
****
Offline Offline

Activity: 296


---- The memeator ----


View Profile
August 26, 2015, 11:46:19 AM
 #13326

1) the reward, not the shares ...

2) yes and P2P divide work in shared jobs (that why P2Pool have his sidechain with his shares)

3) P2Pool system with sidechain shares (if you don't work in the sidechain, you don't have reward)

4) Yes, because the sidechain of shared work contain somes jobs already done by your miner (jobs are associated at bitcoin receive adress).

5) Yes, but it's automated by P2Pool system (not by the admin. of node).

6) launch p2pool command with ? (or help) to view ALL the command available to set a node for miners.

Thanks for clarification .

I have one more question with one major concern about p2pool.

Let us say one farm has 1 PH miners.

When that farm pointed to a p2pool he will have his revenue according to his hash power.

Let us assume that farm run his own p2pool node locally .

let us also assume that the total hash power of p2pool became 4 PH after that farm pointed it is miners to p2pool .

The chance for that farm to submit the right share for blocked mined by p2pool will be about 25% , right?

So, what if the farm owner run his own local node by choose to give his local node 100% fees , this mean what ever block mined by other p2pool nodes he will get 25% of the revenue and he will keep 100% of the coins mined by his node because he run it node with 100% fees.

Is this correct.

If this is correct then this is will be a major concern about p2pool.

Thank you
p3yot33at3r
Sr. Member
****
Offline Offline

Activity: 266



View Profile
August 26, 2015, 12:07:22 PM
 #13327


Is this correct.

If this is correct then this is will be a major concern about p2pool.

Thank you

No, It's not correct  Wink
Medow
Sr. Member
****
Offline Offline

Activity: 296


---- The memeator ----


View Profile
August 26, 2015, 12:08:48 PM
 #13328

It's not correct  Wink

Why is that ?

Let me understand.
GingerAle
Hero Member
*****
Offline Offline

Activity: 742


View Profile WWW
August 26, 2015, 12:17:05 PM
 #13329

quotes kinda hacked for clarification
question

2) Does all nodes working on the same block ? and how they share between nodes?

Answer

2) yes and P2P divide work in shared jobs (that why P2Pool have his sidechain with his shares)

( snip )
(snip)

As I tried to have clarified in this seperate topic:

https://bitcointalk.org/index.php?topic=1077798.0

I thought that all nodes are working on their own version of the next block, with a common coinbase transaction (based on the share chain). Thus, participating in p2pool is more akin to a mining cooperative than a conventional pool, such that in p2pool a bunch of independent full nodes (ledger + hashing power) are working together but independently on unique nodes, whereas in a conventional pool, everyone is working to hash on one node (so miners are really just submitting hash, not creating their own blocks).

So, they're not *really* working on the same block in the sense that my p2pool node could include a different bunch of transactions than yours (depending on my fee levels etc), but they *are* working on the same block in the sense that our coinbase transaction is common and, more or less, the block is pulling from the same mempool, so the transactions will be similar.

< Monero Compile Instructions >   < Track your bitcoins! > < Track them again! > < Monero NVIDIA mining instructions > < MONERODO : An operating system for your dedicated decentralized node device > <<< What is fungibility? >>> 46P88uZ4edEgsk7iKQUGu2FUDYcdHm2HtLFiGLp1inG4e4f9PTb4mbHWYWFZGYUeQidJ8hFym2WUmWc p34X8HHmFS2LXJkf <<< Free subdomains at moneroworld.com!! >>> <<< If you don't want to run your own node, point your wallet to node.moneroworld.com, and get connected to a random node! >>> @@@@@ Simple Monero Node Installer and Monitor for Windows @@@@@
Medow
Sr. Member
****
Offline Offline

Activity: 296


---- The memeator ----


View Profile
August 26, 2015, 12:28:11 PM
 #13330

As I tried to have clarified in this seperate topic:

https://bitcointalk.org/index.php?topic=1077798.0

I thought that all nodes are working on their own version of the next block, with a common coinbase transaction (based on the share chain). Thus, participating in p2pool is more akin to a mining cooperative than a conventional pool, such that in p2pool a bunch of independent full nodes (ledger + hashing power) are working together but independently on unique nodes, whereas in a conventional pool, everyone is working to hash on one node (so miners are really just submitting hash, not creating their own blocks).

So, they're not *really* working on the same block in the sense that my p2pool node could include a different bunch of transactions than yours (depending on my fee levels etc), but they *are* working on the same block in the sense that our coinbase transaction is common and, more or less, the block is pulling from the same mempool, so the transactions will be similar.

From what i understand that is the node that submit the right share will take the fees .

If that is the situation what will stop the node owner from running his node with 100% fees and keep all coin?
p3yot33at3r
Sr. Member
****
Offline Offline

Activity: 266



View Profile
August 26, 2015, 12:52:17 PM
 #13331

If that is the situation what will stop the node owner from running his node with 100% fees and keep all coin?

What's to stop any pool doing that?

A miner can find out what fees a node is charging by adding "/fee" to end of the node address (most nodes charge 0 fees).

If you're thinking of starting up a node (preferred), or are interested in mining a p2pool node, have a read of the p2pool wiki & through this thread -you'll find answers to all your questions  Wink
windpath
Legendary
*
Offline Offline

Activity: 938


View Profile WWW
August 26, 2015, 01:31:21 PM
 #13332

As I tried to have clarified in this seperate topic:

https://bitcointalk.org/index.php?topic=1077798.0

I thought that all nodes are working on their own version of the next block, with a common coinbase transaction (based on the share chain). Thus, participating in p2pool is more akin to a mining cooperative than a conventional pool, such that in p2pool a bunch of independent full nodes (ledger + hashing power) are working together but independently on unique nodes, whereas in a conventional pool, everyone is working to hash on one node (so miners are really just submitting hash, not creating their own blocks).

So, they're not *really* working on the same block in the sense that my p2pool node could include a different bunch of transactions than yours (depending on my fee levels etc), but they *are* working on the same block in the sense that our coinbase transaction is common and, more or less, the block is pulling from the same mempool, so the transactions will be similar.

From what i understand that is the node that submit the right share will take the fees .

If that is the situation what will stop the node owner from running his node with 100% fees and keep all coin?

In short nothing. The fees are set on a per node basis, a node running with 100% fees will submit all shares for that specific node for the benefit of that nodes operator. That being said, unless you wanted to donate to a specific node, you would never mine on someone elses 100% fee node.

Put another way, and why it is not an issue, the fee is specific to the node and it's own shares, not shares found by other nodes.

For example, if I wanted to run a node just for myself and not encourage other miners to mine on it setting a 100% fee is a good way to ensure that. However by setting the fee at 100% I do not affect any other nodes.

The "Read This First" post here is a good place to start: http://p2pool.org/

Edit: in re-reading your posts I think you may be confusing the node fee and the transaction fees of a bitcoin block, they are completely separate. A node fee is imposed on all miners on a given node, bitcoin transaction fees are based on what transactions that node is including in a given block and unrelated to the node fee.

Medow
Sr. Member
****
Offline Offline

Activity: 296


---- The memeator ----


View Profile
August 26, 2015, 03:16:47 PM
 #13333

In short nothing. The fees are set on a per node basis, a node running with 100% fees will submit all shares for that specific node for the benefit of that nodes operator. That being said, unless you wanted to donate to a specific node, you would never mine on someone elses 100% fee node.

Put another way, and why it is not an issue, the fee is specific to the node and it's own shares, not shares found by other nodes.

For example, if I wanted to run a node just for myself and not encourage other miners to mine on it setting a 100% fee is a good way to ensure that. However by setting the fee at 100% I do not affect any other nodes.

The "Read This First" post here is a good place to start: http://p2pool.org/

Edit: in re-reading your posts I think you may be confusing the node fee and the transaction fees of a bitcoin block, they are completely separate. A node fee is imposed on all miners on a given node, bitcoin transaction fees are based on what transactions that node is including in a given block and unrelated to the node fee.


I understand now.

The node fees will be deducted from the miner connected to that node and every miners on other node will have their share safe.

Let us say that there is a node that have 100% fees and that node is big enough and submit 50% of share on p2pool when p2pool hit a block.

Then that node will have all the 12.5 coins + 1/2 transactions fees of that block and give nothing to miners. But the rest of 12.5 coins + 1/2 transaction fees will be shared between all miners on the rest of the node.

notbatman
Legendary
*
Offline Offline

Activity: 1050



View Profile
August 26, 2015, 03:39:30 PM
 #13334

P2pool is awesome! My 9W LED lamp got a case of the gremlins and caused a massive power surge crashing my computer and corrupting my blockchain file. Fortunately I just connected to the closest adjacent node and kept on mining without missing a beat. Only 40 weeks to go after 10 hours of re-indexing... LOL.



A 9W LED did this! If the plastic wasn't translucent I'd be clueless... They beamed a 1000W of microwaves into my light bulb with HAARP or something WTF is going on here? I'm not switching to the XT scam fork no matter how many watts gets beamed into my light bulb! Wait I don't even have a light anymore, I need a new fucking plug/lamp. Surprisingly the bulb/lamp still works but I'm not plugging it in.
yslyung
Legendary
*
Offline Offline

Activity: 1064


Mine Mine Mine


View Profile
August 26, 2015, 03:50:54 PM
 #13335

to the newbie few post back...

if you are on your own node mining with your own btc add. i don;t see any reason why to set a 100% fee n charge yourself with a fee ?

setup your own node & mine on your own node will be best

if you have half of p2p hashing power, i'd say almost a yes you would get half the rewards but it could be less depending on how efficient your node is ... sometimes you hit more shares & sometimes you hit less shares & depends when a block comes along the way. also reliability of your pc or server that hosts your node, there could be some downtime.

ah i almost forgot, if you found the block you'll get a little extra coins. 0.5% more.

then prolly a little more too from merged mining.

agreed with windpath, do some reading. there's lots of info out there & also ask questions here.

try to setup your own node & point a small amt of hashpower to it & see how it goes.

not difficult to do, just some reading, trial & errors.


@nobatman ..... get a SSD
Meuh6879
Legendary
*
Offline Offline

Activity: 1092



View Profile
August 26, 2015, 06:57:27 PM
 #13336

@nobatman ..... get a SSD

It can corrupt, too ... if you use a too big cache mempool ( dbcache=50 for me, it's OK and safe from corruption ).

I have a 840 EVO 512 Go SSD (not work very good behing 40°C, need fan !).

French ... but not so much   ---===---   P2P ... it's people at the end   ---===---   P2Pool (10,9 GH/s).
Comment miner des bitcoins ? Un tutoriel est là : https://bitcointalk.org/index.php?topic=1114415.0
Bitcoin change everything ... an explain of this fact : https://www.youtube.com/watch?v=joITmEr4SjY
notbatman
Legendary
*
Offline Offline

Activity: 1050



View Profile
August 26, 2015, 07:13:53 PM
 #13337

@nobatman ..... get a SSD

It can corrupt, too ... if you use a too big cache mempool ( dbcache=50 for me, it's OK and safe from corruption ).

I have a 840 EVO 512 Go SSD (not work very good behing 40°C, need fan !).

I see SSDs for $10k and read that they're little space heaters with a short life span. The cost needs to come down, way way way down and the current technology is clearly inferior to HDDs.

I think a UPS could have prevented this.
TheAnalogKid
Sr. Member
****
Offline Offline

Activity: 266


View Profile
August 26, 2015, 07:37:07 PM
 #13338

I see SSDs for $10k and read that they're little space heaters with a short life span. The cost needs to come down, way way way down and the current technology is clearly inferior to HDDs.

I think a UPS could have prevented this.
$10k?  Where are you looking...

http://www.newegg.com/Product/Product.aspx?Item=N82E16820147360&cm_re=256g_ssd-_-20-147-360-_-Product

An SSD will hands down beat out any mechanical hard drive from the performance angle.  Durability might be an issue long-term as they do have a limited amount of writes capable, but they're cheap enough.

And yeah, a UPS is key, I have all my electronics on them at home - computers, TV's, stereo, etc.  It does more than just battery, it normalizes your power and keeps surges and dips from harming them.

p3yot33at3r
Sr. Member
****
Offline Offline

Activity: 266



View Profile
August 27, 2015, 09:52:02 AM
 #13339

Agree with the SSD & UPS statements - essential for me anyways.

Nice to see a few blocks rolling in again at last  Smiley
electron-coin
Full Member
***
Offline Offline

Activity: 169


View Profile
August 27, 2015, 02:55:48 PM
 #13340

Would anybody be willing to help port p2pool to merge mine 8-round blake 256?

We have a $200 USD+ bounty. https://bitcointalk.org/index.php?topic=306894.3240

Thanks.
Pages: « 1 ... 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 [667] 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 ... 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!