I am excited to announce that JoyGift, a practical tool based on JoyID, is now live on the testnet! JoyGift may help CKB reach more users and fill some gaps in our community activities.
With JoyGift, you can send out red envelopes during AMA events, festivals, or other activities to engage with your users and convey your emotions to each other. You can also promote CKB in other communities using CKB red envelopes as a great icebreaker.
We would love to invite you to try out JoyGift on the testnet and share your feedback with us. Your feedback is valuable to us and will help us improve JoyGift for everyone.
To get started:
1、Visit the JoyGift testnet website: dev.joygift.cc
2、Connect with JoyID.
Then you can start sending out red envelopes and experiencing the smoothness of JoyID.
Really happy to see this project happening, I think it’s a great idea!
It also seems to work very well from the bit of testing I have done. But I just have 2 small suggestions:
(1) When you choose to send a gift box instead of the red packet, on the claim screen it still says to ‘claim the red packet’ and has the red packet icon.
Also, I saw someone else on TG bring up the issue where someone could claim all of the gifts by using different accounts. How can you prevent this from happening?
Good question. When distributing rewards for red packet distribution (after the red packet has been claimed out or has expired), the platform will distribute the rewards through a transaction, including the amount each person claimed, the remaining amount, and the platform’s service fee. However, the minimum transfer amount for a JoyID address is 63CKB, just like the minimum amount required to claim a red packet. You are right, we should add a prompt for the minimum fee at the platform service fee stage.
This is a great question. We carefully analyzed this case during the interface design phase because our goal is to reach as many users as possible with the red packets. To prevent robots and users from claiming each red packet multiple times, we implemented the following measures:
When claiming a red envelope, we request a signature that cannot be simulated by a robot, effectively preventing people from using scripts to claim the red packet;
Also when claiming a red envelope, we encrypt the user’s device information as a necessary field for the signature. The platform checks whether the device has already claimed the red envelope.
Of course, achieving 100% assurance that only one person can claim the red envelope is very difficult. We will continue to monitor the logs and research more complex protective measures.