In this version, I focused solely on technical updates, including:
Removing the deprecated OpenBrush library from the WASM smart contracts and migrating the contracts from ink! v4 to ink! v5.
Migrating the Phala Contracts (also known as Phat Contracts) to the new version of Phala Contracts, i.e., Agent Contracts in Phala Cloud.
I plan to perform the migration on Astar Network within the next two weeks. This process will be fully transparent to users, and all unclaimed rewards will remain available for claiming.
Looking at the contracts history (already more than 2 years!), I’m pleased to note the dApp has follow all evolutions in dApp Staking and is composed of multiple contracts, each now implemented using a different version of ink! (v3, v4, v5).
This may not mean much to the user, but I can assure you that, from a technical perspective, it is far from trivial.
In the future, depending on community support, we will decide whether to continue evolving the contracts in line with upcoming functional updates of dApp Staking or with technical updates of the underlying technologies (ink! contracts, Phala Cloud, SubQuery indexer).
Please don’t hesitate to reach out if you have any questions or need further details.
Since Lucky is running on Wasm, it likely won’t work directly on an EVM like Soneium. Also, splitting reward payout pools would be inefficient, so if it’s all within the same money flow, it’s better not to create multiple pools.
If Lucky does something on Soneium, they’ll need to come up with a different new product.
This isn’t an issue if the funding sources are separate, as with Shiden or Astar.
Thanks for the reports, Gui. Most of us are familiar with you and the Lucky dApp. We’d like to see it in better places. Would you consider partnering with Soneium projects in the future? I’m sure it would help increase your visibility.
Hello,
I’m glad to announce that the technical update has been successfully completed.
The main smart contract has been migrated to ink! v5, and the worker has been successfully deployed on Phala Cloud, a trustless infrastructure for verifiable off-chain computing and AI agents, powered by TEE.
Everything is running smoothly, except for raffle 1153, where a parameter in the smart contract was set incorrectly. As a result, the winner of era 1153 received 0.000000000000000053 ASTR instead of 53 ASTR.
We have transferred 53 ASTR to the winner to resolve this issue : Subscan | Astar Extrinsic Details
Regarding migration or expansion to Soneium, the Lucky dApp is built on top of dApp Staking and is intrinsically tied to it.
This means we will not be able to deploy the dApp on Soneium unless dApp Staking itself is also available there.
However, we have already built another dApp named Lotto, which is deployed on Astar L1 (ink! contracts) and Soneium (EVM contracts).
Currently, we are working on a Proof of Concept — Guess The Number — developed with ink! v6 and deployed on PolkaVM.
If the community is interested, we could deploy this dApp (Guess The Number) or other small games (user vs AI) on Soneium.
The library enabling communication between smart contracts, and off-chain computing/AI is already developped.
Makes sense, Lucky staying tied to dApp Staking is clear, but it’s great that you already have Lotto live on both Astar L1 and Soneium. The Guess The Number PoC sounds like a fun way to showcase ink! v6 and PolkaVM too. Small interactive games could be a nice way to spark more community engagement on Soneium.