The Heliax team (developing Anoma & Namada) would like to reach out to you again for an update on the shielded airdrop, previously discussed here. In the time since that post, we have come up with a more detailed protocol design and a small demo to proof-of-concept the most important aspect of the airdrop transaction, and we would like to show it to you and collect feedback.
Both the protocol details and the demo can be found in this GitHub repo.
We would be enthusiastic about any technical feedback you wish to discuss with us concerning protocol correctness, privacy-preservation, and ease of integration into wallets etc. If you wish to discuss the airdrop program please reply to the former post - let’s keep this thread to technical details and discussions only.
Thank you for working so hard to support shielded airdrops
I think you could set a good example for other developers (and Zcash users) by working equally as hard to exclude any support for non shielded airdrops.
Specifically, I think any support of non shielded t address airdrops are a net harm to the community by enabling those that don’t support the core principle of Zcash. Privacy
until now there has been no hardware wallet support to keep ZEC in the shielded pool.
+there’s different reasons why someone holds their ZEC in the transparent pool at a certain point in time.
A brief summary: we have some concerns about the assumption of a private channel between the Zcash and Namada wallets to send \mathsf{rcv^{Sapling}}, and a suggestion that would remove reliance on that.
It should also be noted that the protocol relies on \mathsf{nsk} being private (or else it is not secure against a full viewing key holder). This would prevent it from being applied straightforwardly to Orchard which does not have \mathsf{nsk}.
I’ll clean up our notes and post them tomorrow on Monday.