Features
Another Layer of Security
With using another device, your users have another key share / signature at their own disposal and you can set the security threshold for transactions within your dApp higher
The crypto version of your bank's TAN app
Just like you know it from the bank of your choice, your customers will get a white-label app, to confirm crypto transactions they initiated in your dApp.
Tech Stack Diversification
You lower the risk scenarios by using another tech stack addition to the account abstraction stack of your choice. This ensures, that even in case of a bug or a hack of that stack, your customers will still have access via a second route
The crypto version of your bank's TAN app
Just like you know it from the bank of your choice, your customers will get a white-label app, to confirm crypto transactions they initiated in your dApp.
Another Layer of Security
With using another device, your users have another key share / signature at their own disposal and you can set the security threshold for transactions within your dApp higher
Tech Stack Diversification
You lower the risk scenarios by using another tech stack addition to the account abstraction stack of your choice. This ensures, that even in case of a bug or a hack of that stack, your customers will still have access via a second route
How it works
Step 1
/Initiate
The user initiates and signs a transaction in your dApp
Step 2
/AI Check
The transaction is checked and simulated to find and prevent vulnerabilities
Step 3
/Confirm
The user confirms the transaction within in the white-label mobile app
Web3Auth compatibility
2nd Signature addresses all web3 startups that have build their dApps on account abstraction technology.
You can increase your and your customers’ security by adding a key share (web3Auth) or signer (SAFE SDK), that resides on an additional device and can only confirm (but never initiate) transactions.
You will be able to offer your customers a mobile white-label app, fully branded according to your specs and that works like your banking TAN app.
Upon initiating a transaction in normal flow of your dapp and signing it, the 2nd signature app is triggered and your customer will see a pop-up prompt giving them all relevant transaction data and asking them to confirm or reject the transaction. If confirmed, the transaction is then processed according to the rules set forth by your account abstraction rules.
