Bitcoin Forum
December 05, 2016, 02:43:15 PM *
News: Latest stable version of Bitcoin Core: 0.13.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: sfh  (Read 1381 times)
Anonymous
Guest

sfh
November 16, 2010, 01:03:57 AM
 #1

adg
1480948995
Hero Member
*
Offline Offline

Posts: 1480948995

View Profile Personal Message (Offline)

Ignore
1480948995
Reply with quote  #2

1480948995
Report to moderator
1480948995
Hero Member
*
Offline Offline

Posts: 1480948995

View Profile Personal Message (Offline)

Ignore
1480948995
Reply with quote  #2

1480948995
Report to moderator
1480948995
Hero Member
*
Offline Offline

Posts: 1480948995

View Profile Personal Message (Offline)

Ignore
1480948995
Reply with quote  #2

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

Posts: 1480948995

View Profile Personal Message (Offline)

Ignore
1480948995
Reply with quote  #2

1480948995
Report to moderator
theymos
Administrator
Legendary
*
Offline Offline

Activity: 2492


View Profile
November 16, 2010, 01:08:37 AM
 #2

Is there any way I can confirm, that someone else generated a block for the same block as me, and then it forked, and the other chain happened to grow longer faster?

Search debug.log for "REORGANIZE" right after your "proof-of-work found". That means another chain has gained the lead over your chain.

That's why we have this...
Code:
        // Don't show generated coin until confirmed by at least one block after it
        // so we don't get the user's hopes up until it looks like it's probably accepted.

1NXYoJ5xU91Jp83XfVMHwwTUyZFK64BoAD
theymos
Administrator
Legendary
*
Offline Offline

Activity: 2492


View Profile
November 16, 2010, 01:30:36 AM
 #3

Yikes, I've got it 4 times in there in the last couple of days. Is that each time I found one and it got longer, or anytime I hopped on the shorter chain?

You're more likely to reorganize right after starting Bitcoin while you catch up with the current blocks. If you were running Bitcoin that whole time, I'm not sure why you would get so many. It only happens when you stop working on one branch and start working on another one.

I would be interested in seeing that 24-hour section of your debug.log.

1NXYoJ5xU91Jp83XfVMHwwTUyZFK64BoAD
Anonymous
Guest

November 16, 2010, 10:51:01 AM
 #4

Yikes, I've got it 4 times in there in the last couple of days. Is that each time I found one and it got longer, or anytime I hopped on the shorter chain?

You're more likely to reorganize right after starting Bitcoin while you catch up with the current blocks. If you were running Bitcoin that whole time, I'm not sure why you would get so many. It only happens when you stop working on one branch and start working on another one.

I would be interested in seeing that 24-hour section of your debug.log.

It was actually as of Friday, so a couple of days. I'll send it if you'd like. Further investigation shows it found 2 blocks, and after each of those it had a reorg in there. Plus two others. One, right near the start, and one earlier today. Definitely weird. Burns me that it looks like I found two but they weren't accepted, darn it haha.

I hate that feeling when you scratched a scratch lotto ticket and think you won only to realise the last number needed an extra zero.  Sad
ByteCoin
Sr. Member
****
Offline Offline

Activity: 416


View Profile
November 18, 2010, 12:57:28 AM
 #5

Are there really so many hashes found that go to waste?

The quote in the comment in ui.cpp says that by design something in the region of 10% of blocks generated won't be accepted, presumably because another block has been found slightly before and is propagating across the network but hasn't reached our computer yet. For about 10% of blocks to be wasted the propagation time for a block from one generator to another would have to be of the order of about a minute! Surely block propagation can't take that long?

Could some keen miner (Artforz) please scour their logfile and find out what the ratio of accepted to rejected blocks is in real life?

Also, I notice that it's in the miner's mutual best interests (jointly and severally) to ensure that they connect directly with each other and not with or via non-generating clients.  It's most important to connect to generators with the highest hash rate.
In fact, there's no incentive for generators to talk to non-generators at all unless non-generators are offering a transaction with a fee!

ByteCoin
FreeMoney
Legendary
*
Offline Offline

Activity: 1246


Strength in numbers


View Profile WWW
November 18, 2010, 01:20:52 AM
 #6

Are there really so many hashes found that go to waste?

The quote in the comment in ui.cpp says that by design something in the region of 10% of blocks generated won't be accepted, presumably because another block has been found slightly before and is propagating across the network but hasn't reached our computer yet. For about 10% of blocks to be wasted the propagation time for a block from one generator to another would have to be of the order of about a minute! Surely block propagation can't take that long?

Could some keen miner (Artforz) please scour their logfile and find out what the ratio of accepted to rejected blocks is in real life?

Also, I notice that it's in the miner's mutual best interests (jointly and severally) to ensure that they connect directly with each other and not with or via non-generating clients.  It's most important to connect to generators with the highest hash rate.
In fact, there's no incentive for generators to talk to non-generators at all unless non-generators are offering a transaction with a fee!

ByteCoin

Is the fact that they might send a fee or might generate enough? What is the real cost of connecting? Why not just keep connecting to more and more people?

Play Bitcoin Poker at sealswithclubs.eu. We're active and open to everyone.
Pages: [1]
  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!