We need to move to fully on-chain, non-custodial, rug-free,…
We need to move to fully on-chain, non-custodial, rug-free, and interoperable ecosystem
In our wallet files (json for example) we should be able to configure socialName and avatarURL as fields (as we do in Panda wallet)
Except Panda should preserve these fields in the json file
So when you import back into Panda or SHUAllet, the socialName and avatarURL are set immediately so you truly own your social data on-chain
We then extend this with .OG and verified PFPs via those same fields or different ones
If I set my OG or name to 79.og, then the app/wallet checks if I own that inscription. Then my OG is verified, across all apps and wallets
Same for PFP, if my avatarURL is set to an inscription txid that I own in my wallet, then my PFP is verified.
Replies
[[treechat inspiration]]
Yessss
if i could lock i would lock, simple
yesss!
I give PandaWallet permission to charge me a fee to lock/stake my wallet, so as to make it a profitable service for them. Say 2 BSV locked for 10,000 blocks, with a notification to withdraw or re-stake at 9,500 blocks.
Wells Fargo has recently started charging me $25/month for a checking account. That totally makes sense to me. If the wallet/account is to be Private, and the funds to be used at your discretion and not as investment collateral for the bank, then it makes sense to stake/entrust that with a monthly payment. Let's everyone know you're not FTXing fools.
Maybe wallet file could have a reference to a txid that contains meta data (saved using b:// protocol?), such as socialName and avatarURL, which verifiably originates from the wallet.