Utility for your NFTs
If you own BAYC #1234, anyone can send you ETH and NFTs with 1234.bayc.pfp instead of your address. If you own the NFT, you own the .pfp.
If you own BAYC #1234, anyone can send you ETH and NFTs with 1234.bayc.pfp instead of your address. If you own the NFT, you own the .pfp.
.pfp is live experiment on mainnet ethereum. Let's see what's possible.
1) Use a burner wallet with nothing worth stealing in it
2) Connect your wallet
3) Click the Send NFT or Send ETH tab
4) Send something
5) Verify it sent with etherscan
6) Tweet about it
CHECK THAT THE TRANSACTION IS CORRECT BEFORE APPROVING
Please use small values, this is in the testing stages
CHECK THAT THE TRANSACTION IS CORRECT BEFORE APPROVING!
Every NFT has an owner and a token ID. The .pfp smart contract creates a routing layer that uses an NFT's project name, address, and token ID's.
By using information already present in the ERC721 token standard,
one transaction can create addresses for every NFT in many collections.
As a proof of concept I've routed 72 NFT collections and created over 800,000 unique addresses in this single transaction
for 2.2 gas per address!
1.bayc.pfp - 9999.bayc.pfp
1.avime.pfp - 9999.avime.pfp
--insert 69 other projects here--
1.mfer.pfp - 10020.mfer.pfp
Since the NFT's native ownerOf(id) function is used, if you send the NFT to a new address, it automagically updates.
Currently, you can send NFTs to other .pfp addresses from this website. Large institutional players aren't interested in integrating experimental projects into their
platforms. There will be a lot of friction getting the likes of Opensea or Metamask to integrate .pfp.
It may never happen...
I think this idea has alot of potential. If you see the value and want to see it developed further, please:
- Follow and like/retweet .pfp content on twitter
- Tweet at users who flex their PFPs
- Spread the word to NFT bag holders
