Topic: listsinceblock on a dead-end fork? (Read 876 times)
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.
bump?
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.
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.
Jump to: