Bitcoin Forum

Bitcoin => Bitcoin Technical Support => Topic started by: onemorebtc on February 18, 2015, 12:21:48 PM



Title: syncing new node (two log curiosities)
Post by: onemorebtc on February 18, 2015, 12:21:48 PM
at first i saw that during sync there were thousands of orphan blocks. why? who broadcasts them still?

second i saw this log lines:
2015-02-18 12:17:12 ERROR: AcceptToMemoryPool : nonstandard transaction: dust
2015-02-18 12:17:13 ERROR: AcceptToMemoryPool: : nonstandard transaction input

(there is a colon to much)

regards


Title: Re: syncing new node (two log curiosities)
Post by: funkenstein on February 18, 2015, 02:18:02 PM
Dust and nonstandard inputs are to be expected on an open network, but logging of nonstandard error messages is a bit strange? 

Did somebody say log?


Title: Re: syncing new node (two log curiosities)
Post by: onemorebtc on February 18, 2015, 02:38:15 PM
Dust and nonstandard inputs are to be expected on an open network, but logging of nonstandard error messages is a bit strange? 

Did somebody say log?

its consequent to log a nonstand error in an nonstandard way ;)


Title: Re: syncing new node (two log curiosities)
Post by: onemorebtc on February 19, 2015, 09:02:58 PM
at first i saw that during sync there were thousands of orphan blocks. why? who broadcasts them still?

bump

anyone?
i'd really like to know why so much old and orphaned blocks are still distributed. i dont see any reason for this.

or did i just misread my log?


Title: Re: syncing new node (two log curiosities)
Post by: zvs on February 20, 2015, 05:25:16 PM
at first i saw that during sync there were thousands of orphan blocks. why? who broadcasts them still?

bump

anyone?
i'd really like to know why so much old and orphaned blocks are still distributed. i dont see any reason for this.

or did i just misread my log?
when you're downloading the entire blockchain, that includes orphaned blocks

there also used to be a bug where it'd spit out some godawful amount of orphan blocks when you were DLing from several different sources.  i think that was fixed, not sure


Title: Re: syncing new node (two log curiosities)
Post by: onemorebtc on February 21, 2015, 03:07:16 PM
at first i saw that during sync there were thousands of orphan blocks. why? who broadcasts them still?

bump

anyone?
i'd really like to know why so much old and orphaned blocks are still distributed. i dont see any reason for this.

or did i just misread my log?
when you're downloading the entire blockchain, that includes orphaned blocks

there also used to be a bug where it'd spit out some godawful amount of orphan blocks when you were DLing from several different sources.  i think that was fixed, not sure

i synced with 0.9.4 so it may be that it was this bug.

i dont understand why "downloading the hole chain" does include orphans too. afaik they are not broadcasted (as they dont have any use)