Bitcoin Forum
May 02, 2024, 11:50:13 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: syncing new node (two log curiosities)  (Read 2006 times)
onemorebtc (OP)
Sr. Member
****
Offline Offline

Activity: 266
Merit: 250


View Profile
February 18, 2015, 12:21:48 PM
 #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

transfer 3 onemorebtc.k1024.de 1
1714650613
Hero Member
*
Offline Offline

Posts: 1714650613

View Profile Personal Message (Offline)

Ignore
1714650613
Reply with quote  #2

1714650613
Report to moderator
1714650613
Hero Member
*
Offline Offline

Posts: 1714650613

View Profile Personal Message (Offline)

Ignore
1714650613
Reply with quote  #2

1714650613
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
funkenstein
Legendary
*
Offline Offline

Activity: 1066
Merit: 1050


Khazad ai-menu!


View Profile WWW
February 18, 2015, 02:18:02 PM
 #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?

"Give me control over a coin's checkpoints and I care not who mines its blocks."
http://vtscc.org  http://woodcoin.info
onemorebtc (OP)
Sr. Member
****
Offline Offline

Activity: 266
Merit: 250


View Profile
February 18, 2015, 02:38:15 PM
 #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

transfer 3 onemorebtc.k1024.de 1
onemorebtc (OP)
Sr. Member
****
Offline Offline

Activity: 266
Merit: 250


View Profile
February 19, 2015, 09: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?

transfer 3 onemorebtc.k1024.de 1
zvs
Legendary
*
Offline Offline

Activity: 1680
Merit: 1000


https://web.archive.org/web/*/nogleg.com


View Profile WWW
February 20, 2015, 05: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
onemorebtc (OP)
Sr. Member
****
Offline Offline

Activity: 266
Merit: 250


View Profile
February 21, 2015, 03:07:16 PM
 #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)

transfer 3 onemorebtc.k1024.de 1
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!