Bitcoin Forum
May 14, 2024, 02:11:04 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: listsinceblock on a dead-end fork?  (Read 852 times)
danielW (OP)
Sr. Member
****
Offline Offline

Activity: 277
Merit: 253


View Profile
April 09, 2015, 04:18:28 AM
 #1

What happens if the block hash returned by listsinceblock ends up being a block on a dead-end fork?

What will subsequent listsinceblock calls return (that use the returned hash as a param)?

Im talking in the context of using listsinceblock to monitor incoming bitcoin payments.
1715695864
Hero Member
*
Offline Offline

Posts: 1715695864

View Profile Personal Message (Offline)

Ignore
1715695864
Reply with quote  #2

1715695864
Report to moderator
1715695864
Hero Member
*
Offline Offline

Posts: 1715695864

View Profile Personal Message (Offline)

Ignore
1715695864
Reply with quote  #2

1715695864
Report to moderator
1715695864
Hero Member
*
Offline Offline

Posts: 1715695864

View Profile Personal Message (Offline)

Ignore
1715695864
Reply with quote  #2

1715695864
Report to moderator
I HATE TABLES I HATE TABLES I HA(╯°□°)╯︵ ┻━┻ TABLES I HATE TABLES I HATE TABLES
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
danielW (OP)
Sr. Member
****
Offline Offline

Activity: 277
Merit: 253


View Profile
April 13, 2015, 12:45:08 PM
 #2

bump?
Cryddit
Legendary
*
Offline Offline

Activity: 924
Merit: 1129


View Profile
April 14, 2015, 01:27:26 AM
 #3

The expected behavior is that if there are no further blocks in the fork, listsinceblock will return no data.  As far as it's concerned the effect is the same as the very next block just taking a longer-than-expected time to arrive. 
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!