ilyakooo0/urbit
1
0
Fork 0
mirror of https://github.com/ilyakooo0/urbit.git synced 2025-01-05 13:55:54 +03:00
Code Issues Packages Projects Releases Wiki Activity

argue about rewinding 40 blocks whenever we lose the filter

Browse Source 
in case someone's debugging this and wants to understand the decisions
made.
This commit is contained in:
Philip Monk 2018-11-02 15:53:59 -07:00
parent 7faad4de1a
commit 8deed09311
No known key found for this signature in database
GPG Key ID: B66E1F02604E44EC
1 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
sys/vane/jael.hoon
View File

@ -1989,6 +1989,18 @@
~& [%unhandled-filter-error +.rep]
+>
~& [%filter-timed-out--recreating block=latest-block +.rep]
:: arguably should rewind 40 blocks on the off chance the chain reorganized
:: when we blinked. this will also restart the filter.
::
:: (restore-block ?:((lth latest-block 40) 0 (sub.add latest-block 40)))
::
:: counter-argument: it's a royal pain to restore from a snapshot
:: every time you can't ping the node for 5 minutes. this is likely
:: to destabilize the network. better to manually restore if we
:: notice an anomaly.
::
:: third way: don't trust anything that doesn't have 40 confirmations
::
new-filter
:: kick polling timer, only if it hasn't already been.
=? +> ?& ?=(%| -.source)