Kris Nuttycombe

> @nuttycom suggested that instead of associating expiry with addresses, we could add it to [ZIP 321](https://zips.z.cash/zip-0321) Payment Request URIs. That would get around the diversified address linkability problem (because...

I guess that we could start by just applying this optimization by checking whether the batch we're working on starts at the block above the fully-scanned height; it would give...

One important use case for memo extension is the ability to provide signed reply-to addresses; in the case of a signature approach based on ZIP 304 extended to Orchard, the...

With respect to a memo pruning height, it's important to consider incentives. What incentive does a user have to request that their memo be optionally prunable? It's basically the user...

It doesn't seem to me like zcash/zcash#3693 is fully obsoleted by ZIP 317; it's orthogonal so I've reopened it.

This proposal will probably be subsumed by a proposal to decouple memos from outputs in NU6.

Another topic that needs discussion here is padding of outputs/actions, particularly in the case of cross-pool transfers. Outputs and actions are currently automatically padded by the Sapling and Orchard bundle...

@str4d that's a perfectly valid solution though, right? It's not currently supported in wallets, but there are no changes needed to the protocol for a wallet to to add a...

Also, I'll note that turnstiles don't depend upon transparent (Bitcoin script) functionality at all - turnstiled amounts are a property of the shielded parts of the transaction.

We have added introspection methods to the `ZcashAddress` type to reveal the properties that this PR was intended to expose.