Quick update on the past couple of weeks.
Spent time reviewing and design/discussion with @jaspervdm around PIBD changes for HF4 -
I think we are getting close to getting this initial work to a place where we can merge it.
“Flexible peer filtering” is in review and hoping to merge soon -
Spent time looking into what would be required to rebuild our “prune list” when receiving PIBD segments. The “prune list” tracks pruned/compacted sections of the output and rangeproof PMMR structures. This “prune list” is critical for correct reads in to the hash and data files on disk to correctly calculate byte offsets to handle pruned data.
This culminated in a rework of our append() implementation on our PruneList. We not have consistent (also simpler and more efficient) logic for building/rebuilding/reading from disk.
This is also up for review and should be hopefully merged soon.
Also took some time to investigate future support for FlyClient (https://eprint.iacr.org/2019/226.pdf) as we wanted to make sure our proposed DAA changes (https://github.com/mimblewimble/grin-rfcs/pull/61) were compatible with FlyClient.
There are currently some open questions regarding our header MMR and what data we commit to in intermediate nodes.
We are hoping to hear back from Benedikt Bunz regarding this. I would like to avoid finding ourselves in a position where FlyClient support would necessitate a subsequent hardfork post HF4.