Skip to content

Commit

Permalink
Merge pull request #41 from lukso-network/link-controller-fund-pages
Browse files Browse the repository at this point in the history
Update controller fund guide
  • Loading branch information
Hugoo authored Jan 23, 2024
2 parents 76a1a0d + d8dceed commit 22a1cd2
Show file tree
Hide file tree
Showing 3 changed files with 20 additions and 8 deletions.
20 changes: 19 additions & 1 deletion docs/extension/guides/fund-controller.md
Original file line number Diff line number Diff line change
Expand Up @@ -52,6 +52,24 @@ If you are using a regular wallet, [add LUKSO](https://docs.lukso.tech/networks/

:::danger Importance of Backups

If you continuously use your funds to send transactions on various extensions, we highly recommend always saving the private keys of the extension controllers. You can display and copy them by _revealing the private key_ within the _Settings_ screen. This backup is essential as every extension has an individual controller. If you import or recover the profile without saving the previous private key, you cannot [get back your controller funds](./get-controller-funds.md) after.
We highly recommend to only send small amounts of LYX to the controller of your extension and ensure to **save their private keys**. You can display and copy them by _revealing the private key_ within the _Settings_ screen. This backup is essential as every extension has an individual controller. If you import or recover the profile without saving the previous private key, you cannot [get back your controller funds](./get-controller-funds.md) after.

:::

Once the extension's controller is funded with LYX, you can select it within the transaction screen of the Universal Profile Extension:

<div style={{textAlign: 'center'}}>

<img
src="/img/extension/transaction-controller-setting.png"
alt="Transaction Controller Setting"
width="400"
/>

</div>

:::success Default Payment

Once your funded controller is selected in the extension, it will stay as default payment option for transactions until its changed back to the Transaction Relay Service.

:::
8 changes: 1 addition & 7 deletions docs/general/common-errors.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,10 +16,4 @@ This error occurs if a user deployed his Universal Profile through a 3rd party p
width="400"
/>

To **solve this issue**, users have to add a new controller to their Universal Profile. This controller must then be funded with LYX to execute transactions without any Transaction Relay Service. Within the transaction screen of the Universal Profile Extension, users can then define the controller they want to use like in the following picture:

<img
src="/img/general/transaction-controller-setting.png"
alt="Transaction Controller Setting"
width="400"
/>
To **solve this issue**, users have to [**fund the extension's controller**](../extension/guides/fund-controller.md) with LYX to execute transactions without any Transaction Relay Service. Within the transaction screen, users can then select to use their own controller's funds.

0 comments on commit 22a1cd2

Please sign in to comment.