Andromeda Web Application
  • Introduction
    • Overview
    • ADO Builder
    • App Builder
    • Assets
    • App Store
    • CLI
  • Learning the Basics
    • Setting Up your Wallet
    • The Token Standards
      • CW721: Non-Fungible Token (NFT) Standard
      • CW20: Fungible Token (CW20) Standard
    • Using Execute Messages
    • Using Queries
    • ADO Ownership
  • Guides and Examples
    • ADO Builder
      • Building Your First App
      • Building your First NFT Collection
        • Setting Up NFT Metadata
      • Creating your First NFT Auction House
      • NFT Marketplace App
      • Crowdfund App
      • CW20 Exchange
      • Auction Using CW20 Tokens
      • Extended Marketplace
      • Commission Based Sales Application
      • Vesting and Staking App
    • App Builder
      • NFT Auction Marketplace
    • Embeddables
      • NFT Auction
    • Using CLI to Interact with Apps
    • Importing/Exporting Data
  • Staking
    • Andromeda Staking
  • Data and Statistics
    • Tokenomics Dashboard
Powered by GitBook
On this page
  • What is ADO Ownership
  • ADO Ownership Transfer
  • Disown an ADO
  1. Learning the Basics

ADO Ownership

PreviousUsing QueriesNextADO Builder

Last updated 8 months ago

In this section, we will be looking ADO ownership, what it means, and how it can be transferred from one user to another.

What is ADO Ownership

In case of Apps, the user address creating the App will receive ownership over all the components.

Whenever an ADO is created, it registers an owner address inside the ADO's state. By default, this ownership is assigned to the address that has created the ADO. This owner address is the only address allowed to call the owner restricted execute messages on the ADO. These messages are usually used to set up the ADO or update it's state. An example would be updating who receives funds from a splitter.

ADO Ownership Transfer

In some cases, a user might want to transfer ownership to another user/address. All our ADOs have this functionality built in, allowing an owner to send a request to another user for ownership transfer. Whenever the request is sent, the second user needs to accept the request for the transfer to occur. This is to prevent users from sending unwanted ADOs to other users without their permission.

Let us go through a small example of tranferring an ADO to another address. In the ADO Builder, create a new App with any component:

Now after publishing, go to the assets page, and from the list of execute messages, select "Ownership":

This will open up the ownership panel:

To send a transfership request, select "Update Onwer". Here we can specify the following:

  • Expiration: Specify the time when the request expires. After it is reached, the second user can no longer accept ownership of the ADO.

Ideally, use another one of your Keplr wallets as the new owner. This will allow you to test the full process easily.

  • New Owner: The address you are sending the request to.

Once these are specified, you can publish the message. This will take you to the asset view for the component:

You can also access this page through the main assets, by clicking on the eye symbol for the component then selecting "more info".

In order to complete the transfer, we need to accept the offer using the address that we specified as the new owner.

The easiest way to do this, is to share the URL of the asset page of the component. When the second users pastes it into their browser, they will get the following:

You can check out the "Executing on non-owned ADOs" section for more ways to do this.

An easy way to test this would be using 2 of your Keplr wallets and simply switching between them.

You can notice a small tag in yellow next to the ADO type that sais "External ADO". This signifies that the ADO you are viewing is not owned by your connected address. Now lets change that by accepting the ownership request we have sent to this address.

Select "Modifiers" and then "Ownership" like we did earlier. Then select "Option 1" and from the dropdown list, select "Accept Ownership":

If you are looking to transfer ownership of an entire App, you would need to do this on every component, including the App component itself.

You can also find a "Revoke ownership offer" message. This can be called by the original owner to remove the offer for the ADO transfer. Can only be done before the new owner has accepted the offer.

Once published, the ADO ownership transfer is complete and this address is now the new owner of the ADO. Looking at the assets page, we can see that the timelock is now in the new owner's assets:

As we did not transfer the App, make sure the asset filter is not set to Apps as that is the default for it. Otherwise the ADO will not show.

Disown an ADO

Another option that users have, is to disown an ADO. To disown an ADO, means to relinquish ownership from that ADO forever, making it impossible for anyone to ever own it again.

This can be used in cases where the owner of an application wants to ensure the users that the configurations of the ADO will never be changed ever again. Whether that be the % royalty on NFTs or a fee taken by the ADO, once the ADO is disowned, these will remain the same forever.

Disowning an ADO does not mean that it will no longer function, but all owner restricted messages can never be called ever again.

To disown an ADO, we also use the "Ownership" execute message and select "Option 1" and then the "Disown" option from the dropdown:

Once published, if you select the eye symbol for the ADO from the assets page, you will notice the owner address is now "null":