Watcher about optics-monorepo HOT 5 CLOSED

setup map with key being the old root 

loop {
  let (home_up, rep_up) = join ( 
    poll home for updates,
    poll replica for updates,
  }
  for both {
      check if already exists in map
      if exists { 
        if new_root_in_map != new_root_in_update { submit double update } 
      } else { store in map }
  }   
}

from optics-monorepo.

future goal: persist the update map to disk using SQLite or Sled or leveldb. load from disk on bootup

from optics-monorepo.

we have to guard against the case where a fraudulent updater submits a fraudulent update to just 1 replica, and an honest update to the home chain

from optics-monorepo.

This sound like a reasonable approach or will there be too many updates to story in memory?

Store list of all updates in hashmap (filter through all Update events and check for fraud as you fill map)

Loop {

• Poll (listen for) signed updates from home and store them in map (same as relayer::poll_updates but store results)

• For each new update, check for double update using map

  • If double update detected call doubleUpdate on home + all assigned replicas

}

from optics-monorepo.

  let (home_up, rep_up) = join ( 
    poll home for updates,
    poll replica for updates,
  }

Don't I only need to track Home since Replica doesn't actually produce any updates? Like double update fraud will only come from something originating from Home so doesn't the watcher just observe the home and then notify home + replicas if fraud detected?

from optics-monorepo.