UP Send Funds

This operates on a UP that is already deployed on a network other than LUKSO — the UP itself doesn't sign this transaction. The one signing is the controller wallet (e.g. MetaMask) connected to the destination network, with the TRANSFERVALUE (native currency) and CALL (tokens and NFTs) permissions on that UP. That's why there are two separate connections here: (1) connect your UP only to read its address conveniently — no signature here; (2) connect MetaMask (or another wallet) on the network where the UP was redeployed, and that wallet is the one signing the funds transfer.

The network where your UP was redeployed (not LUKSO). The signing wallet from step 3 must be connected to this same network — the status in step 3 shows the wallet's current network, check it before proceeding.

Only used to read the UP address — no signature or transaction happens at this point. If you want to operate on a UP other than the one connected in your extension, you can enter its address manually below.

This is the wallet that actually signs the funds transfer, on the network chosen in step 1 — it must be connected to that network, not to LUKSO. It's normal to have both the UP extension and MetaMask active in the browser at the same time: use the right one for each step.

💡 Funds: two addresses, both yours
• Your UP address (the same on every network) is your account: send funds to it only after the deploy and the test on this network have succeeded: if something goes wrong (wrong controller key, failed deploy) funds sent earlier would stay stuck.
• The controller address (the wallet in MetaMask) is the key that signs. Every operation costs a small fee (gas), and the controller pays it, not the UP.
👉 So send some funds to the controller too, on the same network (e.g. POL on Polygon, ETH on Base or Arbitrum): enough for a few transactions. Without them the controller cannot sign anything, even if the UP is full.