Open erinredwing opened 4 months ago
Hi Erin,
The only half-way decent solution that I can think of is to either use sns or create a similar standard to hold this linked information. You could do this today with sns by adding an about:
field with something like airdrop address: bc1p2wmz0qurl7hkrmapjuavtwk0gnd7eahk2lucyj2lh4gxp6vxxxxxxxxxxx
and hold that inscription in your more secure wallet to create the link.
The problem with this is that you rely upon the airdropper to a) know to check for something like this and then, b) use the address it finds instead of the one they already know for you.
What do you think about this type of a solution?
a simple metaprotocol would suffice where you explicitly declare an address as owned by you and then respond from that address with a similar transaction. this could be delegate inscriptions using metadata and metaprotocol fields. could be fortified with signatures added. would need to be a standard so ecosystem adopts it.
I want to be able to link an address with another address such that someone can see that two addresses with inscriptions in them are associated with each other.
I could see this being useful for things like airdrops, where people want to store their valuable inscriptions in a more secure wallet, but then have a browser extension wallet where they would receive airdrops associated with the secure wallet/address.