(Post title made stupid because the forum software complains otherwise, sorry.)
Implementing consistent controller tags seems reasonably possible, and in particular the concept of controllers that differ only in emergency override conditions opens some convenient software design possibilities.
I’m still unsure of the following:
- What strategies do we plan to follow to talk to the wrappers-only world, which can’t conveniently reduce a controller tag, without being too expensive?
- When and why, in terms of timing and maybe system operator choice, do we reduce DAGs? It seems like we might want to do this on receipt, since we’re already updating the latest attestations at that time anyway, but it’s less clear about send records; the paper is focused on how and under which conditions it’s legal to do this, which makes sense for the paper, but I don’t have a good model yet of how to employ this, besides opportunistically doing it whenever something is touched.