A dapp maybe not with an innovative idea at its base, but that could become one with time and a correct use of technology to reach a goal.
The reports are constant and frequent, this is what everyone should do, thanks for your updates. This deserves
Hello,
The Lotto Dapp V2 (multichain version) is available on the following testnets:
- Minato (Soneium testnet),
- Moonbase (Moonbeam testnet),
- Shibuya (Astar testnet).
https://lotto-evm.netlify.app/
Feel free to play with it and give us your feedback.
If you want to know more about Lotto Multichain dApp, you can watch this video :
https://youtu.be/AB7sxpdMGxw
And this one to better understand the communication between the smart contracts:
https://youtu.be/jwdbL1Mynw8
Hi @GuiGou
I’m really impressed by the dApp you are building.
Would there be a way to get some kind of noticiation if the raffle has been closed and if you won/loose?
I think if there is a way to auto enable those noficiation through X or Telegram, a user gets reminded the next day and if you add a CTA in that notification to play again that day.
I’m just thinking about myself, that I sometimes just forgot and be reminded days later
Great progress! I’m a big fan of the Lotto/Lucky team. Keep up the great work!
I have great respect for your steady development and expansion. I am also looking forward to the deployment of Minato and the upcoming Soneium Mainnet.
Thanks @Zorounashi @AstarHood @bao @tksarah ,
It’s nice to read your messages and encouragements. It’s the result of a lot of work but the dApp is not completed yet. It is a bit like my baby that I want to see grow. And for sure, I would need your support for the future.
Thanks @AstarHood for your support and your idea.
Notification management is in our todo list but there are a lot of things to do before
It’s a good idea and I hope to implement it on the dApp.
Hello, for second second monthly report, here are the progress and completed steps between October 23th and November 22th.
I have worked 18 FTE during this period and the following steps have been completed.
-
The subquery multi-chain indexer is live on the testnets and reads data from contracts deployed on Shibuya, Minato and Moonbase.
About data coming from Minato, there is a delay (several minutes) before receiving the data. For the user experience, it could be an issue and I hope to be able to fix it. -
The UI has been updated and now handles interactions with EVM chains.
-
A beta version has been deployed on Shibuya, Minato and Moonbase.
-
This video explains the Lotto Multichain dApp: https://youtu.be/AB7sxpdMGxw
-
This version explains the interaction between smart contracts: https://youtu.be/jwdbL1Mynw8
Here are the difficulties encountered:
-
Regarding the Subquery indexer, the delay before receiving the data from Minato could be an issue for the user experience.
-
When I stress tested the communication between smart contracts, I had to face problems related to the reorg in Shibuya side (re-orgs are normal).
In this situation, the contract deployed on Phala reads data that what are not finalized and this data can be obsolete because of the reorg. This can cause problems when synchronizing states.
To fix this issue, the contract must read only finalized data. I am preparing a fix to solve this issue.
Next steps:
-
Fix the above issues
-
Improve the way to use the VRF (Verifiable Random Function) to be sure there is no way to predict the future winning numbers even with advanced tools like Chopsticks.
-
Remove the deprecated OpenBrush library from wasm smart contracts (unfortunately I couldn’t find a library to replace it) and migrate the contract from Ink! v4 to Ink! v5.
Transversal steps:
- Documentation
- Promotion and testing campaign. We are participating in LFGM campaign. It’s our way of introducing Astar to Soneium users.
- Find additional funding.
Regarding the rewards (60 600 ASTR), they are held in this wallet (Yqsi4q2qYPHhujTNqceFq5KpF6bbptHzh8U9BkVjvae6XQE) and will be used as described above when a first version will be deployed on the mainnet.
Some numbers about Lotto V1 deployed on Astar Native.
So far 20 draws have taken place. There was 13 652 participations for 1 117 different addresses. Thanks to tle LFGM Campaign!
About Lotto V2 (multichain version) deployed on Minato, there was 554 participations for 218 different addresses in two days. Again, thanks to tle LFGM Campaign!
Thank you for sharing the progress and detailed plan.
The milestones achieved are interesting, and It looks like the next steps will bring solutions to the issues. Let me know how I can contribute to your ongoing efforts.
Hello,
here is a new version of the UI: https://reorg--lotto-evm.netlify.app/
Please feel free to give us your feedback.
Thanks for sharing the updated version! The interface looks great and is easy to understand for a wide audience. Keep up the awesome work!
Thank you so much for the detailed update! It is really a big progress that has been made, including deploying the subquery multi-chain indexer on testnets and beta versions across multiple chains. Early adoption numbers look great from the LFGM campaign.
Addressing challenges like delays in data and handling reorgs effectively will further enhance the user experience. Looking forward to seeing the next improvements, especially around VRF and the migration to Ink! v5. Keep up the excellent work!
Thank you very much for the recap information. Looking at the number of participants, it seems to be a very good sign. Many people seem to really enjoy the lottery. Cheering fully for you! =)
Hello, for third monthly report, here are the progress between November 23th and December 22th.
I have worked 13 FTE during this period and the following steps have been completed.
-
Regarding the subquery multi-chain indexer and the delay to receive the data from Minato, it’s because the subquery multi-chain indexer multichain indexes only finalized blocks.
It’s the current behaviour of the subquery when the multichain mode is enabled. This issue has been reported to SubQuery Team, they are already working on it.
In the meantime, I have found a workaround and the issue is fixed on our side. -
During the communication between smart contracts, the wasm contract deployed on Phala Network now reads only finalized data to manage potential reorg issues (re-orgs are normal).
For more information, please read the previous report.
The issue is fixed now on our side. -
A new version of the UI have been deployed on the testnet: https://reorg--lotto-evm.netlify.app/
Current step:
- Improve the way to use the VRF (Verifiable Random Function) to be sure there is no way to predict the future winning numbers even with advanced tools like Chopsticks.
This development is done in 80%.
Next step
- Remove the deprecated OpenBrush library from wasm smart contracts and migrate the contract from Ink! v4 to Ink! v5.
Transversal steps:
- Documentation + tests
- Find additional funding for development and the jackpot: We have applied for a grant from the Moonbeam Foundation and opened a discussion on OpenGov: Jackpot Funding for Lotto Multichain dApp - Temp Check | Polkassembly
Regarding the rewards (106 000 ASTR) since the beginning, they are held in this wallet (Yqsi4q2qYPHhujTNqceFq5KpF6bbptHzh8U9BkVjvae6XQE) and will be used as described above when a first version will be deployed on the mainnet.
Impressive progress.
Wishing you success with the upcoming upgrades and securing additional funding.
Thank you very much for the progress update. The UI looks easy to understand and should help make it easier for people to participate in activities. I’ll wait for the complete version. =)
Full support to GuiGou.
Hello and Happy New Year to all!
The previous post in OpenGov was deleted by mistake because moderators thought it was spam.
So I recreated the discussion and after discussion with an OpenGov moderator, it should not be deleted anymore: Jackpot Funding for Lotto Multichain dApp [Temp Check] | Polkassembly
If you appreciate our work, just add a comment to show the seriousness of our team.
We are working in the Astar and Phala ecosystem for 2 years but no one really knows us in Polkadot Gov. This is why we need your support!
Even if you don’t necessarily like the dApp, just say that the team is serious and what we build is solid: Lucky dApp is live on Shiden and Astar for almost two years despite the evolutions of the dApp Staking which led to changes on the dApp side.
In addition, we are one of the few teams developing with Ink! and now Solidity
Hello,
Here is the github with the smart contracts implementation: GitHub - GuiGou12358/lotto-multichain-contracts
This version is functional and can be deployed on Soneium when it is live.
However, we will continue to improve this version, in particular, the following points:
- Remove the deprecated OpenBrush library from wasm smart contracts and migrate the contracts from Ink! v4 to Ink! v5.
- Migrate the Phala Contracts (aka Phat Contract) to new version of Phala Contract i.e. Agent Contract).
- Use NFTs as entry ticket and receipt
- Manage the jackpot and liquidity on the different channels. The winner must be able to claim, via a smart contract, his jackpot on the blockchain on which he participated. For this, the liquidity must be routed to the right blockchain.
In order to continue developments, we wish to continue to benefit from the UCG.
@Gaius_sama What are the steps to follow? Do I have to create a proposal in subsquare?
Obviously, I will write the monthly report next week.