UP Publish Implementation

A Universal Profile is a proxy that delegates everything to an implementation (LSP0 for the profile, LSP6 for the Key Manager). Profiles created with different contract versions point to different implementations: if your profile's one does not exist on the target network, the profile would be "mute" there. LUKSO published its implementations through Nick's factory (0x4e59b448…4956C), a deterministic deployer that lives at the same address on almost every EVM network: replaying the exact same transaction on the target network creates the implementation at the exact same address. This page reads the original transaction from LUKSO, mathematically checks that it produces the expected address, and has your wallet sign it. The same applies to the infrastructure contracts used by the deploy, such as the LSP23 factory (0x2300000A…) or the post-deployment module: if LUKSO published them through Nick's factory, this page publishes them the same way (otherwise it says so). The same goes for ChainIntegrate's NFT reception extension (0x7F68e744…C03e), used by the "NFT reception on the UP" page: it is published on LUKSO through Nick's factory and is published the same way, by choosing it below. It is permissionless and harmless: anyone can do it, it gives nobody any control over any profile, and it only costs gas.

Usually found automatically. If not: open the contract address on the LUKSO explorer, Details tab, and copy the hash of the "at txn" link in the Creator row.

Only needed if the page cannot read the transaction from either the RPC or the explorer: on the LUKSO explorer open the creation transaction and copy the "Raw input" field (it starts with 0x). It is safe: the page mathematically checks that this data produces exactly the implementation address, and any other data is rejected.

Any account with a little gas on the target network: it only pays for the transaction and gets no permission on anything.