Feedback:
One section I believe could improve developers', and even users', understanding/intuition of the private inner workings of Aztec is one dedicated to explaining what happens, for example, when a user calls a private function in a very thorough yet ELI5 way. When I say thorough, I mean explaining every piece involved in the interaction, from the user device to the wallet to the trees, and so on - the complete flow of what takes place when a function is called. The best example of this, and where I got the idea from, is this article by Tincho Abbate: https://www.notonlyowner.com/learn/what-happens-when-you-send-one-dai. His article is excellent albeit very long, I'm suggesting something more concise but with a similar concept: explaining most of what happens under the hood in an easy-to-understand way, unifying the entire flow, which should allow for improving intuition.
Feedback:
One section I believe could improve developers', and even users', understanding/intuition of the private inner workings of Aztec is one dedicated to explaining what happens, for example, when a user calls a private function in a very thorough yet ELI5 way. When I say thorough, I mean explaining every piece involved in the interaction, from the user device to the wallet to the trees, and so on - the complete flow of what takes place when a function is called. The best example of this, and where I got the idea from, is this article by Tincho Abbate: https://www.notonlyowner.com/learn/what-happens-when-you-send-one-dai. His article is excellent albeit very long, I'm suggesting something more concise but with a similar concept: explaining most of what happens under the hood in an easy-to-understand way, unifying the entire flow, which should allow for improving intuition.