Over the last couple of months, I have transferred more than 1,000 NFTs from my 6529 hardware wallet to the 6529 Museum gnosis multi-sig
Improvements can be made...
2/ I am pretty sophisticated and pretty careful and I spent most of the time terrified that I would fumble a cultural grail and, like the dead ringers, send it into the ether
3/ Right now the transfer function on all major marketplaces is absolutely a raw, naked, unassisted transfer.
You put an ETH address in a box and off you go.
If you screw it up, well, sucks to be you.
4/ What can go wrong?
a) you paste the wrong address
b) you accidentally hit a key and mess it up
c) you have malware overwriting your copy paste
d) you get socially engineered
e) other fun attack vectors
5/ Fortunately, the sites can fix this easily with a 2 step process as follows 🙏
Page 1: You enter the address, either by copy-pasting it in or selecting from your address book of addresses that you have sent to before
Then you go to page 2 (confirmation page)
6/ Page 2: The site pulls confirmation data of the receiving address to help you before you hit transfer, such as:
a) ENS name
b) OpenSea (SR, FND) acct name
c) how many times you have transferred to it b4
d) Images of what is in that addresses
7/ Most people transfer among their own addresses so these prior activity indicators would all but eliminate errors in my opinion.
If I saw that I was transferring to OS/6529Museum and I have transferred 1,000+ NFTs to this address before, I would feel pretty good
8/ The difference between usability and "where we are today" is 100 industry wide actions like this.
Software should be our careful friend here, checking for us before we hit 'submit' that everything looks normal.
We should view every lost BAYC as an industry failure
9/ It is not normally societally acceptable to make a small error and lose $1M.
So we need to treat every lost/stolen NFT as an NFT industry manufacturing defect to drive out of the system so everyone does not end up on Meta in the end.
10/ The answer here is mostly software. The underlying platform is permissionless and unforgiving.
There is no macho pride in reading ETH addys character by character. Software is great at boring stuff like this
11/ As NFTs are about to go parabolic into normie land, every platform should have a specialized front-end team with no other responsibility than providing affordances to reduce user error (like the ones above).
And their OKR should be user errors/month/100K users.
LFG 🙏🚀
12/ See my exchange with @fluffypony below re malware.
And if here for the first time, more about an open metaverse here:
The short answer is that "yes, in fact we want them to come, so long as it is on decentralized blockchains"
I know this is going to disconcert some of you, but bear with me for the thought process.
2/ Let's start by going to the future.
In 10 years, we will have digital objects all around us - in augmented reality, in virtual reality and on 3D (and 2D) websites.
It would make a lot of sense for those objections to be persistent and cross-application.
3/ In other words, it would make a lot of sense to be able to take your, say, Fidenza or Toadz from one application to another:
- galleries
- metaverses
- social networks
- marketplaces
- valuation sites
Have you ever thought about this in the non-NFT world?
It is basically an unsolved problem, as far as I can tell.
Let's work through an example:
2/ Let's lay out a scenario to make it real:
a) You are, say, 30 years old and will pass away at 80, halfway through this exercise
b) You have a 1 year old.
c) Your 1 year old will have a kid at 30 and pass away at 80.
d) Your grandkid will be 70 years old in 100 years
3/ What are we trying to preserve?
Let's keep it simple - the few tens of thousands or hundreds of thousands of digital photographs you have taken over the years.