Inspiration
Traditional single-signature wallets can be vulnerable to unauthorized access and potential loss of funds if the private key is compromised. By implementing a multisig wallet with multiple signatures required for transaction authorization, you add an extra layer of security. This solution helps mitigate the risk of a single point of failure and enhances the overall security of the wallet.
What it does
MultiSig wallet, leveraging LIT PKPS, FVM, Polybase and Axelar, offers an added layer of security and control by requiring multiple signatures for transaction authorization. This unique combination allows users to create MultiSig wallets using their Google accounts with web3 wallets like MetaMask, resulting in heightened security and increased control compared to traditional single-signature wallets. Additionally, Axelar facilitates seamless token transfers across different blockchains, further enhancing the wallet's functionality and interoperability.
How we built it
MultiSig was built by using LIT PKPS with Google oAuth2.0, Axelar, Polybase and FVM.
Built With
- axelar
- fvm
- lit
- nextjs
- polybase
- solidity
Log in or sign up for Devpost to join the conversation.