NFT reception on the UP (experimental)

Let your Universal Profile receive ERC-721 and ERC-1155 NFTs on a network where you redeployed it (for example purchases on OpenSea).
Home

0 · How it works

When a standard NFT is delivered with a "safe transfer", the token contract asks the recipient whether it can receive it. A UP answers only through an extension (LSP17) registered in its data; redeployed UPs usually have none, so purchases fail ("wallet cannot receive").

This page: (1) if needed, takes you to the publishing page to publish on the network the NFTReceiverExtension, a minimal contract with no owner, data or funds, always at the same address on every network; (2) registers it on the UP with a single atomic Key Manager transaction: it grants the controller the permission to add extensions, registers the extension, and sets the controller's permissions back to exactly what they were. If any part fails, nothing changes. Before signing you see the list of operations and the simulation result.
⚠️ Read before using this page

1 · Network

2 · Your UP

3 · Controller (MetaMask) and check

MetaMask with the UP controller's key, on the chosen network. It pays the gas. The check starts by itself and runs again if you change network, UP, account or MetaMask's network.
The check starts by itself once network, UP and MetaMask are set.

4 · Actions

If the extension does not exist on this network yet, the page gives you the link to the publishing page: there anyone can publish it, with any wallet and without a UP; it only costs gas and gives no control over any UP. Then, here, with the UP's controller you prepare the enabling: the page shows every operation and simulates it; only then can you sign.
No operation prepared.