Henry de Valence

(This is blocked on governance implementation).

Closed accidentally by Github, the `Withdraw` action hasn't been made, only the prerequisite `Address` changes have.

The "TCT spec" referenced in this issue *is* part of the implementation, though, it's designed to test that specific implementation, and isn't useful outside of that context. So we should...

Since this is just a performance optimization, we should wait to implement it until the chain is feature-complete, at which point we'll just have the view service to implement it...

One thing to note about these ideas is that they're aiming to optimize the case where there is a lot of transaction activity (and hence, scanning to do, note commitments...

Removed from milestone because it's not important to do this now, only to do it eventually. > the swap component will need to write a boolean into the JMT Rather...

We should wait to do this until we have a plan on whether and how we want to integrate the existing TCT code, or go for an alternate path forward...

We'd originally had an idea of fetching full transactions by note commitment, and including random note commitments as chaff to obscure exactly which transactions were fetched. But this has the...

To start, a basic MVP of the design sketched in #1053 is in #1057

Hmm, wouldn't this potentially reveal information about the user's delegation? If we did this, and someone saw an undelegation where there's an empty block preceding it, someone could learn that...