Author

Topic: syncing new node (two log curiosities) (Read 2022 times)

sr. member
Activity: 266
Merit: 250
February 21, 2015, 11:07:16 AM
#6
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)
zvs
legendary
Activity: 1680
Merit: 1000
https://web.archive.org/web/*/nogleg.com
February 20, 2015, 01:25:16 PM
#5
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
sr. member
Activity: 266
Merit: 250
February 19, 2015, 05:02:58 PM
#4
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?
sr. member
Activity: 266
Merit: 250
February 18, 2015, 10:38:15 AM
#3
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 Wink
legendary
Activity: 1066
Merit: 1050
Khazad ai-menu!
February 18, 2015, 10:18:02 AM
#2
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?
sr. member
Activity: 266
Merit: 250
February 18, 2015, 08:21:48 AM
#1
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
Jump to: