Brainstorming for Namada's roadmap ⚡

[Matteo]

Privacy technology has a high threshold for ordinary users. It is recommended to reduce the difficulty of use through visualization tools (such as privacy transaction status trackers) and community education programs (such as AMA, developer competitions).

[hjg888]

Currently, the block synchronization time is too long. This problem really needs to be solved, otherwise it will be difficult to use. Neo also used some technologies to solve the problem of wallet block synchronization, which can be used as a technical reference

[cwgoes]

Are you talking about synchronizing the chain state (with a full node), synchronizing shielded balances (with shielded sync), or something else altogether?

[Gavin]

i should also mention that i think Namada governance improvements will be important

• Unbundle governance voting power from consensus voting power · Issue #4215 · anoma/namada · GitHub
• IBC-specific governance proposal type & independent tally settings · Issue #3475 · anoma/namada · GitHub
• sponsoring for Governance proposal deposits · Issue #3479 · anoma/namada · GitHub

[Daniel]

I’ve just made the first steps in that matter today (posted results on both internal related post and on Discord, on Campfire testnet channel). Here’s a direct link to the Discord’s message, just in case: Discord

@cwgoes

I don’t know whether Penumbra supports (or will support) non-native token incentives, that’s a good question to ask them directly if you have contacts there. Connecting Namada and Penumbra – and creating an UM:NAM pool – should be possible, I think someone will need to test out IBC relaying though (support for both Namada and Penumbra was recently merged upstream in Hermes, but I’m not sure if they’ve been tested together).