Astar Network connects you to web3. It is the gateway for projects across enterprises, entertainment & gaming in Japan and beyond, driving global adoption and delivering web3 to billions. Astar leverages a multi-layered tech stack powered by Polygon and Polkadot to offer customizable blockchain solutions that accelerate web3 adoption. With zk-powered Ethereum L2 Scaling (zkEVM), EVM, WASM, and a cutting-edge ecosystem, Astar delivers robust, secure, and interoperable web3 technology.

Hooon

Astar Admin

eth-balance

balance-of

Astar Network

Hello, please find the discussion in forum here:&nbsp;
<a href="https://forum.astar.network/t/lucky-dapp-update-the-dapp-owner/7227">https://forum.astar.network/t/lucky-dapp-update-the-dapp-owner/7227</a>
&nbsp;
Because the Lucky dApp is 100% automated and technically decentralized via smart contracts on Astar Network and Phala Network, the current owner of the dApp is a smart contract.
&nbsp;
It&rsquo;s been like this since we registered Lucky in the dApp Staking. Indeed, in the dApp Staking V2, developer rewards were always sent to the dApp owner.
&nbsp;
However, the dApp owner is also the address granted to update the description of the dApp in the Astar Portal. This is why we never updated the description of the dApp from the beginning.
&nbsp;
With the dAppStaking V3, a new concept has been introduced: the beneficiary. This means we can seperate the owner of the dApp and the beneficiary of the rewards. For Lucky, the beneficiary of the rewards will always be the wasm smart contract, to remain 100% automated and technically decentralized. But to update the description of the dApp in the Astar Portal, the Lucky team address (ZjyoCabAjvNo9Evx1jc4Kysi3mG5ynchMcn6JPkR5c4SiYh) must be the dApp owner (until the chain extension for dApp staking is available and the Lucky governance is also decentralized).
&nbsp;
To update the dApp owner of the dApp in Astar, we have to call the setdappowner method in the dapp_staking pallet with the following parameters on Astar Network:
Wasm smart contract: ZSV1GVepvmWFdshMWgczS4zYvmmwEsBjWQjN4WDpUEFRRPy
New owner: ZjyoCabAjvNo9Evx1jc4Kysi3mG5ynchMcn6JPkR5c4SiYh
encoded call data: 0x2203019af6e0a491173f73b570b4b4e0c04f319f496bcc3650da8166b39f42e056996ea84ef8c0efdd519e001cb3f5b6351725178283edf1b122a464f0a0f425699759
&nbsp;
Normally, this call must be run by the dApp owner (ie the smart contract). Because there is no chain extension for dApp staking in wasm smart contracts, the smart contact cannot call this extrinsic. That is why I created this proposal to request to call this extrinsic with sudo/root privileges.
&nbsp;
It was sucessfully tested on Shibuya and Shiden few months ago. This proposal is to run the extrinsic call on Astar Network.
&nbsp;

- **Problem Statement:** Updating the dApp owner for Lucky dApp in Astar Network to separate rewards beneficiary and description updater.
- **Significance:** Ensuring 100% automation and technical decentralization while allowing for dApp description updates.
- **Proposed Solution:** Requesting sudo/root privileges to call the setdappowner method in the dapp_staking pallet with specific parameters.
- **Expected Outcomes:** Successful execution of the extrinsic call on Astar Network for dApp owner update.