Nathan Wilcox

Any progress here? What are some next steps? Any way I can help? I'd really appreciate this feature because I frequently do "offline" development where I run `cargo doc`, then...

I came to make the same suggestion. However, I also prefer precision and explicitness, so I wouldn't recommend always supporting `Into` on every `new` param. Here are some brainstorms about...

Any update on this issue? The primary reason I found and tried `static_assertions` is precisely to verify relationships between const generic parameters. The work-around seems like a completely different approach,...

You're right that there's not clear criteria for closing this ticket... Hrm... I'll think about it.

The problem with this approach is that it's the end-user that should decide on the policy, not a library or an application. For example, having a Tor SOCKS proxy on...

The big trade-off here is between efficiency and privacy. With orchard actions, we have "this thing might have any combination of an input, an output, and/or a memo" which provides...

BTW, I just filed a very general ticket #629 partially reminded of it by this conversation. If we could find a more scalable architecture, it may remove a lot of...

cc'ing @ioptio since she's working on user education and this dovetails with that, and we were just recently having a conversation about the need for this kind of document. One...

Just a general comment about the context of this ZIP: First of all, this is a "hobby / self-interest" project on my part, not an [@Electric-Coin-Company](https://github.com/Electric-Coin-Company). This is because at...

Privacy / Threat Model rough/rushed thoughts: Much thanks to [@defuse 's comment](https://github.com/zcash/zips/pull/391#issuecomment-673082232) for prompting me to clarify threat model: > * The different protocol actions, like sending versus receiving transactions,...