You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Team name: Cryptinsurance Team members: @AccentSandeep@Heggz@MikeStale Team leader:@Heggz What problem are you trying to solve?: 'Fat finger' mistypes can be a big issue for new users who start sending transactions on the Ethereum network. The lack of checksums for addresses can mean that significant amounts of Ether may get sent to random or non-existent accounts. We propose to create a smart contract users can opt in to which allows them to insure against mis-typed addresses whether in the hex format, or as an ENS address. Why do you think Blockchain/SmartContract may be the right approach?: Since the problem is already based on a blockchain, it makes sense to insure it on a blockchain using an automated smart contract which can check for close differences between the intended address and mistake address sent to.
API/DATA/Gadget you are thinking about using: N/A
What area do you need help on?: Insurance expertise
The text was updated successfully, but these errors were encountered:
Team name: Cryptinsurance
Team members: @AccentSandeep @Heggz @MikeStale
Team leader: @Heggz
What problem are you trying to solve?: 'Fat finger' mistypes can be a big issue for new users who start sending transactions on the Ethereum network. The lack of checksums for addresses can mean that significant amounts of Ether may get sent to random or non-existent accounts. We propose to create a smart contract users can opt in to which allows them to insure against mis-typed addresses whether in the hex format, or as an ENS address.
Why do you think Blockchain/SmartContract may be the right approach?: Since the problem is already based on a blockchain, it makes sense to insure it on a blockchain using an automated smart contract which can check for close differences between the intended address and mistake address sent to.
API/DATA/Gadget you are thinking about using: N/A
What area do you need help on?: Insurance expertise
The text was updated successfully, but these errors were encountered: