14 lines
1.6 KiB
JSON
14 lines
1.6 KiB
JSON
{
|
|
"HubID": "2181",
|
|
"Date": "3/27/2023",
|
|
"HubTags": [
|
|
"External Platform Posts"
|
|
],
|
|
"Contacts": "",
|
|
"Companies": "",
|
|
"File": "",
|
|
"Image": "",
|
|
"Summary": "#web3 wallets are too insecure at present and if I hold all my #nfts in one account, the risk to getting drained is too high. Might an solution emerge through #accountabstraction ? Here's my thoughts.",
|
|
"Notes": "<p>#web3 wallets are too insecure at present and if I hold all my #nfts in one account, the risk to getting drained is too high. Might an solution emerge through #accountabstraction ? Here's my thoughts.</p><p>I consider myself pretty web3 wallet savvy but was rugged once because I clicked the wrong link. The loss was really low because as a practice, I send all my NFTs and assets to cold wallet accounts that I never use to transact. I use a transaction account to do my buying and selling via a hot wallet and only keep in what I need to execute the transaction.<br /></p><p>But this process I use offers a very poor user experience, adds costs, friction, time. Plus, what makes the UX much worse is that to interact with services that look into my wallet to confirm I own an NFT, I have to give them access to my holding account, which I am loath to do because it presents a security risk.</p><p>The better thing is some sort of account proxy using #zk proofs that will synthetically allow me to represent what I own via my transaction account.</p><p>I have seen proposals for this but nothing emerged yet for mainstream use.</p><p>Perhaps via #accountabstraction we will see this being implemented.</p>"
|
|
}
|