Bitcoin Forum
December 09, 2016, 03:54:32 PM *
News: Latest stable version of Bitcoin Core: 0.13.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 616 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 ... 744 »
  Print  
Author Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool  (Read 2033342 times)
windpath
Legendary
*
Offline Offline

Activity: 938


View Profile WWW
August 21, 2015, 07:16:00 PM
 #13301

Awesome! Already had our first commit with some fixes from Rav3nPL, thanks!

As he has been around a while (longer then I anyway), is a contributor to the main source, and maintains a branch with support for many alt-coins, he now has commit access as well.

I also added ForrestV if he would care to contribute...

Edit: Also changed the default branch to gh-pages, so https://github.com/ChainQuery/p2pool.org resolves to the site branch.


1481298872
Hero Member
*
Offline Offline

Posts: 1481298872

View Profile Personal Message (Offline)

Ignore
1481298872
Reply with quote  #2

1481298872
Report to moderator
1481298872
Hero Member
*
Offline Offline

Posts: 1481298872

View Profile Personal Message (Offline)

Ignore
1481298872
Reply with quote  #2

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

Activity: 266



View Profile
August 21, 2015, 07:32:36 PM
 #13302

Yup, bit of a whizz is our Rav3nPL  Smiley

This is great stuff windpath - kudos.
yslyung
Legendary
*
Offline Offline

Activity: 1064


Mine Mine Mine


View Profile
August 21, 2015, 08:07:58 PM
 #13303

Awesome! Already had our first commit with some fixes from Rav3nPL, thanks!

As he has been around a while (longer then I anyway), is a contributor to the main source, and maintains a branch with support for many alt-coins, he now has commit access as well.

I also added ForrestV if he would care to contribute...

Edit: Also changed the default branch to gh-pages, so https://github.com/ChainQuery/p2pool.org resolves to the site branch.



http://p2pool-nodes.info/ is listed on the site but it ain;t working anymore.

looks like the hunt for 3rd block of the day has just begun.
Carlton Banks
Legendary
*
Offline Offline

Activity: 1470



View Profile
August 22, 2015, 08:17:35 AM
 #13304

Has there been any word from forrestv as to weather this new "XT" client is actually compatible with p2pool with it's different block size params?

I'm using XT. Working good here. Still looking into what it actually patches and how it effects mining. Any info would be appreciated.

I wonder how this will change mining? Would it give Big pools a bigger advantage?
I know KNC are supporting it and that's one of there biggest sponsors.
Of course Bitmain is for this too.
Coming to a hard-fork means I'm supporting it at the moment.
"ChinaPool" is definitely going to kick it's weight around if this flies or not.
How do you feel about this please share.


XT is compatible now. It will not be compatibile after the arranged fork date (January 11th 2016)

The main change is it implements BIP 101, Gavin Andresen's proposal to increase the blocksize limit to 8MB, followed by a doubling of that limit every two years until a final target limit of 8 gigabytes is reached in the year 2033.

Other significant changes are:

  • Longest chain no longer wins, chain validity is determined using checkpoints periodically added by the XT devs to the code
  • Tor nodes are deprioritised from connection as an anti-DOS measure
  • Permitted Tor exit nodes are, at present, hard coded into the XT client

As p2pool miners, I would investigate the implications of the blocksize changes, and also of the changes to the chain consensus rules.


Also be aware: this model of absolute blocksize limits isn't a very good one (it worked well up to now, but it is true that we are beginning to "run out of road" using this paradigm). A dynamic limit of some type is perhaps a better option, but I am also interested to hear any other concepts that haven't yet been given an airing. There is a productive discussion (no, really!) going on in the Development and Technical sub (https://bitcointalk.org/index.php?topic=1154536.0). Here's what I had to say about this in another thread:

"Is it really such a great plan to make predictions about what technology we'll be running the bitcoin network on, decades into the future? I would argue that as we approach the steeper part of the curve of technological progress, making accurate predictions will become increasingly more difficult. Perhaps it is worth taking an optimistic view of progress when conducting some aspects of long term planning. But when you're designing something vital, prudence and conservatism is a much more appropriate strategy. Only the absolute basics in life are more vital than monetary systems."

Vires in numeris
p3yot33at3r
Sr. Member
****
Offline Offline

Activity: 266



View Profile
August 22, 2015, 08:38:02 AM
 #13305

Has there been any word from forrestv as to weather this new "XT" client is actually compatible with p2pool with it's different block size params?

Forrestv - if you're lurking, it would be interesting to hear your point of view  Wink
Meuh6879
Legendary
*
Offline Offline

Activity: 1092



View Profile
August 22, 2015, 02:43:13 PM
 #13306

http://p2pool-nodes.info/ is listed on the site but it ain;t working anymore.

looks like the hunt for 3rd block of the day has just begun.

use this : http://nodes.p2pool.co/

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
jonnybravo0311
Legendary
*
Offline Offline

Activity: 1008


Mine at Jonny's Pool


View Profile WWW
August 22, 2015, 03:10:34 PM
 #13307

XT is compatible now. It will not be compatibile after the arranged fork date (January 11th 2016)

The main change is it implements BIP 101, Gavin Andresen's proposal to increase the blocksize limit to 8MB, followed by a doubling of that limit every two years until a final target limit of 8 gigabytes is reached in the year 2033.

Other significant changes are:

  • Longest chain no longer wins, chain validity is determined using checkpoints periodically added by the XT devs to the code
  • Tor nodes are deprioritised from connection as an anti-DOS measure
  • Permitted Tor exit nodes are, at present, hard coded into the XT client

As p2pool miners, I would investigate the implications of the blocksize changes, and also of the changes to the chain consensus rules.
Great points Carlton.  Using XT means you are implicitly accepting all of the changes it brings to the table - not just the increased block size from BIP101.

I also agree that setting arbitrary limits like the ones proposed in BIP101 provides an artificial barrier that may or may not need to be changed as technology progresses in the future.

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.
Carlton Banks
Legendary
*
Offline Offline

Activity: 1470



View Profile
August 22, 2015, 03:26:14 PM
 #13308

Great points Carlton.  Using XT means you are implicitly accepting all of the changes it brings to the table - not just the increased block size from BIP101.

I also agree that setting arbitrary limits like the ones proposed in BIP101 provides an artificial barrier that may or may not need to be changed as technology progresses in the future.

Thank you, although I must point out that the text of mine that you quoted are the facts as I perceive them, not any kind of arguments.


The part of my post you didn't quote are my opinions about how to strategise for the future growth of Bitcoin, although I hope you might consider those to be good points. I would be interested to hear anybody elses views on such matters also, debating on the main board about these issues is tough when you have to explain alot of the details.

Vires in numeris
p3yot33at3r
Sr. Member
****
Offline Offline

Activity: 266



View Profile
August 22, 2015, 04:44:56 PM
 #13309

Looks like p2pool's recent outstanding luck has bought a big player back - currently at over 2.5Ph/s  Smiley
forrestv
Hero Member
*****
Offline Offline

Activity: 510


View Profile
August 22, 2015, 05:04:34 PM
 #13310

Has there been any word from forrestv as to weather this new "XT" client is actually compatible with p2pool with it's different block size params?

Forrestv - if you're lurking, it would be interesting to hear your point of view  Wink

If the fork to 8MB blocks happens, P2Pool will require changes to support 8MB blocks and its own fork to get everyone using the changes. That said, it's a ways off and the changes should be pretty straightforward.

1J1zegkNSbwX4smvTdoHSanUfwvXFeuV23
yslyung
Legendary
*
Offline Offline

Activity: 1064


Mine Mine Mine


View Profile
August 22, 2015, 05:15:51 PM
 #13311

Has there been any word from forrestv as to weather this new "XT" client is actually compatible with p2pool with it's different block size params?

Forrestv - if you're lurking, it would be interesting to hear your point of view  Wink

If the fork to 8MB blocks happens, P2Pool will require changes to support 8MB blocks and its own fork to get everyone using the changes. That said, it's a ways off and the changes should be pretty straightforward.

let's hope there will an earlier warning compared to the last one so that everyone on p2p will have ample time to switch over. would be also great to see some improvements.

in the meanwhile, whereisblock ?
squidicuz
Jr. Member
*
Offline Offline

Activity: 50


View Profile
August 22, 2015, 05:21:47 PM
 #13312

XT is compatible now. It will not be compatibile after the arranged fork date (January 11th 2016)

The main change is it implements BIP 101, Gavin Andresen's proposal to increase the blocksize limit to 8MB, followed by a doubling of that limit every two years until a final target limit of 8 gigabytes is reached in the year 2033.

Other significant changes are:

  • Longest chain no longer wins, chain validity is determined using checkpoints periodically added by the XT devs to the code
  • Tor nodes are deprioritised from connection as an anti-DOS measure
  • Permitted Tor exit nodes are, at present, hard coded into the XT client

As p2pool miners, I would investigate the implications of the blocksize changes, and also of the changes to the chain consensus rules.


Also be aware: this model of absolute blocksize limits isn't a very good one (it worked well up to now, but it is true that we are beginning to "run out of road" using this paradigm). A dynamic limit of some type is perhaps a better option, but I am also interested to hear any other concepts that haven't yet been given an airing. There is a productive discussion (no, really!) going on in the Development and Technical sub (https://bitcointalk.org/index.php?topic=1154536.0). Here's what I had to say about this in another thread:

"Is it really such a great plan to make predictions about what technology we'll be running the bitcoin network on, decades into the future? I would argue that as we approach the steeper part of the curve of technological progress, making accurate predictions will become increasingly more difficult. Perhaps it is worth taking an optimistic view of progress when conducting some aspects of long term planning. But when you're designing something vital, prudence and conservatism is a much more appropriate strategy. Only the absolute basics in life are more vital than monetary systems."

Thank you.

The changes to the consensus rules are appalling, as well as some of the other features of Bitcoin XT.
BIP101 may be an answer, but there could be a better solution that we can all stand behind.  We must work to all agree on a plan for the future that scales and doesn't divide us.  A solution that everyone can support will eventually be found.
p3yot33at3r
Sr. Member
****
Offline Offline

Activity: 266



View Profile
August 22, 2015, 05:41:44 PM
 #13313

Has there been any word from forrestv as to weather this new "XT" client is actually compatible with p2pool with it's different block size params?

Forrestv - if you're lurking, it would be interesting to hear your point of view  Wink

If the fork to 8MB blocks happens, P2Pool will require changes to support 8MB blocks and its own fork to get everyone using the changes. That said, it's a ways off and the changes should be pretty straightforward.

Thanks forrestv - good to hear your point of view. Having said that, I am totally opposed to the new Bitcoin XT client for a few reasons, one of which I pointed out on a different thread:  https://bitcointalk.org/index.php?topic=1157317.0

ie: Hard coded TOR exit nodes hand picked by "someone" is a massive security danger to anyone using them. I definitely won't be using the XT client.

windpath
Legendary
*
Offline Offline

Activity: 938


View Profile WWW
August 22, 2015, 06:16:38 PM
 #13314

http://p2pool-nodes.info/ is listed on the site but it ain;t working anymore.

looks like the hunt for 3rd block of the day has just begun.

use this : http://nodes.p2pool.co/

This has been updated.

luthermarcus
Full Member
***
Offline Offline

Activity: 206



View Profile
August 22, 2015, 09:14:04 PM
 #13315

Just checked on my node and I haven't received a share for a while and my payments are going down using XT.
Since I changed nothing else I'm assuming it has something  to do with the new default settings in XT.
Yea I have to figure out how to revert back now. I really wish i could do this without reinstalling bitcoin core over and waiting for the blockchain to download.


Update: Seems like after restarting things went back to normal.
TheRealSteve
Hero Member
*****
Offline Offline

Activity: 686

FUN > ROI


View Profile
August 22, 2015, 09:42:32 PM
 #13316

I really wish i could do this without reinstalling bitcoin core over and waiting for the blockchain to download.
I don't know about whatever P2Pool issues you may be facing - but you can install XT over Core and Core over XT and just have them use the existing block chain data files - no need to re-download it all.

yslyung
Legendary
*
Offline Offline

Activity: 1064


Mine Mine Mine


View Profile
August 23, 2015, 01:16:33 AM
 #13317

Just checked on my node and I haven't received a share for a while and my payments are going down using XT.
Since I changed nothing else I'm assuming it has something  to do with the new default settings in XT.
Yea I have to figure out how to revert back now. I really wish i could do this without reinstalling bitcoin core over and waiting for the blockchain to download.


could be the sudden BIG hashrate that showed up snatching some shares & shares do expire in p2p after some time.

when hashrate goes up, min p2p share difficulty goes up too & it is more difficult to get a share if your hashrate is too low.

maybe you can try to use YOUR_BTC_ADD/1 ... "/1" tells the node to give your miner min p2p share diff instead of high diff but high diff shares is more valuable but min share diff enables you to get more share.

also try to point your miners to the closest node to you as latency plays a BIG role in p2p.

stand to be corrected.
luthermarcus
Full Member
***
Offline Offline

Activity: 206



View Profile
August 23, 2015, 08:15:36 AM
 #13318

Just checked on my node and I haven't received a share for a while and my payments are going down using XT.
Since I changed nothing else I'm assuming it has something  to do with the new default settings in XT.
Yea I have to figure out how to revert back now. I really wish i could do this without reinstalling bitcoin core over and waiting for the blockchain to download.


could be the sudden BIG hashrate that showed up snatching some shares & shares do expire in p2p after some time.

when hashrate goes up, min p2p share difficulty goes up too & it is more difficult to get a share if your hashrate is too low.

maybe you can try to use YOUR_BTC_ADD/1 ... "/1" tells the node to give your miner min p2p share diff instead of high diff but high diff shares is more valuable but min share diff enables you to get more share.

also try to point your miners to the closest node to you as latency plays a BIG role in p2p.

stand to be corrected.

I was considering a the higher hashrate but that doesn't explain why i haven't had a share for 24 hours. The difficulty I use for my miners should be the ok because of past experience. I think that they changed the default blocksize to current max which why it was taking longer to get a share because at first started off great was grabbing shares like normal then I check on it a day later and the orphan rate shot up. The next day the stats haven't changed so I recently restarted it seems to be doing better but I'm keeping an eye on it. You may be right about the latency because the blocksizre increase to the full 1mb is by default on XT but I get anywhere from 100 to 160MB/s which i think is really fast latency shouldn't be an issue unless comcast is fucking something up like they do. Maybe I'm overlooking something else they changed hope a reset is all my miner, node and bitcoin needed.
I did what you said too I let it kick to the backup node and my payout started to go up while I reset XT.

Update: Seems like after restarting things went back to normal.
luthermarcus
Full Member
***
Offline Offline

Activity: 206



View Profile
August 23, 2015, 08:27:34 AM
 #13319

I really wish i could do this without reinstalling bitcoin core over and waiting for the blockchain to download.
I don't know about whatever P2Pool issues you may be facing - but you can install XT over Core and Core over XT and just have them use the existing block chain data files - no need to re-download it all.

That's what I thought too I thought I was going to have a separate icon and I was just eager to try XT. Even though it does use the Core it changes it changes certain Core default values and after reading more about it I'm less opportunistic about XT and if it's going to cause latency issues it could be counter productive. I want to check this out more. Anyone have a link for a front-end with all the graphs to measure latency and such....
Meuh6879
Legendary
*
Offline Offline

Activity: 1092



View Profile
August 24, 2015, 03:43:06 PM
 #13320

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)




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
Pages: « 1 ... 616 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 ... 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!