Let me just say that in terms of what I think is most urgent, a good mobile wallet for ios/android is at top of that list.
The way Anoma implements intents (the resource machine) could be understood as a generalization of ZK rollups, but it probably won’t help much with fraud proofs, which are only needed for optimistic rollups and very specific to the details of the optimistic rollup involved. However, a resource machine verifier/executor could be deployed to existing chains, which would allow them to easily support ZK rollups (and Anoma applications more generally) - this might be interesting.
This project appears to be attempting to implement a much weaker data protection model than Namada (or Zcash, or Penumbra, etc.). I’m not quite sure what their motivations are, but I think we’re pursuing pretty different goals.
For Ethereum users to shield their ETH and Ethereum ecosystem tokens in Namada’s MASP a private bridge with Ethereum would be required to have a UX that allows them to shield their assets and bring them back to Ethereum to use their assets with privacy within Ethereum? Without a private bridge, privacy will be within the IBC ecosystem, so Ethereum users could use the MASP and use their shielded assets within the IBC ecosystem, but to also keep the privacy and go back to Ethereum and use their shielded assets within the Ethereum ecosystem a private bridge would be required? The trustless Ethereum bridge that Namada was building was transparent? What are the plans for this bridge and can it be made private? To attract ETH and Ethereum assets in the MASP I think this is important, because Ethereum users may want to use Namada to get privacy within their Ethereum ecosystem, but maybe they are not so interested to onboard or use their shielded ETH within IBC?
I am currently working on Namada Desktop and Mobile Wallet, GitHub - chimmykk/Namada-SDK: A Rust implementation of a Namada SDK featuring functionalities to transfer, create, derive, and import wallets
Built with Namada Rust SDK, using Tauri for Desktop
and Mobile Application ,
If you would like to contribute you’re welcome
We will post some update more often as we go!
There have been a slow progress as i am only the lead dev working on it,
I am gathering my fellow from Uni to help me complete it,
Expecting it to be done by Mid December, with basic functionality of shielded transfer, transparent , IBC.
Hopefully can add more features as we go forward,
Below are some basic UI/UX of the Application
Please ignore the address and dummy data for now
Planning to integrate with Backend and show some update in next few days!
That’s awesome!
It’s great to see you working on a mobile app. This will definitely help onboard more users and open up exciting possibilities.
Can’t wait to try it out!
Let me know if you need a beta tester
Sure, will do! Once we roll out the development process
Hey Ruslan,
I hope you’re doing great!
Have you finally started working on a multisig management interface?
@cwgoes there is a discussion in the Cosmos hub forum about private/consortium blockchains. If for example several financial institutions have their own consortium/private blockchains, if they connect with IBC could they use Namada to transfer assets/data with privacy outside their private/consortium blockchain to other public or private/consortium blockchains within the IBC ecosystem?
@cwgoes with IBC Eureka (IBC v2) there wouldn’t be a need for a trustless Ethereum bridge or bridges to Solana or other VM L1s, it would be directly connected via IBC v2? This would mean then that any IBC v2 asset could use the MASP like all current IBC classic assets? Would this mean also that Ethereum L2s could have interoperability amongst themselves and also with the IBC classic and IBC v2 ecosystem? Also would IBC v2 only support fast finality consensus chains meaning IBC v2 wouldn’t yet offer an IBC v2 connection to Bitcoin?
Also, a key issue before was offering private bridges but with IBC v2 it could just be like classic shielded IBC which means no need for private bridges if there is shielded IBC v2?
Edit: it seems that IBC v2 could also support probabilistic finality chains like Bitcoin. Initially when it launches in Q1-Q2 2025 it will support only Ethereum L1, for the L2s fraud proofs are still required and for other L1s like Solana seems more work is needed also