Gal Rogozinski

Update: Apparently it gets stuck on an almost infinite loop trying to `updateMilestoneIndexOfMilestoneTransactions` Apparently lots of confirmed txs are missing their snapshot index... I think it is because of a...

Now that compass depth is set to 0 I think this issue can be done. This is because we will always have a chain of milestones. When a node receives...

A good logic can be the following: Have 2 boot modes quick/normal: In quick mode: 1. Try to load the latest MS 2. If it is solid and ledger state...

Normal mode is equivalent to running the node with `revalidate` I am doing an experiment with quick mode, but it is still blocked until #1448 is completed

As a quick way to get this working is to add a configuration that will tell us which milestone we want to start tracking from This way we are unblocked...

Just to make the above clearer. The plan is: 1. upon bootstrap find the latest milestone value from the snapshot and from the configuration `MILESTONE_INDEX_TO_TRACK` 2. Start looking for `MILESTONE_INDEX_TO_TRACK`....

Important to note the above solution is based on the assumption that milestones always reference each other, so upon solidifying we should get them all

Broadcast it every minute or check what hornet does

If we find that there is no need for a new `model` object then just rename `TipsViewModel`. I deeply dislike everything that is named `ViewModel` in IRI

Related to #918 Thanks, posting this issue will bring the matter to a higher priority