This page operates on a UP that is already deployed on a
network other than LUKSO — it's not the same as just connecting the UP extension. The UP itself doesn't sign
transactions on another network: the one signing is the controller wallet (e.g. MetaMask) connected to that
network, with the right permissions on the UP. That's why the page asks for two separate connections: (1) connect
your UP only to read its address conveniently — no signature here; (2) connect MetaMask (or another wallet) on the
destination network where you redeployed the UP, and that wallet is the one sending the test transaction.
1 · Network to operate on
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.
2 · Profile to test
Not connected.
Only used to read the UP address — no signature
or transaction happens at this point. If you want to test a UP other than the one connected in your extension, you
can enter its address manually below.
3 · Signing wallet (the controller)
This is the wallet that actually operates the UP 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.
Not connected.
4 · Test
Writes a test key (up.test.ping) with a unique value,
then reads it back on-chain to confirm. Doesn't touch existing data, doesn't require funds on the UP — only gas
for the transaction from the signing wallet.
