Challenges
#BUIDLathon 2023 Infrastructure + Scalability
We allow users to perform all transaction anonymously in the network via a wallet that can only be executed from a valid zero knowledge proof. And so, the owner of the wallet will be able to remain anonymous will performing the transactions on chain
Anything Snaps ?
We utlize Metamask Snap to allow user to directly perform transaction from our snaps. Our snaps will be responsible in: 1. Importing the Facade Wallet address to initiate our Snap process 2. generate proof via wasm circuit 3. notify zkWallet owner should a proof has been signed by other owners of the same wallet. This process is done via cron job of metamask snap. 4. submit proof to Facade Wallet via our relayer that we have run on our own server
Best Multi-Network Deployment using Infura
Our relayer service also creates the smart wallet anonymously for users and we utilize Infura to deploy to multiple networks
Best Use of Polygon
We utlize the cheap execution fee to verify the groth16 proof which would be expensive to do so on Mainnet
Deploy your Dapp on Infura with MetaMask and Truffle Dashboard
We uses infura in our relayer service as our RPC provider to send proofs to Facade wallet
Deploy a Dapp on an L2 using Infura and Truffle
We use Truffle for our smart contract development and we use Infura as our RPC provider in our relayer serviceWe
Build a MetaMask snap using the Truffle Snaps Box
We use Truffle for our smart contract development and utilizes the Metamask snap template to scaffold for our Snap project
Security 🔒& Scalability 🌱
We allow users to perform all transaction anonymously in the network via a wallet that can only be executed from a valid zero knowledge proof. And so, the owner of the wallet will be able to remain anonymous will performing the transactions on chain
Applied ZK, with a side of Scroll
We allow users to perform all transaction anonymously in the network via a wallet that can only be executed from a valid zero knowledge proof. And so, the owner of the wallet will be able to remain anonymous will performing the transactions on chain. We utilize the cheap execution fee to verify the groth16 proof which would be expensive to do so on Mainnet
MetaMask Snaps - Identity 🪪 & Communication 💬
We utlize Metamask Snap to allow user to directly perform transaction from our snaps. Our snaps will be responsible in: 1. Importing the Facade Wallet address to initiate our Snap process 2. generate proof via wasm circuit 3. notify zkWallet owner should a proof has been signed by other owners of the same wallet. This process is done via cron job of metamask snap. 4. submit proof to Facade Wallet via our relayer that we have run on our own server
Deploy your smart contract on Scroll
We utilize the cheap execution fee to verify the groth16 proof which would be expensive to do so on Mainnet
Project details
Smart wallets these days do not have the ability to 'hide' the owners that are responsible for making the transaction through it. This allows anyone with abit of Etherscan knowledge to track the Eoa's that are responsible for all transaction made by that smart wallet. if the smart wallet possesses a large amount of assets, this may pose a life hazard towards the real owners as malicious actors may target the owners and threaten them to obtain their assets.
These are problems that could be avoided should the owner of the smart wallet be unknown from the start. The current status quo for transferring assets anonymously will be to use Tornado Cash or similar mixer protocols to blind the traces of the transaction. This method works but only limited to asset transfers. What if, we would like to extend to that capabiliy? What if we also want to interact with various smart contract anonymously such as defi protocols....
Facade Wallet aims to achieve that. We allows owners to perform all transaction as would a normal Multisig Wallet but anonymous by default. Using the power of zero knowledge proofs, the owner will generate the proof locally, proving that the owner has signed a transaction call data correctly as well as also proving the ownership of the wallet.
The proof is then passed on to a relayer and the proof contains reveals the transaction call data which will then be executed by Facade. Inputs such as the owner of the wallet and the signature are either encrypted or passed in as private inputs to the circuit.
The wallet, upon receiving the proof, will verify the proof and if correct, execute the transaction call data as would a normal smart wallet, thereby allowing a transaction to be performed anonymously.